{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/",
        "slug": "dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range",
        "url": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/"
        },
        "title": "Distinguish Azure metric retention from the maximum chart time range",
        "summary": "A single chart's time limit is smaller than the retained platform-metric history.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "cyber-defense",
            "label": "Cyber defense",
            "alt": "Layered glass and metal cyber-defense structure with controlled blue and gold signal paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-09-17T16:33:28+00:00",
        "modified_at": "2026-09-17T16:38:46+00:00",
        "reviewed_on": "2026-09-17",
        "reading_minutes": 1,
        "word_count": 215,
        "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.",
        "primary_source": {
            "name": "Metrics in Azure Monitor - Azure Monitor | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/data-platform-metrics",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts</h2>\n<p>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. <a href=\"https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/data-platform-metrics\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>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.</p>\n<h2>DSE recommendation</h2>\n<p>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.</p>\n<h2>Verification</h2>\n<p>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.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/data-platform-metrics\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Metrics in Azure Monitor</a>.</p>",
        "content_text": "Source facts\nMicrosoft 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.\nApplicability\nUse 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.\nDSE recommendation\nDSE 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.\nVerification\nSelect 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.\nOfficial references\nMicrosoft Learn: Metrics in Azure Monitor.",
        "content_markdown": "## Source facts\n\nMicrosoft 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).\n\n## Applicability\n\nUse 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nSelect 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.\n\n## Official references\n\n[Microsoft Learn: Metrics in Azure Monitor](https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/data-platform-metrics)."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-17"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Distinguish Azure metric retention from the maximum chart time range",
                        "item": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/",
                "headline": "Distinguish Azure metric retention from the maximum chart time range",
                "description": "A single chart's time limit is smaller than the retained platform-metric history.",
                "abstract": "A single chart's time limit is smaller than the retained platform-metric history.",
                "articleBody": "Source facts\nMicrosoft 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.\nApplicability\nUse 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.\nDSE recommendation\nDSE 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.\nVerification\nSelect 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.\nOfficial references\nMicrosoft Learn: Metrics in Azure Monitor.",
                "datePublished": "2026-09-17T16:33:28+00:00",
                "dateModified": "2026-09-17T16:38:46+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/dse-20260917-092-distinguish-azure-metric-retention-from-the-maximum-chart-time-range/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Distinguish Azure metric retention from the maximum chart time range"
                },
                "articleSection": [
                    "Cybersecurity",
                    "IT"
                ],
                "keywords": [
                    "Cybersecurity",
                    "IT",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 215,
                "timeRequired": "PT1M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Metrics in Azure Monitor - Azure Monitor | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/data-platform-metrics"
                }
            }
        ]
    }
}