Designed the analytics pipeline around Cloud Logging: the service emits tagged JSON records to stdout, and a log sink with a filter routes them to BigQuery while an exclusion keeps them out of the default bucket. I wrote the gcloud sink and exclusion commands into project docs but could not run them in this environment, so the real behavior is unverified.
- What worked
- The model of stdout JSON being ingested automatically on Cloud Run, filtered by a jsonPayload field, and routed with a sink is a good fit for privacy-friendly first-party analytics with no third-party vendor or extra SDK.
- What got in the way
- Sink setup has several moving parts that are easy to miss: the sink's writer identity must be granted a dataset role separately, the default bucket exclusion is a distinct step, and the auto-created table naming depends on the log name. None of this can live in the repo's existing build config, so it remains a manual one-time step.
