INFRASTRUCTURE EVIDENCE
Google Cloud Add GCP infrastructure context to evidence.
GKE, Cloud Run and Cloud SQL metadata explain where production runs in Google Cloud. AutoObserve maps resource relationships onto telemetry identity — alongside Cloud Monitoring and your existing stack.
- Evidence
- Resource metadata · Cloud context
- Source
- GCP Asset Inventory
- Enables
- Infrastructure relationships
- Status
- Preview
Google Cloud
Resource metadata
AutoObserve
Infrastructure context
Investigation
WHY THIS INTEGRATION MATTERS
GCP context connects telemetry to cloud reality.
When checkout-api degrades, project, region and backing Cloud SQL instance matter. GCP infrastructure evidence adds that layer to connected investigations.
Resource relationships
Map services to GKE workloads, Cloud Run services and databases.
Cloud identity
Enrich telemetry with project and resource identifiers.
Infrastructure change
Correlate Cloud Audit Log events with production behaviour.
GKE bridge
Pair GKE cluster metadata with Kubernetes runtime evidence.
EVIDENCE RECEIVED
Resource metadata and cloud context from Google Cloud
GCP Asset Inventory metadata becomes infrastructure evidence — linked to service identity and runtime topology.
- Resource metadata
- Cloud context
Discover
Inventory GKE, Cloud Run and database resources in scope.
Map
Link GCP resources to Kubernetes and telemetry identity.
Correlate
Join infrastructure context with metrics, logs and traces.
Investigate
Start incidents with GCP relationships already resolved.
HOW AUTOOBSERVE USES THIS EVIDENCE
Evidence becomes infrastructure investigation context.
Cloud Monitoring is not replaced — GCP metadata is connected. AutoObserve treats cloud resources as one evidence class in a multi-signal investigation.
Provides
- Resource metadata
- Cloud context
AutoObserve creates
- Infrastructure relationships
- Cloud identity
- Resource topology
- Change correlation
Google Cloud is where it runs. AutoObserve is how you connect it.
CONNECT GCP INFRASTRUCTURE
Ingest GCP metadata alongside telemetry.
Asset Inventory, Audit Log and GKE paths feed the same evidence model — scoped to projects you operate.
Query GCP Asset Inventory for connected resource metadata.
GCP APIs
AutoObserve connector
AutoObserve
QUICK START
Connect Google Cloud infrastructure evidence
Configure service account access and project scope, then verify checkout-api resolves to GCP context.
Configure GCP access
Grant read-only roles for target projects and enabled APIs.
Link GKE runtime
Connect GKE clusters for combined cloud and Kubernetes context.
Verify infrastructure context
Confirm checkout-api resolves to project and backing resources.
WHAT SUCCESS LOOKS LIKE
GCP context resolved. Infrastructure ready.
Success means services map to GCP resources — not merely that service accounts are configured.
Resources discovered
checkout-api backing stores appear in infrastructure context.
Project resolved
Production project appears on service identity.
Cross-signal correlation
GCP metadata aligns with telemetry during incidents.
REAL INCIDENT
Same checkout spike — service identity in focus.
The canonical checkout-api degradation with identity context highlighted — the resource linkage that grounds telemetry in Google Cloud infrastructure.
Metric
14:31:00
Checkout latency +184%
Walk through the evidence chain · 1/6
Evidence step 1 of 6
TROUBLESHOOTING
Common Google Cloud integration failures
Problem
No resources discovered
Likely cause
Service account lacks asset viewer or container viewer roles.
Resolution
Verify IAM roles and enabled APIs for Asset Inventory and GKE.
Verify
checkout-api backing resources appear within one sync window.
Problem
Resources present but not linked to services
Likely cause
GCE/GKE labels do not match telemetry service.name.
Resolution
Align GCP labels with Kubernetes labels and OTel resource attributes.
Verify
Cloud SQL instance links to checkout-api in investigation context.
Problem
Stale resource metadata
Likely cause
Asset export interval too long or project scope too broad.
Resolution
Narrow scope to production projects and reduce sync lag.
Verify
Resource state matches production during incident window.
PRODUCTION INTELLIGENCE
How Google Cloud contributes to production understanding
GCP infrastructure evidence enables resource relationship reasoning inside connected production intelligence.
| Evidence | Enables |
|---|---|
| Resource metadata | Infrastructure relationships |
| Cloud context | Project scope |
| Audit Log events | Infrastructure change correlation |
DESIGN PARTNERS
Validate this evidence source with your production stack.
Design partners connect real evidence sources and validate investigation workflows before GA — with direct engineering access.