{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/", "slug": "dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition", "url": "https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/" }, "title": "Choose autoscale default capacity for a missing-metric condition", "summary": "The default count has a specific role when autoscale cannot read its resource metric.", "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:03+00:00", "modified_at": "2026-09-17T16:42:35+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 209, "potentially_affected": "Use this review when selecting or revising an autoscale setting's default capacity. Identify the resource metric and the workload expected during a monitoring interruption. Keep the default's missing-metric purpose distinct from the profile's minimum, maximum and ordinary rule thresholds.", "dse_recommendation": "DSE recommends asking the service owner to justify the default against an agreed reduced-observability scenario.", "primary_source": { "name": "Best practices for autoscale - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-best-practices", "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

Microsoft explains that when autoscale has a problem reading the resource metric, it increases capacity to the configured default if the current count is lower. If the current count already exceeds that default, this behavior does not scale it inward. The default is therefore a specific fallback count. Microsoft Learn.

\n

Applicability

\n

Use this review when selecting or revising an autoscale setting’s default capacity. Identify the resource metric and the workload expected during a monitoring interruption. Keep the default’s missing-metric purpose distinct from the profile’s minimum, maximum and ordinary rule thresholds.

\n

DSE recommendation

\n

DSE recommends asking the service owner to justify the default against an agreed reduced-observability scenario. Record the expected behavior when current capacity is below the default and when it is above. Assess application readiness at that capacity using approved workload evidence, and document who handles the underlying telemetry failure.

\n

Verification

\n

Review the deployed default and compare it with the approved scenario. In a controlled exercise where appropriate, observe the setting’s behavior when the metric is unavailable and compare lower- and higher-capacity cases. Restore normal collection and confirm fresh evaluations. Retain capacity observations separately from application-response evidence; a matching instance count alone does not prove acceptable service behavior.

\n

Official references

\n

Microsoft Learn: Best practices for autoscale.

", "content_text": "Source facts\nMicrosoft explains that when autoscale has a problem reading the resource metric, it increases capacity to the configured default if the current count is lower. If the current count already exceeds that default, this behavior does not scale it inward. The default is therefore a specific fallback count. Microsoft Learn.\nApplicability\nUse this review when selecting or revising an autoscale setting’s default capacity. Identify the resource metric and the workload expected during a monitoring interruption. Keep the default’s missing-metric purpose distinct from the profile’s minimum, maximum and ordinary rule thresholds.\nDSE recommendation\nDSE recommends asking the service owner to justify the default against an agreed reduced-observability scenario. Record the expected behavior when current capacity is below the default and when it is above. Assess application readiness at that capacity using approved workload evidence, and document who handles the underlying telemetry failure.\nVerification\nReview the deployed default and compare it with the approved scenario. In a controlled exercise where appropriate, observe the setting’s behavior when the metric is unavailable and compare lower- and higher-capacity cases. Restore normal collection and confirm fresh evaluations. Retain capacity observations separately from application-response evidence; a matching instance count alone does not prove acceptable service behavior.\nOfficial references\nMicrosoft Learn: Best practices for autoscale.", "content_markdown": "## Source facts\n\nMicrosoft explains that when autoscale has a problem reading the resource metric, it increases capacity to the configured default if the current count is lower. If the current count already exceeds that default, this behavior does not scale it inward. The default is therefore a specific fallback count. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-best-practices).\n\n## Applicability\n\nUse this review when selecting or revising an autoscale setting’s default capacity. Identify the resource metric and the workload expected during a monitoring interruption. Keep the default’s missing-metric purpose distinct from the profile’s minimum, maximum and ordinary rule thresholds.\n\n## DSE recommendation\n\nDSE recommends asking the service owner to justify the default against an agreed reduced-observability scenario. Record the expected behavior when current capacity is below the default and when it is above. Assess application readiness at that capacity using approved workload evidence, and document who handles the underlying telemetry failure.\n\n## Verification\n\nReview the deployed default and compare it with the approved scenario. In a controlled exercise where appropriate, observe the setting’s behavior when the metric is unavailable and compare lower- and higher-capacity cases. Restore normal collection and confirm fresh evaluations. Retain capacity observations separately from application-response evidence; a matching instance count alone does not prove acceptable service behavior.\n\n## Official references\n\n[Microsoft Learn: Best practices for autoscale](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-best-practices)." }, "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-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/", "url": "https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Choose autoscale default capacity for a missing-metric condition", "item": "https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/", "url": "https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/", "headline": "Choose autoscale default capacity for a missing-metric condition", "description": "The default count has a specific role when autoscale cannot read its resource metric.", "abstract": "The default count has a specific role when autoscale cannot read its resource metric.", "articleBody": "Source facts\nMicrosoft explains that when autoscale has a problem reading the resource metric, it increases capacity to the configured default if the current count is lower. If the current count already exceeds that default, this behavior does not scale it inward. The default is therefore a specific fallback count. Microsoft Learn.\nApplicability\nUse this review when selecting or revising an autoscale setting’s default capacity. Identify the resource metric and the workload expected during a monitoring interruption. Keep the default’s missing-metric purpose distinct from the profile’s minimum, maximum and ordinary rule thresholds.\nDSE recommendation\nDSE recommends asking the service owner to justify the default against an agreed reduced-observability scenario. Record the expected behavior when current capacity is below the default and when it is above. Assess application readiness at that capacity using approved workload evidence, and document who handles the underlying telemetry failure.\nVerification\nReview the deployed default and compare it with the approved scenario. In a controlled exercise where appropriate, observe the setting’s behavior when the metric is unavailable and compare lower- and higher-capacity cases. Restore normal collection and confirm fresh evaluations. Retain capacity observations separately from application-response evidence; a matching instance count alone does not prove acceptable service behavior.\nOfficial references\nMicrosoft Learn: Best practices for autoscale.", "datePublished": "2026-09-17T16:33:03+00:00", "dateModified": "2026-09-17T16:42:35+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/" }, "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-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/#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": "Choose autoscale default capacity for a missing-metric condition" }, "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": 209, "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": "Best practices for autoscale - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-best-practices" } } ] } }