When Zinniad is killed via SIGTERM/SIGKILL/SIGINT, don't report the error to Sentry.
These signal codes are triggered when somebody terminates the process from outside. It's not a problem in Zinnia, there is nothing we can do about this.
Before:
ERROR Spark crashed via signal SIGTERM
Reporting the problem to Sentry for inspection by the Station team.
Zinnia main loop ended
Starting zinniad with config CliArgs { /* ... */ }
After:
ERROR Spark crashed via signal SIGTERM
Zinnia main loop ended
Starting zinniad with config CliArgs { /* ... */ }
When Zinniad is killed via SIGTERM/SIGKILL/SIGINT, don't report the error to Sentry.
These signal codes are triggered when somebody terminates the process from outside. It's not a problem in Zinnia, there is nothing we can do about this.
Before:
After:
The Sentry issue: