git404hub

what is mysql-healthz fr?

kelseyhightower/mysql-healthz — explained in plain English

Analysis updated 2026-07-17 · repo last pushed 2016-06-27

7GoAudience · ops devopsComplexity · 2/5DormantSetup · moderate

tl;dr

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.

vibe map

mindmap
  root((mysql-healthz))
    Inputs
      MySQL connection
      Healthz checks
    Outputs
      OK or error status
      Healthz endpoint
    Use Cases
      Monitor database health
      Trigger auto-restart
      Detect connectivity issues
    Tech Stack
      Go
      MySQL

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Expose a healthz endpoint that reports whether a MySQL database is actually reachable, not just whether the process is running.

VIBE 2

Let an orchestration platform automatically detect database connectivity failures and restart or reroute traffic.

VIBE 3

Catch unresponsive database connections early in a containerized deployment without human intervention.

what's the stack?

GoMySQL

how it stacks up fr

kelseyhightower/mysql-healthzdemomanito/helperemersion/minilustre
Stars777
LanguageGoGoGo
Last pushed2016-06-272023-03-072019-01-07
MaintenanceDormantDormantDormant
Setup difficultymoderateeasymoderate
Complexity2/51/54/5
Audienceops devopsgeneralresearcher

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

README doesn't detail configuration or dependencies, so setup specifics require reading the source.

License is not stated in the available content.

in plain english

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.

prompts (copy fr)

prompt 1
Deploy mysql-healthz alongside my MySQL container so my orchestration platform can check database health via an endpoint.
prompt 2
Explain how mysql-healthz translates a MySQL connection check into a healthz-style OK or error response.
prompt 3
Help me configure my Kubernetes liveness probe to hit the healthz endpoint exposed by mysql-healthz.
prompt 4
Show me how to run mysql-healthz to monitor a MySQL database's reachability in a container environment.

Frequently asked questions

what is mysql-healthz fr?

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.

What language is mysql-healthz written in?

Mainly Go. The stack also includes Go, MySQL.

Is mysql-healthz actively maintained?

Dormant — no commits in 2+ years (last push 2016-06-27).

What license does mysql-healthz use?

License is not stated in the available content.

How hard is mysql-healthz to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is mysql-healthz for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.