DataDog Agent - Traces
version 6.7.0
or aboveDataDog Agent - TCP Logs
version 6.6
or aboveDataDog Agent - HTTP Logs
version 6.13
or aboveadditional_endpoints
within the apm_config
section in your datadog.yaml
file:
apm_config
section in your datadog.yaml
file, add an additional endpoint in the same section. Datadog agent does not support multiple apm_config
sections. YAML
file: /etc/datadog-agent/datadog.yaml
additional_endpoints
within the logs_config
section in your datadog.yaml
file:
datadog.middleware.io
) without the protocol scheme (https://
) datadog-values.yaml
file that you created from step 3 here:
logs_config
or the apm_config
from the below file depending on what data you would like to send to Middleware. datadog-values.yaml
file that will send logs and APM traces to the Middleware platform:
DD_APM_ENABLED
and DD_APM_ADDITION_ENDPOINTS
environment variables are in addition to existing environment variables (e.g. DD_API_KEY
, DD_SITE
, etc.) that may already be defined in your Datadog Agent’s task definition. <Your MW API Key>
with your desired Middleware API key from your Middleware account. DD_API_KEY
, DD_SITE
, etc.) that may already be defined in your Datadog Agent’s task definition. <Your MW API Key>
with your desired Middleware API key from your Middleware account. api_key
(or environment variable DD_API_KEY
) in the /etc/datadog/datadog.yaml
file to something invalid.
api_key
or set it to an empty value. api_key
and site
to invalid values:
apm_config
target is http://datadog.middleware.io
whereas the logs_config
Host
field value is datadog.middleware.io
(without https://
).
apm_config
and logs_config
section in the following configuration file: /etc/datadog/datadog.yaml
datadog-agent
and cluster-agent
pods are operational with a liveness and readiness check for both pods.
datadog-values.yaml
and ensure that the agent
section is at the same level as the datadog
section. The agent
section should NOT be inside the datadog
section.