Tell sysadmin when geo-logcursor isn't running
Problem to solve
- I've accidentally left the service stopped a few times and then later wondered why events aren't syncing.
- Recently, we added a feature to geo-logcursor to stop if it has failed every loop for over X minutes.
It would be helpful to be told geo-logcursor service may not be running on the Admin Area > Geo > Nodes page.
Intended users
Further details
Proposal
-
Detect geo-logcursor inactivity. (E.g. the lease is not taken) -
Add this info to GeoNodeStatus -
Output this info in rake gitlab:geo:check -
Also show an error like geo-logcursor service may not be runningon Admin Area > Geo > Nodes. -
Add documentation and link to it from the errors
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
- Stop all geo-logcursor services on a secondary node
- See the error on Admin Area > Geo > Nodes
- See the error in
rake gitlab:geo:check
What is the type of buyer?
- Premium
- Ultimate
Links / references
Edited by Michael Kozono