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/prepare-data.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,9 +25,7 @@ First you need to prepare your data for training and inference.
25
25
26
26
Multivariate Anomaly Detection supports two types of data schemas: **OneTable** and **MultiTable**. You could use either of these schemas to prepare your data and upload to Storage Account for further training and inference.
27
27
28
-
29
-
> [!div class="mx-imgBorder"]
30
-
> 
28
+
:::image type="content" source="./media/prepare-data/two-schemas.png" alt-text="Diagram of two data schemas with three steps: data preparation, training, inference." lightbox="./media/prepare-data/two-schemas.png":::
31
29
32
30
#### Schema 1: OneTable
33
31
**OneTable** is one CSV file that contains all the variables that you want to train a Multivariate Anomaly Detection model and one `timestamp` column. Download [One Table sample data](https://mvaddataset.blob.core.windows.net/public-sample-data/sample_data_5_3000.csv)
@@ -37,8 +35,7 @@ Multivariate Anomaly Detection supports two types of data schemas: **OneTable**
37
35
38
36
***Example:***
39
37
40
-
> [!div class="mx-imgBorder"]
41
-
> 
38
+

42
39
43
40
#### Schema 2: MultiTable
44
41
@@ -53,7 +50,7 @@ Multivariate Anomaly Detection supports two types of data schemas: **OneTable**
53
50
***Example:***
54
51
55
52
> [!div class="mx-imgBorder"]
56
-
> 
53
+
> 
57
54
58
55
> [!NOTE]
59
56
> If your timestamps have hours, minutes, and/or seconds, ensure that they're properly rounded up before calling the APIs.
@@ -67,7 +64,7 @@ Once you prepare your data with either of the two schemas above, you could uploa
67
64
1.[Create a Storage Account](https://portal.azure.com/#create/Microsoft.StorageAccount-ARM), fill out the fields, which are similar to the steps when creating Anomaly Detector resource.
68
65
69
66
> [!div class="mx-imgBorder"]
70
-
> 
67
+
> 
71
68
72
69
2. Select **Container** to the left in your Storage Account resource and select **+Container** to create one that will store your data.
73
70
@@ -80,7 +77,7 @@ Once you prepare your data with either of the two schemas above, you could uploa
80
77
Once your data is uploaded, select your CSV file and copy the **blob URL** through the small blue button. (Please paste the URL somewhere convenient for further steps.)
81
78
82
79
> [!div class="mx-imgBorder"]
83
-
> 
80
+
> 
84
81
85
82
**Upload *MultiTable* data**
86
83
@@ -89,17 +86,18 @@ Once you prepare your data with either of the two schemas above, you could uploa
89
86
Once your data is uploaded, go into the folder, and select one CSV file in the folder, copy the **blob URL** and only keep the part before the name of this CSV file, so the final blob URL should ***link to the folder***. (Please paste the URL somewhere convenient for further steps.)
90
87
91
88
> [!div class="mx-imgBorder"]
92
-
> 
89
+
> 
93
90
94
91
4. Grant Anomaly Detector access to read the data in your Storage Account.
95
92
* In your container, select **Access Control(IAM)** to the left, select **+ Add** to **Add role assignment**. If you see the add role assignment is disabled, please contact your Storage Account owner to add Owner role to your Container.
96
93
97
94
> [!div class="mx-imgBorder"]
98
-
> 
95
+
> 
99
96
100
97
* Search role of **Storage Blob Data Reader**, **click on it** and then select **Next**. Technically, the roles highlighted below and the *Owner* role all should work.
101
98
102
-

99
+
> [!div class="mx-imgBorder"]
100
+
> 
103
101
104
102
* Select assign access to **Managed identity**, and **Select Members**, then choose the anomaly detector resource that you created earlier, then select **Review + assign**.
0 commit comments