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

[Question]: How to handle Watchdog, which are always critical #61

Open
wattebausch opened this issue Nov 27, 2024 · 1 comment
Open
Labels
feature New feature or request question Further information is requested
Milestone

Comments

@wattebausch
Copy link

Ask a question

Hello everyone,

We use prometheus for our kubernetes cluster. As written in your article (https://blog.netways.de/blog/2023/07/25/check_prometheus-ist-jetzt-oeffentlich-verfuegbar/), we define all rules there. And we use the default Rules like general.rules

We would like to use your plugin, but we have a question about how you handle the watchdog. This is set to active by default.
https://runbooks.prometheus-operator.dev/runbooks/general/watchdog
(If not firing then it should alert external systems that this alerting system is no longer working.)

If we now query ‘alerts’ in this way, we always have a critical state.

thanks for your plugin, looks great.

@wattebausch wattebausch added the question Further information is requested label Nov 27, 2024
@martialblog
Copy link
Member

Hi, thanks for the feedback.

I think you raise an interesting point regarding "dead man's switch" alerts, which is a common use case.
Not sure yet how the plugin should handle this, but I'll give it some thought.

Any ideas are welcome.

Cheers,
Markus

@martialblog martialblog added this to the v0.3.0 milestone Nov 28, 2024
@martialblog martialblog added the feature New feature or request label Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants