# Allow for the Snapshot Debugger collection plan before expecting a snapshot of an exception

> Why does the default snapshot threshold of one still require an exception to occur twice?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-124-allow-for-the-snapshot-debugger-collection-plan-before-expecting-a-snapshot-of-an/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:29:52+00:00
- Modified: 2026-09-10T00:52:38+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Explainer
- DSE priority: Information
- Topics: IT
- Reading time: 2 minutes

## What you need to know

Why does the default snapshot threshold of one still require an exception to occur twice?

## Potentially affected

Application Insights Snapshot Debugger for supported .NET server applications; desktop clients such as WPF, Windows Forms and UWP are excluded.

## DSE recommendation

Test the exception's collection-plan lifecycle with controlled repetitions instead of treating the first missing snapshot as a broken uploader.

## Article

## Source facts

Snapshot Debugger counts exceptions by problem ID and adds the ID to a collection plan when the threshold is reached. With the default ThresholdForSnapshotting value of one, the same exception must occur twice before a snapshot is created. Collection also defaults to one snapshot per ten minutes, and the uploader is limited to fifty per day. WPF, Windows Forms and UWP clients are unsupported. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/snapshot-debugger/snapshot-debugger).

## Applicability

This concerns supported .NET server applications with Snapshot Debugger enabled. Microsoft warns that snapshots can contain sensitive variable and parameter values; use safe test data and appropriately controlled access. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/snapshot-debugger/snapshot-debugger).

## DSE recommendation

Test the exception’s collection-plan lifecycle with controlled repetitions instead of treating the first missing snapshot as a broken uploader. Record the configured threshold and rate limits before the test. Choose one identifiable, safe exception scenario and keep its repetitions distinct from unrelated exceptions. Do not raise production capture limits simply to make an initial test look successful.

## Verification

Compare the exception observations, elapsed time and snapshot availability with the configured collection behavior. Confirm that the test did not exceed an applicable capture or upload limit before escalating a missing artifact. If capture still fails under the expected conditions, preserve the settings and sanitized event sequence for focused troubleshooting. Report the actual observations rather than claiming that every exception receives a snapshot or that one successful capture proves complete diagnostic coverage.

## Official references

[Microsoft Learn: Snapshot Debugger process](https://learn.microsoft.com/en-us/azure/azure-monitor/snapshot-debugger/snapshot-debugger). Source reviewed September 9, 2026.

## Primary reference

- Name: Snapshot Debugger for .NET Exception Debugging - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/snapshot-debugger/snapshot-debugger
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Allow for the Snapshot Debugger collection plan before expecting a snapshot of an exception,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-124-allow-for-the-snapshot-debugger-collection-plan-before-expecting-a-snapshot-of-an/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.