Monitoring Master/etcd Node VMs

Page last updated:

Warning: Pivotal Container Service (PKS) v1.4 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy.
To stay up to date with the latest software and security updates, upgrade to a supported version.

This topic includes information about monitoring the master/etcd node VMs in your Enterprise Pivotal Container Service (Enterprise PKS) deployment. You can monitor Kubernetes cluster health by monitoring and gathering metrics from etcd.

Enterprise PKS co-locates etcd, an open source distributed key value store, on Kubernetes master node VMs. The master node VMs use etcd for service discovery and configuration sharing within the cluster.

For more information about etcd, see the etcd documentation on GitHub.

For more information about configuring master/etcd nodes in the Enterprise PKS tile, see the Plans section of Installing Enterprise PKS for your IaaS:

Monitor etcd

The etcd VM provides monitoring data on its client port. You can enable the /debug endpoint for more verbose logging, but this can decrease cluster performance.

For more information about monitoring etcd, see Monitoring etcd on GitHub.

Gather Metrics from etcd

Each etcd VM exposes metrics on a /metrics endpoint. Connect a metrics system to etcd
 to gather information from the endpoint about cluster health.

You can configure any monitoring system of your choice to gather metrics. For example, the etcd documentation recommends using the open source Prometheus monitoring service. For more information, see the Prometheus documentation.

Troubleshoot etcd

We recommend working with Pivotal or VMware Support to troubleshoot master/etcd node VMs. The monitoring and metrics data you gather from the master/etcd node VMs can help the Support team diagnose and troubleshoot errors.

Please send any feedback you have to