{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/", "slug": "dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus", "url": "https://update.dsesecurity.com/updates/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/" }, "title": "Remove case-only distinctions before combining metrics in Managed Prometheus", "summary": "Will Azure Managed Prometheus preserve two series that differ only by letter case?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "managed-it", "label": "Managed IT operations", "alt": "A controlled technology lifecycle progressing from assessment to approved production.", "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "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-10T00:22:01+00:00", "modified_at": "2026-09-10T02:14:32+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 228, "potentially_affected": "Prometheus metric producers sending case-distinguished names or labels to Azure Monitor managed service for Prometheus.", "dse_recommendation": "Review metric and label identities for case-only collisions before directing their producers into the same managed workspace.", "primary_source": { "name": "Query Prometheus Metrics using the API and PromQL - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/prometheus-api-promql", "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": "

Source facts

\n

Azure Managed Prometheus treats metric names, label names and label values case-insensitively, unlike native self-managed Prometheus. Series differing only by letter case become one series. Samples arriving at the same timestamp for those case-only variants can have one randomly discarded, and returned casing is not predictable. Microsoft recommends producing or scraping with a consistent case. Microsoft Learn.

\n

Applicability

\n

Use this identity check when moving or combining self-managed metric streams. Decide whether case differences merely express inconsistent spelling or actually distinguish different entities in the producer’s model.

\n

DSE recommendation

\n

Review metric and label identities for case-only collisions before directing their producers into the same managed workspace. Where distinct entities currently rely on case, design a genuinely distinct identifier rather than simply lowercasing both into the same value. Coordinate naming changes with dashboard and rule owners, preserving the intended meaning of each series. Do not use the casing returned by one query as a durable identity convention.

\n

Verification

\n

In a bounded test, inspect representative source series and compare their intended identities with the managed result. Include case-only variants and simultaneous timestamps where appropriate, without claiming that the surviving variant will be deterministic. Confirm the revised identifiers remain distinct and that affected queries select the intended population. Retain the producer-to-series mapping as the acceptance evidence before expanding collection.

\n

Official references

\n

Microsoft Learn: Managed Prometheus query behavior. Source reviewed September 9, 2026.

", "content_text": "Source facts\nAzure Managed Prometheus treats metric names, label names and label values case-insensitively, unlike native self-managed Prometheus. Series differing only by letter case become one series. Samples arriving at the same timestamp for those case-only variants can have one randomly discarded, and returned casing is not predictable. Microsoft recommends producing or scraping with a consistent case. Microsoft Learn.\nApplicability\nUse this identity check when moving or combining self-managed metric streams. Decide whether case differences merely express inconsistent spelling or actually distinguish different entities in the producer’s model.\nDSE recommendation\nReview metric and label identities for case-only collisions before directing their producers into the same managed workspace. Where distinct entities currently rely on case, design a genuinely distinct identifier rather than simply lowercasing both into the same value. Coordinate naming changes with dashboard and rule owners, preserving the intended meaning of each series. Do not use the casing returned by one query as a durable identity convention.\nVerification\nIn a bounded test, inspect representative source series and compare their intended identities with the managed result. Include case-only variants and simultaneous timestamps where appropriate, without claiming that the surviving variant will be deterministic. Confirm the revised identifiers remain distinct and that affected queries select the intended population. Retain the producer-to-series mapping as the acceptance evidence before expanding collection.\nOfficial references\nMicrosoft Learn: Managed Prometheus query behavior. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nAzure Managed Prometheus treats metric names, label names and label values case-insensitively, unlike native self-managed Prometheus. Series differing only by letter case become one series. Samples arriving at the same timestamp for those case-only variants can have one randomly discarded, and returned casing is not predictable. Microsoft recommends producing or scraping with a consistent case. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/prometheus-api-promql).\n\n## Applicability\n\nUse this identity check when moving or combining self-managed metric streams. Decide whether case differences merely express inconsistent spelling or actually distinguish different entities in the producer’s model.\n\n## DSE recommendation\n\nReview metric and label identities for case-only collisions before directing their producers into the same managed workspace. Where distinct entities currently rely on case, design a genuinely distinct identifier rather than simply lowercasing both into the same value. Coordinate naming changes with dashboard and rule owners, preserving the intended meaning of each series. Do not use the casing returned by one query as a durable identity convention.\n\n## Verification\n\nIn a bounded test, inspect representative source series and compare their intended identities with the managed result. Include case-only variants and simultaneous timestamps where appropriate, without claiming that the surviving variant will be deterministic. Confirm the revised identifiers remain distinct and that affected queries select the intended population. Retain the producer-to-series mapping as the acceptance evidence before expanding collection.\n\n## Official references\n\n[Microsoft Learn: Managed Prometheus query behavior](https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/prometheus-api-promql). Source reviewed September 9, 2026." }, "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-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/", "url": "https://update.dsesecurity.com/updates/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Remove case-only distinctions before combining metrics in Managed Prometheus", "item": "https://update.dsesecurity.com/updates/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/", "url": "https://update.dsesecurity.com/updates/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/", "headline": "Remove case-only distinctions before combining metrics in Managed Prometheus", "description": "Will Azure Managed Prometheus preserve two series that differ only by letter case?", "abstract": "Will Azure Managed Prometheus preserve two series that differ only by letter case?", "articleBody": "Source facts\nAzure Managed Prometheus treats metric names, label names and label values case-insensitively, unlike native self-managed Prometheus. Series differing only by letter case become one series. Samples arriving at the same timestamp for those case-only variants can have one randomly discarded, and returned casing is not predictable. Microsoft recommends producing or scraping with a consistent case. Microsoft Learn.\nApplicability\nUse this identity check when moving or combining self-managed metric streams. Decide whether case differences merely express inconsistent spelling or actually distinguish different entities in the producer’s model.\nDSE recommendation\nReview metric and label identities for case-only collisions before directing their producers into the same managed workspace. Where distinct entities currently rely on case, design a genuinely distinct identifier rather than simply lowercasing both into the same value. Coordinate naming changes with dashboard and rule owners, preserving the intended meaning of each series. Do not use the casing returned by one query as a durable identity convention.\nVerification\nIn a bounded test, inspect representative source series and compare their intended identities with the managed result. Include case-only variants and simultaneous timestamps where appropriate, without claiming that the surviving variant will be deterministic. Confirm the revised identifiers remain distinct and that affected queries select the intended population. Retain the producer-to-series mapping as the acceptance evidence before expanding collection.\nOfficial references\nMicrosoft Learn: Managed Prometheus query behavior. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:22:01+00:00", "dateModified": "2026-09-10T02:14:32+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/" }, "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-20260909-595-remove-case-only-distinctions-before-combining-metrics-in-managed-prometheus/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Remove case-only distinctions before combining metrics in Managed Prometheus" }, "articleSection": [ "IT" ], "keywords": [ "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 228, "timeRequired": "PT2M", "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": "Query Prometheus Metrics using the API and PromQL - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/prometheus-api-promql" } } ] } }