[
https://issues.apache.org/jira/browse/NIFI-9291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-9291:
-----------------------------------
Issue Type: New Feature (was: Improvement)
> Improve HTTP Access Logging
> ---------------------------
>
> Key: NIFI-9291
> URL: https://issues.apache.org/jira/browse/NIFI-9291
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework, Security
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The NiFi REST API includes a {{RequestLogger}} implemented as a Java Servlet
> Filter which logs requests using the following format:
> {noformat}
> Attempting request for (<IDENTITY>) <METHOD> <URL> (source ip: <REMOTE_IP>)
> {noformat}
> The {{RequestLogger}} writes this message prior to request completion, so it
> is does not include HTTP response status information.
> The identity field may not include username information when authenticating
> using a JWT. Additional information, such as User Agent and negotiated TLS
> version could also provide useful details.
> HTTP request logging should be improved to include additional details and
> output information in a standardized format.
> The [W3C Extended Log File Format|https://www.w3.org/TR/WD-logfile.html]
> provides one potential option for access logging. The Common Log Format and
> Combined Log Format also provide de facto standards for access logging, while
> omitting some fields.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
