Bug 1480760 - [RFE] Specify "X-Correlation-ID" header for log correlation when making REST calls to Candlepin
[RFE] Specify "X-Correlation-ID" header for log correlation when making REST ...
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Subscription Management (Show other bugs)
Unspecified Unspecified
unspecified Severity high (vote)
: GA
: --
Assigned To: Justin Sherrill
Sanket Jagtap
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-08-11 16:05 EDT by Craig Donnelly
Modified: 2018-02-21 11:54 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-02-21 11:54:37 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 20488 None None None 2017-08-11 16:05 EDT

  None (edit)
Description Craig Donnelly 2017-08-11 16:05:38 EDT
Description of problem:

When making REST calls to Candlepin the "X-Correlation-ID" request header should be set. This header can be used to specify a correlation id that will be printed out with every log message in Candlepin. This will make it easy to correlate requests from the Foreman logs with the Candlepin logs. Support for this header was added in Candlepin 2.0.

Version-Release number of selected component (if applicable):

Additional info:
This should be included for assistance in troubleshooting cross-component issues, so that we can track a single request or action across all components.
Comment 3 pm-sat@redhat.com 2017-09-20 00:14:53 EDT
Upstream bug assigned to jsherril@redhat.com
Comment 4 pm-sat@redhat.com 2017-09-26 14:16:56 EDT
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20488 has been resolved.
Comment 5 Sanket Jagtap 2017-12-12 04:20:40 EST
Build: Satellite 6.3.0 snap28

The request send to satellite is reflected in the candlepin log in csid field
which would be helpful while dealing with cross component issues

2017-12-12 04:16:32 431a45c1 [app] [I] Started GET "/katello/api/v2/products/45" for at 2017-12-12 04:16:32 -0500
2017-12-12 04:16:32 431a45c1 [app] [I] Processing by Katello::Api::V2::ProductsController#show as JSON
2017-12-12 04:16:32 431a45c1 [app] [I]   Parameters: {"api_version"=>"v2", "id"=>"45"}
2017-12-12 04:16:32 431a45c1 [app] [I] Current user: admin (administrator)

==> /var/log/candlepin/candlepin.log <==
2017-12-12 04:16:32,336 [thread=http-bio-8443-exec-8] [req=8ba82326-e597-4964-8171-092d1aa633f3, org=, csid=431a45c1] INFO  org.candlepin.common.filter.LoggingFilter - Request: verb=GET, uri=/candlepin/owners/Default_Organization/products/215223095592/?include=name&include=attributes.name&include=attributes.value&include=productContent.content.contentUrl&include=productContent.content.label&include=productContent.content.modifiedProductIds&include=productContent.content.type&include=productContent.content.id&include=productContent.content.name
2017-12-12 04:16:32,352 [thread=http-bio-8443-exec-8] [req=8ba82326-e597-4964-8171-092d1aa633f3, org=, csid=431a45c1] INFO  org.candlepin.common.filter.LoggingFilter - Response: status=200, content-type="application/json", time=16
Comment 6 pm-sat@redhat.com 2018-02-21 11:54:37 EST
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/RHSA-2018:0336

Note You need to log in before you can comment on or make changes to this bug.