GCP Private Service Connect (PSC)

Overview

If you are on Google Cloud, and have a VPC in one of the regions listed below, you can use Google Cloud Private Service Connect (PSC) to send logs, metrics, and traces to Oodle without traversing the public internet.

Current supported GCP regions:

• asia-south1
• us-west2

Send an email to [email protected] if you need support for a different GCP region.

Prerequisite

To configure PSC, you will need the Service Attachment URI for your region:

Region	Service Attachment URI
asia-south1	projects/oodle-psc/regions/asia-south1/serviceAttachments/receiver
us-west2	projects/oodle-psc/regions/us-west2/serviceAttachments/receiver

Setup

Connect PSC Endpoint

1. Open the Connect endpoint page.

2. Fill in the form:

   

   Field	Value
   Target	Published service
   Target service	Service Attachment URI for your region (see table above)
   Endpoint name	A descriptive name, e.g. oodle-asia-south1
   Network / Subnetwork	Your consumer VPC and subnet
   IP address	Reserve or select a private internal IP from the subnet
   Enable global access	Enable if you need cross-region connectivity

3. Click Add endpoint.

4. Verify the status shows Accepted, and note down the IP address. We will use this IP address later to setup private DNS.

   

Setup Private DNS

1. Open the "Create a DNS zone" page.

2. Fill in the form:

   

   Field	Value
   Zone type	Private
   DNS name	collector.oodle.ai
   Options	Private
   Networks	Your VPC

3. Click Create.

4. On the next screen, click Add standard.

   

5. Create an A record for *.collector.oodle.ai pointing to the PSC endpoint IP address.

   

Ingestion endpoints

A single PSC endpoint serves logs, metrics, and traces. Every Oodle ingestion hostname is a subdomain of collector.oodle.ai, so the wildcard A record for *.collector.oodle.ai created above routes all three signals through the same endpoint. There is nothing signal-specific to configure on the PSC side.

Point your agents and SDKs at the usual Oodle ingestion URLs. Inside your VPC they now resolve to the PSC endpoint instead of the public internet:

Signal	Endpoint host	Example URL
Logs	<instance>-logs.collector.oodle.ai	https://<instance>-logs.collector.oodle.ai/ingest/v1/logs
Metrics (Prometheus)	<instance>.collector.oodle.ai	https://<instance>.collector.oodle.ai/v1/prometheus/<instance>/write
Standard OTLP	<instance>-otlp.collector.oodle.ai	https://<instance>-otlp.collector.oodle.ai/v1/metrics, /v1/traces, /v1/logs

Replace <instance> with your Oodle instance id. For the full list of endpoints and agent configuration per signal, see the logs, metrics, and traces integration guides. The URLs are identical to the public ones; private DNS is what keeps the traffic on PSC.

Conclusion

With this setup, all the GCP resources that are exposed to the private DNS will send logs, metrics, and traces to Oodle via the PSC and not over the public internet.