Actions
Feature #15863
closedLog request IDs (tagged logging) in production.log
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Description
Request IDs can be added to Foreman's logs to make it easier to trace all log messages relating to a particular request when they interleave from multiple server processes.
Rails stores an ID in the request environment by default, and since Rails 5, the default configuration is to log it. The request ID is derived from the X-Request-ID header, otherwise a random UUID. Since Foreman uses the logging gem without tagging support instead of the default Rails logger, implementing this requires passing the extra information to its MDC/NDC (context) storage.
Updated by The Foreman Bot over 8 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3678 added
Updated by Dominic Cleal over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset d97deb49dc07939998565bec0cef582082a8d91d.
Updated by Lukas Zapletal over 8 years ago
- Related to Feature #15876: Send request and session ids to foreman-proxy as HTTP headers added
Updated by Dominic Cleal over 8 years ago
- Related to Feature #10982: Add logging to smart proxy requests (ProxyAPI) added
Updated by Dominic Cleal over 8 years ago
- Translation missing: en.field_release set to 160
Updated by Ivan Necas over 7 years ago
- Related to Bug #19017: Use request id instead of session id of tagged logging added
Actions