Error tracking

​

Turn it on

levelrail-cli apps error-tracking enable web

SENTRY_DSN=https://<key>@cp.example.com/api/v1/sentry/1

​

SDK setup

import * as Sentry from '@sentry/node'
Sentry.init({ dsn: process.env.SENTRY_DSN, release: process.env.GIT_SHA })

import os, sentry_sdk
sentry_sdk.init(dsn=os.environ["SENTRY_DSN"], release=os.environ.get("GIT_SHA"))

sentry.Init(sentry.ClientOptions{Dsn: os.Getenv("SENTRY_DSN"), Release: os.Getenv("GIT_SHA")})
defer sentry.Flush(2 * time.Second)

​

How errors are grouped

1. The SDK’s own fingerprint, when it is more than ["{{ default }}"].
2. The exception type plus the innermost in-app stack frame (module or file, and function; line numbers are ignored so a code edit does not split an issue).
3. The message with digits, hex ids and UUIDs collapsed, for events with no exception.

​

CLI

levelrail-cli apps errors list web --status open --since 24h
levelrail-cli apps errors get web <fingerprint>
levelrail-cli apps errors resolve web <fingerprint>
levelrail-cli apps errors ignore web <fingerprint>

​

Retention and limits

• Events are scrubbed of values under keys such as authorization, cookie, password, secret and token before they are stored.
• Each issue keeps its newest 20 events (APP_ERROR_EVENTS_PER_ISSUE), each at most 64 KiB.
• Issues and events age out with the logs retention window (APP_LOGS_RETENTION).
• A request body is capped at 1 MiB after decompression; gzip is accepted.
• Each app may send 600 requests a minute (APP_ERROR_INGEST_PER_MIN). Past that the receiver answers 429 with Retry-After, which SDKs honor.
• Sessions, transactions, attachments and other envelope item types are accepted and ignored.