# Distinguish Azure metric retention from the maximum chart time range

> A single chart's time limit is smaller than the retained platform-metric history.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:33:28+00:00
- Modified: 2026-09-17T16:38:46+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, IT
- Reading time: 1 minutes

## What you need to know

A single chart's time limit is smaller than the retained platform-metric history.

## Potentially affected

Use this review for platform or custom metrics viewed in the Metrics tile. Identify the metric category and requested interval before drawing conclusions about historical availability. Keep this guidance separate from Prometheus retention, log-based metrics and any configured external export destination.

## DSE recommendation

DSE recommends recording the requested period and then inspecting it in supported chart intervals.

## Article

## Source facts

Microsoft distinguishes 93-day retention for platform and custom metrics from the 30-day maximum time span for one Metrics-tile chart. It advises checking the selected start and end dates when a chart is blank or incomplete. The stated chart restriction does not apply to log-based metrics. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/data-platform-metrics).

## Applicability

Use this review for platform or custom metrics viewed in the Metrics tile. Identify the metric category and requested interval before drawing conclusions about historical availability. Keep this guidance separate from Prometheus retention, log-based metrics and any configured external export destination.

## DSE recommendation

DSE recommends recording the requested period and then inspecting it in supported chart intervals. Preserve the metric name, resource and aggregation while moving across the historical window. Ask the reporting owner to distinguish unavailable measurements from a display-range limitation in the final report. Avoid changing retention settings solely because one overlong chart appears empty.

## Verification

Select a supported interval containing known historical measurements and confirm that the chart renders. Move the interval to cover the remainder of the period being investigated and record any actual gaps. Compare those gaps with independent collection evidence where available. Retain the time-picker settings so a reviewer can reproduce the history check rather than relying on an unlabeled screenshot.

## Official references

[Microsoft Learn: Metrics in Azure Monitor](https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/data-platform-metrics).

## Primary reference

- Name: Metrics in Azure Monitor - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/data-platform-metrics
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Distinguish Azure metric retention from the maximum chart time range,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.