{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/",
        "slug": "dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm",
        "url": "https://update.dsesecurity.com/updates/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/"
        },
        "title": "Check App Service slots when Profiler sessions compete for the same VM",
        "summary": "Account for running deployment slots in a profiling-contention investigation.",
        "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:34:50+00:00",
        "modified_at": "2026-09-17T16:35:03+00:00",
        "reviewed_on": "2026-09-17",
        "reading_minutes": 1,
        "word_count": 208,
        "potentially_affected": "Use this review after observing the documented profiling-session problem. Identify the applications, running slots and App Service plans involved, together with the deployment schedule. This diagnosis does not establish that every missing profile is caused by session contention.",
        "dse_recommendation": "DSE recommends inventorying slot use with the application owners before changing profiling.",
        "primary_source": {
            "name": "Troubleshoot the .NET Profiler - Azure Monitor | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-troubleshooting",
            "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>For too many active Application Insights profiling sessions, Microsoft identifies running deployment slots as participants that compete for a profiling session on their VM. Its remedies include stopping unused slots, disabling unnecessary profiling and moving applications between App Service plans. It also discusses staging-slot profiling during deployments. <a href=\"https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-troubleshooting\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Use this review after observing the documented profiling-session problem. Identify the applications, running slots and App Service plans involved, together with the deployment schedule. This diagnosis does not establish that every missing profile is caused by session contention.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends inventorying slot use with the application owners before changing profiling. Choose the smallest approved adjustment that tests the contention explanation. Do not stop a slot merely because it is labeled staging; confirm its current purpose and preserve its previous state. Schedule any test around active releases and retain a reversal plan.</p>\n<h2>Verification</h2>\n<p>Record the initial error and the applications sharing the affected arrangement. Apply the approved adjustment, request a bounded profiling session and confirm whether a usable trace appears. Repeat the relevant deployment case if it caused the original symptom. Restore required slot behavior and document whether the evidence supports contention or requires another diagnostic branch.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-troubleshooting\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Troubleshoot the .NET Profiler</a>.</p>",
        "content_text": "Source facts\nFor too many active Application Insights profiling sessions, Microsoft identifies running deployment slots as participants that compete for a profiling session on their VM. Its remedies include stopping unused slots, disabling unnecessary profiling and moving applications between App Service plans. It also discusses staging-slot profiling during deployments. Microsoft Learn.\nApplicability\nUse this review after observing the documented profiling-session problem. Identify the applications, running slots and App Service plans involved, together with the deployment schedule. This diagnosis does not establish that every missing profile is caused by session contention.\nDSE recommendation\nDSE recommends inventorying slot use with the application owners before changing profiling. Choose the smallest approved adjustment that tests the contention explanation. Do not stop a slot merely because it is labeled staging; confirm its current purpose and preserve its previous state. Schedule any test around active releases and retain a reversal plan.\nVerification\nRecord the initial error and the applications sharing the affected arrangement. Apply the approved adjustment, request a bounded profiling session and confirm whether a usable trace appears. Repeat the relevant deployment case if it caused the original symptom. Restore required slot behavior and document whether the evidence supports contention or requires another diagnostic branch.\nOfficial references\nMicrosoft Learn: Troubleshoot the .NET Profiler.",
        "content_markdown": "## Source facts\n\nFor too many active Application Insights profiling sessions, Microsoft identifies running deployment slots as participants that compete for a profiling session on their VM. Its remedies include stopping unused slots, disabling unnecessary profiling and moving applications between App Service plans. It also discusses staging-slot profiling during deployments. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-troubleshooting).\n\n## Applicability\n\nUse this review after observing the documented profiling-session problem. Identify the applications, running slots and App Service plans involved, together with the deployment schedule. This diagnosis does not establish that every missing profile is caused by session contention.\n\n## DSE recommendation\n\nDSE recommends inventorying slot use with the application owners before changing profiling. Choose the smallest approved adjustment that tests the contention explanation. Do not stop a slot merely because it is labeled staging; confirm its current purpose and preserve its previous state. Schedule any test around active releases and retain a reversal plan.\n\n## Verification\n\nRecord the initial error and the applications sharing the affected arrangement. Apply the approved adjustment, request a bounded profiling session and confirm whether a usable trace appears. Repeat the relevant deployment case if it caused the original symptom. Restore required slot behavior and document whether the evidence supports contention or requires another diagnostic branch.\n\n## Official references\n\n[Microsoft Learn: Troubleshoot the .NET Profiler](https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-troubleshooting)."
    },
    "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-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-17"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Check App Service slots when Profiler sessions compete for the same VM",
                        "item": "https://update.dsesecurity.com/updates/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/",
                "headline": "Check App Service slots when Profiler sessions compete for the same VM",
                "description": "Account for running deployment slots in a profiling-contention investigation.",
                "abstract": "Account for running deployment slots in a profiling-contention investigation.",
                "articleBody": "Source facts\nFor too many active Application Insights profiling sessions, Microsoft identifies running deployment slots as participants that compete for a profiling session on their VM. Its remedies include stopping unused slots, disabling unnecessary profiling and moving applications between App Service plans. It also discusses staging-slot profiling during deployments. Microsoft Learn.\nApplicability\nUse this review after observing the documented profiling-session problem. Identify the applications, running slots and App Service plans involved, together with the deployment schedule. This diagnosis does not establish that every missing profile is caused by session contention.\nDSE recommendation\nDSE recommends inventorying slot use with the application owners before changing profiling. Choose the smallest approved adjustment that tests the contention explanation. Do not stop a slot merely because it is labeled staging; confirm its current purpose and preserve its previous state. Schedule any test around active releases and retain a reversal plan.\nVerification\nRecord the initial error and the applications sharing the affected arrangement. Apply the approved adjustment, request a bounded profiling session and confirm whether a usable trace appears. Repeat the relevant deployment case if it caused the original symptom. Restore required slot behavior and document whether the evidence supports contention or requires another diagnostic branch.\nOfficial references\nMicrosoft Learn: Troubleshoot the .NET Profiler.",
                "datePublished": "2026-09-17T16:34:50+00:00",
                "dateModified": "2026-09-17T16:35:03+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260917-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/"
                },
                "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-010-check-app-service-slots-when-profiler-sessions-compete-for-the-same-vm/#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": "Check App Service slots when Profiler sessions compete for the same VM"
                },
                "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": 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": "Troubleshoot the .NET Profiler - Azure Monitor | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-troubleshooting"
                }
            }
        ]
    }
}