Error tracking for the project you ship

Three things turn a pile of stack traces into something you can act on: grouping makes the same bug one issue, release context helps you investigate a deploy window, and sourcemaps point the trace at your real code.

• Grouping and triage: matching stack frames collapse into a single issue with an event count, and you mark each one new, ignored or resolved.
• Releases: tag every deploy with a version. An issue shows recorded release context, which helps you investigate the deploy window.
• Sourcemap symbolication: upload the sourcemap alongside your build, and a stack trace from a minified bundle resolves back to the original file, line and function name.

Install the SDK and initialize it once, near the top of your entry file. It catches unhandled exceptions and unhandled promise rejections and reports them to your project.

npm install @postdeploy/sdk

Add the Hex package, start PostDeploy under your application supervisor, and put PostDeploy.Plug near the start of your Phoenix pipeline.

{:postdeploy_sdk, "~> 0.2.0"}

Stated plainly, because finding out after you integrate is worse than reading it here. Observe does not ingest logs. It does not collect traces. It does not compute metrics. It does not record session replay. It tracks errors, and only errors.

PostDeploy includes 50,000 error events a month, during the trial and after it for $29 a month. Each pillar has its own allowance. See the full set of limits on the pricing page.