Fix incorrect type conversion of average response time in Haproxy dashboards #8404
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsoriano
added
module
Metricbeat
jsoriano
force-pushed
the
haproxy-dashboard-milliseconds
branch
from
7137560 to
6cd4bf6
Compare
jsoriano
changed the title
exekias
approved these changes
Sep 24, 2018
jsoriano
added a commit
to jsoriano/beats
that referenced
this pull request
Sep 24, 2018
…hboards (elastic#8404) (cherry picked from commit ede435c)
jsoriano
added
v6.5.0
and removed
needs_backport
jsoriano
added a commit
to jsoriano/beats
that referenced
this pull request
Sep 24, 2018
…hboards (elastic#8404) (cherry picked from commit ede435c)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…hboards (elastic#8404) (elastic#8407) (cherry picked from commit 1e56e20)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Average response time in haproxy dashboard was being converted from seconds to milliseconds, but it is already in milliseconds, so it was showing values 1000 times greater than the expected ones.
Reported in https://discuss.elastic.co/t/average-response-time-on-haproxy-dashboard/149391