Versions Compared

Key

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

...

OOM provides two mechanims to monitor the real-time health of an ONAP deployment: a Consul GUI for a human operator or downstream monitoring systems and Kubernetes liveness probes that enable automatic healing of failed containers.

Consul

OOM deploys a 3 instance Consul server cluster that provides a real-time health monitoring capability for all of the ONAP components.  For each of the ONAP components a Consul health check has been created, here is an example from the AAI model loader:

...

where a GUI much like the following will be found:

consul-health.png


The 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-32
 JIRA story tracks this work.

Liveness

Liveness probes are used by the Kubernetes manager to monitor the real-time health of the containers in an ONAP deployment.  If the liveness probe fails, Kubernetes will kill off the failed container and start a new container to replace it. The liveness probe have same parameters as the readiness probes described in the Deploy section. For example, to monitor the SDNC component has following liveness probe can be found in the SDNC DB deployment specification:


livenessProbe:
  exec:
    command: ["mysqladmin""ping"]
  initialDelaySeconds: 30
  periodSeconds: 10
  timeoutSeconds: 5