When filtering in logs for the pattern:
*Reading started filter_pattern"
I noticed that the correlation_id contains doubled usernames (usually used to differentiate the downloaded files) and the correct case should be only one correlation_id.
What comes from this one is that the download poller health api endpoint (going from this path /monitoring/connection-health-check/) is failing for one and succeeding for the other, and we have alerts setup depending on these endpoints.
When filtering in logs for the pattern:
*Reading started filter_pattern"
I noticed that the correlation_id contains doubled usernames (usually used to differentiate the downloaded files) and the correct case should be only one correlation_id.
What comes from this one is that the download poller health api endpoint (going from this path /monitoring/connection-health-check/) is failing for one and succeeding for the other, and we have alerts setup depending on these endpoints.