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 Misses
in
events/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 your agent's 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
Check the module debug output. Run the following command as netdata
user:
./go.d.plugin -d -m k8s_kubelet