[ 
https://issues.apache.org/jira/browse/NIFI-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vansh Chaudhary reassigned NIFI-15073:
--------------------------------------

    Assignee: Vansh Chaudhary

> Add ability to be able to define reporting level in 
> SiteToSiteBulletinReportingTask
> -----------------------------------------------------------------------------------
>
>                 Key: NIFI-15073
>                 URL: https://issues.apache.org/jira/browse/NIFI-15073
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 2.0.0
>         Environment: All
>            Reporter: Craig Patrick
>            Assignee: Vansh Chaudhary
>            Priority: Major
>
> *As a* NiFi ETL developer
> *I want to* have the ability to configure the level at which a 
> SiteToSiteBulletinReportingTask reports at
> *So that* I can handle bulletin reports in different ways depending on error 
> level.
> In the current implementation of the SiteToSiteBulletinReportingTask, there 
> is no possibility in the configuration to define the "level" of bulletin 
> which gets reported. This would be a great addition as it means we can handle 
> logging of different levels (WARN for example) in a separate process and 
> allow only severe level errors to be sent to the bulletin.
> As an opposite to this, it may be that we want info to be logged to the 
> bulletin as well as more severe alerts.
> Suggestion would be to either:
>  # offer the ability to select multiple levels (either via tick boxes or drop 
> down, or comma delimited list) or...
>  # select theĀ *lowest* level of bulletin to report on (for example, INFO 
> would report on anything INFO and above)
> Selecting specific levels would allow the opportunity to set up multiple 
> bulletins for different levels which could then act differently (local 
> logging for INFO for example, but ERROR level could go to Sentry).



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

Reply via email to