Add Cluster Metrics instructions
Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
This commit is contained in:
Naarcha-AWS
parent
9d9c9bf020
commit
f04c81f4b5
|
|
@ -9,7 +9,6 @@ nav_order: 15
|
|||
|
||||
Use the alerting API to programmatically manage monitors and alerts.
|
||||
|
||||
|
||||
---
|
||||
|
||||
#### Table of contents
|
||||
|
|
|
|||
|
|
@ -185,8 +185,7 @@ Whereas query-level monitors run your specified query and then check whether the
|
|||
|
||||
1. Add a trigger to your monitor.
|
||||
|
||||
---
|
||||
|
||||
---
|
||||
## Create triggers
|
||||
|
||||
Steps to create a trigger differ depending on whether you chose **Visual editor**, **Extraction query editor**, or **Anomaly detector** when you created the monitor.
|
||||
|
|
@ -406,3 +405,112 @@ Acknowledged | Someone has acknowledged the alert, but not fixed the root cause.
|
|||
Completed | The alert is no longer ongoing. Alerts enter this state after the corresponding trigger evaluates to false.
|
||||
Error | An error occurred while executing the trigger---usually the result of a a bad trigger or destination.
|
||||
Deleted | Someone deleted the monitor or trigger associated with this alert while the alert was ongoing.
|
||||
|
||||
---
|
||||
|
||||
## Create cluster metrics monitor
|
||||
|
||||
In addition to monitoring conditions for indexes, the alerting plugin allows monitoring conditions on clusters. Alerts that can be set by ClusterMetrics to watch for when:
|
||||
|
||||
- The health of your cluster reaches a status of yellow or red.
|
||||
- CPU usages reaches a specified threshold.
|
||||
- JVM memory usage reaches a specified threshold.
|
||||
- The total number of documents stores reaches a specified amount.
|
||||
|
||||
To create a cluster metrics monitor:
|
||||
|
||||
1. Select **Alerting** > **Monitors** > **Create monitor**.
|
||||
2. Select the **Per cluster metrics monitor** option.
|
||||
3. In the Query section, pick the **Request type** from the dropdown.
|
||||
4. (Optional) If you want to filter the API response to use only certain path parameters, enter those parameters under **Query parameters**. Most APIs that can be used to monitor cluster status support path parameters as described in their documentation (e.g., comma-separated lists of index names).
|
||||
5. In the Triggers section, indicate what conditions trigger an alert. The trigger condition autopopulates a painless ctx variable. For example, a cluster monitor watching for Cluster Stats uses the trigger condition `ctx.results[0].indices.count <= 0`, which triggers an alert based on the number of indices returned by the query. For more specificity, add any additional painless conditions supported by the API. To see an example of the condition response, select **Preview condition response**.
|
||||
6. In the Actions sections, indicate how you want your users to be notified when a trigger condition is met.
|
||||
7. Select **Create**. Your new monitor appears in **Monitors** list.
|
||||
|
||||
### Supported APIs
|
||||
|
||||
Trigger conditions use responses from the following APIs. Most APIs that can be used to monitor cluster status support path parameters as described in their documentation (e.g., comma-separated lists of index names). However, they do not support query parameters.
|
||||
|
||||
1. [_cluster/health](https://opensearch.org/docs/latest/opensearch/rest-api/cluster-health/)
|
||||
2. [_cluster/stats](https://opensearch.org/docs/latest/opensearch/rest-api/cluster-stats/
|
||||
3. [_cluster/settings](https://opensearch.org/docs/latest/opensearch/rest-api/cluster-settings/)
|
||||
4. [_nodes/stats](https://opensearch.org/docs/latest/opensearch/popular-api/#get-node-statistics)
|
||||
5. _[cat/pending_tasks](https://opensearch.org/docs/latest/opensearch/rest-api/cat/cat-pending-tasks/)
|
||||
6. [_cat/recovery](https://opensearch.org/docs/latest/opensearch/rest-api/cat/cat-recovery/
|
||||
7. [_cat/snapshots](https://opensearch.org/docs/latest/opensearch/rest-api/cat/cat-snapshots/)
|
||||
8. [_cat/tasks](https://opensearch.org/docs/latest/opensearch/rest-api/cat/cat-tasks/)
|
||||
|
||||
### Restrict API fields
|
||||
|
||||
If you want to hide fields from the API response that you do not want exposed for alerting, create a `supported_json_payloads.json` file in the alerting plugin. The file functions as an allow list for the API fields you want to use in an alert. Cluster metric monitors can only be created for API's referenced by the supported payloads file. Furthermore, only fields reference in the supported files can create trigger conditions.
|
||||
|
||||
This ``supported_json_payloads.json` allows for a cluster metrics monitor to be created for the `_cluster/stats` API, and triggers conditions for the `indices.shards.total` and `indices.shards.index.shards.min` fields.
|
||||
|
||||
```json
|
||||
"/_cluster/stats": {
|
||||
"indices": [
|
||||
"shards.total",
|
||||
"shards.index.shards.min"
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### Painless triggers
|
||||
|
||||
Painless scripts define triggers for cluster metrics monitors, similar to query or bucket-level monitors that are defined using the extraction query definition option. Painless scripts are compromised of at least one statement and any additional functions you wish to execute.
|
||||
|
||||
The cluster metrics monitor supports up to **ten** triggers.
|
||||
|
||||
In this example, a JSON object creates a trigger that sends an alert when the Cluster Health is yellow. `script` points the `source` to the painless script `ctx.results[0].status == \"yellow\`.
|
||||
|
||||
```json
|
||||
{
|
||||
"name": "Cluster Health Monitor",
|
||||
"type": "monitor",
|
||||
"monitor_type": "query_level_monitor",
|
||||
"enabled": true,
|
||||
"schedule": {
|
||||
"period": {
|
||||
"unit": "MINUTES",
|
||||
"interval": 1
|
||||
}
|
||||
},
|
||||
"inputs": [
|
||||
{
|
||||
"uri": {
|
||||
"api_type": "CLUSTER_HEALTH",
|
||||
"path": "_cluster/health/",
|
||||
"path_params": "",
|
||||
"url": "http://localhost:9200/_cluster/health/"
|
||||
}
|
||||
}
|
||||
],
|
||||
"triggers": [
|
||||
{
|
||||
"query_level_trigger": {
|
||||
"id": "Tf_L_nwBti6R6Bm-18qC",
|
||||
"name": "Yellow status trigger",
|
||||
"severity": "1",
|
||||
"condition": {
|
||||
"script": {
|
||||
"source": "ctx.results[0].status == \"yellow\"",
|
||||
"lang": "painless"
|
||||
}
|
||||
},
|
||||
"actions": []
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
See [trigger variables](#trigger-variables), for more painless ctx options.
|
||||
|
||||
### Limitations
|
||||
|
||||
Currently, the cluster metrics monitor has the following limitations:
|
||||
|
||||
- You cannot create monitor for remote clusters.
|
||||
- The OpenSearch cluster must be in a state where an indexes conditions can be monitored and actions can be executed against the index.
|
||||
- Removing resource permissions from a user will not prevent that user’s preexisting monitors for that resource from executing.
|
||||
- Users with permissions to create monitors are not blocked from creating monitors for resources for which they do not have permissions; however, those monitors will not execute.
|
||||
Loading…
Reference in New Issue