Skip to content

Commit acf49d3

Browse files
committed
Merge branch 'auto-tuning' of https://github.com/L3vin/azure-docs into mrb_05_12_2022_metrics_advisor
2 parents 8ef1c7c + 97ef5fd commit acf49d3

File tree

7 files changed

+77
-0
lines changed

7 files changed

+77
-0
lines changed

articles/applied-ai-services/metrics-advisor/how-tos/configure-metrics.md

Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,68 @@ You can click the **Incidents** tab to view anomalies, and find a link to the [I
3434

3535
A metric can apply one or more detection configurations. There is a default configuration for each metric, which you can edit or add to, according to your monitoring needs.
3636

37+
### (NEW) Detection configuration auto-tuning based on anomaly preference
38+
39+
Detection configuration auto-tuning is a new feature released in Metrics Advisor, mainly to address the painpoints of following:
40+
41+
- In different use cases, the interest on types of anomaly is different. Some may be interested in sudden spikes or dips, but in some other cases, spikes/dips or transient anomalies are not critical. Previously it's hard to distinguish the configuration for different anomaly types, the new auto-tuning feature has made this possible. As of now, there're 5 anomaly patterns supported:
42+
43+
1. Spike
44+
2. Dip
45+
3. Increase
46+
4. Decrease
47+
5. Steady
48+
49+
- Sometimes, there might be many dimensions within one metric, which would split the metric into hundreds, thousands or even more time series to be monitored. However, they are not equally important. Take revenue as an example, the number on small regions or niche product category would be quite tiny and also not that stable. The new auto-tuning feature has made it possible to fine tune configuration based on series value range.
50+
51+
Eventually, users don't need to spend long time to fine tune the configuration again and again, and also alert noise will be reduced by applying the 'customized' configuration.
52+
53+
> [!NOTE]
54+
> The auto-tuning feature is only applied on 'Smart detection' method.
55+
56+
**Prerequisite on triggering auto-tuning**
57+
58+
After the metrics are onboarded to Metrics Advisor, the system will try to perform statistics on the metrics to categorize 'anomaly pattern' types and 'series value' distribution. By providing those to the users, users can further fine tune the configuration based on their specific preference. At the beginning, it will show a status of 'Initializing'.
59+
60+
:::image type="content" source="../media/metrics/autotuning-initializing.png" alt-text="Initializing auto-tuning" lightbox="../media/metrics/autotuning-initializing.png":::
61+
62+
**Choose to enable auto-tuning on 'anomaly pattern' and 'series value'**
63+
64+
As the pain-points shared before, the feature enables users to tuning detection configuration from two perspective 'anomaly pattern' and 'series value'. Based on specific use case, users can choose which one to be enabled or both.
65+
66+
- For 'anomaly pattern' preference, the system will list out different anomaly patterns that observed in the metric. Users can choose which ones they're interested in and select them, the unselected ones their sensitivity will be **reduced** by default.
67+
68+
- For 'series value' preference, it really depends on specific use case. If users would like to use a higher sensitivity for series with higher values, and decrease sensitivity on low value ones, or vice versa. Then please check the checkbox.
69+
70+
:::image type="content" source="../media/metrics/autotuning-initializing.png" alt-text="Initializing auto-tuning" lightbox="../media/metrics/autotuning-preference.png":::
71+
72+
**Tune the configuration for selected anomaly patterns**
73+
74+
If interested anomaly patterns have been chosen, the next step is to fine tune the configuration for each. There's a global 'sensitivity' that applied for all series. For each anomaly pattern, users can tune the 'adjustment', which is based on the global 'sensitivity'.
75+
76+
Please remember to tune on each anomaly pattern that been chosen respectively.
77+
78+
:::image type="content" source="../media/metrics/autotuning-initializing.png" alt-text="Initializing auto-tuning" lightbox="../media/metrics/autotuning-pattern.png":::
79+
80+
**Tune the configuration for each series value group**
81+
82+
After the system performs statistics on all time series within the metric, several series value groups are generated automatically. Same as above, users can fine tune the 'adjustment' for each series value group according to specific business needs.
83+
84+
There will be a default adjustment been configured to get the best detection results, but it can be further tuned.
85+
86+
:::image type="content" source="../media/metrics/autotuning-initializing.png" alt-text="Initializing auto-tuning" lightbox="../media/metrics/autotuning-value.png":::
87+
88+
**Set up alert rules**
89+
90+
Even the detection configuration on capturing valid anomalies is tuned, it's still important to input 'alert
91+
rules' to make sure the final alert rules can meet eventual business needs. There're a bunch of rules can be set, like 'filter rules' or 'snooze continuous alert rules'...
92+
93+
:::image type="content" source="../media/metrics/autotuning-initializing.png" alt-text="Initializing auto-tuning" lightbox="../media/metrics/autotuning-alert.png":::
94+
95+
96+
After configuring all above settings, the system will orchestrate them together and automatically detect anomalies based on inputted preference. The goal to get the best configuration that works for each metric can be achieved much easier by the new 'auto-tuning' feature!
97+
98+
3799
### Tune the configuration for all series in current metric
38100

39101
This configuration will be applied to all the series in this metric, except for ones with a separate configuration. A metric level configuration is applied by default when data is onboarded, and is shown on the left panel. Users can directly edit metric level config on metric page.

articles/applied-ai-services/metrics-advisor/index.yml

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,3 +78,18 @@ landingContent:
7878
links:
7979
- text: Support and help options
8080
url: ../../cognitive-services/cognitive-services-support-options.md?context=/azure/cognitive-services/metrics-advisor/context/context
81+
82+
- title: Blog posts
83+
linkLists:
84+
-linkListType: reference
85+
links:
86+
- text: Introducing Metrics Advisor - A new Cognitive Service
87+
url: https://techcommunity.microsoft.com/t5/azure-ai/introducing-metrics-advisor-a-new-cognitive-service/ba-p/1668025
88+
- text: Protect your organization's growth by using Azure Metrics Advisor
89+
url: https://techcommunity.microsoft.com/t5/azure-ai/protect-your-organization-s-growth-by-using-azure-metrics/ba-p/2564682
90+
- text: Supply Chain Anomaly Detection and Root Cause Analysis with Azure Metric Advisor
91+
url: https://techcommunity.microsoft.com/t5/azure-ai/supply-chain-anomaly-detection-and-root-cause-analysis-with/ba-p/2871920
92+
- text: Customer support: How Azure Metrics Advisor can help improve customer satisfaction
93+
url: https://techcommunity.microsoft.com/t5/azure-ai-blog/customer-support-how-azure-metrics-advisor-can-help-improve/ba-p/3038907
94+
- text: Detecting Methane Leaks using Azure Metrics Advisor
95+
url: https://techcommunity.microsoft.com/t5/ai-cognitive-services-blog/detecting-methane-leaks-using-azure-metrics-advisor/ba-p/3254005
46.5 KB
Loading
25.5 KB
Loading
76 KB
Loading
59.5 KB
Loading
72.1 KB
Loading

0 commit comments

Comments
 (0)