opensearch-project / opensearch-project/alerting
Support multiple CRON expressions
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 82
- Forks
- 133
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 9
Description
Thursday Aug 22, 2019 at 14:15 GMT
Originally opened as https://github.com/opendistro-for-elasticsearch/alerting/issues/100
Complex schedules require more than 1 CRON expression, currently you can only enter 1 CRON expression. This forces you to create complex logic in painless scripting in triggers to create blackout windows which would be much better done using CRON.
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 files, tests, or entry points are named. Start by locating how the current single CRON expression is parsed and scheduled, then trace how monitor triggers use it. Done means a monitor can accept multiple CRON expressions and use them for complex schedules without requiring Painless blackout logic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100