opensearch-project / opensearch-project/alerting
Exporting alerting objects
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 82
- Forks
- 133
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 9
Description
Monday Mar 09, 2020 at 19:43 GMT
Originally opened as https://github.com/opendistro-for-elasticsearch/alerting/issues/172
Users would like to be able to export alerting objects (monitors, alerts, destinations) for importing into a different cluster
https://discuss.opendistrocommunity.dev/t/exporting-alerts/2081/5
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 with the linked community discussion and the issue's original context. Clarify the export format, import interface, and how monitors, alerts, and destinations should be represented; the issue does not name files, tests, or an entry point, so a newcomer cannot yet verify when the work is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100