BIND 10 #1897: b10-stats-httpd and HTTP logging
BIND 10 Development
do-not-reply at isc.org
Fri Jan 11 14:07:19 UTC 2013
#1897: b10-stats-httpd and HTTP logging
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: enhancement | Status: new
Priority: medium | Milestone:
Component: statistics | Sprint-20130122
Keywords: | Resolution:
Sensitive: 0 | CVSS Scoring:
Sub-Project: Core | Defect Severity: N/A
Estimated Difficulty: 4 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jelte):
The patch looks ok in terms of how it works.
About the format, i think we have three reasonable options:
Currently it does 'bind10 style logs' which, as the log message, print
CommonLog-style data:
{{{
2013-01-11 12:20:42.112 DEBUG [b10-stats-httpd.stats-httpd/8646]
STATHTTPD_HTTPLOG localhost - - [11/Jan/2013 12:20:42] "GET
/bind10/statistics/xml/ HTTP/1.1" 200 -
}}}
So it is not exactly commonlog, and it contains redundant info (hardcoded
'- -', datetime twice), but everything after the STATHTTPD_HTTPLOG is in
the common style.
An alternative would be not doing that style at all, and print it in the
bind10-style, e.g.:
{{{
2013-01-11 12:20:42.112 DEBUG [b10-stats-httpd.stats-httpd/8646]
STATHTTPD_HTTPLOG localhost "GET /bind10/statistics/xml/ HTTP/1.1" 200
}}}
Advantage: internal consistency. Disadvantage: all resemblance to common
log lost.
And the third would be to do it entirely in common log style, as the
example above:
{{{
localhost.localdomain - - [18/Apr/2012 17:14:27] "GET
/bind10/statistics/xml HTTP/1.1" 200 -
}}}
This option does require us to modify the logging library (to set layout)
and our 'own' message would be kinda inconsistent though.
--
Ticket URL: <http://bind10.isc.org/ticket/1897#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list