Hi David,
Don't have any good idea for "octopus" (other than ops log), but you can do
that (and more) in "pacific" using lua scripting on the RGW:
https://docs.ceph.com/en/pacific/radosgw/lua-scripting/
Yuval
On Thu, Apr 1, 2021 at 7:11 PM David Orman <ormandj(a)corenode.com> wrote:
Hi,
Is there any way to log the x-amz-request-id along with the request in
the rgw logs? We're using beast and don't see an option in the
configuration documentation to add headers to the request lines. We
use centralized logging and would like to be able to search all layers
of the request path (edge, lbs, ceph, etc) with a x-amz-request-id.
Right now, all we see is this:
debug 2021-04-01T15:55:31.105+0000 7f54e599b700 1 beast:
0x7f5604c806b0: x.x.x.x - - [2021-04-01T15:55:31.105455+0000] "PUT
/path/object HTTP/1.1" 200 556 - "aws-sdk-go/1.36.15 (go1.15.3; linux;
amd64)" -
We've also tried this:
ceph config set global rgw_enable_ops_log true
ceph config set global rgw_ops_log_socket_path /tmp/testlog
After doing this, inside the rgw container, we can socat -
UNIX-CONNECT:/tmp/testlog and see the log entries being recorded that
we want, but there has to be a better way to do this, where the logs
are emitted like the request logs above by beast, so that we can
handle it using journald. If there's an alternative that would
accomplish the same thing, we're very open to suggestions.
Thank you,
David
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io