What is Error Tracking?

Error Tracking receives the errors, traces, profiles and sessions that the official Sentry SDKs send, groups errors into issues with source-mapped stack traces, and alerts you when something breaks.

Last updated 18 November 2026View as Markdown

Error Tracking speaks Sentry's protocol. The official Sentry SDKs (JavaScript, Next.js, Node.js, Python, Go and the others) send to it unmodified: only the DSN changes. sentry-cli and the bundler plugins (withSentryConfig) upload source maps to it the same way they upload to Sentry.

When to use it

  • You want to see your app's errors, grouped into issues with readable stack traces, and be told when a new one appears or an old one comes back.
  • You already use a Sentry SDK and want the events kept on Deutsche Cloud instead.
  • You want slow requests, slow database statements, crashing releases and hot functions of the same app in the same place: traces, the Queries tab, release health and profiles come from the same SDK.

Concepts

Term What it is
Project One app or service. It has DSN keys, a retention, an optional rate limit and alert settings.
DSN The address an SDK sends to, https://<public key>@errors.<domain>/<project number>. It can send, never read.
DSN key One credential of a project. A project can have several, each with its own DSN and rate limit; revoke one alone.
Event One error or message as the SDK sent it: exception and stack trace, breadcrumbs, request, tags, contexts.
Issue Events grouped by their fingerprint. It is unresolved, resolved or ignored, and has a short id such as WEB-1A.
Transaction One page load, navigation or server request, with its spans. Transactions of one request share a trace.
Release The version an event came from (release in Sentry.init). Source maps and release health are per release.
Alert rule A condition (new issue, many events, many users, crash-free sessions falling) with filters and mail or webhooks.

See Issues and grouping.

Pricing

What Price
Error events, the first 10 000 a month free
Error events, up to 1 000 000 a month €0.15 per 1 000
Error events, up to 10 000 000 a month €0.08 per 1 000
Error events beyond 10 000 000 a month €0.04 per 1 000
Stored events, attachments, source maps €0.10 per GB-month
Trace spans, the first 1 000 000 a month free, then €2.00 per million
Profile hours, the first 10 a month free, then €0.03 per hour

The tiers count accepted error events per organization and calendar month; refused events and sessions are not billed. Trace spans count every span of an accepted transaction, its own root span included. Profile hours are the length of every transaction profile and continuous-profiling chunk. Spans and profile hours are metered; where they are not charged yet, your usage shows them as "metered, not charged yet", with what they would cost.

Interfaces

  • The Deutsche Cloud Console: Error Tracking in the service menu.
  • The CLI: dcloud errors … (see the CLI Command Reference).
  • The API: /errors/api (see the API Reference).
  • Terraform: dcloud_errors_project.
  • Sentry's own API at https://errors.<domain>/api/0/, for sentry-cli and Sentry API clients (see Use the Sentry API).

Next steps

Did this page help you?