@kapa.ai is DD agent can be disabled to be injected in containers?

The knowledge sources do not explicitly describe any mechanism in Airbyte to inject a Datadog agent into containers, nor a specific flag to disable such an injection. What they do show is: • Datadog integration is controlled via environment variables like

PUBLISH_METRICS

,

METRIC_CLIENT

,

DD_AGENT_HOST

,

DD_DOGSTATSD_PORT

, and

OTEL_COLLECTOR_ENDPOINT

.[Configuring Airbyte; Config 2.0] • In Kubernetes/Helm manifests and issues,

DD_AGENT_HOST

,

DD_DOGSTATSD_PORT

, and other

DD_*

vars are present but often unset or removed by init containers, which effectively disables Datadog metrics/tracing for those pods.[Helm env vars; Init container unsetting DD vars] From this, the only documented way to “disable” Datadog for Airbyte workloads is: • Do not set

PUBLISH_METRICS=true

. • Leave

METRIC_CLIENT

empty (or not set). • Ensure

DD_AGENT_HOST

/

DD_DOGSTATSD_PORT

are not set (or are explicitly unset by your manifests/init containers). If you are referring to an automatic sidecar/agent injection mechanism (e.g., via a Datadog admission controller), there is no mention of that in the Airbyte docs or issues provided, so I cannot confirm any Airbyte-specific setting to disable such injection. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.