Geo: Add logs to out-of-date check
What does this MR do and why?
Make it easier to find out when and why a Git fetch of a project repo gets proxied to the primary.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Example log output (prettified for readability, normally it would be on one-line):
{
"severity": "INFO",
"time": "2024-06-25T00:04:19.714Z",
"correlation_id": "01J16BAAD993SWFZD2D5NK03V8",
"class": "Geo::ProjectRepositoryRegistry",
"gitlab_host": "gdk2.test",
"message": "out-of-date",
"replicable_name": "project_repository",
"replicable_id": 7,
"reason": "sync failed"
}
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Perform Git pulls. Sometimes immediately after Git push. You should see up-to-date
and out-of-date
logs in GDK/gitlab/log/geo.log
.
Edited by Michael Kozono