kelseyhightower/mysql-healthz — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2016-06-27
Expose a healthz endpoint that reports whether a MySQL database is actually reachable, not just whether the process is running.
Let an orchestration platform automatically detect database connectivity failures and restart or reroute traffic.
Catch unresponsive database connections early in a containerized deployment without human intervention.
| kelseyhightower/mysql-healthz | demomanito/helper | emersion/minilustre | |
|---|---|---|---|
| Stars | 7 | 7 | 7 |
| Language | Go | Go | Go |
| Last pushed | 2016-06-27 | 2023-03-07 | 2019-01-07 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | moderate | easy | moderate |
| Complexity | 2/5 | 1/5 | 4/5 |
| Audience | ops devops | general | researcher |
Figures from each repo's GitHub metadata at analysis time.
README doesn't detail configuration or dependencies, so setup specifics require reading the source.
mysql-healthz is a small tool that helps your infrastructure monitor whether a MySQL database is actually reachable and working, not just whether the database process is running on the server. It bridges two commonly used systems: the standard MySQL database and Kubernetes-style "healthz" endpoints, which are simple web addresses that automated systems check to see if something is healthy. In many deployment setups, automated orchestration tools constantly check a healthz endpoint to see if everything is functioning as expected. A healthz endpoint typically returns a simple "OK" or an error status code. This tool acts as an adaptor by connecting to your MySQL database and exposing its status through such an endpoint. When the orchestration tool checks that endpoint, the tool runs a quick check on the database and reports back whether the connection is successful. This is primarily useful for teams running applications in automated container environments. For example, if you have a web application that relies on a database, and that database becomes unresponsive, you want your system to automatically detect that failure and potentially restart or reroute traffic. By using this adaptor, your orchestration platform can catch database connectivity issues early and take corrective action without human intervention. The README doesn't go into detail about specific configuration, dependencies, or setup instructions. What is clear from the project's description and its implementation in Go is that it serves a very specific purpose: translating database health into a format that infrastructure monitoring can easily consume. It is a focused, lightweight utility rather than a full-featured monitoring suite.
A lightweight Go tool that checks whether a MySQL database is actually reachable and exposes the result as a healthz endpoint for automated orchestration systems.
Mainly Go. The stack also includes Go, MySQL.
Dormant — no commits in 2+ years (last push 2016-06-27).
License is not stated in the available content.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.