Where Does Self-Hosted Sentry Store Data?
Sentry event storage volumes and service config paths on Linux for self-hosted error tracking. With backup tips.
Last updated
Sentry splits state across many containers. Postgres keeps projects and users. ClickHouse and Snuba keep event samples. Redis and Kafka buffer ingestion between them. Each persists through its own named volume.
Settings live in config.yml and sentry.conf.py with secrets and mail options. The installer generates them per release. Back up all data volumes with both configs. Events without project metadata are just orphaned rows. Symbolication needs debug files uploaded. Alert rules route issues to chat channels.
Where Sentry stores this, by platform
sentry_postgres (Postgres volume)
Project database volume with users and issue metadata. Dump Postgres for portable backups. Inspect for the host mountpoint.
sentry/config.yml
Main settings with secrets and mail options for the self-hosted stack. Keep a copy off the server. Rebuilding with fresh secrets breaks auth.
Frequently asked questions
what do i back up for a Sentry move
Back up the Postgres, ClickHouse, and Kafka volumes with config.yml and sentry.conf.py. Events flow through Relay into storage. Configs hold secrets. All pieces restore tracking.
where are Sentry volumes on the host
Run docker volume ls to list sentry volumes, then inspect for mountpoints. Names gain a compose prefix like sentry_postgres. The .env file holds release and secrets.
Notice an outdated path? Let us know.