Bug 1465741 - RFE: add blkin tracing to RGW
RFE: add blkin tracing to RGW
Status: NEW
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RGW (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: 4.0
Assigned To: Matt Benjamin (redhat)
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2017-06-28 01:38 EDT by Kyle Bader
Modified: 2018-05-09 07:27 EDT (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:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kyle Bader 2017-06-28 01:38:32 EDT
Figuring out why a particular RGW request is painful and often requires annoyingly verbose debug levels. Gathering the logs and making sense of them is not an easy task, especially when load balancers and multiple radosgw instances are involved.

It would be fantastic if the RGW extended the "blkin" work [1] such that a client could originate the trace identifier. With this implemented end to end we could see a marvelous waterfall chart of where latencies come from.

While typically reserved for response headers, perhaps we could support either "x-amz-id-2" or "x-amz-request-id" as request headers to pass the trace identifier.

If someone is using a proxy, eg. HAproxy, they would of course need to configure it to pass the header along.

[1] https://github.com/ceph/blkin
[2] https://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonResponseHeaders.html

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