Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
There is no unique identifier to correlate the logging per API request.
See the logging fragment below.
- There is a Content View Publish requested
- Followed shortly by a call to Tasks
- Then we see the Tasks "Completed" response
- Then we see the another "Completed" response, for which we _think_ it it related to the Publish response. But this might also be from an other concurrent request
2015-09-21 09:54:01 [I] Processing by Katello::Api::V2::ContentViewsController#publish as */*
2015-09-21 09:54:01 [I] Parameters: {"per_page"=>9999, "api_version"=>"v2", "id"=>"38", "content_view"=>{}}
2015-09-21 09:54:01 [I] Authorized user hoici(hoici )
2015-09-21 09:54:01 [I] Processing by ForemanTasks::Api::TasksController#bulk_search as */*
2015-09-21 09:54:01 [I] Parameters: {"per_page"=>9999, "searches"=>[{"type"=>"task", "task_id"=>"eba81e76-2642-4f42-937b-ab6b08c6c79b"}], "task"=>{}}
2015-09-21 09:54:01 [I] Authorized user hoici(hoici )
2015-09-21 09:54:02 [I] Completed 200 OK in 1499ms (Views: 1.9ms | ActiveRecord: 19.1ms)
2015-09-21 09:54:06 [I] Rendered text template (0.0ms)
2015-09-21 09:54:06 [I] Completed 204 No Content in 25023ms (Views: 5.6ms | ActiveRecord: 35.7ms)
The more concurrent actions are handled by Sat6 the more the logging will be interwoven and harder to correlate which logging belongs together.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Start 20 Concurrent ContentView publish actions
2. Query the Tasks controller
3.
Actual results:
Unclear which logging belongs to which request
Expected results:
Unique identifier prefixing the logging, e.g. for the above example:
2015-09-21 09:54:01 [I][Req 12345] Processing by Katello::Api::V2::ContentViewsController#publish as */*
2015-09-21 09:54:01 [I][Req 12345] Parameters: {"per_page"=>9999, "api_version"=>"v2", "id"=>"38", "content_view"=>{}}
2015-09-21 09:54:01 [I][Req 12345] Authorized user hoici(hoici )
2015-09-21 09:54:01 [I][Req 67890] Processing by ForemanTasks::Api::TasksController#bulk_search as */*
2015-09-21 09:54:01 [I][Req 67890] Parameters: {"per_page"=>9999, "searches"=>[{"type"=>"task", "task_id"=>"eba81e76-2642-4f42-937b-ab6b08c6c79b"}], "task"=>{}}
2015-09-21 09:54:01 [I][Req 67890] Authorized user hoici(hoici )
2015-09-21 09:54:02 [I][Req 67890] Completed 200 OK in 1499ms (Views: 1.9ms | ActiveRecord: 19.1ms)
2015-09-21 09:54:06 [I][Req 12345] Rendered text template (0.0ms)
2015-09-21 09:54:06 [I][Req 12345] Completed 204 No Content in 25023ms (Views: 5.6ms | ActiveRecord: 35.7ms)
Additional info:
See also BZ1264324 for Pulp logging, that is also missing a unqiue identifier to correlate the logging messages
Description of problem: There is no unique identifier to correlate the logging per API request. See the logging fragment below. - There is a Content View Publish requested - Followed shortly by a call to Tasks - Then we see the Tasks "Completed" response - Then we see the another "Completed" response, for which we _think_ it it related to the Publish response. But this might also be from an other concurrent request 2015-09-21 09:54:01 [I] Processing by Katello::Api::V2::ContentViewsController#publish as */* 2015-09-21 09:54:01 [I] Parameters: {"per_page"=>9999, "api_version"=>"v2", "id"=>"38", "content_view"=>{}} 2015-09-21 09:54:01 [I] Authorized user hoici(hoici ) 2015-09-21 09:54:01 [I] Processing by ForemanTasks::Api::TasksController#bulk_search as */* 2015-09-21 09:54:01 [I] Parameters: {"per_page"=>9999, "searches"=>[{"type"=>"task", "task_id"=>"eba81e76-2642-4f42-937b-ab6b08c6c79b"}], "task"=>{}} 2015-09-21 09:54:01 [I] Authorized user hoici(hoici ) 2015-09-21 09:54:02 [I] Completed 200 OK in 1499ms (Views: 1.9ms | ActiveRecord: 19.1ms) 2015-09-21 09:54:06 [I] Rendered text template (0.0ms) 2015-09-21 09:54:06 [I] Completed 204 No Content in 25023ms (Views: 5.6ms | ActiveRecord: 35.7ms) The more concurrent actions are handled by Sat6 the more the logging will be interwoven and harder to correlate which logging belongs together. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start 20 Concurrent ContentView publish actions 2. Query the Tasks controller 3. Actual results: Unclear which logging belongs to which request Expected results: Unique identifier prefixing the logging, e.g. for the above example: 2015-09-21 09:54:01 [I][Req 12345] Processing by Katello::Api::V2::ContentViewsController#publish as */* 2015-09-21 09:54:01 [I][Req 12345] Parameters: {"per_page"=>9999, "api_version"=>"v2", "id"=>"38", "content_view"=>{}} 2015-09-21 09:54:01 [I][Req 12345] Authorized user hoici(hoici ) 2015-09-21 09:54:01 [I][Req 67890] Processing by ForemanTasks::Api::TasksController#bulk_search as */* 2015-09-21 09:54:01 [I][Req 67890] Parameters: {"per_page"=>9999, "searches"=>[{"type"=>"task", "task_id"=>"eba81e76-2642-4f42-937b-ab6b08c6c79b"}], "task"=>{}} 2015-09-21 09:54:01 [I][Req 67890] Authorized user hoici(hoici ) 2015-09-21 09:54:02 [I][Req 67890] Completed 200 OK in 1499ms (Views: 1.9ms | ActiveRecord: 19.1ms) 2015-09-21 09:54:06 [I][Req 12345] Rendered text template (0.0ms) 2015-09-21 09:54:06 [I][Req 12345] Completed 204 No Content in 25023ms (Views: 5.6ms | ActiveRecord: 35.7ms) Additional info: See also BZ1264324 for Pulp logging, that is also missing a unqiue identifier to correlate the logging messages