You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 4, 2024. It is now read-only.
I have searched existing issues, it hasn't been reported yet
Use case description
When a function is producing constant errors, a Baselime alert with a higher frequency will "spam" the target channels with alerts for the same root issue.
It would be great to have a way of ensuring an alert that is triggered for the same root cause does not spam channels but instead has a status to say that the issue is persisting. When the errors stop, the status can revert to OK or equivalent.
It is also important for the "same root cause" check to have a way of differentiating between event (bodies) that are different but have the same underlying cause.
Proposed solution (optional)
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Use case description
When a function is producing constant errors, a Baselime alert with a higher frequency will "spam" the target channels with alerts for the same root issue.
It would be great to have a way of ensuring an alert that is triggered for the same root cause does not spam channels but instead has a status to say that the issue is persisting. When the errors stop, the status can revert to
OK
or equivalent.It is also important for the "same root cause" check to have a way of differentiating between event (bodies) that are different but have the same underlying cause.
Proposed solution (optional)
No response
The text was updated successfully, but these errors were encountered: