Study guide
2.4 Application Insights & Diagnostic Monitoring Design
Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Orientation
1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide
2 Chapter 2: Logging, Monitoring & Diagnostics Design
2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design
3 Chapter 3: Authentication & Authorization Design
3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design
4 Chapter 4: Governance, Compliance & Identity Governance Design
4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design
5 Chapter 5: Relational Data Storage Design
5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design
6 Chapter 6: Semi-Structured & Unstructured Data Storage Design
6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design
7 Chapter 7: Data Integration & Analytics Design
7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design
8 Chapter 8: Backup & Disaster Recovery Design
8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design
9 Chapter 9: High Availability Design
9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design
10 Chapter 10: Compute Solution Design
10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)
11 Chapter 11: Application Architecture Design
11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)
12 Chapter 12: Migration Design
12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)
13 Chapter 13: Network Solution Design
13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design
14 Chapter 14: Final Review, Exam Strategy & Career Path
14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path
2.4 Application Insights & Diagnostic Monitoring Design
Key Takeaways Explain This Topic AI
Application Insights is Azure Monitor's APM layer for code-level visibility -- it complements, not replaces, platform-level diagnostic settings and metrics
All current Application Insights resources are workspace-based, storing telemetry in App* Log Analytics tables with 90 days of free default retention
The Azure Monitor OpenTelemetry Distro is the current recommended server-side instrumentation path; browser telemetry still uses the separate JavaScript SDK
Adaptive sampling (default) controls ingestion cost automatically; use fixed-rate sampling or exclusions only when specific telemetry must never be dropped
A diagnostic setting on an Application Insights resource cannot target its own backing Log Analytics workspace -- a common exam trap
Last updated: July 2026
Why This Topic Matters on AZ-305
This section is the second half of the split Recommend a monitoring solution bullet, focused on application-level observability rather than platform infrastructure. AZ-305 scenarios test whether you know when infrastructure-level Azure Monitor data (VM metrics, NSG flow logs) is insufficient and an Application Insights design is required to answer "is the problem in my code or in the platform underneath it?" — a distinction the exam metadata itself calls out as a defining design skill for this credential.
Core Concepts: Application Insights as an APM Layer
Application Insights is the Application Performance Monitoring (APM) feature of Azure Monitor. It is not a replacement for platform-level Azure Monitor — it is a complementary layer that instruments application code to answer questions platform metrics cannot: which specific dependency call is slow, which exception is spiking, and how a single user request traced across multiple services.
Two facts define a modern Application Insights design:
Workspace-based resource model. Every current Application Insights resource stores its telemetry inside a Log Analytics workspace , using dedicated App* tables ( AppRequests , AppDependencies , AppExceptions , AppTraces , AppEvents , AppMetrics , AppPageViews , AppAvailabilityResults , AppBrowserTimings , AppPerformanceCounters , AppSystemEvents ). Each of these tables defaults to 90 days of free retention , independently adjustable.
OpenTelemetry-based instrumentation. Microsoft's current recommended path for server-side apps (web apps, VMs, Azure Functions, AKS) is the Azure Monitor OpenTelemetry Distro , built on the vendor-neutral OpenTelemetry (OTel) standard, rather than the older classic per-language SDKs. Many platforms also support auto-instrumentation ("codeless") for zero-code data collection, while switching to the code-based Distro unlocks deeper configuration. Browser telemetry is the one major exception: client-side JavaScript still uses the dedicated Application Insights JavaScript SDK , which is not OpenTelemetry-based.
Key Application Insights Capabilities
- Capability What it answers
- Application Map Visual dependency graph — which services call which, and where latency/failures cluster
Live Metrics Sub-second, real-time view of active requests, failures, and server health — for watching a deployment as it happens
Distributed tracing / transaction search Follows one request end-to-end across service boundaries via correlation IDs
Availability tests Synthetic monitoring (URL ping tests, multi-step tests) that proactively check endpoint uptime and responsiveness from outside the app
Smart Detection Automatic anomaly detection for performance and failure patterns, without hand-written alert rules
Profiler / Snapshot Debugger Code-level diagnosis — captured performance traces and debug snapshots taken automatically when exceptions occur
Sampling: The Cost/Completeness Trade-off
High-traffic applications generate more telemetry than is cost-effective (or useful) to ingest in full. Application Insights supports:
Adaptive sampling (the default) — automatically adjusts the volume of telemetry sent to hit a target ingestion rate, preserving proportional visibility without manual tuning.
Fixed-rate sampling — a manually configured, constant percentage of telemetry is retained.
The architectural trade-off to recognize on the exam: sampling reduces both ingestion cost and the risk of throttling under load, but overly aggressive sampling can hide rare, high-value events such as an infrequent but critical exception. A production design for a high-traffic, cost-sensitive app typically defaults to adaptive sampling; a design where every failure must be captured (for example, a payment processing path) may instead exclude or minimize sampling on failure telemetry specifically.
A Diagnostic Settings Trap Specific to Application Insights
There is one Application Insights-specific constraint worth memorizing because it appears as a plausible-sounding wrong answer on architecture questions: a diagnostic setting on an Application Insights resource cannot target the same Log Analytics workspace that resource is already based on. Practically, if you need to also export Application Insights diagnostic data via a diagnostic setting (for example, to a Storage account or a different workspace for cross-tenant consolidation), the destination workspace must be a different one than the resource's own backing workspace, and the requesting user should not have simultaneous RBAC access to both, to avoid duplicate data appearing in queries.
Scenario Walkthrough
A multi-tier e-commerce application runs on Azure App Service (web tier) and Azure Kubernetes Service (order-processing tier). During a promotional sale, the team needs to determine whether checkout latency comes from application code or the underlying platform, needs an early warning if a payment API dependency starts failing, and must control ingestion cost given a 50x traffic spike. The correct design: instrument both tiers with the Azure Monitor OpenTelemetry Distro feeding a workspace-based Application Insights resource on the same Log Analytics workspace already used for platform-level diagnostic settings (so App* tables and infrastructure resource logs can be correlated in one KQL query); enable Application Map to visually separate app-code latency from platform latency; configure adaptive sampling to absorb the traffic spike economically while carving out an exception to fully capture payment-dependency failures; and layer a Smart Detection -derived alert rule plus an availability test hitting the checkout endpoint from multiple regions for synthetic uptime monitoring.
Key Takeaways
Application Insights is Azure Monitor's APM layer for code-level visibility; it complements, not replaces, platform-level diagnostic settings and metrics.
All current Application Insights resources are workspace-based, storing telemetry in App* Log Analytics tables with 90 days of free default retention.
The Azure Monitor OpenTelemetry Distro is the current recommended server-side instrumentation path; browser telemetry still uses the separate JavaScript SDK.
Adaptive sampling controls ingestion cost automatically; use fixed-rate sampling or sampling exclusions only when specific telemetry (like payment failures) must never be dropped.
A diagnostic setting on an Application Insights resource cannot target its own backing Log Analytics workspace — remember this as a common wrong-answer trap.