[
https://issues.apache.org/jira/browse/NIFI-9291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445989#comment-17445989
]
ASF subversion and git services commented on NIFI-9291:
-------------------------------------------------------
Commit 605346ae0f15dd755c37b7e8802039fba8e5afd1 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=605346a ]
NIFI-9291 Added NiFi HTTP request logging
- Added nifi.web.request.log.format property
- Added Filters to set and retrieve authenticated username for logging
Signed-off-by: Joe Gresock <[email protected]>
This closes #5527.
> Add Configurable 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)
