opensearch-project / opensearch-project/alerting
Support for Alert Trigger Chaining
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 82
- Forks
- 133
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 9
Description
Tuesday Apr 30, 2019 at 17:16 GMT
Originally opened as https://github.com/opendistro-for-elasticsearch/alerting/issues/44
A mechanism of chaining we should support is chaining triggers. The focus is to conditionally execute additional monitors/triggers based on based on previous trigger outcomes.
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
Start by reading the alerting code for monitors and triggers, since the issue does not name specific files, tests, or entry points. Define how trigger outcomes should conditionally execute additional monitors or triggers, then add coverage for the agreed chaining behavior; the issue provides no more specific completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100