- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
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.
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
.
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.