Actions
Bug #42254
closedmgr/dashboard: move request and response log to a separated event/access log with W3C format
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
General - Back-end
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Changes proposed:
- Instead of printing 2 different logs for every request and response, a single request-response trace should be printed. This is common practice in webservers (apache and nginx): it makes sense as for every request there's one and only one response (details on the log fields available in Apache).
- Instead of the current custom log line formatting, mixing bracketed fields ([]) with plain ones, we could use the widespread W3C Extended log format.
- Instead of logging/hiding events based on any logging priority, either ALL events should be logged or ONLY a subset of HTTP responses (4xx, 5xx, ...).
- Due to the distinct nature of application log vs. event/access log, it's recommended to store access/event log into a separate file (this also makes easier any parsing for further post-processing).
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 146 to General - Back-end
Actions