On Thu, Mar 8, 2018 at 2:22 PM, David Turner <drakonstein@xxxxxxxxx> wrote: > I remember some time ago Yehuda had commented on a thread like this saying > that it would make sense to add a logging/auditing feature like this to RGW. > I haven't heard much about it since then, though. Yehuda, do you remember > that and/or think that logging like this might become viable. I vaguely remember Matt was working on this. Matt? Yehuda > > > On Thu, Mar 8, 2018 at 4:17 PM Aaron Bassett <Aaron.Bassett@xxxxxxxxxxxxx> > wrote: >> >> Yea thats what I was afraid of. I'm looking at possibly patching to add >> it, but i really dont want to support my own builds. I suppose other >> alternatives are to use proxies to log stuff, but that makes me sad. >> >> Aaron >> >> >> On Mar 8, 2018, at 12:36 PM, David Turner <drakonstein@xxxxxxxxx> wrote: >> >> Setting radosgw debug logging to 10/10 is the only way I've been able to >> get the access key in the logs for requests. It's very unfortunate as it >> DRASTICALLY increases the amount of log per request, but it's what we needed >> to do to be able to have the access key in the logs along with the request. >> >> On Tue, Mar 6, 2018 at 3:09 PM Aaron Bassett <Aaron.Bassett@xxxxxxxxxxxxx> >> wrote: >>> >>> Hey all, >>> I'm trying to get something of an audit log out of radosgw. To that end I >>> was wondering if theres a mechanism to customize the log format of civetweb. >>> It's already writing IP, HTTP Verb, path, response and time, but I'm hoping >>> to get it to print the Authorization header of the request, which containers >>> the access key id which we can tie back into the systems we use to issue >>> credentials. Any thoughts? >>> >>> Thanks, >>> Aaron >>> CONFIDENTIALITY NOTICE >>> This e-mail message and any attachments are only for the use of the >>> intended recipient and may contain information that is privileged, >>> confidential or exempt from disclosure under applicable law. If you are not >>> the intended recipient, any disclosure, distribution or other use of this >>> e-mail message or attachments is prohibited. If you have received this >>> e-mail message in error, please delete and notify the sender immediately. >>> Thank you. >>> >>> _______________________________________________ >>> ceph-users mailing list >>> ceph-users@xxxxxxxxxxxxxx >>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >> >> > _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |