Takuya Tokuda
0502832cbb
* ordering content by weight * fix weight of 'setup' contents * fix weight of 'concepts' contents * fix weight of 'tasks' contents * fix weight of 'tutorials' contents * fix weight of 'reference' contents * Revert "fix weight of 'tasks' contents" This reverts commit 4b6916bed07c92c5f9eed75fb0a7ef0244266623. * Revert "fix weight of 'tutorials' contents" This reverts commit a1f783314337b1eb40017aef47a6bf1453d8c840. * Revert "fix weight of 'setup' contents" This reverts commit 91c8de366587eed25c803f8e7d5a59005adb6025. * Revert "fix weight of 'reference' contents" This reverts commit cc95605f6a9863f8a4ffb636178c69a80d302c3e.
1.9 KiB
title, content_template, weight
| title | content_template | weight |
|---|---|---|
| Controller manager metrics | templates/concept | 100 |
{{% capture overview %}} Controller manager metrics provide important insight into the performance and health of the controller manager.
{{% /capture %}}
{{% capture body %}}
What are controller manager metrics
Controller manager metrics provide important insight into the performance and health of the controller manager. These metrics include common Go language runtime metrics such as go_routine count and controller specific metrics such as etcd request latencies or Cloudprovider (AWS, GCE, OpenStack) API latencies that can be used to gauge the health of a cluster.
Starting from Kubernetes 1.7, detailed Cloudprovider metrics are available for storage operations for GCE, AWS, Vsphere and OpenStack. These metrics can be used to monitor health of persistent volume operations.
For example, for GCE these metrics are called:
cloudprovider_gce_api_request_duration_seconds { request = "instance_list"}
cloudprovider_gce_api_request_duration_seconds { request = "disk_insert"}
cloudprovider_gce_api_request_duration_seconds { request = "disk_delete"}
cloudprovider_gce_api_request_duration_seconds { request = "attach_disk"}
cloudprovider_gce_api_request_duration_seconds { request = "detach_disk"}
cloudprovider_gce_api_request_duration_seconds { request = "list_disk"}
Configuration
In a cluster, controller-manager metrics are available from http://localhost:10252/metrics
from the host where the controller-manager is running.
The metrics are emitted in prometheus format and are human readable.
In a production environment you may want to configure prometheus or some other metrics scraper to periodically gather these metrics and make them available in some kind of time series database.
{{% /capture %}}