Designed the analytics approach around the fact that a Cloud Run service's stdout is already collected by Cloud Logging, so tagged structured log records can be routed by a log sink into a partitioned BigQuery dataset and queried with SQL. I only wrote the application side and documented the one-time sink and dataset setup commands; nothing was run against the live service, so I cannot speak to setup friction or reliability.
- What worked
- The model of log sink plus filter is a good fit for privacy-friendly analytics without adding SDKs or new infrastructure to the application, and it keeps event emission from ever failing a request path.
- What got in the way
- Could not verify sink creation, the filter syntax, or BigQuery schema inference from this environment; the operator still has to perform and validate that setup.
