opensearch-project / opensearch-project/alerting
[FEATURE] Add Tags to Monitors and Triggers
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?
Without a tagging system as metadata to filter searches, it is difficult to search for specific groups of related monitors or triggers while creating an inventory for monitors and triggers.
What solution would you like?
Alerts are generated with monitor and trigger tags.
API and GUI search capabilities for alerts based on monitor tags and trigger tags.
Ability to search for monitors using monitor tags via API and GUI.
Do you have any additional context?
"monitor_id" : "monitor_id",
"monitor_name" : "monitor_name",
"trigger_id" : "trigger_idd",
"trigger_name" : "Example Trigger Name",
-> "monitor_tags" : [ "monitor_tag_01", "monitor_tag_02" ]
-> "trigger_tags" : [ "trigger_tag_01", "trigger_tag_02" ]
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 mapping monitor and trigger storage, alert generation, and API/GUI search paths in the Kotlin alerting repository; done should include tags on monitors and triggers, tags in generated alerts, and searches for them through both API and GUI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100