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/applied-ai-services/metrics-advisor/how-tos/configure-metrics.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ This allows you to not have to spend as much effort fine tuning your configurati
60
60
61
61
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 this functionality, you can further fine tune the configuration based on their specific preferences. At the beginning, it will show a status of **Initializing**.
:::image type="content" source="../media/metrics/autotuning-initializing.png" alt-text="Screenshot of Metrics Advisor UI with Initializing auto-tuning text visible" lightbox="../media/metrics/autotuning-initializing.png":::
64
64
65
65
#### Choose to enable auto-tuning on anomaly pattern and series value
66
66
@@ -70,30 +70,30 @@ The feature enables you to tune detection configuration from two perspectives **
70
70
71
71
- For the **series value** option, your selection will depend on your specific use case. You'll have to decide if you want to use a higher sensitivity for series with higher values, and decrease sensitivity on low value ones, or vice versa. Then check the checkbox.
:::image type="content" source="../media/metrics/autotuning-preference.png" alt-text="Screenshot with a toggle button for apply pattern preference and apply value preference selected." lightbox="../media/metrics/autotuning-preference.png":::
74
74
75
75
#### Tune the configuration for selected anomaly patterns
76
76
77
77
If specific anomaly patterns are chosen, the next step is to fine tune the configuration for each. There's a global **sensitivity** that is applied for all series. For each anomaly pattern, you can tune the **adjustment**, which is based on the global **sensitivity**.
78
78
79
79
You must tune each anomaly pattern that has been chosen individually.
:::image type="content" source="../media/metrics/autotuning-pattern.png" alt-text="Screenshot of auto-tuning pattern UI within Metrics Advisor" lightbox="../media/metrics/autotuning-pattern.png":::
82
82
83
83
#### Tune the configuration for each series value group
84
84
85
85
After the system generates statistics on all time series within the metric, several series value groups are created automatically. As described above, you can fine tune the **adjustment** for each series value group according to your specific business needs.
86
86
87
87
There will be a default adjustment configured to get the best detection results, but it can be further tuned.
:::image type="content" source="../media/metrics/autotuning-value.png" alt-text="Screenshot of pattern based sensitivity UI with adjustment for anomaly patterns, spike -30 highlighted on a slider with a range from -100 to 100." lightbox="../media/metrics/autotuning-value.png":::
90
90
91
91
#### Set up alert rules
92
92
93
93
Even once the detection configuration on capturing valid anomalies is tuned, it's still important to input **alert
94
94
rules** to make sure the final alert rules can meet eventual business needs. There are a number of rules that can be set, like **filter rules** or **snooze continuous alert rules**.
:::image type="content" source="../media/metrics/autotuning-alert.png" alt-text="Screenshot of setup alert rules UI within Metrics Advisor product." lightbox="../media/metrics/autotuning-alert.png":::
97
97
98
98
After configuring all the settings described in the section above, the system will orchestrate them together and automatically detect anomalies based on your inputted preferences. The goal is to get the best configuration that works for each metric, which can be achieved much easier through use of the new **auto-tuning** capability.
0 commit comments