opensearch-project / opensearch-project/alerting
[FEATURE] Performance guidance for Document-level monitors / alerting
@lezzago is already working on this.
Since Oct 27, 2022.
- Dominant language
- Kotlin
- Stars
- 82
- Forks
- 133
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 9
Description
Is your feature request related to a problem?
We plan to soon start testing some use cases requiring many different combinations of monitors, queries, triggers, and actions for document level monitoring, but are not quite clear the best way to implement, at scale, to achieve best performance.
What solution would you like?
Can we get some guidance on performance impacts of building out many different monitor object, vs packing more queries into one monitoring object, impact of one vs many trigger definitions in in the context of a monitoring definition, etc…
It would also be great to update the docs with such guidance :slight_smile:
What alternatives have you considered?
n/a
Do you have any additional context?
https://forum.opensearch.org/t/performance-guidance-for-document-level-monitors-alerting/11216/1
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.
Assessment
This issue has not been assessed yet.