Error tracking
Contents
Error tracking captures exceptions from across your stack and turns them into issues you can prioritize, assign, and resolve. Because PostHog already knows what's happening in your product, every issue comes with the affected user's session replay, events, and properties attached, so you can see what went wrong instead of trying to reproduce it.
Where you can use it
You triage and resolve issues in the PostHog web app. The other surfaces let you debug and fix issues without leaving your existing tools.
PostHog Web
Monitor, assign, and resolve issues, each with the affected user's replay and events in view.
Monitor issues →PostHog MCP
Pull up issues and stack traces and debug them from any MCP client or AI agent.
Debug over PostHog MCP →PostHog CLI
Upload source maps and debug symbols from your build so stack traces stay readable.
Upload symbols →Where its data comes from
Error tracking runs on the exceptions your app sends to PostHog. SDKs capture them automatically, source maps make the stack traces readable, and releases tie each exception back to the deploy that caused it.
SDKs
Capture exceptions automatically from web, backend, and mobile SDKs across your stack.
Install an SDK →Source maps
Upload source maps and symbol sets so minified stack traces point back to your real code.
Upload source maps →Releases
Tag exceptions with the release and commit that introduced them to spot regressions fast.
Track releases →