Skip to main content

Kubelet monitoring with Netdata

Kubelet is an agent that runs on each node in the cluster. It makes sure that containers are running in a pod.

This module will monitor one or more kubelet instances, depending on your configuration.

Charts#

It produces the following charts:

  • API Server Audit Requests in requests/s
  • API Server Failed Data Encryption Key(DEK) Generation Operations in events/s
  • API Server Latencies Of Data Encryption Key(DEK) Generation Operations in observes/s
  • API Server Latencies Of Data Encryption Key(DEK) Generation Operations Percentage in %
  • API Server Storage Envelope Transformation Cache Missesinevents/s`
  • Number Of Containers Currently Running in containers
  • Number Of Pods Currently Running in pods
  • Bytes Used By The Pod Logs On The Filesystem in bytes
  • Runtime Operations By Type in operations/s
  • Docker Operations By Type in operations/s
  • Docker Operations Errors By Type in operations/s
  • Node Configuration-Related Error in bool
  • PLEG Relisting Interval Summary in microseconds
  • PLEG Relisting Latency Summary in microseconds
  • Token Requests To The Alternate Token Source in requests/s
  • REST Client HTTP Requests By Status Code in requests/s
  • REST Client HTTP Requests By Method in requests/s

Per every plugin:

  • Volume Manager State Of The World in state

Configuration#

Edit the go.d/k8s_kubelet.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/k8s_kubelet.conf

Needs only url to kubelet metric-address. Here is an example for 2 instances:

jobs:
- name: local
url: http://127.0.0.1:10255/metrics
- name: remote
url: http://203.0.113.10:10255/metrics

For all available options please see module configuration file.

Troubleshooting#

To troubleshoot issues with the k8s_kubelet collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

First, navigate to your plugins directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the setting plugins directory. Once you're in the plugin's directory, switch to the netdata user.

cd /usr/libexec/netdata/plugins.d/
sudo -u netdata -s

You can now run the go.d.plugin to debug the collector:

./go.d.plugin -d -m k8s_kubelet

Reach out

If you need help after reading this doc, feel free to create an issue in the netdata/netdata repo or join our community forum to search for an answer. There's a good chance someone else has already found a solution to the same issue.

Documentation

Community

Last updated on