Network Traffic
Traffic is always initiated by the Agent to Datadog. No sessions are ever initiated from Datadog back to the Agent.
Overview
All Agent traffic is sent over SSL. The destination is dependent on the Datadog service and site. To see destinations based on your site, use the SITE
selector on the right.
Destinations
- APM
trace.agent.
- Live Containers & Live Process
process.
- Network Device Monitoring
ndm-intake.
- Orchestrator
orchestrator.
- Profiling
intake.profile.
- Real User Monitoring (RUM)
rum.
session-replay.
- Synthetics private location
- Worker v>=1.5.0
intake.synthetics.
is the only endpoint to configure.
API test results for worker v>0.1.6 intake.synthetics.
Browser test results for worker v>0.2.0 intake-v2.synthetics.
API test results for worker v<0.1.5 api.
- Logs & HIPAA logs
- TCP:
agent-intake.logs.datadoghq.com
HTTP: agent-http-intake.logs.datadoghq.com
Other: See logs endpoints - HIPAA logs legacy
tcp-encrypted-intake.logs.datadoghq.com
lambda-tcp-encrypted-intake.logs.datadoghq.com
gcp-encrypted-intake.logs.datadoghq.com
http-encrypted-intake.logs.datadoghq.com
- Logs & HIPAA logs
- TCP:
agent-intake.logs.datadoghq.eu
HTTP: agent-http-intake.logs.datadoghq.eu
Other: See logs endpoints - HIPAA logs legacy
tcp-encrypted-intake.logs.datadoghq.eu
lambda-tcp-encrypted-intake.logs.datadoghq.eu
gcp-encrypted-intake.logs.datadoghq.eu
http-encrypted-intake.logs.datadoghq.eu
- Logs & HIPAA logs
- HTTP:
agent-http-intake.logs.us3.datadoghq.com
Other: See logs endpoints - HIPAA logs legacy
lambda-tcp-encrypted-intake.logs.us3.datadoghq.com
gcp-encrypted-intake.logs.us3.datadoghq.com
http-encrypted-intake.logs.us3.datadoghq.com
- Logs & HIPAA logs
- HTTP:
agent-http-intake.logs.us5.datadoghq.com
Other: See logs endpoints - HIPAA logs legacy
lambda-tcp-encrypted-intake.logs.us5.datadoghq.com
gcp-encrypted-intake.logs.us5.datadoghq.com
http-encrypted-intake.logs.us5.datadoghq.com
- All other Agent data
<VERSION>-app.agent.
For example, Agent v7.31.0 reports to 7-31-0-app.agent.
. Therefore you must add *.agent.
to your inclusion list in your firewall(s).
Since v6.1.0, the Agent also queries Datadog’s API to provide non-critical functionality (For example, display validity of configured API key):
Agent >= 7.18.0/6.18.0 api.
Agent < 7.18.0/6.18.0 app.
All of these domains are CNAME records pointing to a set of static IP addresses. These addresses can be found at https://ip-ranges.
.
The information is structured as JSON following this schema:
{
"version": 1, // <-- incremented every time this information is changed
"modified": "YYYY-MM-DD-HH-MM-SS", // <-- timestamp of the last modification
"agents": { // <-- the IPs used by the Agent to submit metrics to Datadog
"prefixes_ipv4": [ // <-- list of IPv4 CIDR blocks
"a.b.c.d/x",
...
],
"prefixes_ipv6": [ // <-- list of IPv6 CIDR blocks
...
]
},
"api": {...}, // <-- same for non-critical Agent functionality (querying information from API)
"apm": {...}, // <-- same structure as "agents" but IPs used for the APM Agent data
"logs": {...}, // <-- same for the logs Agent data
"process": {...}, // <-- same for the process Agent data
"orchestrator": {...}, // <-- same for the process Agent data
"synthetics": {...}, // <-- not used for Agent traffic (Datadog source IPs of bots for synthetic tests)
"webhooks": {...} // <-- not used for Agent traffic (Datadog source IPs delivering webhooks)
}
Each section has a dedicated endpoint, for example:
https://ip-ranges./logs.json
for the IPs used to receive logs data over TCP.https://ip-ranges./apm.json
for the IPs used to receive APM data.
Inclusion
Add all of the ip-ranges
to your inclusion list. While only a subset are active at any given moment, there are variations over time within the entire set due to regular network operation and maintenance.
Open ports
All outbound traffic is sent over SSL through TCP / UDP.
Open the following ports to benefit from all the Agent functionalities:
Outbound
Inbound
Used for Agent services communicating with each other locally within the host only.
- 5000/tcp
- Port for the go_expvar server
- 5001/tcp
- Port the IPC API listens to
- 5002/tcp
- Port for the Agent browser GUI
- 8125/udp
- Port for DogStatsD unless
dogstatsd_non_local_traffic
is set to true. This port is available on localhost: 127.0.0.1
, ::1
, fe80::1
. - 8126/tcp
- Port for the APM receiver
Outbound
- 443/tcp
- Port for most Agent data (Metrics, APM, Live Processes/Containers)
- 123/udp
- Port for NTP (more details on the importance of NTP).
See default NTP targets.
Inbound
- 8125/udp
- Port for DogStatsD unless
dogstatsd_non_local_traffic
is set to true. This port is available on localhost: 127.0.0.1
, ::1
, fe80::1
. - 8126/tcp
- Port for the APM Receiver
- 17123/tcp
- Agent forwarder, used to buffer traffic in case of network splits between the Agent and Datadog
- 17124/tcp
- Optional graphite adapter
Using proxies
For a detailed configuration guide on proxy setup, see Agent Proxy Configuration.
Data buffering
If the network becomes unavailable, the Agent stores the metrics in memory.
The maximum memory usage for storing the metrics is defined by the forwarder_retry_queue_payloads_max_size
configuration setting. When this limit is reached, the metrics are dropped.
Agent v7.27.0+ stores the metrics on disk when the memory limit is reached. Enable this capability by setting forwarder_storage_max_size_in_bytes
to a positive value indicating the maximum amount of storage space, in bytes, that the Agent can use to store the metrics on disk.
The metrics are stored in the folder defined by the forwarder_storage_path
setting, which is by default /opt/datadog-agent/run/transactions_to_retry
on Unix systems and C:\ProgramData\Datadog\run\transactions_to_retry
on Windows.
To avoid running out of storage space, the Agent stores the metrics on disk only if the total storage space used is less than 95 percent. This limit is defined by forwarder_storage_max_disk_ratio
setting.
Further Reading
Additional helpful documentation, links, and articles: