Diagnostics SDK
Overview
Drop-in .NET, Node.js and Python packages that turn crashes into pre-categorized, AI-triaged tickets.
Diagnostics SDK overview
TicketMan Diagnostics is a drop-in package that reports crashes and errors from your .NET and Node.js applications to your TicketMan AI suite, where they become grouped, pre-categorized tickets for AI root-cause analysis and, on the Dev Server plan, an agentic fix.
Plug and play: install the package, set two environment variables, done. Without a configured endpoint the SDK is completely inert: a no-op client, no background threads, no disk or network activity, near-zero overhead.
Packages
| Package | Use for |
|---|---|
TicketMan.Diagnostics (NuGet) | Any .NET 10 app: console, worker services, WPF, WinForms. |
TicketMan.Diagnostics.AspNetCore (NuGet) | ASP.NET Core apps. Adds HTTP error capture plus request and user context. |
@ticketman/diagnostics (npm) | Node.js ≥ 20 apps. Zero runtime dependencies; ships Express middleware plus pino and winston log integrations. |
Every SDK implements the same versioned wire contract, including the same cross-language fingerprint — the same defect in a .NET service and a Node service groups into the same incident.
What it captures
By default the SDK reports the exception and stack, a stable fingerprint for
grouping, runtime and environment state, recent log breadcrumbs (ILogger in
.NET; pino or winston in Node.js), and (in ASP.NET Core or Express) the request
URL, method and status. Masking of secrets is always on.
User identity, request bodies and minidumps are strictly opt-in. See What data is collected.
How it fits the loop
The SDK is stage one of the self-healing support loop: it is what turns a crash in your running software into a ticket in TicketMan AI, automatically, with no one having to notice and file it by hand.
Next
- Quick start: install and initialize in minutes.
- What data is collected: complete inventory of all captured fields.
- Configuration: every environment variable.
- Desktop integration: WPF and WinForms.
- Troubleshooting: when reports do not arrive.