Skip to main content

GCP Logging Sink

A GCP Logging Sink is an export rule that tells Cloud Logging to stream log entries that match a chosen filter to an external destination – Cloud Storage, BigQuery, or Pub/Sub. Sinks can be created at the project, folder, organisation, or logging-bucket level and are the primary mechanism for moving logs out of Cloud Logging for long-term retention or further analysis.
Official documentation: https://cloud.google.com/logging/docs/export/configure_export

Supported Methods​

  • GET: Get GCP Logging Sink by "gcp-logging-sink-name"
  • LIST: List all GCP Logging Sink items
  • SEARCH

gcp-logging-bucket​

A sink defined at the bucket scope is attached to a specific logging bucket; the bucket is therefore the parent resource of the sink. Overmind links the sink to the bucket to show where the exported logs originate.

gcp-storage-bucket​

If the sink’s destination is Cloud Storage, the referenced storage bucket appears as a linked resource. This lets you trace where the log files will be written.

gcp-big-query-dataset​

When a sink exports to BigQuery, it points at a particular dataset. Overmind links the sink to that dataset so you can understand which table will receive the streamed logs.

gcp-pub-sub-topic​

For sinks configured to send logs to Pub/Sub, the destination topic is linked. This shows which topic – and therefore which downstream subscribers – will receive the exported log entries.