You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cognitive-services/Anomaly-Detector/How-to/multivariate-how-to.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ ms.author: mbullwin
17
17
The Multivariate Anomaly Detector (MVAD) provides two primary methods to detect anomalies compared with Univariate Anomaly Detector (UVAD), **training** and **inference**. During the inference process, you can choose to use an asynchronous API or a synchronous API to trigger inference one time. Both of these APIs support batch or streaming scenarios.
18
18
19
19
The following are the basic steps needed to use MVAD:
20
-
1. Create an Anomaly Detector resource in the Azure Portal.
20
+
1. Create an Anomaly Detector resource in the Azure portal.
21
21
1. Prepare data for training and inference.
22
22
1. Train an MVAD model.
23
23
1. Get model status.
@@ -41,7 +41,7 @@ Generally, multivariate anomaly detector includes a set of APIs, covering the wh
41
41
|`/multivariate/models/{modelId}/export`| Export model as a Zip file. |
42
42
43
43
44
-
## Create an Anomaly Detector resource in Azure Portal
44
+
## Create an Anomaly Detector resource in Azure portal
45
45
46
46
* Create an Azure subscription if you don't have one - [Create one for free](https://azure.microsoft.com/free/cognitive-services)
47
47
* Once you have your Azure subscription, [create an Anomaly Detector resource](https://ms.portal.azure.com/#create/Microsoft.CognitiveServicesAnomalyDetector) in the Azure portal to get your API key and API endpoint.
@@ -237,7 +237,7 @@ Failures are usually caused by model issues or data issues. You cannot perform i
237
237
238
238
### Get inference results (asynchronous only)
239
239
240
-
You need the `resultId` to get results. `resultId` is obtained from the response header when you submit the inference request. Consult [this page for instructions to query the inference results.](https://westus2.dev.cognitive.microsoft.com/docs/services/AnomalyDetector-v1-1-preview/operations/GetDetectionResult)
240
+
You need the `resultId` to get results. `resultId` is obtained from the response header when you submit the inference request. Consult [this page for instructions to query the inference results](https://westus2.dev.cognitive.microsoft.com/docs/services/AnomalyDetector-v1-1-preview/operations/GetDetectionResult).
241
241
242
242
A sample response looks like this:
243
243
@@ -367,7 +367,7 @@ The response contains the result status, variable information, inference paramet
367
367
## (NEW) Inference with synchronous API
368
368
369
369
> [!NOTE]
370
-
> In v1.1-preview.1, we support synchronous API and add more fields in inference result for both asynchronous API and synchronous API, you could upgrade the API version to access to these features. Once you upgrade, you'll no longer use previous model trained in old version, you should retrain a model to fit for new fields.
370
+
> In v1.1-preview.1, we support synchronous API and add more fields in inference result for both asynchronous API and synchronous API, you could upgrade the API version to access to these features. Once you upgrade, you'll no longer use previous model trained in old version, you should retrain a model to fit for new fields.[Learn more about v1.1-preview.1](https://westus2.dev.cognitive.microsoft.com/docs/services/AnomalyDetector-v1-1-preview-1/operations/DetectAnomaly).
371
371
372
372
With the synchronous API, you can get inference results point by point in real time, and no need for compressing and uploading task like training and asynchronous inference. Here are some requirements for the synchronous API:
373
373
* Need to put data in **JSON format** into the API request body.
0 commit comments