Skip to main content

Kube-proxy collector

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.

Metrics

All metrics have "k8s_kubeproxy." prefix.

MetricScopeDimensionsUnits
kubeproxy_sync_proxy_rulesglobalsync_proxy_rulesevents/s
kubeproxy_sync_proxy_rules_latency_microsecondglobal0.001, 0.002, 0.004, 0.008, 0.016, 0.032, 0.064, 0.128, 0.256, 0.512, 1.024, 2.048, 4.096, 8.192, 16.384, +Infobserves/s
kubeproxy_sync_proxy_rules_latencyglobal0.001, 0.002, 0.004, 0.008, 0.016, 0.032, 0.064, 0.128, 0.256, 0.512, 1.024, 2.048, 4.096, 8.192, 16.384, +Infpercentage
rest_client_requests_by_codeglobala dimension per HTTP status coderequests/s
rest_client_requests_by_methodglobala dimension per HTTP methodrequests/s
http_request_durationglobal0.5, 0.9, 0.99microseconds

Configuration

Edit the go.d/k8s_kubeproxy.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_kubeproxy.conf

Needs only url to kube-proxy metric-address. Here is an example for several instances:

jobs:
- name: local
url: http://127.0.0.1:10249/metrics

- name: remote
url: http://203.0.113.1:10249/metrics

For all available options please see module configuration file.

Troubleshooting

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.

  • Navigate to the plugins.d directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the plugins setting under [directories].

    cd /usr/libexec/netdata/plugins.d/
  • Switch to the netdata user.

    sudo -u netdata -s
  • Run the go.d.plugin to debug the collector:

    ./go.d.plugin -d -m k8s_kubeproxy

Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.