Update-sentry
Jump to navigation
Jump to search
Context: This procedure was written at the time of Sentry 25.10.0, and applies to upgrades performed on the sentry server.
Important Notes
- It is possible to skip version while upgrading, except for Hard-Stops, which you need to install before updating to newer releases, see Sentry docs on hard stops
- Always consult the official Sentry upgrade documentation first.
Pre-upgrade Steps
- Read the release notes and prepare accordingly if some specific actions need to be taken
- Schedule and announce the maintenance window
- Create a maintenance period in Zabbix
- Create a backup and/or snapshot
Upgrade Procedure
- Navigate to `/opt/sentry`
- Run `git fetch --tags`
- Run `git checkout <tag of release you want to update to>`
- Compare `./sentry/config.yml` with `./sentry/config.example.yml`, amend where necessary
- Compare `.sentry/sentry.conf.py` with `./sentry/sentry.conf.example.py`, amend where necessary
- Compare `./.env.delftsolutions` with `./.env` , amend where necessary
- Until we use Podman, Sentry finally lowers the docker-compose version requirement, or until the below steps stop working:
- In file install/dc-detect-version.sh need to modify the dcr variable (short for docker compose run, is boilerplate) command to remove the --pull flag
- In file install/_min-requirements.sh lower the min required version to at most 2.26.1 (or what version is currently installed)
- Run `./install.sh`
- Run `docker compose --env-file .env.delftsolutions up -d`
Post-upgrade Steps
- Go to Issues > Alerts
- Pick an alert rule (the kaboom-api rule is suggested), go to the alert edit page
- On the page, click the button "Send Test Notification", announce the notifications were as expected when they come in
- Once you've made sure everything is running as expected remove the snapshot and maintenance period