Guide

Quickstart: first event in five minutes

jentry ingests two wire formats: the Sentry protocol (unmodified Sentry SDKs — best for errors, works for everything) and OpenTelemetry OTLP (best if you're already OTel-instrumented). Pick either; both land in the same project, quotas and alerts.

1 · Create a project and get your keys

In jentry: Projects → New project. Every project has a DSN of the form:

https://<publicKey>@jentry.app/<projectId>

The public key in the DSN is safe to ship in clients. The project's secret key (Settings → Client Keys) is server-only — it authenticates source-map, artifact and coverage uploads.

2a · Errors via a Sentry SDK (any language)

import * as Sentry from '@sentry/node';
Sentry.init({ dsn: 'https://<publicKey>@jentry.app/<projectId>' });

// verify:
Sentry.captureException(new Error('hello jentry'));

That's the whole integration — jentry speaks the Sentry envelope protocol, so every official Sentry SDK (browser, Node, Python, PHP, Ruby, Go, mobile…) works unchanged. Migrating from Sentry is a DSN host swap.

2b · Traces via OpenTelemetry

export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="https://jentry.app/api/<projectId>/otlp/v1/traces"
export OTEL_EXPORTER_OTLP_HEADERS="x-jentry-key=<publicKey>"
# http/protobuf (the SDK default) and http/json both work

3 · Verify

Errors: your test exception appears under Issues within seconds, grouped and stack-traced.
Traces: requests appear under Performance; open one to see the span waterfall.
Nothing arriving? Check the DSN/projectId pair, then Settings → Client Keys → key enabled.

Next: wire releases + source maps (readable stack traces), then alerts. Each has its own guide in these docs.

Try jentry free

Hosted error tracking & performance monitoring. Works with your Sentry SDKs — send your first event in minutes.

Get started — free jentry vs Sentry