Azure Monitor insights

Action group webhooks fail silently when target endpoints block Azure Monitor's source IP addresses, with no clear error surfaced to operators until they investigate specific fired alerts.

Email, SMS, and voice call notifications are rate-limited (100 emails/hour per address, 1 SMS or call per 5 minutes per phone number), causing subsequent critical alerts to be silently dropped during incident storms.

When a single user unsubscribes from an action group email, all distribution list members are unsubscribed, causing organization-wide notification gaps without obvious visibility to other users.

Application Insights Sampling Hiding Critical Failures

Default Application Insights sampling (max 20 items/second) can cause missed exceptions and request failures, obscuring critical production issues during troubleshooting.

Azure resources like App Service, Storage Accounts, and Key Vault don't emit platform metrics to Log Analytics or metrics pipeline when diagnostic settings are not configured, limiting troubleshooting to resource-level views only.

Guest (classic) metrics like memory pressure, disk queue depth, and per-process CPU usage are missing when Azure Diagnostics Extension is not enabled, limiting root cause analysis to host-level metrics only.

Missing Container Insights Data After Onboarding

No metrics appearing in Container Insights 15+ minutes after enabling indicates agent deployment issues, workspace authentication problems, or data collection configuration errors.

Resources that don't constantly emit metrics (e.g., stopped VMs, idle transactions) create data gaps. Alert rules may miss the first evaluation when new time series start after >24h of inactivity.

Static alert thresholds in cloud environments generate excessive noise during normal traffic fluctuations and miss real anomalies during expected high-traffic periods, causing teams to ignore critical alerts.

Alert rules configured with specific dimension values only monitor individual time series (e.g., per-disk, per-region), missing aggregate resource-level issues that span multiple dimension values.

New resources deployed through IaC or manual provisioning lack monitoring coverage because discovery and configuration are manual processes, creating blind spots that persist until the next audit cycle.

Metrics appear missing when users lack Monitoring Reader or workspace-level permissions, preventing troubleshooting even when data is being collected, particularly in cross-workspace scenarios.

Cloud costs remain high when underutilized resources are not systematically identified and rightsized, as manual reviews don't scale and Azure Advisor recommendations are ignored or not integrated into operations workflows.

Azure Monitor metrics fail to appear when the Microsoft.Insights resource provider is not registered for the subscription, causing complete monitoring blindness despite correct resource and metric selection.

Locking y-axis boundaries causes metric lines to render outside visible chart area, making performance degradation invisible even when metrics breach thresholds significantly.

Filters applied to one chart on a dashboard propagate to all charts in the pane, excluding all data from unrelated charts and creating false impressions of resource health.

Database Performance Bottlenecks Invisible Without Query Insights

SQL database performance issues remain undiagnosed without Query Performance Insights enabled, as high-level CPU and memory metrics don't reveal slow queries, missing indexes, or inefficient execution plans.

Application performance degradation attributed to network issues remains unresolved without Network Watcher and Traffic Manager analysis to identify packet loss, routing inefficiencies, or CDN misconfigurations.