Anthias sends error reports to Sentry, and you can turn them off
The web interface, background worker and viewer now report errors to the Anthias maintainers by default, which is how several fixes in this release were found. You can turn the reports off or send them to your own Sentry project instead.
From Anthias 2026.06.3, the web interface, the background worker and the viewer report errors to Sentry. Reporting is on by default, and the reports go to a Sentry project whose address is built into Anthias, so the maintainers can see which boards and builds fail in the field. Several fixes in this release came from those reports.
What a report contains
A report is sent when one of these services hits an error it doesn't handle, or logs a message at error level. Each one carries:
- the error and its stack trace, including the values of the variables in the code where it happened
- recent log lines from the same service
- for an error in the web interface, the request that caused it: its address, its headers, and the form data it carried, with fields named like passwords or tokens removed
- the Anthias version and the build it came from
- the device type, such as
pi4-64orx86, the kernel version and architecture, the board model on boards that have a device tree, and whether the device runs on balena
By default a report from the web interface also includes the client's IP address, the signed-in user, and the cookies and other headers that can identify someone. Set analytics_opt_out to True in anthias.conf, the setting that also turns off the usage telemetry, and those are left out. The reports themselves are still sent.
Errors that fix themselves aren't reported, such as Redis restarting or a browser closing a request early.
Turn it off or send it elsewhere
The SENTRY_DSN environment variable on the anthias-server, anthias-celery and anthias-viewer containers decides where reports go. An empty value turns reporting off. The address (DSN) of your own Sentry project sends the reports there instead.
On a docker-compose install, add SENTRY_DSN= to the environment list of those 3 services in ~/anthias/docker-compose.yml and recreate the containers. The upgrade script writes that file again from docker-compose.yml.tmpl on every upgrade, so add the line again after you upgrade. On balena, set SENTRY_DSN as a device variable in balenaCloud.