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
Request to fix the unit of time in the latency field in the traefik access log ( either ms OR s or configurable ). Right now it alternates between msec and sec based on the magnitude, which makes it non-trivial process, like for example for elk.
Samples below:
10.84.192.15 - - [25/Jul/2016:13:43:37 +0530] "GET /apis/" HTTP/1.1" 200 78 "" "Jersey/2.13 (HttpUrlConnection 1.8.0_60)" 234252 "api" "http://prd-server:8080" 6.45837ms
10.84.192.16 - - [25/Jul/2016:13:44:49 +0530] "POST /apis/" 200 67 "" "Jersey/2.13 (HttpUrlConnection 1.8.0_60)" 235155 "api" "http://prd-server:8080" 1.053089843s #===> Prefer this to be msec too.
The text was updated successfully, but these errors were encountered:
GH traefik#559 points out that the logging of the elapsed time is inconsistent
depending on the scale of the measured time; this is due to Duration’s
String handling.
With this PR, I propose that traefik logs millis, and not fractions of
millis.
Request to fix the unit of time in the latency field in the traefik access log ( either ms OR s or configurable ). Right now it alternates between msec and sec based on the magnitude, which makes it non-trivial process, like for example for elk.
Samples below:
10.84.192.15 - - [25/Jul/2016:13:43:37 +0530] "GET /apis/" HTTP/1.1" 200 78 "" "Jersey/2.13 (HttpUrlConnection 1.8.0_60)" 234252 "api" "http://prd-server:8080" 6.45837ms
10.84.192.16 - - [25/Jul/2016:13:44:49 +0530] "POST /apis/" 200 67 "" "Jersey/2.13 (HttpUrlConnection 1.8.0_60)" 235155 "api" "http://prd-server:8080" 1.053089843s #===> Prefer this to be msec too.
The text was updated successfully, but these errors were encountered: