Kube-proxy is a network proxy that runs on each
node in your cluster, implementing part of the Kubernetes Service.
This module will monitor one or more
kube-proxy instances, depending on your configuration.
It produces the following charts:
- Sync Proxy Rules in
- Sync Proxy Rules Latency in
- Sync Proxy Rules Latency Percentage in
- REST Client HTTP Requests By Status Code in
- REST Client HTTP Requests By Method in
- HTTP Requests Duration in
go.d/k8s_kubeproxy.conf configuration file using
edit-config from the
Netdata config directory, which is typically at
cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/k8s_kubeproxy.conf
kube-proxy metric-address. Here is an example for several instances:
- name: local
- name: remote
For all available options please see module configuration file.
To troubleshoot issues with the
k8s_kubeproxy 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
netdata.conf and look for the setting
plugins directory. Once you're in the plugin's directory, switch
sudo -u netdata -s
You can now run the
go.d.plugin to debug the collector:
./go.d.plugin -d -m k8s_kubeproxy