[jira] [Updated] (NIFI-6628) Separate out logging of extensions vs. nifi framework

["Mark Payne (Jira)" <ji...@apache.org>]

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

Mark Payne updated NIFI-6628:
-----------------------------
    Attachment: 0001-NIFI-6628-Updates-to-logback-to-ensure-that-app-log-.patch

> Separate out logging of extensions vs. nifi framework
> -----------------------------------------------------
>
>                 Key: NIFI-6628
>                 URL: https://issues.apache.org/jira/browse/NIFI-6628
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Mark Payne
>            Assignee: Alessandro D'Armiento
>            Priority: Major
>         Attachments: 0001-NIFI-6628-Updates-to-logback-to-ensure-that-app-log-.patch
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> Currently, nifi has 3 logs that are generated: `nifi-app.log`, `nifi-user.log`, and `nifi-bootstrap.log`. The vast majority of logs are written to `nifi-app.log`. This can result in the app log being extremely verbose and difficult to follow if there are Processors that are configured with an invalid username/password, etc. that result in spewing a lot of errors. As a result, it can be very difficult to find error messages about framework/app itself.
> We should update the `logback.xml` file to add a new `nifi-framework.log` file that contains framework-related loggers and let everything else go to `nifi-app.log`



--
This message was sent by Atlassian Jira
(v8.3.4#803005)