GitHub Sign in
Health Overview

Health Overview

The health overview gives you a live snapshot of your Tindra instance: database size, data volumes, retention status, and quota usage. It is intended for self-hosting admins and instance owners who want to know whether their instance is healthy before they get a "disk full" surprise.

Access it at Settings > Health.

Tindra health overview

Viewing the health overview requires the manage_projects permission.

Database size

Shows the total size of the Postgres database in MB or GB. Use this to track growth and size your storage accordingly.

Data volumes

For each data type (events, transactions, logs), the health overview shows:

Metric Description
Total count All records currently stored
24h ingestion rate Records received in the last 24 hours
Oldest record age How far back your data goes
Retention expiry Days until the oldest data is purged

Retention expiry is color-coded:

  • Green: more than 30 days of headroom
  • Yellow: 10-30 days
  • Red: under 10 days, or already past retention

If records are showing as red, either data is ingesting faster than expected or your RETENTION_DAYS setting is lower than intended.

Quota gauges

If your instance has limits configured (PROJECT_LIMIT, EVENT_LIMIT, USER_LIMIT), the health overview shows current usage against each limit with a progress bar.

Gauge What it measures
Projects Active projects vs. project limit
Events Events in the current billing period vs. event cap
Users Active users vs. user limit

The event gauge turns orange at 80% usage and red at 95%. For managed instances, this corresponds to the plan's event cap. For self-hosted instances, limits are optional and only shown if configured.

Self-hosting guidance

For a healthy self-hosted instance, watch for:

  • Database growth outpacing disk: the 24h ingestion rate tells you how fast you're filling up
  • Retention set too short: if oldest records are always very recent, data is being purged before you'd want to review it
  • Retention set too long: if database size is growing faster than expected, reduce RETENTION_DAYS

See Configuration for the relevant environment variables.