Skip to main content


Plugin: go.d.plugin Module: k8s_kubeproxy


This collector monitors Kubeproxy instances.

This collector is supported on all platforms.

This collector supports collecting metrics from multiple instances of this integration, including remote instances.

Default Behavior


This integration doesn't support auto-detection.


The default configuration for this integration does not impose any limits on data collection.

Performance Impact

The default configuration for this integration is not expected to impose a significant performance impact on the system.


Metrics grouped by scope.

The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.

Per Kubeproxy instance

These metrics refer to the entire monitored application.

This scope has no labels.


k8s_kubeproxy.kubeproxy_sync_proxy_rules_latency_microsecond0.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
k8s_kubeproxy.kubeproxy_sync_proxy_rules_latency0.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
k8s_kubeproxy.rest_client_requests_by_codea dimension per HTTP status coderequests/s
k8s_kubeproxy.rest_client_requests_by_methoda dimension per HTTP methodrequests/s
k8s_kubeproxy.http_request_duration0.5, 0.9, 0.99microseconds


There are no alerts configured by default for this integration.



No action required.



The configuration file name for this integration is go.d/k8s_kubeproxy.conf.

You can edit the configuration file using the edit-config script from the Netdata config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/k8s_kubeproxy.conf


The following options can be defined globally: update_every, autodetection_retry.

Config options
update_everyData collection frequency.1no
autodetection_retryRecheck interval in seconds. Zero means no recheck will be scheduled.0no
urlServer URL.
timeoutHTTP request timeout.1no
usernameUsername for basic HTTP
passwordPassword for basic HTTP
proxy_usernameUsername for proxy basic HTTP
proxy_passwordPassword for proxy basic HTTP
methodHTTP request method.GETno
bodyHTTP request
headersHTTP request
not_follow_redirectsRedirect handling policy. Controls whether the client follows redirects.nono
tls_skip_verifyServer certificate chain and hostname validation policy. Controls whether the client performs this check.nono
tls_caCertification authority that the client uses when verifying the server's
tls_certClient TLS
tls_keyClient TLS



A basic example configuration.

- name: local

HTTPS with self-signed certificate

Do not validate server certificate chain and hostname.

- name: local
tls_skip_verify: yes


Debug Mode

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

Getting Logs

If you're encountering problems with the k8s_kubeproxy collector, follow these steps to retrieve logs and identify potential issues:

  • Run the command specific to your system (systemd, non-systemd, or Docker container).
  • Examine the output for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem.

System with systemd

Use the following command to view logs generated since the last Netdata service restart:

journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep k8s_kubeproxy

System without systemd

Locate the collector log file, typically at /var/log/netdata/collector.log, and use grep to filter for collector's name:

grep k8s_kubeproxy /var/log/netdata/collector.log

Note: This method shows logs from all restarts. Focus on the latest entries for troubleshooting current issues.

Docker Container

If your Netdata runs in a Docker container named "netdata" (replace if different), use this command:

docker logs netdata 2>&1 | grep k8s_kubeproxy

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