Feature #40714
closedusage log differ from civetweb and beast
0%
Description
The default "rgw enable usage log = true” in civetweb used to output for each operation
2019-07-08 21:25:27.885673 7f25aac8c700 1 ====== starting new request req=0x7f25aac860a0 =====
2019-07-08 21:25:27.886992 7f25aac8c700 1 ====== req done req=0x7f25aac860a0 op status=0 http_status=200 ======
2019-07-08 21:25:27.887040 7f25aac8c700 1 civetweb: 0x55fef2f47000: 10.5.5.13 - - [08/Jul/2019:21:25:27 -0600] "GET / HTTP/1.1" 200 0 - Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
but with beast we get
2019-07-08 23:17:49.695 7fe6a2b0a700 1 ====== starting new request req=0x55ff63d728e0 =====
2019-07-08 23:17:49.707 7fe6a2b0a700 1 ====== req done req=0x55ff63d728e0 op status=0 http_status=200 latency=0.012s ======
1. Massive change of what is “default”.
2. I like seeing the latency but without knowing what kind of operation it is, it’s an incomplete log entry.
3. The ideal output would be a combination of both of the above, something like
2019-07-08 21:25:27.885673 7f25aac8c700 1 ====== starting new request req=0x7f25aac860a0 =====
2019-07-08 21:25:27.886992 7f25aac8c700 1 ====== req done req=0x7f25aac860a0 op status=0 http_status=200 latency=0.012s ======
2019-07-08 21:25:27.887040 7f25aac8c700 1 [08/Jul/2019:21:25:27 -0600] "GET / HTTP/1.1" 200 0
Is there a way to show both latency and operations type logs?
I enabled
rgw enable ops log = true
in ceph.conf
[client.rgw.osd2]
rgw frontends = "beast port=80"
rgw dns name = osd2.yxz.com
rgw enable usage log = true
rgw enable ops log = true
Description: Enable logging for each successful Ceph Object Gateway operation.
Type: Boolean
Default: false
And it did not add anything to the log.
2019-07-08 23:42:53.575 7f82e70d3700 1 ====== starting new request req=0x55677211a8e0 =====
2019-07-08 23:42:53.575 7f82e70d3700 1 ====== req done req=0x55677211a8e0 op status=0 http_status=200 latency=0s ======
2019-07-08 23:42:53.575 7f82e68d2700 1 ====== starting new request req=0x55677211a8e0 =====
2019-07-08 23:42:53.599 7f82e68d2700 1 ====== req done req=0x55677211a8e0 op status=0 http_status=200 latency=0.024s ======
It would be ideal to have beast/civetweb log similarly and have it backported to Nautilus.