- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Google Cloud Private Service Connect (PSC) allows you to send telemetry to Datadog without using the public internet.
Datadog exposes some of its data intake services in Google Cloud as Private Service Connect published services, as seen in the table of published services.
You can configure a PSC endpoint to expose a private IP address for each Datadog intake service. This IP address routes traffic to the Datadog backend. You can then configure a Google Cloud Private DNS Zone to override the DNS names corresponding to the products for each endpoint that is consumed.
In your Google Cloud console, navigate to Network services > Private Service Connect.
Go to the Endpoints section. Click on Connect endpoint.
datadog-<SERVICE>
. For example: datadog-api
.us-central1
region.Note: Datadog exposes PSC producer endpoints from the us-central1
region. These endpoints support global access, allowing services to connect from any region. However, the forwarding rule must be created in the us-central1
region.
Click Add endpoint. Verify that your status is Accepted. Take note of the IP address, as this is used in the next section.
In your Google Cloud console, navigate to Network services > Cloud DNS.
Click on Create zone.
Next, create an A
record that points to the endpoint IP. On the Zone details page of the zone you created, click on Add record set.
A
.There are two Datadog Intake Services that are subdomains of the (agent.
) domain. Because of this, the Private Hosted Zone is slightly different from other intakes.
Create a Private Zone for (agent.
), as outlined in the Create a DNS Zone section. Then add the three records below.
DNS name | Resource record type | IPv4 address |
---|---|---|
(apex) | A | IP address for your metrics endpoint |
* | A | IP address for your metrics endpoint |
trace | A | IP address for your traces endpoint |
Note: this zone requires a wildcard (*
) record that points to the IP address for your metrics endpoint. This is because Datadog Agents submit telemetry using a versioned endpoint in the form (<version>-app.agent.
).
To verify your configuration, SSH into one of your local nodes and run a dig
command similar to the following:
Verify that that the wildcard is routing to the metrics endpoint
> dig +noall +answer 7-49-0-app.agent.us5.datadoghq.com
The response resembles:
7-49-0-app.agent.us5.datadoghq.com. 300 IN A 10.1.0.4
Verify that the trace subdomain is routing to the traces endpoint
> dig +noall +answer trace.agent.us5.datadoghq.com
The response resembles:
trace.agent.us5.datadoghq.com. 300 IN A 10.1.0.9
Ensure that the IP address in the response matches the one associated with your PSC target.
Datadog intake service | PSC target name | Private DNS name |
---|---|---|
Logs (Agent) | projects/datadog-prod-us5/regions/us-central1/serviceAttachments/nlb-logs-agent-intake-psc | agent-http-intake.logs.us5.datadoghq.com |
Logs (User HTTP Intake) | projects/datadog-prod-us5/regions/us-central1/serviceAttachments/nlb-logs-intake-psc | http-intake.logs.us5.datadoghq.com |
API | projects/datadog-prod-us5/regions/us-central1/serviceAttachments/nlb-api-psc | api.us5.datadoghq.com |
Metrics | projects/datadog-prod-us5/regions/us-central1/serviceAttachments/nlb-metrics-agent-psc | agent.us5.datadoghq.com |
Containers | projects/datadog-prod-us5/regions/us-central1/serviceAttachments/nlb-orchestrator-psc | orchestrator.us5.datadoghq.com |
Process | projects/datadog-prod-us5/regions/us-central1/serviceAttachments/nlb-process-psc | process.us5.datadoghq.com |
Profiling | projects/datadog-prod-us5/regions/us-central1/serviceAttachments/nlb-logs-http-profile-psc | intake.profile.us5.datadoghq.com |
Traces | projects/datadog-prod-us5/regions/us-central1/serviceAttachments/nlb-trace-edge-psc | agent.us5.datadoghq.com |
Database Monitoring | projects/datadog-prod-us5/regions/us-central1/serviceAttachments/nlb-dbm-metrics-psc | dbm-metrics-intake.us5.datadoghq.com |
Remote Configuration | projects/datadog-prod-us5/regions/us-central1/serviceAttachments/nlb-fleet-psc | config.us5.datadoghq.com |
Private Service Connect (PSC) allows you to send telemetry to Datadog without using the public internet.
Datadog exposes some of its data intake services in Google Cloud Platform as PSC published services, as seen in the table of published services.
You can configure a PSC endpoint to expose a private IP address for each Datadog intake service. This IP address routes traffic to the Datadog backend. You can then configure a Google Cloud Private DNS Zone to override the DNS names corresponding to the products for each endpoint that is consumed.
In your GCP console, navigate to Network services > Private Service Connect.
Go to the Endpoints section. Click on Connect endpoint.
datadog-<SERVICE>
. For example: datadog-metrics
.europe-west3
region.Note: Datadog exposes PSC producer endpoints from the europe-west3
region. These endpoints support global access, allowing services to connect from any region. However, the forwarding rule must be created in the europe-west3
region.
Click Add endpoint. Verify that your status is Accepted. Take note of the IP address, as this is used in the next section.
In your Google Cloud console, navigate to Network services > Cloud DNS.
Click on Create zone.
Next, create an A
record that points to the endpoint IP. On the Zone details page of the zone you created, click on Add record set.
A
.There are two Datadog Intake Services that are subdomains of the (agent.
) domain. Because of this, the Private Hosted Zone is slightly different from other intakes.
Create a Private Zone for (agent.
), as outlined in the Create a DNS Zone section. Then add the three records below.
DNS name | Resource record type | IPv4 address |
---|---|---|
(apex) | A | IP address for your metrics endpoint |
* | A | IP address for your metrics endpoint |
trace | A | IP address for your traces endpoint |
Note: this zone requires a wildcard (*
) record that points to the IP address for your metrics endpoint. This is because Datadog Agents submit telemetry using a versioned endpoint in the form (<version>-app.agent.
).
To verify your configuration, SSH into one of your local nodes and run a dig
command similar to the following:
Verify that that the wildcard is routing to the metrics endpoint
> dig +noall +answer 7-49-0-app.agent.datadoghq.eu
The response resembles:
7-49-0-app.agent.datadoghq.eu. 300 IN A 10.1.0.4
Verify that the trace subdomain is routing to the traces endpoint
> dig +noall +answer trace.agent.datadoghq.eu
The response resembles:
trace.agent.datadoghq.eu. 300 IN A 10.1.0.9
Ensure that the IP address in the response matches the one associated with your PSC target.
Datadog intake service | PSC target name | Private DNS name |
---|---|---|
Logs (Agent) | projects/datadog-prod/regions/europe-west3/serviceAttachments/nlb-logs-agent-intake-psc | agent-http-intake.logs.datadoghq.eu |
Logs (User HTTP Intake) | projects/datadog-prod/regions/europe-west3/serviceAttachments/nlb-logs-intake-psc | http-intake.logs.datadoghq.eu |
API | projects/datadog-prod/regions/europe-west3/serviceAttachments/nlb-api-psc | api.datadoghq.eu |
Metrics | projects/datadog-prod/regions/europe-west3/serviceAttachments/nlb-metrics-agent-psc | agent.datadoghq.eu |
Containers | projects/datadog-prod/regions/europe-west3/serviceAttachments/nlb-orchestrator-psc | orchestrator.datadoghq.eu |
Process | projects/datadog-prod/regions/europe-west3/serviceAttachments/nlb-process-psc | process.datadoghq.eu |
Profiling | projects/datadog-prod/regions/europe-west3/serviceAttachments/nlb-logs-http-profile-psc | intake.profile.datadoghq.eu |
Traces | projects/datadog-prod/regions/europe-west3/serviceAttachments/nlb-trace-edge-psc | agent.datadoghq.eu |
Database Monitoring | projects/datadog-prod/regions/europe-west3/serviceAttachments/nlb-dbm-metrics-psc | dbm-metrics-intake.datadoghq.eu |
Remote Configuration | projects/datadog-prod/regions/europe-west3/serviceAttachments/nlb-fleet-psc | config.datadoghq.eu |