Log Viewer
Tindra captures structured log entries from your applications alongside errors and transactions. The log viewer is a live, searchable feed of all log output sent via the Sentry SDK.
Enabling log capture
Log capture requires SDK support for the Sentry logs API. The JavaScript and Node.js SDKs support this. For other languages, check your SDK's changelog for logs or structured logging support.
JavaScript / Node.js
import * as Sentry from '@sentry/browser'; // or @sentry/node
Sentry.init({
dsn: 'https://your-key@your-hostname.tindra.sh/1',
});
// Logs are captured automatically from console.log/warn/error
// Or use the Sentry logger directly:
Sentry.logger.info('User signed in', { userId: user.id });
Sentry.logger.warn('Quota approaching limit', { usage: 0.9 });
Sentry.logger.error('Payment failed', { orderId: order.id });
Viewing logs
Navigate to Logs in the sidebar. The viewer shows:
- Timestamp: when the log entry was received
- Level: trace, debug, info, warning, error, fatal
- Message: the log body
- Environment: the environment tag from the SDK
Click any row to expand it and see full attributes, trace ID, release, and any structured data attached to the entry.
Filtering
| Filter | How to use |
|---|---|
| Level | Show only entries at or above a severity (e.g., warning and above) |
| Environment | Scope to production, staging, etc. |
| Search | Full-text search across log messages |
The viewer auto-refreshes every 5 seconds.
Trace correlation
Log entries that carry a trace ID are linked to their parent transaction. If your SDK is configured with tracing enabled, log entries captured during a traced request will include the trace_id automatically.
Retention
Log entries follow the same retention policy as events, set by RETENTION_DAYS.