Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standard unit for traefik latency in access log #559

Closed
krishnanvrphonepe opened this issue Jul 25, 2016 · 1 comment
Closed

Standard unit for traefik latency in access log #559

krishnanvrphonepe opened this issue Jul 25, 2016 · 1 comment
Labels

Comments

@krishnanvrphonepe
Copy link

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.

@vdemeester vdemeester added the kind/enhancement a new or improved feature. label Jul 25, 2016
jangie added a commit to jangie/traefik that referenced this issue Aug 15, 2016
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.
@jangie
Copy link
Contributor

jangie commented Aug 15, 2016

@krishnanvrphonepe functionality for consistency is merged as of #619

@errm errm closed this as completed Nov 10, 2016
@traefik traefik locked and limited conversation to collaborators Sep 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants