If you wish to send data to more than one destination, such as a second Datadog organization or other internal infrastructure, you can configure the Agent to send data to additional endpoints. To set up the Agent to send different kinds of data to multiple endpoints or API keys, use the following configurations.
You can add the YAML configuration to your datadog.yaml or launch the Agent with the appropriate environment variables.
In datadog.yaml:
additional_endpoints:
"https://app.datadoghq.com":
- apikey2
- apikey3
"https://app.datadoghq.eu":
- apikey4
DD_ADDITIONAL_ENDPOINTS='{\"https://app.datadoghq.com\": [\"apikey2\", \"apikey3\"], \"https://app.datadoghq.eu\": [\"apikey4\"]}'
In datadog.yaml:
apm_config:
[...]
additional_endpoints:
"https://trace.agent.datadoghq.com":
- apikey2
- apikey3
"https://trace.agent.datadoghq.eu":
- apikey4
profiling_additional_endpoints:
"https://trace.agent.datadoghq.com":
- apikey2
- apikey3
"https://trace.agent.datadoghq.eu":
- apikey4
DD_APM_ADDITIONAL_ENDPOINTS='{\"https://trace.agent.datadoghq.com\": [\"apikey2\", \"apikey3\"], \"https://trace.agent.datadoghq.eu\": [\"apikey4\"]}'
DD_APM_PROFILING_ADDITIONAL_ENDPOINTS='{\"https://trace.agent.datadoghq.com\": [\"apikey2\", \"apikey3\"], \"https://trace.agent.datadoghq.eu\": [\"apikey4\"]}'
In datadog.yaml:
process_config:
[...]
additional_endpoints:
"https://mydomain.datadoghq.com":
- apikey2
- apikey3
"https://mydomain.datadoghq.eu":
- apikey4
DD_PROCESS_ADDITIONAL_ENDPOINTS='{\"https://mydomain.datadoghq.com\": [\"apikey2\", \"apikey3\"], \"https://mydomain.datadoghq.eu\": [\"apikey4\"]}'
In datadog.yaml:
orchestrator_explorer:
[...]
orchestrator_additional_endpoints:
"https://mydomain.datadoghq.com":
- apikey2
- apikey3
"https://mydomain.datadoghq.eu":
- apikey4
DD_ORCHESTRATOR_EXPLORER_ORCHESTRATOR_ADDITIONAL_ENDPOINTS='{\"https://mydomain.datadoghq.com\": [\"apikey2\", \"apikey3\"], \"https://mydomain.datadoghq.eu\": [\"apikey4\"]}'
In datadog.yaml:
evp_proxy_config:
[...]
additional_endpoints:
"https://mydomain.datadoghq.com":
- apikey2
- apikey3
"https://mydomain.datadoghq.eu":
- apikey4
DD_EVP_PROXY_CONFIG_ADDITIONAL_ENDPOINTS='{\"https://mydomain.datadoghq.com\": [\"apikey2\", \"apikey3\"], \"https://mydomain.datadoghq.eu\": [\"apikey4\"]}'
In datadog.yaml:
logs_config:
use_http: true
additional_endpoints:
- api_key: "apiKey2"
Host: "agent-http-intake.logs.datadoghq.com"
Port: 443
is_reliable: true
DD_LOGS_CONFIG_USE_HTTP=true
DD_LOGS_CONFIG_ADDITIONAL_ENDPOINTS="[{\"api_key\": \"apiKey2\", \"Host\": \"agent-http-intake.logs.datadoghq.com\", \"Port\": 443, \"is_reliable\": true}]"
In datadog.yaml:
database_monitoring:
samples:
use_http: true
additional_endpoints:
- api_key: "apiKey2"
Host: "mydomain.datadoghq.com"
Port: 443
is_reliable: true
activity:
use_http: true
additional_endpoints:
- api_key: "apiKey2"
Host: "mydomain.datadoghq.com"
Port: 443
is_reliable: true
metrics:
use_http: true
additional_endpoints:
- api_key: "apiKey2"
Host: "mydomain.datadoghq.com"
Port: 443
is_reliable: true
DD_DATABASE_MONITORING_SAMPLES_USE_HTTP=true
DD_DATABASE_MONITORING_SAMPLES_ADDITIONAL_ENDPOINTS="[{\"api_key\": \"apiKey2\", \"Host\": \"mydomain.datadoghq.com\", \"Port\": 443, \"is_reliable\": true}]"
DD_DATABASE_MONITORING_ACTIVITY_USE_HTTP=true
DD_DATABASE_MONITORING_ACTIVITY_ADDITIONAL_ENDPOINTS="[{\"api_key\": \"apiKey2\", \"Host\": \"mydomain.datadoghq.com\", \"Port\": 443, \"is_reliable\": true}]"
DD_DATABASE_MONITORING_METRICS_USE_HTTP=true
DD_DATABASE_MONITORING_METRICS_ADDITIONAL_ENDPOINTS="[{\"api_key\": \"apiKey2\", \"Host\": \"mydomain.datadoghq.com\", \"Port\": 443, \"is_reliable\": true}]"
In datadog.yaml:
network_devices:
metadata:
use_http: true
additional_endpoints:
- api_key: "apiKey2"
Host: "mydomain.datadoghq.com"
Port: 443
is_reliable: true
snmp_traps:
forwarder:
use_http: true
additional_endpoints:
- api_key: "apiKey2"
Host: "mydomain.datadoghq.com"
Port: 443
is_reliable: true
netflow:
forwarder:
use_http: true
additional_endpoints:
- api_key: "apiKey2"
Host: "mydomain.datadoghq.com"
Port: 443
is_reliable: true
DD_NETWORK_DEVICES_METADATA_USE_HTTP=true
DD_NETWORK_DEVICES_METADATA_ADDITIONAL_ENDPOINTS="[{\"api_key\": \"apiKey2\", \"Host\": \"mydomain.datadoghq.com\", \"Port\": 443, \"is_reliable\": true}]"
In datadog.yaml:
compliance_config:
endpoints:
use_http: true
additional_endpoints:
- api_key: "apiKey2"
Host: "mydomain.datadoghq.com"
Port: 443
is_reliable: true
DD_COMPLIANCE_CONFIG_ENDPOINTS_USE_HTTP=true
DD_COMPLIANCE_CONFIG_ENDPOINTS_ADDITIONAL_ENDPOINTS="[{\"api_key\": \"apiKey2\", \"Host\": \"mydomain.datadoghq.com\", \"Port\": 443, \"is_reliable\": true}]"
In datadog.yaml:
runtime_security_config:
endpoints:
use_http: true
additional_endpoints:
- api_key: "apiKey2"
Host: "mydomain.datadoghq.com"
Port: 443
is_reliable: true
DD_RUNTIME_SECURITY_CONFIG_ENDPOINTS_USE_HTTP=true
DD_RUNTIME_SECURITY_CONFIG_ENDPOINTS_ADDITIONAL_ENDPOINTS="[{\"api_key\": \"apiKey2\", \"Host\": \"mydomain.datadoghq.com\", \"Port\": 443, \"is_reliable\": true}]"
For data from these products, when setting up additional endpoints, you must explicitly set use_http to tell the Agent which transport to use. The same transport configuration is shared among all additional endpoints.
The is_reliable setting (First available in Agent 7.34.0) tells the Agent to treat this endpoint with the same priority as the primary endpoint. The primary endpoint is always reliable. This ensures that data is not missed if a destination becomes unavailable.
For example, if you’re sending data to the main endpoint and an additional endpoint with is_reliable: true, and one endpoint becomes unavailable, data continues to flow to the other endpoint. If both endpoints become unavailable, the Agent stops reading and sending data until at least one endpoint recovers. This ensures all data makes it to at least one reliable endpoint.
The is_reliable setting defaults to true in Agent 7.37.0+. Unreliable endpoints only send data if at least one reliable endpoint is available. You may define multiple additional endpoints with a mixed usage of is_reliable values. Datadog recommends that you use the default is_reliable setting.
You can add the YAML configuration to your datadog.yaml or launch the Agent with the appropriate environment variables.
If you’re using the Datadog Agent Helm chart, you must configure these settings with a configmap. In the values.yaml, set useConfigMap: true
and add the relevant settings to customAgentConfig.
# agents.useConfigMap -- Configures a configmap to provide the agent configuration. Use this in combination with the `agents.customAgentConfig` parameter.
useConfigMap: true
# agents.customAgentConfig -- Specify custom contents for the datadog agent config (datadog.yaml)
## ref: https://docs.datadoghq.com/agent/guide/agent-configuration-files/?tab=agentv6
## ref: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/config_template.yaml
## Note the `agents.useConfigMap` needs to be set to `true` for this parameter to be taken into account.
customAgentConfig:
additional_endpoints:
"https://app.datadoghq.com":
- apikey2
- apikey3
"https://app.datadoghq.eu":
- apikey4
logs_config:
use_http: true
additional_endpoints:
- api_key: "apiKey2"
Host: "agent-http-intake.logs.datadoghq.com"
Port: 443
is_reliable: true
If you’re using the Datadog Agent operator, similarly, you can set the agent.customConfig.configData key. All configurable keys are documented in v1 and v2.