Autodiscovery Auto-Configuration

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

When the Agent runs as a container, it tries by default to Autodiscover other containers around it based on default Autodiscovery configuration files named auto_conf.yaml. You can find these files in the corresponding conf.d/<INTEGRATION>.d/ folders for the following integrations:

Auto-Configuration files

The auto_conf.yaml configuration files cover all required parameters to set up a specific integration, with their corresponding Autodiscovery Templates Variables in place to take into account the containerized environment.

Customizing configuration

The auto configuration logic only supports the default configuration for any integration above. If you want to customize your Datadog integration configuration, see the Integrations Templates documentation to learn how to configure your Agent Autodiscovery. Any configuration discovered through Kubernetes Annotations or Docker Labels for a given container takes precedence over the auto_conf.yaml file.

Disabling auto-configuration

To disable the Agent from using the auto_conf.yaml configuration, you can add the DD_IGNORE_AUTOCONF environment variable for the desired integration(s) to disable. The following examples would have the Agent ignore the redisdb.d/auto_conf.yaml and istio.d/auto_conf.yaml file and avoid automatically setting up these integrations.

To disable auto configuration integration(s) with Helm, add datadog.ignoreAutoconfig to your values.yaml:

datadog:
 #List of integration(s) to ignore auto_conf.yaml.
  ignoreAutoConfig:
    - redisdb
    - istio

To disable auto configuration integration(s) with your DaemonSet, add the DD_IGNORE_AUTOCONF variable to your Agent manifest:

DD_IGNORE_AUTOCONF="redisdb istio"

Further Reading