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

minor fixes

This commit is contained in:
ashwinkumar12345 2021-10-04 12:41:37 -07:00
parent 72c710d5a3
commit 1c10355a79
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
_monitoring-plugins/ad/api.md
View File

@ -793,7 +793,7 @@ POST _plugins/_anomaly_detection/detectors/results/_search
}
```
You can query the anomaly results of a historical detector with the `task_id`:
You can query the anomaly results for historical analysis with the `task_id`:
#### Request
@ -1570,7 +1570,7 @@ GET _plugins/_anomaly_detection/detectors/<detectorId>?job=true
}
```
Use `task=true` to get historical detector task information.
Use `task=true` to get historical analysis task information.
#### Request
@ -3195,7 +3195,7 @@ For a single-entity detector:
The `total_entities` parameter shows you the total number of entities including the number of category fields for a detector.
Getting the total count of entities is an expensive operation for a detector with more than one category field. By default, a real-time detector counts the number of entities up to a value of 10,000 and a historical detector counts the number of entities up to a value of 1,000.
Getting the total count of entities is an expensive operation for a detector with more than one category field. By default, a real-time detector counts the number of entities up to a value of 10,000 and historical analysis counts the number of entities up to a value of 1,000.
The `profile` operation also provides information about each entity, such as the entity’s `last_sample_timestamp` and `last_active_timestamp`. `last_sample_timestamp` shows the last document in the input data source index containing the entity, while `last_active_timestamp` shows the timestamp when the entity’s model was last seen in the model cache.
@ -3237,7 +3237,7 @@ GET _plugins/_anomaly_detection/detectors/<detectorId>/_profile?_all=true
}
```
For a historical detector, specify `_all` or `ad_task` to see information about its latest task:
For historical analysis, specify `_all` or `ad_task` to see information about its latest task:
#### Request

2
_monitoring-plugins/ad/index.md
View File

@ -153,7 +153,7 @@ If you stop or delete a detector, make sure to delete any monitors associated wi
To see all the configuration settings for a detector, choose the **Detector configuration** tab.
1. To make any changes to the detector configuration, or fine tune the time interval to minimize any false positives, go to the **Detector configuration** section and choose **Edit**.
- You need to stop a real-time or historical detector to change its configuration. Confirm that you want to stop the detector and proceed.
- You need to stop real-time or historical analysis to change its configuration. Confirm that you want to stop the detector and proceed.
1. To enable or disable features, in the **Features** section, choose **Edit** and adjust the feature settings as needed. After you make your changes, choose **Save and start detector**.
### Step 8: Manage your detectors