SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool
Some alerts once detected can take days to resolve.
Describe the solution you'd like
it would would nice if we could visit the Triggered Alerts pane and acknowledge an alert that is in the firing state.
Once acknowledged, it should not fire again until the state changes to resolved OR it could reduce the firing frequency to once every 24 hours.
A single setting that allows users to configure a global alert fire frequency could also work. e.g. 6 hours, 12 hours, 1 day, 2 days, etc could also work.
Describe alternatives you've considered
Disabling the alert rule entirely, but new alerts would not trigger.
Creating a state machine in the alert channel webhook, to track and filter previously fired alerts.
Additional context
Add any other context or screenshots about the feature request here.
Thank you for your feature request – we love each and every one!
Is your feature request related to a problem?
Please describe.
Some alerts once detected can take days to resolve.
Describe the solution you'd like
it would would nice if we could visit the
Triggered Alerts
pane and acknowledge an alert that is in the firing state. Once acknowledged, it should not fire again until the state changes to resolved OR it could reduce the firing frequency to once every 24 hours.A single setting that allows users to configure a global alert fire frequency could also work. e.g. 6 hours, 12 hours, 1 day, 2 days, etc could also work.
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
Thank you for your feature request – we love each and every one!