[ 
https://issues.apache.org/jira/browse/NIFI-8650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760144#comment-17760144
 ] 

ASF subversion and git services commented on NIFI-8650:
-------------------------------------------------------

Commit d4147ca442087f8bd7d73decbcb03780c80a0d50 in nifi's branch 
refs/heads/main from Tamas Palfy
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d4147ca442 ]

NIFI-8650 Added Flow Analysis Rules

- Added new extensible Component Type: FlowAnalysisRule
- Added DisallowComponentType Rule implementation
- Flow Analysis Rules can be managed from the UI under Controller Settings -> 
Flow Analysis Rules
- Flow Analysis Rules can be set up with an enforcement policy of WARN or 
ENFORCE
- Flow Analysis Rules can evaluate an individual Component or a Process Group

This closes #7191

Signed-off-by: David Handermann <[email protected]>


> Flow Analysis
> -------------
>
>                 Key: NIFI-8650
>                 URL: https://issues.apache.org/jira/browse/NIFI-8650
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core Framework
>            Reporter: Tamas Palfy
>            Assignee: Tamas Palfy
>            Priority: Major
>             Fix For: 2.0.0
>
>          Time Spent: 14h
>  Remaining Estimate: 0h
>
> Add new concept: Flow analysis based on user-defined rules
> Flow analysis runs check wether the flow is in a "proper" state.
> What constitutes "proper" is defined by the users by creating flow analysis 
> rules.
> These rules are a new type of component and behave as such in almost every 
> aspect. (They can have properties, they can be added to nifi as extensions 
> via nars, they are versioned, persisted in flow.xml etc.)
> The framework takes care of running the rules as appropriate.
> Each rule is provided a representation of the flow (or part of it) - defined 
> by an interface - and may analyze it in any way it seems fit. The result of 
> the analysis is represented by zero or more rule violation objects that the 
> framework accepts and handles from then on.
> The effect of the analysis result by a given rule depends on the type of the 
> rule, which can be either _recommendation_ or _policy_.
> Recommendations are information displayed to the user.
> Policies are more strict. Apart from being available to be viewed by the user 
> (similar to recommendations), they also invalidate the components that 
> violated the corresponding rule.
> The analysis results can be displayed and can be disabled (ignored) or 
> re-enabled.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to