Azure Monitor does not count NULL values as valid metric measurements. An average containing missing measurements therefore uses fewer inputs; it does not silently substitute zero for them. Custom metrics use NULL when data is absent, while each platform resource provider chooses whether its metric records NULL or zero. Alerts consume the values written by that provider. Microsoft Learn.
\nCount measures the number of observations rather than their magnitudes. For most metrics, Average is calculated from Sum divided by Count. Line charts can represent NULL intervals with dotted or dashed segments. Microsoft Learn.
\nUse this interpretation for Azure Monitor platform and custom metrics, including standard Application Insights metrics. Identify the exact metric and provider before deciding what an empty interval means.
\nDSE recommends reviewing the available measurement count alongside the average when a reporting source disappears. Keep the selected dimensions and interval consistent during the comparison. Ask whether the apparent improvement reflects the same population of observations or fewer participating measurements. Document the provider’s actual missing-data behavior before adopting an alert threshold based on the displayed average.
\nCompare a controlled interval with complete reporting against one with a known collection gap. Reconcile available Sum, Count and Average values where the metric supports those aggregations. Confirm how the chart renders the gap and how the chosen alert treats the written values. Preserve that example so a later dashed segment is not casually described as a measured zero.
\n