[ceph-users] Re: radosgw beast access logs

Sure. You can track the nautilus backport's progress in https://tracker.ceph.com/issues/47042. On Wed, Aug 19, 2020 at 12:25 PM Wesley Dillingham wrote: > > We would very much appreciate having this backported to nautilus. > > Respectfully, > > Wes Dillingham > w...@wesdillingham.com > LinkedIn

[ceph-users] Re: radosgw beast access logs

We would very much appreciate having this backported to nautilus. Respectfully, *Wes Dillingham* w...@wesdillingham.com LinkedIn On Wed, Aug 19, 2020 at 9:02 AM Casey Bodley wrote: > On Tue, Aug 18, 2020 at 1:33 PM Graham Allan wrote: > > > >

[ceph-users] Re: radosgw beast access logs [EXT]

On 19/08/2020 14:01, Casey Bodley wrote: Yes, this was implemented by Mark Kogan in https://github.com/ceph/ceph/pull/33083 . It looks like it was backported to Octopus for 15.2.5 in https://tracker.ceph.com/issues/45951. Is there interest in a nautilus backport too? I don't think we'd be

[ceph-users] Re: radosgw beast access logs

On Tue, Aug 18, 2020 at 1:33 PM Graham Allan wrote: > > Are there any plans to add access logs to the beast frontend, in the > same way we can get with civetweb? Increasing the "debug rgw" setting > really doesn't provide the same thing. > > Graham > -- > Graham Allan - g...@umn.edu > Associate