Add human-readable HTTP client stats #134296
Merged
Conversation
This file contains hidden or 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
Today the timestamps in the HTTP client stats output are not rendered as proper human-readable timestamps even when `?human=true` is specified. This commit adds the missing human-readable variants of these fields.
DaveCTurner
added
>enhancement
:Distributed Coordination/Network
elasticsearchmachine
added
the
Team:Distributed Coordination
Collaborator
|
Hi @DaveCTurner, I've created a changelog YAML for you. |
Collaborator
|
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
DaveCTurner
added
auto-backport
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Sep 8, 2025
Today the timestamps in the HTTP client stats output are not rendered as proper human-readable timestamps even when `?human=true` is specified. This commit adds the missing human-readable variants of these fields.
Collaborator
💚 Backport successful
|
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 8, 2025
rjernst
pushed a commit
to rjernst/elasticsearch
that referenced
this pull request
Sep 9, 2025
Today the timestamps in the HTTP client stats output are not rendered as proper human-readable timestamps even when `?human=true` is specified. This commit adds the missing human-readable variants of these fields.
sarog
pushed a commit
to portsbuild/elasticsearch
that referenced
this pull request
Sep 11, 2025
Today the timestamps in the HTTP client stats output are not rendered as proper human-readable timestamps even when `?human=true` is specified. This commit adds the missing human-readable variants of these fields.
sarog
pushed a commit
to portsbuild/elasticsearch
that referenced
this pull request
Sep 19, 2025
Today the timestamps in the HTTP client stats output are not rendered as proper human-readable timestamps even when `?human=true` is specified. This commit adds the missing human-readable variants of these fields.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Today the timestamps in the HTTP client stats output are not rendered as
proper human-readable timestamps even when
?human=trueis specified.This commit adds the missing human-readable variants of these fields.