Bug 1465741 - RFE: add blkin tracing to RGW
Summary: RFE: add blkin tracing to RGW
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 4.0
Assignee: Matt Benjamin (redhat)
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-28 05:38 UTC by Kyle Bader
Modified: 2022-02-21 18:06 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-20 14:27:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Kyle Bader 2017-06-28 05:38:32 UTC
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.