dump-collect

Configure and collect crash dump artifacts for .NET CoreCLR and NativeAOT applications.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill dump-collect-1k-off
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dump-collect
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/dump-collect
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill dump-collect-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you enable automatic crash dump collection or capture an on-demand dump for modern .NET applications so you can preserve diagnostic artifacts without getting stuck on analysis.

Core Features & Use Cases

  • CoreCLR dump collection (auto or on-demand): Configure environment variables for automatic dump creation on crash or collect dumps from running processes using supported tools.
  • NativeAOT dump collection (full dumps): Use OS-level core dump mechanisms or createdump-based alternatives, respecting NativeAOT’s full-dump requirement.
  • Container/Kubernetes readiness: Apply required Linux capabilities (like SYS_PTRACE), volume/storage setup, and verification steps to ensure dumps actually land where you expect.
  • Scope guardrails: The Skill explicitly avoids analysis/triage steps and focuses only on enabling and collecting dump files.

Quick Start

Enable crash dump collection for your CoreCLR app by setting the required dump environment variables and ensuring your dump output directory exists and is writable.

Frequently Asked Questions about dump-collect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect .NET crash dumps in a Kubernetes production environment?

To collect .NET crash dumps in Kubernetes, apply required Linux capabilities like SYS_PTRACE, configure volume storage for output paths, and set runtime-specific environment variables to ensure dumps land correctly in the container.

What is the difference between collecting dumps for CoreCLR and NativeAOT applications?

CoreCLR dump collection supports automatic and on-demand capture using environment variables and runtime tools, whereas NativeAOT requires OS-level core dump mechanisms or createdump-based alternatives for full dumps.

How do I configure automatic crash dump generation for a running .NET process?

Configure automatic crash dump generation by setting the required CoreCLR environment variables for dump creation on crash, and verifying that your designated dump output directory exists and is writable.

Do I need special permissions to capture diagnostic dumps from Docker containers?

Capturing diagnostic dumps from Docker containers requires specific Linux capabilities such as SYS_PTRACE, along with proper volume and storage setup, to ensure the dump files are written to the expected output paths.

Can this Skill analyze the .NET crash dumps it helps collect?

No, this Skill explicitly avoids analysis and triage steps, focusing solely on enabling automatic and on-demand crash dump collection while enforcing safe guardrails like correct permissions and post-collection cleanup reminders.

What should I do after successfully capturing a crash dump from a production app?

After capturing a crash dump, you should disable any temporary dump settings and environment variables to prevent storage overflow, as the Skill enforces collection-only guardrails and does not perform dump analysis.