Quick Start

Get your first error event into Tindra in under five minutes.

Prerequisites#

• A Tindra instance (managed or self-hosted. See Self-Hosting)
• A project created in Settings > Projects. Choose Verify setup after creation, or Check setup on an existing project, to copy its DSN and confirm delivery.

Step 1: Install an SDK#

All standard Sentry SDKs work with Tindra. No Tindra-specific package required.

Step 2: Configure the DSN#

Point the SDK at your Tindra instance instead of sentry.io. The DSN format is identical.

Laravel#

composer require sentry/sentry-laravel

In .env:

SENTRY_LARAVEL_DSN=https://your-key@your-hostname.tindra.sh/1

Publish the config:

php artisan vendor:publish --provider="Sentry\Laravel\ServiceProvider"

JavaScript#

npm install @sentry/browser

import * as Sentry from '@sentry/browser';

Sentry.init({
  dsn: 'https://your-key@your-hostname.tindra.sh/1',
});

Node.js#

npm install @sentry/node

import * as Sentry from '@sentry/node';

Sentry.init({
  dsn: 'https://your-key@your-hostname.tindra.sh/1',
});

Python#

pip install sentry-sdk

import sentry_sdk

sentry_sdk.init(
    dsn="https://your-key@your-hostname.tindra.sh/1",
)

Step 3: Send a test event#

On the project's setup page, choose Start setup check and run its generated snippet. Browser JavaScript and Node.js snippets include the check's tindra_setup tag. For another SDK, attach that tag with the displayed check ID to your test event's scope. See Project Setup for the full workflow.

These ordinary smoke tests also send an error, but they will not confirm a tagged setup check on their own:

Laravel#

php artisan sentry:test

JavaScript / Node.js#

Sentry.captureException(new Error('Hello Tindra'));

Python#

sentry_sdk.capture_exception(Exception("Hello Tindra"))

Step 4: Verify#

For a tagged check, wait for Test event received on the setup page and choose View event. Confirmation means the matching event was stored; Queued means storage is still unconfirmed. The issue link can appear shortly afterward while processing finishes.

For an ordinary smoke test, open Issues and find the error. Check project, environment, and time filters if it is not visible. Flush pending SDK events before a short-lived process exits.

Troubleshooting#

Events not appearing?

1. Confirm the DSN is correct and points to your Tindra hostname.
2. For managed instances, check your instance is running (green status in the dashboard).
3. Check that the SDK is not suppressing events in your environment (sample rate, environment filters, etc.).

For delivery diagnostics, expired checks, and optional tracing or profiling checks, see Project Setup. For SDK-specific configuration, see the SDK guides.