Skip to main content

Capture production errors

Install the SDK for your runtime with one ingest key. Errors arrive grouped into issues, with the release, environment and user you attach.

facts checked on

Choose your runtime

JavaScript
@postdeploy/sdk on npm, for Node.js 18 or later and Cloudflare Workers.
Ruby
postdeploy on RubyGems, for Ruby 3.0 or later, Rack and Rails.
Elixir
postdeploy_sdk on Hex, for Elixir, Plug and Phoenix.

Get an ingest key

Tip: Create one source per environment. The key sets the environment, so an event sent as staging with a production key is stored as production.

  1. Step 1. Ask your connected agent to create an Observe source for one environment.

    Prompt text
    Create an Observe source named api for the production environment. Show me the key.
  2. Step 2. Store the key as POSTDEPLOY_API_KEY in your server secrets. It starts with obs_ and PostDeploy shows it once.

What each event carries

Each event carries the exception type, message and stack trace, the release you set, and the environment from the key. It also carries the user, tags and context you attach. Observe groups matching events into one issue.

Verify

Open Observe in the dashboard. The title counts open issues, and the table shows the error with its source and environment, for example "api, production".

Limits

  • SDKs exist for JavaScript, Ruby and Elixir only.
  • Observe records errors. It does not ingest logs, collect traces, or record session replay.

Send your first signal today.

14 days free, no card required. Then $29 a month.

Start your 14-day free trial