Skip to content

Geo: Display secondary replication lag on console (if lag > 0 seconds)

What does this MR do?

This MR introduces the ability to provide a console_message which will be displayed by gitlab-shell (gitlab-shell!287 (merged)) if present.

For EE and Geo setups, we display the DB replication lag on the customers console if the lag > 0 seconds.

What are the relevant issue numbers?

Does this MR meet the acceptance criteria?

Closes #9217 (closed)

Edited by Ash McKenzie

Merge request reports