On 01.06.2010 14:56, Rainer Jung wrote:
I repeatedly inserted millisecond or microsecond timestamps as well as
PID and thread ID information into the ErrorLog when trying to diagnose
problems, most often in combination with additional log lines.
Due to the increased load and capability of systems and increasing
amount of concurrency, would those features be interesting by default?
1) Sub-second timestamps in error log
Committed as r952203.
2) PID and thread ID
PID and thread id are useful, because the can be correlated with the
access_log (when added there). they also help to understand, which
messages belong "together" when multiple log events are intertwined.
Committed as r952201.
3) Related things for access log
There's a related open Bugzilla about adding sub-second timestamps (not:
duration) to the access log (BZ 49251). The OP suggests to use %M for an
absolute timestamp. It would be nice to improve the strftime use of
%{format}t to allow for a proprietary microsecond letter which will add
the microsecond part of the actual time. I found no standards defined
for that.
Any comments on my patch at:
http://people.apache.org/~rjung/patches/httpd-trunk-adding-milliseconds-and-microseconds-to-the-access-log.patch
It extends the patterns used by %{...}t. More detailed explanations at
the beginning of the patch.
Rainer
