opensearch-project / opensearch-project/alerting
Add support for tags on destinations / monitors
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 82
- Forks
- 133
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 9
Description
Saturday Jun 15, 2019 at 13:48 GMT
Originally opened as https://github.com/opendistro-for-elasticsearch/alerting/issues/70
When using the API to configure alerting, it would be helpful to create destinations (and potentially monitors) with tags so that the destinations could be retrieved by searching for a given set of tags.
For example, when creating a new monitor, I might want to re-use the destination for "production" and "team A", but there doesn't appear to be a good way to explicitly label destinations so they can be programatically retrieved.
As a couple of workarounds, I suppose:
- this information could be stored in the name of a destination
- the underlying object in the index could be updated
Related to #56 a bit.
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 reviewing the alerting API behavior for creating and retrieving destinations, then compare the related discussion in #56. Define the scope for tagging destinations and possible monitor support, including how a set of tags is queried and what successful assignment and retrieval should look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100