Store downstream errors in their own table

What does this MR do and why?

Store downstream errors in their own table

Changelog: other

References

Enabled in production at #563006 (comment 2714861753)

Screenshots or screen recordings

And we're getting data in the table:

gitlabhq_dblab=# select count(*) from p_ci_job_messages;
 count
-------
 13248
(1 row)

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #562953 (closed)

Edited by Marius Bobin

Merge request reports

Loading