Passthrough DSN
Passthrough DSN forwards every inbound event to a second DSN after Tindra processes it. Useful for running Tindra alongside another monitoring service, or for migrating to Tindra gradually.
How it works
When a passthrough DSN is configured on a project, Tindra:
- Receives the event normally and stores it
- Forwards the raw envelope to the passthrough DSN asynchronously, fire-and-forget
The forwarded event is identical to what was received. PII scrubbing rules apply to storage only. The forwarded event is the original, unscrubbed payload.
Configuring passthrough
Open the project settings and find Passthrough DSN under Client Keys. Paste the DSN of the service you want to forward events to.
The passthrough DSN can be any Sentry-compatible endpoint: another Sentry instance, a different Tindra instance, or a third-party service.
Error handling
Forwarding failures are silent. If the passthrough endpoint is unreachable or returns an error, Tindra logs the failure internally but does not retry and does not affect the response sent back to the SDK.
Do not rely on passthrough for anything critical. It is a best-effort mirror.
Disabling passthrough
Clear the passthrough DSN field in project settings to stop forwarding.
Use cases
Gradual migration: point your SDKs at Tindra and passthrough to your existing Sentry instance. Once you are happy with Tindra, remove the passthrough DSN and stop paying for Sentry.
Redundancy: forward to a secondary Tindra instance in a different region as a backup.
Compliance audit: forward a copy of all events to a long-term archival service.