alerting
alerting copied to clipboard
opensearch-project
📟 Get notified when your data meets certain conditions by setting up monitors, alerts, and notifications
Backport 03595f838e925e378b59ad27fc1916e275acb913 from #1766.
![opensearch-trigger-bot[bot] avatar](https://avatars.githubusercontent.com/u/80134844?v=4 "opensearch-trigger-bot[bot] avatar"){kind=avatar}
Backport 03595f838e925e378b59ad27fc1916e275acb913 from #1766.
* shards assignment to local Node when fanout flag is disabled Signed-off-by: Riya Saxena * shards assignment to local Node when fanout flag is disabled Signed-off-by: Riya Saxena * shards...
- Incremented version to **2.17.2-SNAPSHOT**.
**Is your feature request related to a problem?** Currently, alerting only supports alerts based on trigger conditions, which, when true, mark the alert as active. However, when the alert is...
**What solution would you like?** Currently, the alerting backend only supports sending notification messages with time values (e.g., [trigger start and end times](https://github.com/opensearch-project/alerting/blob/main/alerting/src/main/kotlin/org/opensearch/alerting/script/TriggerExecutionContext.kt#L16-L17)) in UTC. The alerting plugin is just...
### Describe the bug When using alerting the .opensearch-alerting-config-lock shard isn't rotated and can grow past a recoverable shard size which then breaks all alerting. Because this is a shard...
### Description Small change to only limit the `Cancelling the migration process.` log line if a scheduled migration exists. This log line can be seen whenever an index is created...
**What is the bug?** missing cluster permission cluster:admin/opensearch/alerting/workflow/write in alerting_full_access role **How can one reproduce the bug?** Steps to reproduce the behavior: User is trying to create a composite monitor...
- Incremented version to **2.18.1-SNAPSHOT**.
Metadata
Owner
Metadata
📟 Get notified when your data meets certain conditions by setting up monitors, alerts, and notifications