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

use case: sandbox incident status #3009

Open
00041275 opened this issue Jan 12, 2025 · 4 comments
Open

use case: sandbox incident status #3009

00041275 opened this issue Jan 12, 2025 · 4 comments

Comments

@00041275
Copy link
Contributor

Help me solve the problem via keep. I have alerts coming from 500 servers using Zabbix. The truth is that I don't care until 50% of them go down. I don't need to create an incident until alerts appear on 250 servers. In general, what is the best way to proceed in a case when you have alerts, if some kind of sandbox for waiting for the threshold of sufficiency for an alert to be recalculated? Maybe some kind of sandbox status will appear in the incident by correlation that does not require action?

@00041275 00041275 changed the title sandbox incident status use case: sandbox incident status Jan 12, 2025
@shahargl
Copy link
Member

Mmm that’s interesting use case.

We have the concept of “incident candidate” which is the case where you “maybe” eventually have an incident but maybe not.

maybe we can extend it to the threshold use case

@00041275
Copy link
Contributor Author

ncident candidate

Where is it status?
image

@00041275
Copy link
Contributor Author

How to use "Incident-candidate", where I need it fire? in doc, I can't understand how to use it in practice.

@shahargl
Copy link
Member

its not a "status" but kinda boolean (incident candidate is either true/false). its a whole different table. I think it will be better to demo it or smth.

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

2 participants