You are implementing an Azure Monitor alert solution for an Azure App Service web application. You need to create an alert rule that triggers when the web application's CPU percentage deviates significantly from its historical baseline. The alert must trigger an Azure Function to execute diagnostic scripts and send an email notification to the operations team. Which configuration should you implement?
- Create a metric alert rule that uses dynamic thresholds. Create an action group containing both an Azure Function action and an Email/SMS/Push/Voice action.Cevap
- BCreate an activity log alert rule that uses dynamic thresholds. Create an action group containing both an Azure Function action and an Email/SMS/Push/Voice action.
- CCreate a log search alert rule with a Kusto Query Language (KQL) query that does not filter by time range. Create an action group containing a Webhook action to call the Azure Function.
- DCreate a metric alert rule that uses static thresholds. Create an action group containing an Azure Function action where the function code initializes telemetry tracking without a connection string.
Cevap
Create a metric alert rule that uses dynamic thresholds. Create an action group containing both an Azure Function action and an Email/SMS/Push/Voice action.
The correct configuration is to create a metric alert rule with dynamic thresholds combined with an action group that contains both an Azure Function action and an Email/SMS/Push/Voice action. Dynamic thresholds apply machine learning to automatically establish baselines and flag anomalies for resource metrics such as CPU percentage. Action groups natively support multiple action types, allowing the system to run an automated diagnostic function and email the team concurrently.
Adım Adım Çözüm
Anahtar Kavram
Azure Monitor Metric Alerts with Dynamic Thresholds and Action Group Actions