Destinations

The network endpoints accessed by the tracers are dependent on the Datadog site. To see destinations based on your Datadog site, click the DATADOG SITE selector on the right.

The following HTTP endpoints must be accessible from the host where your tests are executed:

• api.
• citestcycle-intake.
• citestcov-intake.
• http-intake.logs.
• instrumentation-telemetry-intake.
• webhook-intake.

Static IP addresses

Some of these domains are CNAME records that point 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
  "<SECTION-NAME>": {                    // <-- the section for a specific service
      "prefixes_ipv4": [                 // <-- list of IPv4 CIDR blocks
        "a.b.c.d/x",
        ...
      ],
      "prefixes_ipv6": [                 // <-- list of IPv6 CIDR blocks
        ...
      ]
  },
  ...
}

Each section has a dedicated endpoint, for example https://ip-ranges./api.json.

Inclusion

Add all of the ip-ranges to your inclusion list. Although only a subset is active at any given moment, variations occur over time within the entire set due to regular network operation and maintenance.

Further Reading

Additional helpful documentation, links, and articles:

Set up Test Optimization for your languageDOCUMENTATION Forwarding Environment Variables for Tests in ContainersDOCUMENTATION Troubleshooting Test OptimizationDOCUMENTATION