- Docker 17.05.0+
- Compose 1.23.0+
Minimum Hardware Requirements:
- You need at least 2400MB RAM
To get started with all the defaults, simply clone the repo and run
./install.sh in your local check-out.
There may need to be modifications to the included example config files (
sentry/sentry.conf.example.py) to accommodate your needs or your environment (such as adding GitHub credentials). If you want to perform these, do them before you run the install script and copy them without the
.example extensions in the name (such as
sentry/sentry.conf.py) before running the
The recommended way to customize your configuration is using the files below, in that order:
.envw/ environment variables
We currently support a very minimal set of environment variables to promote other means of configuration.
If you have any issues or questions, our Community Forum is at your service! Everytime you run the install script, it will generate a log file,
sentry_install_log-<ISO_TIMESTAMP>.txt with the output. Sharing these logs would help people diagnose any issues you might be having.
We continously push the Docker image for each commit made into Sentry, and other services such as Snuba or Symbolicator to our Docker Hub and tag the latest version on master as
:latest. This is also usually what we have on sentry.io and what the install script uses. You can use a custom Sentry image, such as a modified version that you have built on your own, or simply a specific commit hash by setting the
SENTRY_IMAGE environment variable to that image name before running
If you want to use different or specific images for other services, you may create a
docker-compose.overrides.yaml file in the repo and override the
image field for the corresponding services.
We strongly recommend keeping the
latest tags for all, if you are using this repository directly. We also recommend using specific commit tags if you are consuming any of our Docker images in an environment that needs consistent deploys such as a Helm chart.
Sentry comes with a cleanup cron job that prunes events older than
90 days by default. If you want to change that, you can change the
SENTRY_EVENT_RETENTION_DAYS environment variable in
.env or simply override it in your environment. If you do not want the cleanup cron, you can remove the
sentry-cleanup service from the
Securing Sentry with SSL/TLS
You need to be on at least Sentry 9.1.2 to be able to upgrade automatically to the latest version. If you are not, upgrade to 9.1.2 first by checking out the 9.1.2 tag on this repo.
install.sh script is meant to be idempotent and to bring you to the latest version. What this means is you can and should run
install.sh to upgrade to the latest version available. Remember that the output of the script will be stored in a log file,
sentry_install_log-<ISO_TIMESTAMP>.txt, which you may share for diagnosis if anything goes wrong.