opensearch-project / opensearch-project/alerting
[FEATURE] Bucket level monitors expose the bucket params that get stored in alerts in the ctx variable
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 82
- Forks
- 133
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 9
Description
Is your feature request related to a problem?
Currently, users cannot create alert notifications that include the bucket params configured in the monitor query.
What solution would you like?
Adding the bucket params that would be stored in the alert to the ctx variable would allow users to define alert notification messages that better call out what condition was triggered. It will be important to to not store the entire bucket contents in the ctx, just the params that were in the pipeline aggregation defined for the trigger.
What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any additional context?
Add any other context or screenshots about the feature request here.
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 tracing how bucket-level monitor queries build alerts and populate the ctx variable. Identify where pipeline aggregation parameters are available, then verify that only those parameters—not the entire bucket contents—are exposed in alert notification context. Done means notification messages can reference the stored bucket parameters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- backend, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100