Traces, measurements and sessions

These capabilities extend error monitoring. Availability depends on the backend build, configured processors and SDK profile on your installation. A package release alone does not enable OTLP or native crash processing. Start with the integration guide and ask your operator which services are enabled.

Follow a request through services

The trace explorer shows retained spans as a waterfall. Filter by service, environment and version, open an operation, then follow links to related logs and errors when those records exist.

Missing parents, expired spans and incomplete results stay visible. The presence of a root span does not prove that every service reported. Duration is the observed time range, not the sum of overlapping operations.

Send spans through OpenTelemetry. Native SDK request IDs and W3C headers provide correlation; they do not create stored spans on their own.

Explore measurements and set alerts

Measurements retain gauge, sum and histogram semantics, including units and resource attributes. Filter a series by service, environment or typed attributes before comparing values. These are separate from slow-query and slow-method performance issues.

Alert rules bind one project and one series, with a window from 60 to 86,400 seconds. Use last/min/max for gauges, sum/rate for sums, or count/sum/percentile for histograms. Percentiles are estimates with bucket bounds, not exact raw-event percentiles.

Evaluation uses closed windows every minute, with at least 30 seconds of grace. Missing or incomplete data stays unknown, never zero or automatic recovery. A percentile alert fires only when its entire uncertainty interval crosses the threshold. Recovery updates the rule state; this profile does not send an outward recovery notification.

Compare session health across releases

Session health compares outcomes by release and environment. It is separate from browser session replay.

The crash-free rate uses known completed outcomes. Open and abnormal sessions remain unknown and are excluded from its denominator. With no known outcomes, the rate is unavailable, not 100%.

Individual sessions and request aggregates stay separate. Individual updates with an identity can deduplicate; aggregate retries cannot, because the producer provides no unique delivery identity. A session percentage is not a count of distinct people.

Use a compatible Sentry session producer; enabling a native CloseYourIt SDK does not automatically create session records.

Recover original error locations

Private build artifacts let the error detail show the received stack and reconstructed stack separately:

• JavaScript source maps: resolve minified application functions, files and lines.
• R8/ProGuard mappings: reconstruct Java frames and causes, keeping inline calls and ambiguous alternatives visible.
• Native symbols: resolve received native addresses when the platform, architecture and build identity match the uploaded symbols.

Upload artifacts with the CLI's artifact commands using the exact release and required build identifiers. Artifact management requires artifacts.manage; a public SDK key cannot upload or read private artifacts. Remove source contents from source maps before upload, following the CLI guide. Missing, mismatched or deleted artifacts remain explicit; reconstruction never replaces the original error.

Native crash processing needs a compatible SDK and configured processor. The observed C/C++ runtime is Linux arm64; it does not establish macOS, Windows, iOS or Android NDK support. Raw minidumps can contain process memory and secrets: protect their local storage and use the documented crash route, not a generic durable queue.

Verify your installation

Generate a controlled error or operation in a test application, then check the stored record in the intended project, release and environment. Verify both the original and derived stack when testing symbols. Successful upload, exporter flush or HTTP acceptance alone does not prove that data was stored or reconstructed.

For upload commands, see private build artifacts in the CLI.