nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Witt (Jira)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-6628) Separate out logging of extensions vs. nifi framework
Date Thu, 05 Sep 2019 19:52:00 GMT

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

Joseph Witt commented on NIFI-6628:
-----------------------------------

big +1 to this idea

> 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
>            Priority: Major
>
> 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.2#803003)

Mime
View raw message