{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/",
        "slug": "dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart",
        "url": "https://update.dsesecurity.com/updates/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/"
        },
        "title": "Check NAT Gateway metric aggregation before interpreting a connection-count chart",
        "summary": "Avoid counting metric samples when the question concerns the values they contain.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "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:49+00:00",
        "modified_at": "2026-09-17T16:38:45+00:00",
        "reviewed_on": "2026-09-17",
        "reading_minutes": 1,
        "word_count": 208,
        "potentially_affected": "Review saved charts, alert definitions and exported evidence that use NAT Gateway metrics. Identify the exact metric, selected dimensions, aggregation and time interval before comparing totals or interpreting a small amount of unexplained traffic.",
        "dse_recommendation": "DSE recommends including chart configuration alongside any reported measurement.",
        "primary_source": {
            "name": "Metrics and alerts for Azure NAT Gateway - Azure NAT Gateway | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/nat-gateway/nat-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 discourages Count aggregation for NAT Gateway metrics because it counts reported metric values instead of adding their contents. Its guidance uses Sum for connection, byte and packet counts, and Average for datapath availability. The documentation also notes that platform health-check connections can appear in the SNAT connection metric. <a href=\"https://learn.microsoft.com/en-us/azure/nat-gateway/nat-metrics\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Review saved charts, alert definitions and exported evidence that use NAT Gateway metrics. Identify the exact metric, selected dimensions, aggregation and time interval before comparing totals or interpreting a small amount of unexplained traffic.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends including chart configuration alongside any reported measurement. Have the monitoring owner check whether the chosen aggregation answers the operational question. Correct misleading saved views and revisit conclusions that depended on them. Keep application-generated test traffic distinct from the background observations rather than labeling every connection as a user transaction.</p>\n<h2>Verification</h2>\n<p>For a fixed observation interval, compare the approved chart with the same metric values using the documented aggregation. Preserve metric name, filters, interval and configuration with the result. Exercise a small authorized traffic test and check that the chart responds as expected. If numbers still disagree, inspect dimension selection before adjusting capacity or security controls.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/nat-gateway/nat-metrics\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Metrics and alerts for Azure NAT Gateway</a>.</p>",
        "content_text": "Source facts\nMicrosoft discourages Count aggregation for NAT Gateway metrics because it counts reported metric values instead of adding their contents. Its guidance uses Sum for connection, byte and packet counts, and Average for datapath availability. The documentation also notes that platform health-check connections can appear in the SNAT connection metric. Microsoft Learn.\nApplicability\nReview saved charts, alert definitions and exported evidence that use NAT Gateway metrics. Identify the exact metric, selected dimensions, aggregation and time interval before comparing totals or interpreting a small amount of unexplained traffic.\nDSE recommendation\nDSE recommends including chart configuration alongside any reported measurement. Have the monitoring owner check whether the chosen aggregation answers the operational question. Correct misleading saved views and revisit conclusions that depended on them. Keep application-generated test traffic distinct from the background observations rather than labeling every connection as a user transaction.\nVerification\nFor a fixed observation interval, compare the approved chart with the same metric values using the documented aggregation. Preserve metric name, filters, interval and configuration with the result. Exercise a small authorized traffic test and check that the chart responds as expected. If numbers still disagree, inspect dimension selection before adjusting capacity or security controls.\nOfficial references\nMicrosoft Learn: Metrics and alerts for Azure NAT Gateway.",
        "content_markdown": "## Source facts\n\nMicrosoft discourages Count aggregation for NAT Gateway metrics because it counts reported metric values instead of adding their contents. Its guidance uses Sum for connection, byte and packet counts, and Average for datapath availability. The documentation also notes that platform health-check connections can appear in the SNAT connection metric. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/nat-gateway/nat-metrics).\n\n## Applicability\n\nReview saved charts, alert definitions and exported evidence that use NAT Gateway metrics. Identify the exact metric, selected dimensions, aggregation and time interval before comparing totals or interpreting a small amount of unexplained traffic.\n\n## DSE recommendation\n\nDSE recommends including chart configuration alongside any reported measurement. Have the monitoring owner check whether the chosen aggregation answers the operational question. Correct misleading saved views and revisit conclusions that depended on them. Keep application-generated test traffic distinct from the background observations rather than labeling every connection as a user transaction.\n\n## Verification\n\nFor a fixed observation interval, compare the approved chart with the same metric values using the documented aggregation. Preserve metric name, filters, interval and configuration with the result. Exercise a small authorized traffic test and check that the chart responds as expected. If numbers still disagree, inspect dimension selection before adjusting capacity or security controls.\n\n## Official references\n\n[Microsoft Learn: Metrics and alerts for Azure NAT Gateway](https://learn.microsoft.com/en-us/azure/nat-gateway/nat-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-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-17"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Check NAT Gateway metric aggregation before interpreting a connection-count chart",
                        "item": "https://update.dsesecurity.com/updates/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/",
                "headline": "Check NAT Gateway metric aggregation before interpreting a connection-count chart",
                "description": "Avoid counting metric samples when the question concerns the values they contain.",
                "abstract": "Avoid counting metric samples when the question concerns the values they contain.",
                "articleBody": "Source facts\nMicrosoft discourages Count aggregation for NAT Gateway metrics because it counts reported metric values instead of adding their contents. Its guidance uses Sum for connection, byte and packet counts, and Average for datapath availability. The documentation also notes that platform health-check connections can appear in the SNAT connection metric. Microsoft Learn.\nApplicability\nReview saved charts, alert definitions and exported evidence that use NAT Gateway metrics. Identify the exact metric, selected dimensions, aggregation and time interval before comparing totals or interpreting a small amount of unexplained traffic.\nDSE recommendation\nDSE recommends including chart configuration alongside any reported measurement. Have the monitoring owner check whether the chosen aggregation answers the operational question. Correct misleading saved views and revisit conclusions that depended on them. Keep application-generated test traffic distinct from the background observations rather than labeling every connection as a user transaction.\nVerification\nFor a fixed observation interval, compare the approved chart with the same metric values using the documented aggregation. Preserve metric name, filters, interval and configuration with the result. Exercise a small authorized traffic test and check that the chart responds as expected. If numbers still disagree, inspect dimension selection before adjusting capacity or security controls.\nOfficial references\nMicrosoft Learn: Metrics and alerts for Azure NAT Gateway.",
                "datePublished": "2026-09-17T16:33:49+00:00",
                "dateModified": "2026-09-17T16:38:45+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260917-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/"
                },
                "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-071-check-nat-gateway-metric-aggregation-before-interpreting-a-connection-count-chart/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Check NAT Gateway metric aggregation before interpreting a connection-count chart"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Networks & Infrastructure",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 208,
                "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 and alerts for Azure NAT Gateway - Azure NAT Gateway | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/nat-gateway/nat-metrics"
                }
            }
        ]
    }
}