Autodiscovery Auto-Configuration
When the Agent runs as a container, Autodiscovery tries to discover other containers based on default configuration files named auto_conf.yaml. You can find these files in the corresponding conf.d/<INTEGRATION>.d/ folders for the following integrations:
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.
Override auto-configuration
Each auto_conf.yaml file provides a default configuration. To override this, you can add a custom configuration in Kubernetes annotations or Docker Labels.
Kubernetes annotations and Docker Labels take precedence over auto_conf.yaml files, but auto_conf.yaml files take precedence over Autodiscovery configuration set in the Datadog Operator and Helm charts. To use Datadog Operator or Helm to configure Autodiscovery for an integration in the table on this page, you must disable auto-configuration.
Disable auto-configuration
The following examples disable auto-configuration for the Redis and Istio integrations.
In your datadog-agent.yaml, use override.nodeAgent.containers.agent.env to set the DD_IGNORE_AUTOCONF environment variable in the agent container.
apiVersion: datadoghq.com/v2alpha1
kind: DatadogAgent
metadata:
name: datadog
spec:
global:
credentials:
apiKey: <DATADOG_API_KEY>
override:
nodeAgent:
containers:
agent:
env:
- name: DD_IGNORE_AUTOCONF
value: "redisdb istio"
Then, apply the new configuration.
Add datadog.ignoreAutoconfig to your datadog-values.yaml:
datadog:
#List of integration(s) to ignore auto_conf.yaml.
ignoreAutoConfig:
- redisdb
- istio
To disable auto configuration integration(s) with your containerized agent (manual DaemonSet, Docker, ECS), add the DD_IGNORE_AUTOCONF environment variable:
DD_IGNORE_AUTOCONF="redisdb istio"
Further Reading
Additional helpful documentation, links, and articles:
