The GCP Cloud Monitoring (formerly Stackdriver) metrics sink delivers metric events to Google Cloud Monitoring (Metrics API). Use it when you want your worker-emitted metrics to appear as Cloud Monitoring time series, so you can build dashboards, alerts, SLOs, and integrate with the broader Cloud Operations suite.

You can authenticate in one of these ways:

If you don’t explicitly set api_key or credentials_path, ADC is the fallback.

The GCP project ID that will own the published metrics (time series are written into this project).

Defines the monitored resource that the time series will be associated with.

This matters because Cloud Monitoring organizes and queries metrics heavily via resource metadata. If your resource labels don’t match the type’s descriptor, writes will fail.



Cloud Monitoring can differentiate metrics by namespace. If a metric event does not already include a namespace, worker will apply:

This prevents collisions when different metric producers share the same metric name.

Controls end-to-end acknowledgements at the sink level.

This is important when you want “don’t ack unless it’s safely delivered” semantics across the pipeline.

Controls how metric events are grouped before sending.

Because the default is effectively “send immediately”, you’ll get low latency but potentially higher request volume. Increasing batch sizes can improve throughput and reduce API calls, at the expense of latency.

Controls buffering when the sink cannot keep up temporarily.

Guidance:

HTTP(S) proxy support (including no_proxy) for outbound requests to Google APIs.

Advanced outbound behavior:

This is where you tune for:

Standard TLS controls:

Keep verification enabled unless you have a controlled internal interception setup and fully understand the risk.