opensearch-project / opensearch-project/alerting
Chained Alert Triggers failing with Error should create ERROR or not
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 82
- Forks
- 133
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 9
Description
Composite monitors support chained alert triggers. Chained alert trigger conditions evaluate to true when the delegate monitors in the composite monitors generate alerts to satisfy trigger condition.
If workflow or a composite monitor has 3 monitors m1, m2, m3 we can define chained alert trigger conditions could like like m1 || m2 || m3 or any such boolean operator based conditions. If m1 or m2 or m3 generate an alert, chained alert is created in that execution.
If there is an error when executing chained alert trigger should we create a chained alert in error state and send out a notification or should we simply log the error and not notify the user
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by tracing chained alert trigger execution for composite monitors and compare how execution errors are handled. Resolve whether an error creates an ERROR-state chained alert and notification or is only logged; done means the chosen behavior is implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100