Blog · Page 3 of 3
Practical notes on production debugging, SDKs, product analytics, and the decisions behind DebugBundle.
Use the DebugBundle .NET SDK to capture ASP.NET Core requests, worker operations, logs, gRPC, Hangfire, and Azure Functions incidents.
By Owen Far
Capture Java production incidents from Spring Boot, servlet WARs, JAX-RS, WildFly, JBoss, Logback, and javaagent startup paths.
By Owen Far
Capture PHP production errors, Laravel and Symfony exceptions, Monolog events, and browser relay context as structured debug bundles.
By Owen Far
Use the DebugBundle Python SDK to capture Django, Flask, FastAPI, logging, async errors, and browser relay context.
By Owen Far
Capture frontend exceptions, breadcrumbs, network failures, and first-party 5xx responses as structured browser debug bundles.
By Owen Far
How to capture Node.js production errors, request context, logs, probes, and browser relay events as AI-agent-readable debug bundles.
By Owen Far
Designing a debugging tool where AI agents are first-class consumers, not an afterthought bolted onto a human dashboard.
By Owen Far
How DebugBundle's local-first architecture lets you capture, process, and inspect incidents without depending on DebugBundle Cloud.
By Owen Far
The debugging status quo hands AI agents raw logs and expects structured reasoning. DebugBundle was built to close that gap.
By Owen Far
The public-site app now exists as a real Next.js workspace package with shared route groups for marketing, docs, and blog.
By Owen Far
