GreptimeDB Cluster Health Check

Verify a GreptimeDB deployment is healthy after a deploy, upgrade, restart, or scale event. This is a positive verification checklist — confirm things work — not a root-cause hunt. If a check fails or a metric looks off, hand off to greptimedb-performance-diagnosis.

Ask up front: GreptimeDB version, deployment mode (standalone or cluster), and how it's deployed (Kubernetes/operator, Docker, binary). Older versions may lack some metrics, and older Grafana dashboards may lack some panels — supplement from the grafana dashboards directory, where each panel's PromQL is the canonical source for the metric names used below.

Running SQL and viewing metrics/logs. To run the SQL in this guide, use any of: the greptimedb-mcp-server execute_sql tool if available; a MySQL or PostgreSQL client; or the built-in GreptimeDB Dashboard. For metrics and logs, use Grafana/self-monitoring (below). GreptimeDB Enterprise users can use the Management Console, which provides SQL, metrics, and logs in one place.