Other SDKs
Tindra accepts events from any Sentry-compatible SDK. If your language is not in the list below, the full Sentry SDK catalog works without modification.
All supported SDKs
Tindra implements the Sentry envelope protocol. Any SDK that sends events via this protocol will work.
The complete list of official Sentry SDKs is at docs.sentry.io/platforms. Replace the Sentry DSN with your Tindra DSN and everything else stays the same.
Commonly used SDKs not covered in separate guides:
| Language / Platform | Package |
|---|---|
| Rust | sentry (crates.io) |
| Java | sentry (Maven) |
| Kotlin | sentry (Maven) |
| .NET / C# | Sentry (NuGet) |
| Elixir | sentry (Hex) |
| Dart / Flutter | sentry_flutter |
| Swift / iOS | Sentry (SPM) |
| Kotlin / Android | sentry-android |
Configuring any SDK
The only required change is the DSN. Replace https://<key>@sentry.io/<project> with your Tindra DSN:
https://your-key@your-hostname.tindra.sh/1
Find your DSN in your project’s entry in Settings > Projects in your Tindra dashboard.
Features not supported
Some Sentry-specific features do not apply to Tindra:
- Attachments: binary file attachments are not stored
- Session replay: not supported
- Code owners / GitHub integration: not supported
Standard error tracking and performance monitoring work across all SDKs.
Profiling
Profiling is supported. Both wire formats are accepted: transaction-based profiles and continuous profiling chunks. If your SDK can send profiles to Sentry, it can send them to Tindra, and the flame graph shows up on the transaction detail page.
Two caveats. Frames arrive exactly as the SDK sent them, so native platforms that ship raw instruction addresses (iOS, macOS, Android NDK) show addresses rather than function names. And the Sentry Go SDK has no profiler at all, so there is nothing to enable there.
See Profiling for per-SDK setup.
OpenTelemetry
If you are using OpenTelemetry for tracing, the Sentry OTLP endpoint is not supported. Use the Sentry SDK for your language instead. Most Sentry SDKs have an OpenTelemetry integration that bridges OTel spans into the Sentry envelope format.
Application user context
Use your SDK's user-context API to attach a stable id, and clear that context when the user logs out or a reused request or job scope changes ownership. Tindra can then follow that user across captured telemetry. The guide explains identity fallbacks, structured log attributes, and privacy behavior.
Verify project setup
After configuring the SDK, open Check setup for your project in Settings > Projects. Start a fresh check and capture an exception with the displayed tindra_setup tag, then wait for confirmed storage. The Project Setup guide covers generated browser/Node.js snippets, other SDKs, missing data, and optional transaction, profile, and source-map checks.