exceptionfactory commented on code in PR #6390: URL: https://github.com/apache/nifi/pull/6390#discussion_r970059986
########## nifi-docs/src/main/asciidoc/administration-guide.adoc: ########## @@ -182,6 +182,41 @@ Antivirus software can take a long time to scan large directories and the numero * `provenance_repository` * `state` +[[logging_configuration]] +== Logging Configuration +NiFi uses link:https://logback.qos.ch/[logback^] as the runtime logging implementation. The `conf` directory contains a +standard `logback.xml` configuration with default appender and level settings. The +link:https://logback.qos.ch/manual/index.html[logback manual] provides a complete reference of available options. + +=== Standard Log Files +The standard logback configuration includes the following appender definitions and associated log files: + +[options="header"] +|========================= +| File | Description +| `nifi-app.log` | Application log containing framework and component messages +| `nifi-bootstrap.log` | Bootstrap log containing startup and shutdown messages +| `nifi-deprecation.log` | Deprecation log containing warnings for deprecated components and features +| `nifi-request.log` | HTTP request log containing user interface and REST API access messages +| `nifi-user.log` | User log containing authentication and authorization messages +|========================= + +=== Deprecation Logging +The `nifi-deprecation.log` contains warning messages describing components and features that will be removed in +subsequent versions. Deprecation warnings should be evaluated and addressed to avoid breaking changes when upgrading to +a new major version. Resolving deprecation warnings involves upgrading to new components, changing component property +settings, or refactoring custom component classes. + Review Comment: Thanks for the suggestion, will add some additional details. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
