jentry Docs

Create a project, grab your DSN or OTLP endpoint, and send your first error and trace to jentry in about five minutes.

Set up jentry error tracking, performance and Session Replay in browser JavaScript or React with the Sentry browser SDKs.

Set up jentry in Node.js and Express with @sentry/node: errors, tracing and profiling with an instrument-first import.

Wire @sentry/nextjs to jentry: client + server + edge config, global error page, and source maps for the App Router.

Set up sentry-sdk for Python/Django/Flask against jentry: errors, performance, release health sessions, and bigger local variables.

Send OTLP traces to jentry from any OTel SDK or Collector: endpoint, header, both encodings, and how spans map to APM.

How jentry groups errors into issues, the status lifecycle (resolve, archive, regressions), merge/unmerge, priority, and the search syntax.

Transactions, the span-tree waterfall, automatic N+1/slow-query issues with span evidence, Insights modules and Web Vitals in jentry.

Register releases, upload source maps and commits, get suspect-commit attribution, crash-free session rates and resolve-in-release.

Alert rule types (new issue, frequency, metric threshold, anomaly), conditions, channels (email/Slack/Discord/webhook) and HMAC-signed payloads.

Monitor scheduled jobs with Sentry-compatible check-ins (missed/timeout detection) and HTTP uptime checks with downtime issues.

Capture rrweb session replays from the browser SDK and sampled profiles; how ingestion, storage caps and the players work.

How jentry plans meter events (shed, never billed), rate limiting and spike protection, server-side PII scrubbing and inbound filters.