- play_arrow Monitoring
- play_arrow Monitor Using Sources and Sinks
-
ON THIS PAGE
Perform a Health Check
Sample Output
root@primary1> request paragon health-check Health status checking... ======================================================= Get node count of Kubernetes cluster. ======================================================= OK There are 4 nodes in the cluster. ... <output snipped> ... ====================================================== Verifying Elasticsearch ====================================================== OK Opensearch test... Checking health status at opensearch-cluster-master.common:9200... Opensearch is healthy (green). OPENSEARCH VERIFICATION PASS ======================================================= Overall cluster status ======================================================= GREEN
Meaning
The command performs multiple health checks on the cluster and returns a detailed list of all the tests run and each of their results. The health-check command checks for multiple parameters such as:
Kubernetes status
Health of each node (CPU, disk space, memory, I/O latency, and so on)
Database health (Postgres, ArangoDB, OpenSearch, Kafka, and so on)
Ceph storage health
The overall health status is categorized as green, amber, or red. A green status indicates a healthy cluster and that all health checks have passed successfully. A red status that indicates that many health checks have failed and implies serious issues in the cluster. An amber status indicates that there maybe certain noncritical issues in the cluster. The status is returned amber in the following instances:
Nodes have taints
Disk usage or memory usage on any node exceeds 80% of available space.
Disk I/O latency on any node exceeds 100000 ms
Rook ceph status shows HEALTH_WARN
Alternatively, you can also use health-check command from the Linux root
shell to get an overall status of the cluster.
