Back Home

Overview

ReadinessProbe

In the configuration (StatefulSet) yaml for the service

readinessProbe:
    exec: 
       command: ["/usr/bin/zookeeper-probe.sh", "2182"]
    initialDelaySeconds: 10
    timeoutSeconds: 5

Elastic Monitoring

https://www.elastic.co/blog/elastic-uptime-monitoring-7-5-0-released

Monitoring status of Kubernetes services Kubernetes monitoring is particularly challenging due to the dynamic nature of infrastructure and services running on it. To ensure all these services are available and responding requires flexible configuration options. Prior releases of Heartbeat already supported Kubernetes and Docker auto-discovery. In 7.5, we are enhancing Uptime to include hint-based auto-discovery, which is a particularly great fit for monitoring the health of Kubernetes services.

Hints are metadata you attach to an image or pod using labels in Docker or Kubernetes. Before this release, users had to write rules that define how pods and containers would be monitored. For instance, they could specify that any pod with ‘redis’ in the name would have a TCP check on port 6379. Now users can add special labels to pods and containers to configure them for monitoring via Heartbeat directly from Docker and Kubernetes. As soon as the pod or container starts, Heartbeat will check if it contains any hints and launch the proper config for it.

 
kubernates_monitoring.txt · Last modified: 2019/12/18 01:43 by root
 
RSS - 200 © CrosswireDigitialMedia Ltd