You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/edot-cloud-forwarder/gcp.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ The architecture for the {{edot-cf}} GCP is as pictured:
28
28
### Data flow
29
29
30
30
- Ingestion: Logs are sent to a Pub/Sub topic (either directly or using a GCS bucket notification).
31
-
- Processing: A push subscription triggers the Cloud Run service, where an OpenTelemetry collector is running.
31
+
- Processing: A push subscription triggers the Cloud Run service, where an OpenTelemetry Collector is running.
32
32
- Forwarding: The service processes the data and exports it to {{ecloud}} using the {{motlp}}.
33
33
- Failure Handling: If processing or forwarding still fails after retries, the failed messages are routed to a dead-letter topic and archived in a GCS bucket for future analysis.
0 commit comments