You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am in the process of migration from deprecated AbstractNCSARequestLog to CustomRequestLog.
AbstractNCSARequestLog has setLogDateFormat() method which accepts time pattern with "SSS" to log millis.
CustomRequestLog uses DateCache which does not allow time precision less than a second.
Thus I am unable to reproduce old behaviour and log milliseconds.
I have low traffic and do not need to cache formatted time, but I do need milliseconds in logs.
I am asking to add this functionality so I can log RequestTime with milliseconds precision like I did with (now removed) AbstractNCSARequestLog.
The text was updated successfully, but these errors were encountered:
AbstractNCSARequestLog also used the DateCache class, so there should be no change of behaviour to use the CustomRequestLog with code %{HH:mm:ss,SSS}t to format the time.
Otherwise if you really need a more precise ms time we can consider adding another % code option for it.
Jetty version(s)
11.x, 10.x, 9.x
Jetty 9.x is now at End of Community Support
Enhancement Description
I am in the process of migration from deprecated AbstractNCSARequestLog to CustomRequestLog.
AbstractNCSARequestLog has setLogDateFormat() method which accepts time pattern with "SSS" to log millis.
CustomRequestLog uses DateCache which does not allow time precision less than a second.
Thus I am unable to reproduce old behaviour and log milliseconds.
I have low traffic and do not need to cache formatted time, but I do need milliseconds in logs.
I am asking to add this functionality so I can log RequestTime with milliseconds precision like I did with (now removed) AbstractNCSARequestLog.
The text was updated successfully, but these errors were encountered: