- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Azure Private Link allows you to send telemetry to Datadog without using the public internet.
Datadog exposes some of its data intake services as Azure Private Link services.
You can configure Azure Private Link to expose a private IP address for each Datadog intake service; this IP address routes traffic to the Datadog backend. You can then configure an Azure Private DNS Zone to override the DNS names corresponding to the products for each endpoint that is consumed.
In the Azure portal, go to Private Link.
On the left navigation menu, select Private endpoints.
Select Create.
On the Create a private endpoint > Basics page, configure the following:
datadog-api-private-link
) and select your Region.Select Next: Resource to continue.
On the Create a private endpoint > Resource page, configure the following:
Select Next: Virtual Network to continue.
On the Create a private endpoint > Virtual Network page, configure the following:
Select Next: Tags to continue.
On the Create a private endpoint > Tags page, you can optionally set tags. Select Next.
On the Review + create page, review your configuration settings. Then, select Create.
After your private endpoint is created, find it in the list. Take note of this endpoint’s Private IP, as this is used in the next section.
In the Azure portal, go to Private DNS zones.
Select Create.
On the Create Private DNS zone > Basics page, configure the following:
Select Review create.
Review your configuration settings. Then, select Create.
After the Private DNS zone is created, select it from the list.
In the panel that opens, select + Record set.
In the Add record set panel, configure the following:
*
.Select OK to finish.
Datadog intake service | Private Link service name | Private DNS name |
---|---|---|
Logs (Agent) | logs-pl-1.9941bd04-f840-4e6d-9449-368592d2f7da.westus2.azure.privatelinkservice | agent-http-intake.logs.us3.datadoghq.com |
Logs (User HTTP Intake) | logs-pl-1.9941bd04-f840-4e6d-9449-368592d2f7da.westus2.azure.privatelinkservice | http-intake.logs.us3.datadoghq.com |
API | api-pl-1.0962d6fc-b0c4-40f5-9f38-4e9b59ea1ba5.westus2.azure.privatelinkservice | api.us3.datadoghq.com |
Metrics | metrics-agent-pl-1.77764c37-633a-4c24-ac9b-0069ce5cd344.westus2.azure.privatelinkservice | metrics.agent.us3.datadoghq.com |
Containers | orchestrator-pl-1.8ca24d19-b403-4c46-8400-14fde6b50565.westus2.azure.privatelinkservice | orchestrator.us3.datadoghq.com |
Process | process-pl-1.972de3e9-3b00-4215-8200-e1bfed7f05bd.westus2.azure.privatelinkservice | process.us3.datadoghq.com |
Profiling | profile-pl-1.3302682b-5bc9-4c76-a80a-0f2659e1ffe7.westus2.azure.privatelinkservice | intake.profile.us3.datadoghq.com |
Traces | trace-edge-pl-1.d668729c-d53a-419c-b208-9d09a21b0d54.westus2.azure.privatelinkservice | trace.agent.us3.datadoghq.com |
Remote Configuration | fleet-pl-1.37765ebe-d056-432f-8d43-fa91393eaa07.westus2.azure.privatelinkservice | config.us3.datadoghq.com |
Database Monitoring | dbm-metrics-pl-1.e391d059-0e8f-4bd3-9f21-708e97a708a9.westus2.azure.privatelinkservice | dbm-metrics-intake.us3.datadoghq.com |