Metadata-Version: 2.0
Name: datadog-kube-proxy
Version: 1.0.0
Summary: The kube_proxy check
Home-page: https://github.com/DataDog/integrations-core
Author: Datadog
Author-email: packages@datadoghq.com
License: New BSD
Keywords: datadog agent kube_proxy check
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: System Administrators
Classifier: Topic :: System :: Monitoring
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.7
Requires-Dist: datadog-checks-base

# Kube_proxy Integration

## Overview

Get metrics from kube_proxy service in real time to:

* Visualize and monitor kube_proxy states
* Be notified about kube_proxy failovers and events.

## Configuration

The integration relies on the `--metrics-bind-address` option of the kube-proxy, by default it's bound to `127.0.0.1:10249`.
You can either start the agent on the host network if the kube-proxy is also on the host network (default) or start the kube-proxy with the `--metrics-bind-address=0.0.0.0:10249`

Edit the `kube_proxy.yaml` file to point to your server and port, set the masters to monitor

⚠️ If you edit the namespace & metrics name, or add any other metric they will be considered as custom

Please contribute to the integration if you want to add a relevant metric.

## Validation

[Run the Agent's `status` subcommand](https://docs.datadoghq.com/agent/faq/agent-status-and-information/) and look for `kube_proxy` under the Checks section:

    Checks
    ======

        kube_proxy
        -----------
          - instance #0 [OK]
          - Collected 39 metrics, 0 events & 1 service checks

## Compatibility

The kube_proxy check is compatible with all major platforms


