In upstream Foreman release, we include request and optionally session id in logs, so it will be much easier to match the specific request: http://projects.theforeman.org/issues/15863 This small improvement would be very useful to backport into 6.2. TRIAGE NOTES: Very small and standalone patch, zero risk. DOCO NOTES: We need an upgrade note to make this new feature effective, logging.yaml must be modified: :pattern: "%d %.8X{session} [%c] [%.1l] %m\n" Otherwise this won't be used
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15863 has been resolved.
This would make debugging slow requests a lot easier, the current log is difficult to read when there's a lot of activity.
Please add verifications steps for this bug to help QE verify
*** Bug 1435563 has been marked as a duplicate of this bug. ***
Verification steps: 1. preform requests 2. the logs are prefixed by a hash, that groups the requests 2016-07-27T15:38:43 33b38af1 [app] [I] Started GET "/" for 127.0.0.1 at 2016-07-27 15:38:43 +0100 2016-07-27T15:38:45 33b38af1 [app] [I] Completed 200 OK in 1978ms (Views: 1695.6ms | ActiveRecord: 18.5ms 3. for web ui, the hash is determined by a session id: two different users have different hash 4. for API requests, the hash is unique per request.
VERIFIED for 6.2.9-1, the request ids are now logged as the 3rd field in production.log Sat server also exposes this as a X-Request-Id in HTTP response. 2017-03-24 05:53:09 f67c1d8e [app] [I] Started HEAD "/api/v2/organizations" for 10.19.41.18 at 2017-03-24 05:53:09 -0400 2017-03-24 05:53:09 f67c1d8e [app] [I] Processing by Api::V2::OrganizationsController#index as JSON 2017-03-24 05:53:09 f67c1d8e [app] [I] Parameters: {"apiv"=>"v2"} 2017-03-24 05:53:09 f67c1d8e [app] [I] Authorized user admin(Admin User) 2017-03-24 05:53:09 f67c1d8e [app] [I] Rendered api/v2/taxonomies/index.json.rabl within api/v2/layouts/index_layout (5.7ms) 2017-03-24 05:53:09 f67c1d8e [app] [I] Completed 200 OK in 40ms (Views: 6.6ms | ActiveRecord: 14.4ms)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1191
*** Bug 1264827 has been marked as a duplicate of this bug. ***