Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Info
titleCasablanca

This functionality was introduced in the Casablanca release. (PreviouslyIn 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.

Checking the health of a site

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

Code Block
themeRDark
titlesdnc.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 utilizes kubectl to remotely access the PROM pod in order to run the sdnc.monitor script that performs the health checks.

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

Code Block
themeRDark
titlepromoverride.py
root@dev-prom-6485f566fb-hdhzs:/path/to/scripts# ./sdnc.monitor
healthy
root@dev-prom-6485f566fb-hdhzs:/path/to/scripts#


The use of consul checks