-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
feat(inputs.statsd): Add optional temporality and start_time tag for statsd metrics #13087
Conversation
577179d
to
6e9d6f1
Compare
f1f8cf1
to
931ded5
Compare
931ded5
to
d7b8635
Compare
plugins/inputs/statsd/README.md
Outdated
## Enable start_time field, which adds the start time of the metric accumulation | ||
## You should use this together with enable_temporality_tag when using OpenTelemetry output. | ||
enable_start_time_field = false | ||
## Enable temporality tag adds temporality=delta or temporality=commulative tag to the metrics. | ||
enable_temporality_tag = false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only concern is that a user would need to know they need both of these enabled if they want to start tracking delta metrics.
What do you think about a user-facing setting like: temporality = ""
And if it is empty, current behavior happens, if set to delta
it would add the time field and tag temporality='delta' and if set to commulative
then only the tag temporality='commulative'
Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can do that. Maybe enable_aggregation_temporality = true
. We would then start adding temporality
tag based on delete_counters
argument and start passing the start time?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the PR to do this ⬆️
f83de3c
to
a339804
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you! two inline suggestions about commenting out the default value of a config option and then I'm +1
Co-authored-by: Joshua Powers <[email protected]>
Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
gentle ping @srebhan and also maybe @jacobmarble could you take a look, since next PR is for influxdata/influxdb-observability#160 ? :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Sorry for the late response @povilasv!
Thanks! |
Required for all PRs
Ref #12507
The idea here is to allow users to optionally configure aggregation_temporality feature.
It will enable:
Also draft PR in the library that would make use of temporality tag and start_time tags
influxdata/influxdb-observability#160
resolves #