Backport of agent: allow configuration of in-memory telemetry sink. into release/1.7.x #20217
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
hc-github-team-nomad-core
force-pushed
the
backport/f-jrasell-config-telemetry-in-memory/naturally-capable-swine
branch
from
c7e0280 to
471b7de
Compare
jrasell
approved these changes
Mar 25, 2024
jrasell
deleted the
backport/f-jrasell-config-telemetry-in-memory/naturally-capable-swine
branch
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.
Backport
This PR is auto-generated from #20166 to be assessed for backporting due to the inclusion of the label backport/1.7.x.
The below text is copied from the body of the original PR.
This change adds configuration options for setting the in-memory telemetry sink collection and retention durations. This sink backs the metrics JSON API and previously had hard-coded default values.
The new options are particularly useful when running development or debug environments, where metrics collection is desired at a fast and granular rate. This is particularly useful for gauges; currently the last value written in the interval is returned from the API. In situations with spiking/flapping data, this could mean we miss information.
Overview of commits