[monitoring] Add ClearOnVisitHistogram to adapter for go-metrics #330
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.
What does this PR do?
Adds a new type of ClearOnVisitHistogram to monitoring/adapter.
Why is it important?
This type is the same as a go-metrics StandardHistogram, but the Visit function for the new type will call
Clearon the underlying sample. This means the sample is reset each time you visit it. This is useful for things like the beats "Non-zero metrics in the last 30s" log entries.The other difference is that the
Visitfunction only reports the following metrics:This is smaller than the fields produced for the StandardHistogram. This was done to limit the field expansion, and this list of fields was picked because it is the list actually used in the elastic-agent monitoring dashboards.
Checklist
Author's Checklist
Related issues