Skip to content

Commit b6b78e3

Browse files
authored
Merge pull request #185451 from jr-MS/master
update SDK links
2 parents 017baa8 + 89cffe8 commit b6b78e3

File tree

2 files changed

+9
-5
lines changed

2 files changed

+9
-5
lines changed

articles/cognitive-services/Anomaly-Detector/How-to/multivariate-how-to.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,10 @@ Next you need to prepare your training data (and inference data with asynchronou
5959

6060
## Train an MVAD model
6161

62+
In this process, you should upload your data to blob storage and generate a SAS url used for training dataset.
63+
64+
For training data size, the maximum number of timestamps is `1000000`, and a recommended minimum number is `15000` timestamps.
65+
6266
Here is a sample request body and the sample code in Python to train an MVAD model.
6367

6468
```json
@@ -229,7 +233,7 @@ You could choose the asynchronous API, or the synchronous API for inference.
229233
| ------------- | ---------------- |
230234
| More suitable for batch use cases when customers don’t need to get inference results immediately and want to detect anomalies and get results over a longer time period.| When customers want to get inference immediately and want to detect multivariate anomalies in real time, this API is recommended. Also suitable for customers having difficulties conducting the previous compressing and uploading process for inference. |
231235

232-
To perform asynchronous inference, provide the blob source path to the zip file containing the inference data, the start time, and end time.
236+
To perform asynchronous inference, provide the blob source path to the zip file containing the inference data, the start time, and end time. For inference data volume, at least `1 sliding window` length and at most `20000` timestamps.
233237

234238
This inference is asynchronous, so the results are not returned immediately. Notice that you need to save in a variable the link of the results in the **response header** which contains the `resultId`, so that you may know where to get the results afterwards.
235239

@@ -374,7 +378,7 @@ The response contains the result status, variable information, inference paramet
374378
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:
375379
* Need to put data in **JSON format** into the API request body.
376380
* The inference results are limited to up to 10 data points, which means you could detect **1 to 10 timestamps** with one synchronous API call.
377-
* Due to payload limitation, the size of inference data in the request body is limited, which support at most `2880` timestamps * `300` variables.
381+
* Due to payload limitation, the size of inference data in the request body is limited, which support at most `2880` timestamps * `300` variables, and at least `1 sliding window length`.
378382

379383
### Request schema
380384

articles/cognitive-services/Anomaly-Detector/toc.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -89,11 +89,11 @@
8989
- name: .NET
9090
href: https://www.nuget.org/packages/Azure.AI.AnomalyDetector
9191
- name: Java
92-
href: https://repo1.maven.org/maven2/com/azure/azure-ai-anomalydetector/3.0.0-beta.3/
92+
href: https://repo1.maven.org/maven2/com/azure/azure-ai-anomalydetector
9393
- name: Python
94-
href: https://pypi.org/project/azure-ai-anomalydetector/
94+
href: https://pypi.org/project/azure-ai-anomalydetector
9595
- name: Node.js
96-
href: https://www.npmjs.com/package/@azure/ai-anomaly-detector/v/3.0.0-beta.4
96+
href: https://www.npmjs.com/package/@azure/ai-anomaly-detector
9797
- name: Resources
9898
items:
9999
- name: Enterprise readiness

0 commit comments

Comments
 (0)