--- title: Azure Monitor Alerts with KQL & Bicep | daily.dev description: A walkthrough demonstrates setting up custom Azure Monitor alert rules based on your own application telemetry rather than just resource-health alerts. Using... canonical: https://daily.dev/posts/azure-monitor-alerts-with-kql-bicep-4vnjaobki twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Azure Monitor Alerts with KQL & Bicep | daily.dev og:description: A walkthrough demonstrates setting up custom Azure Monitor alert rules based on your own application telemetry rather than just resource-health alerts. Using... og:url: https://daily.dev/posts/azure-monitor-alerts-with-kql-bicep-4vnjaobki og:image: https://api.daily.dev/og/posts/4vnJAObki.png og:image:alt: Azure Monitor Alerts with KQL & Bicep og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Azure Monitor Alerts with KQL & Bicep **[We Are .NET](https://daily.dev/sources/wearedotnet)** · 7 min read · 0 upvotes · 0 comments ## Summary A walkthrough demonstrates setting up custom Azure Monitor alert rules based on your own application telemetry rather than just resource-health alerts. Using Bicep templates, the demo deploys a Log Analytics workspace, Application Insights, an action group, and several KQL-based alert rules covering exceptions, authorization failures, dependency failures, and zero-request availability windows. The presenter triggers a test API to fire these alerts, shows the resulting email notifications, and demonstrates investigating alerts via the query used to trigger them and via Log Analytics, noting logs typically take 1-5 minutes to appear and alerts can take about 5 minutes to notify. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I create custom Azure Monitor alerts based on my own application logs instead of just resource health? Custom alerts can be built using KQL queries against Log Analytics data, deployed through Bicep templates. A typical setup deploys a Log Analytics workspace, Application Insights, an action group, and log alert rules for scenarios like exceptions, authorization failures, dependency failures, and zero requests served over a time window (e.g., 5 minutes), with auto-mitigation configured per alert type. _daily.dev surfaces practical Azure Monitor and Bicep guides for teams wiring up telemetry-driven alerting._ ### Why is my Azure Monitor log alert taking several minutes to trigger an email notification? Delays are expected because logs typically take between 1 and 5 minutes to show up in Log Analytics after an event occurs, and since alert rules query Log Analytics data, the resulting email or notification can take roughly 5 minutes total to arrive after the triggering event. _Developers debugging alerting latency can find real-world Azure Monitor timing details on daily.dev._ ### Why should I set up an alert for zero requests served instead of only error-based alerts on my API? Zero-request alerts catch a failure mode error-based alerts miss: an application that stops serving requests entirely without throwing exceptions. Configuring a log alert rule that fires when no requests are logged for a period, such as 5 minutes, flags this as a warning or informational severity, distinct from hard error alerts like 500 responses or dependency failures. _Engineers designing meaningful alert coverage can track patterns like this via daily.dev._ ## Similar posts on daily.dev - [Building an end-to-end monitoring solution with Azure Arc, Log Analytics and Workbooks–Part 4: Data visualisation with Azure Workbooks](https://daily.dev/posts/building-an-end-to-end-monitoring-solution-with-azure-arc-log-analytics-and-workbooks-part-4-data--npwaymlc4) · The Art of Simplicity · 1 upvotes · 0 comments - [Alert with SQL in Cloud Monitoring Observability Analytics](https://daily.dev/posts/alert-with-sql-in-cloud-monitoring-observability-analytics-z2scmmavi) · Google Cloud · 0 upvotes · 0 comments - [Building an end-to-end monitoring solution with Azure Arc, Log Analytics and Workbooks–Part 1: Overview & Architecture](https://daily.dev/posts/building-an-end-to-end-monitoring-solution-with-azure-arc-log-analytics-and-workbooks-part-1-overv-nbcudlw0l) · The Art of Simplicity · 0 upvotes · 0 comments --- Tags: [#azure](https://daily.dev/tags/azure) [View this post on daily.dev](https://daily.dev/posts/azure-monitor-alerts-with-kql-bicep-4vnjaobki) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Azure Monitor Alerts with KQL & Bicep","url":"https://daily.dev/posts/azure-monitor-alerts-with-kql-bicep-4vnjaobki","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/azure-monitor-alerts-with-kql-bicep-4vnjaobki"},"datePublished":"2026-09-21T07:35:24.311Z","dateModified":"2026-09-21T07:35:45.857Z","description":"A walkthrough demonstrates setting up custom Azure Monitor alert rules based on your own application telemetry rather than just resource-health alerts. Using...","image":"https://i.ytimg.com/vi/T_83eLGWDdg/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/T_83eLGWDdg/sddefault.jpg","isAccessibleForFree":true,"articleSection":"We Are .NET","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"We Are .NET","logo":"https://media.daily.dev/image/upload/s--BsnVOa3i--/f_auto/v1718347410/logos/wearedotnet","url":"https://daily.dev/sources/wearedotnet"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/azure-monitor-alerts-with-kql-bicep-4vnjaobki","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"azure","timeRequired":"PT7M","video":{"@type":"VideoObject","name":"Azure Monitor Alerts with KQL & Bicep","description":"A walkthrough demonstrates setting up custom Azure Monitor alert rules based on your own application telemetry rather than just resource-health alerts. Using...","thumbnailUrl":"https://i.ytimg.com/vi/T_83eLGWDdg/sddefault.jpg","uploadDate":"2026-09-21T07:35:24.311Z","duration":"PT7M","url":"https://api.daily.dev/r/4vnJAObki","embedUrl":"https://www.youtube.com/embed/T_83eLGWDdg"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"We Are .NET","item":"https://daily.dev/sources/wearedotnet"},{"@type":"ListItem","position":3,"name":"Azure Monitor Alerts with KQL & Bicep"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/azure-monitor-alerts-with-kql-bicep-4vnjaobki#faq","mainEntity":[{"@type":"Question","name":"How can I create custom Azure Monitor alerts based on my own application logs instead of just resource health?","acceptedAnswer":{"@type":"Answer","text":"Custom alerts can be built using KQL queries against Log Analytics data, deployed through Bicep templates. A typical setup deploys a Log Analytics workspace, Application Insights, an action group, and log alert rules for scenarios like exceptions, authorization failures, dependency failures, and zero requests served over a time window (e.g., 5 minutes), with auto-mitigation configured per alert type. daily.dev surfaces practical Azure Monitor and Bicep guides for teams wiring up telemetry-driven alerting."}},{"@type":"Question","name":"Why is my Azure Monitor log alert taking several minutes to trigger an email notification?","acceptedAnswer":{"@type":"Answer","text":"Delays are expected because logs typically take between 1 and 5 minutes to show up in Log Analytics after an event occurs, and since alert rules query Log Analytics data, the resulting email or notification can take roughly 5 minutes total to arrive after the triggering event. Developers debugging alerting latency can find real-world Azure Monitor timing details on daily.dev."}},{"@type":"Question","name":"Why should I set up an alert for zero requests served instead of only error-based alerts on my API?","acceptedAnswer":{"@type":"Answer","text":"Zero-request alerts catch a failure mode error-based alerts miss: an application that stops serving requests entirely without throwing exceptions. Configuring a log alert rule that fires when no requests are logged for a period, such as 5 minutes, flags this as a warning or informational severity, distinct from hard error alerts like 500 responses or dependency failures. Engineers designing meaningful alert coverage can track patterns like this via daily.dev."}}]} ```