Examkin

Question

Difficulty: MediumImplement Azure Monitor Alerts and Action Groups

You are implementing Azure Monitor alerts and notifications for an Azure App Service web application. You need to configure a Log Search alert rule to detect failed dependency calls in Application Insights. When the alert fires, it must execute a custom workflow using an Azure Logic App. Which two configurations should you implement?

  1. Configure the alert rule to use an Action Group that includes a Logic App receiver.Answer
  2. Include a time-range filter in the KQL query, such as `where timestamp > ago(5m)`, to scope the Log Search alert rule.Answer
  3. C
    Omit time range filters from the KQL query so the alert evaluation engine can dynamically query all historical tables.
  4. D
    Initialize the Application Insights telemetry SDK in your application code without specifying the connection string.

Answer

Configure the alert rule to use an Action Group that includes a Logic App receiver, and include a time-range filter in the KQL query, such as `where timestamp > ago(5m)`, to scope the Log Search alert rule.
To execute a custom workflow using an Azure Logic App when an alert is triggered, you must configure the alert rule with an Action Group that contains a Logic App receiver. Additionally, Log Search alert rules in Azure Monitor require a KQL query that includes a time-range filter (such as `where timestamp > ago(5m)`) to scope the query and prevent scanning the entire history of telemetry data, which ensures optimal performance and prevents execution limits from being exceeded.

Step-by-Step Solution

1
Analyze the requirements for executing a custom workflow in response to Azure Monitor alerts.
Identify that an Azure Monitor Action Group must be configured with a Logic App receiver.
Action Groups support direct integration with Logic Apps to orchestrate custom workflows.
2
Determine how to query Application Insights telemetry for log search alert rules efficiently.
Ensure that the KQL query specifies a time filter (e.g., `where timestamp > ago(5m)`).
Omitting a time filter causes the query to scan the entire log history, leading to performance degradation and query execution limit errors.

Key Concept

Azure Monitor Log Search Alerts and Action Group Receivers
Rate this question

Topics

Implement Azure Monitor Alerts and Action Groups

More questions from this topic