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

write_riemann thresholds does not honor Hits #1978

Open
faxm0dem opened this issue Oct 5, 2016 · 2 comments
Open

write_riemann thresholds does not honor Hits #1978

faxm0dem opened this issue Oct 5, 2016 · 2 comments

Comments

@faxm0dem
Copy link
Contributor

faxm0dem commented Oct 5, 2016

  • Version of collectd: 5.5.2.20.gaf16be6
  • Operating system / distribution: CentOS 6

Expected behavior

When defining a threshold using e.g. Hits 4 the state sent along the events to riemann should take this into account: only change state to warning|critical after 4 intervals of hitting the thresh.

Actual behavior

As soon as the threshold is passed, events start appearing as state warning|critical.
Notifications however nicely hit the deck only after 4 iterations.

Steps to reproduce

  • define threshold with Hits 1000
  • trigger threshold
  • query riemann for state != "ok"
@octo octo added the Bug A genuine bug label Oct 27, 2016
@octo
Copy link
Member

octo commented Oct 27, 2016

src/write_riemann_threshold.c duplicates much of the original threshold code. This should be unified while fixing this IMHO.

@eero-t
Copy link
Contributor

eero-t commented Jan 26, 2024

src/write_riemann_threshold.c duplicates much of the original threshold code. This should be unified while fixing this IMHO.

@octo Maybe there should be a separate ticket about such unification (referring this ticket)?

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

No branches or pull requests

3 participants