alerting-dashboards-plugin
alerting-dashboards-plugin copied to clipboard
📟 Manage your monitors, alerts and notifications in OpenSearch Dashboards
**What is the bug?** The alerting UI uses this `onRunQuery` ([code link](https://github.com/opensearch-project/alerting-dashboards-plugin/blob/main/public/pages/CreateMonitor/containers/DefineMonitor/DefineMonitor.js#L345)) function to call the ExecuteMonitor API ([documentation link](https://opensearch.org/docs/latest/observing-your-data/alerting/api/#run-monitor)) which performs dry runs of a monitor as it's being...
### Description Fix cypress configuration for 3.0-alpha1. ### Issues Resolved https://github.com/opensearch-project/alerting-dashboards-plugin/pull/1218#issuecomment-2695907599 ### Check List - [ ] New functionality includes testing. - [ ] All tests pass - [ ]...
**Is your feature request related to a problem?** When I am creating an alert message, I want the message to contain as much information as possible, but I do not...
**Is your feature request related to a problem?** When creating an alerting monitor on top of an anomaly detector, the alerting dashboard only provides an easy UI to add trigger...
This is a component issue for `2.20.0`. Coming from https://github.com/opensearch-project/opensearch-build/issues/5295. Please follow the following checklist. __Please refer to the DATES in that post__. How to use this issue ## This...
**What is the bug?** I cannot create a trigger for my alert monitor configured for the anomaly detector. It tells me that "No features have been added to this anomaly...
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin As mentioned in this [META Issue](https://github.com/opensearch-project/opensearch-build/issues/5243), we want to track and increase transparency around the breaking changes planned for the 3.0...
This is a component issue for `2.19.0`. Coming from https://github.com/opensearch-project/opensearch-build/issues/5152. Please follow the following checklist. __Please refer to the DATES in that post__. How to use this issue ## This...
**What is the bug?** Currently, the alerting backend only supports sending trigger start/end time values in UTC format (see https://github.com/opensearch-project/alerting/issues/1744 for request to add custom timezone support). However, the notification...