Skip to content

Do not send parsing errors to Sentry as they are not exceptions

Mehmet Emin INAC requested to merge 342973_dont_send_parsing_errors_to_sentry into master

What does this MR do and why?

It is expected to receive a malformed report artifact which blows up the JSON parsing logic so there is no point to send those errors to Sentry as they are not exceptions.

We are already storing the error messages in security_scans records to notify the users about the failure.

We could send those cases as warnings to Sentry but I couldn't find any case we do at GitLab and didn't want to introduce a new convention.

Related to #342973 (closed).

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports