Investigate invalid chunks and chunks migration exception
Description
After rolling out cloud native build logs in gitlab-org/gitlab
project we saw an increase in Ci::BuildTraceChunk::FailedToPersistDataError
exception rate - https://sentry.gitlab.net/gitlab/gitlabcom/issues/1877775:
This seems to correspond with invalid chunks rate too (around 1 chunk per 2 minutes, around 30 chunks per hours):
Proposal
First step to solve this is to extend the exception message to describe the context of the exception better. This has been done in !44007 (merged)
Edited by Grzegorz Bizon