It came up that sometimes it can happen that (1) both stdout and stderr produce a lot of output (2) both are captured and included in the sentry body, (3) sentry truncates the body to 512 characters (4) a developer is left in the dark as to why that cron job was considered an error (since the stderr part of the cron job has been truncated away).
I am thinking a small line added by default at the top of each sentry message explaining why the cron job was considered an error would help.
It came up that sometimes it can happen that (1) both stdout and stderr produce a lot of output (2) both are captured and included in the sentry body, (3) sentry truncates the body to 512 characters (4) a developer is left in the dark as to why that cron job was considered an error (since the stderr part of the cron job has been truncated away).
I am thinking a small line added by default at the top of each sentry message explaining why the cron job was considered an error would help.