Health Overview

The overview tab is a live snapshot of your Tindra instance: database size, data volumes, retention, and quota usage. Check it before disk fills up, not after.

Access it at Settings > Overview.

Viewing the overview requires the manage_projects permission.

Database size#

The chip in the header is the total Postgres size. Use it to track growth and size your disk.

Profiles count toward the database size but do not have a row of their own in the table below. If the database is growing faster than errors, traces, and logs explain, profiling is the usual reason. Check PROFILE_STORAGE_LIMIT_MB in Profiling.

Retention days sit next to it. 0 shows as Forever.

Data volumes#

Three rows: Errors, Traces, and Logs.

There is no separate "expires in" column. Retention is the chip in the header. Oldest tells you how far back the data actually goes.

If Oldest is always a few hours, either ingest is huge or RETENTION_DAYS is lower than you think.

Quota gauges#

If your instance has limits configured (PROJECT_LIMIT, EVENT_LIMIT, USER_LIMIT), the Usage section shows current usage against each limit.

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

Log and transaction row caps (LOG_ROW_LIMIT, TX_ROW_LIMIT) are not drawn as gauges. They delete oldest rows when the cap is hit. See Configuration.

Self-hosting guidance#

For a healthy self-hosted instance, watch for:

• Database growth outpacing disk: Last 24h tells you how fast you are filling up
• Retention set too short: if Oldest is always very recent, data is being purged before you would review it
• Retention set too long: if database size is growing faster than expected, reduce RETENTION_DAYS

See Configuration for the relevant environment variables.