You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Casablanca

This functionality was introduced in the Casablanca release. (In Beijing, Kubernetes dashboard was suggested for monitoring the general health of a site.)

Overview

In order to make proper decisions as to whether one site should be made active over another, the ability for a particular site to process messaging needs to be ascertained.

Manually checking site health

In order to manually check the health of a site, the operator can run the sdnc.monitor script from the Kubernetes master in the site they are concerned with:

sdnc.makeActive
ubuntu@k8s-s2-master:~/oom/kubernetes/sdnc/resources/geo/bin$ ./sdnc.monitor
healthy
ubuntu@k8s-s2-master:~/oom/kubernetes/sdnc/resources/geo/bin$

This version of the script is actually a wrapper that utilizes kubectl to remotely access the PROM pod in order to run the sdnc.monitor script that actually performs the health checks on components in the site.

Alternatively, the sdnc.monitor script available in the PROM pod can be run directly:

sdnc.monitor
root@dev-prom-6485f566fb-hdhzs:/path/to/scripts# ./sdnc.monitor
healthy
root@dev-prom-6485f566fb-hdhzs:/path/to/scripts#

Advanced health reporting

If an operator wishes to see more detail about the health of site, specifically which health checks are passing and which aren't...

sdnc.makeActive
ubuntu@k8s-s2-master:~/oom/kubernetes/sdnc/resources/geo/bin$ ./sdnc.monitor -parameter
output
output
output
output
ubuntu@k8s-s2-master:~/oom/kubernetes/sdnc/resources/geo/bin$

The use of consul in component health checks

TBD


  • No labels