Skip to content
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

Per metric-type expiry interval #300

Closed
colixxx opened this issue Apr 10, 2020 · 3 comments · Fixed by #309
Closed

Per metric-type expiry interval #300

colixxx opened this issue Apr 10, 2020 · 3 comments · Fixed by #309

Comments

@colixxx
Copy link

colixxx commented Apr 10, 2020

How I can send to back the previous value, if the gauge is not updated at the next flush?

@tiedotguy
Copy link
Collaborator

They should send the previous value if the expiry is non-zero (from #296). As present there's no notion of different expiry intervals for different metric types, so it does mean you'll get 0s from your counters if you set that.

If you want per-metric-type expiry intervals as a feature request it should be fairly trivial to add - but it would be just per type, and not have any configuration on a per metric name or anything.

@colixxx
Copy link
Author

colixxx commented Apr 10, 2020

Yes, it will be good. I want customize expiry-interval per-metric-type.

@tiedotguy tiedotguy changed the title Gauges not send the previous value in flush Per metric-type expiry interval Apr 12, 2020
@tiedotguy
Copy link
Collaborator

I'll leave it for a few days in case anyones interested in picking this up, otherwise I'll do it at some point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants