iSharkFly-Docs
/
opensearch-docs-cn
mirror of https://github.com/iSharkFly-Docs/opensearch-docs-cn
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOC] Fix broken links (#4593) 

* fix links

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>

* fix links

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>

* fix links

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>

* fix links

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>

---------

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
This commit is contained in:
Melissa Vagi 2023-07-20 11:55:04 -06:00 committed by GitHub
parent 3e1e8ce55d
commit b10173b3c5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
_observing-your-data/alerting/api.md
View File

@ -15,7 +15,7 @@ Use the Alerting API to programmatically create, update, and manage monitors and
Introduced 1.0
{: .label .label-purple }
Query-level monitors run the query and check whether or not the results should trigger an alert. Query-level monitors can only trigger one alert at a time. For more information about query-level monitors and bucket-level monitors, see [Create monitors]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/monitors/).
Query-level monitors run the query and check whether or not the results should trigger an alert. Query-level monitors can only trigger one alert at a time. For more information about query-level monitors and bucket-level monitors, see [Creating monitors]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/monitors/).
#### Sample Request
@ -317,7 +317,7 @@ For a full list of timezone names, refer to [Wikipedia](https://en.wikipedia.org
## Bucket-level monitors
Bucket-level monitors categorize results into buckets separated by fields. The monitor then runs your script with each bucket's results and evaluates whether to trigger an alert. For more information about bucket-level and query-level monitors, see [Create monitors]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/monitors/).
Bucket-level monitors categorize results into buckets separated by fields. The monitor then runs your script with each bucket's results and evaluates whether to trigger an alert. For more information about bucket-level and query-level monitors, see [Creating monitors]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/monitors/).
```json
POST _plugins/_alerting/monitors

8
_observing-your-data/alerting/monitors.md
View File

@ -12,7 +12,7 @@ redirect_from:
Proactively monitor your data in OpenSearch with alerting and anomaly detection. Set up alerts to receive notifications when your data exceeds certain thresholds. Anomaly detection uses machine learning (ML) to automatically detect any outliers in your streaming data. You can pair anomaly detection with alerting to ensure that you're notified as soon as an anomaly is detected.
See [Creating monitors](#creating-monitors), [Triggers]({{site.url}}{{site.baseurl}}/observing-your-data/monitors/triggers/), [Actions]({{site.url}}{{site.baseurl}}/observing-your-data/monitors/actions/), and [Notifications]({{site.url}}{{site.baseurl}}/observing-your-data/notifications/index/) to learn more about the use of these alerting features in OpenSearch.
See [Creating monitors](#creating-monitors), [Triggers]({{site.url}}{{site.baseurl}}/observing-your-data/alerting/triggers/), [Actions]({{site.url}}{{site.baseurl}}/observing-your-data/alerting/actions/), and [Notifications]({{site.url}}{{site.baseurl}}/observing-your-data/notifications/index/) to learn more about the use of these alerting features in OpenSearch.
The Alerting plugin provides four monitor types:
@ -32,7 +32,7 @@ To create a monitor:
1. Enter the **Monitor details**, including monitor type, method, and schedule.
1. Select a data source from the dropdown list.
1. Define the metrics in the Query section.
1. Add a [trigger]({{site.url}}{{site.baseurl}}/observing-your-data/triggers/).
1. Add a [trigger]({{site.url}}{{site.baseurl}}/observing-your-data/alerting/triggers/).
1. Select **Create**.
The maximum number of monitors you can create is 1,000. You can change the default maximum number of alerts for your cluster by updating the `plugins.alerting.monitor.max_monitors` setting using the [cluster settings API]({{site.url}}{{site.baseurl}}/observing-your-data/alerting/settings/).
@ -200,6 +200,6 @@ The cluster metrics monitor has the following limitations:
## Next steps
- Learn about [Triggers]({{site.url}}{{site.baseurl}}/observing-your-data/alerting/monitors/triggers/).
- Learn about [Actions]({{site.url}}{{site.baseurl}}/observing-your-data/alerting/monitors/actions/).
- Learn about [Triggers]({{site.url}}{{site.baseurl}}/observing-your-data/alerting/triggers/).
- Learn about [Actions]({{site.url}}{{site.baseurl}}/observing-your-data/alerting/actions/).
- Learn about [Notifications]({{site.url}}{{site.baseurl}}/observing-your-data/notifications/index/).