minor changes
This commit is contained in:
parent
b01c44840a
commit
8fb4c250a0
|
@ -340,7 +340,7 @@ Returns whether the detector configuration has any issues that might prevent Ope
|
|||
|
||||
You can use the validate API to identify issues in your detector configuration before creating the detector.
|
||||
|
||||
The request body consists of the detector configuration and follows the same format as the request body of the [create detector API]({{site.url}}{{site.baseurl}}/monitoring-plugins/ad/api#create-anomaly-detector). You can pass an additional detector parameter to validate a specific detector.
|
||||
The request body consists of the detector configuration and follows the same format as the request body of the [create detector API]({{site.url}}{{site.baseurl}}/monitoring-plugins/ad/api#create-anomaly-detector).
|
||||
|
||||
#### Request
|
||||
|
||||
|
|
|
@ -110,7 +110,7 @@ We recommend experimenting with historical analysis with different feature sets
|
|||
|
||||
## Step 4: Review and create
|
||||
|
||||
Review your detector settings and model configurations to make sure that they're valid and then proceed to select **Create detector**.
|
||||
Review your detector settings and model configurations to make sure that they're valid and then select **Create detector**.
|
||||
|
||||
![Anomaly detection results]({{site.url}}{{site.baseurl}}/images/review_ad.png)
|
||||
|
||||
|
|
Loading…
Reference in New Issue