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

Gauge value after flush #70

Open
sempasha opened this issue Oct 25, 2022 · 1 comment
Open

Gauge value after flush #70

sempasha opened this issue Oct 25, 2022 · 1 comment

Comments

@sempasha
Copy link

We have an issue with metric of gauge type. We expect behavior as described at statsd server's documentation

If the gauge is not updated at the next flush, it will send the previous value.

Expected behavior

Let's say we send gaugor:5|g, so we would get gaugor metric with value of 5 on first flush.
Later if we don't send any gaugor update we still would get gaugor metric with value of 5 on second flush.
Or if we send gaugor:+10|g we would get gaugor metric with value of 15 at second flush.

Actual behavior

We send gaugor:5|g, we get gaugor metric with value of 5 at first flush.
Later if we don't send any gaugor update we wouldn't get any gaugor metric on second flush at all.
Or If we send gaugor:+10|g we would get gaugor metric with value of 10 on second flush.

Consequence

This behavior also affects gauge relative updates, i.e. sending gaugor:+5|g or gaugor:-5|g to update existing gaugor value by specified difference. It is impossible to update existing gauge, because it is forgotten after every flush.

@Albibek
Copy link
Collaborator

Albibek commented Jan 8, 2023

This feature was the one we did not add to bioyino intentionally for performance reasons. It is no problem to add it being enabled by a separate option, but it may take time.

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

No branches or pull requests

2 participants