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
Remove worker_version label_replace workaround for Temporal Cloud backlog metrics
Temporal Cloud now emits temporal_worker_deployment_name and temporal_worker_build_id
as separate labels, so the label_replace recording rule and adapter name alias are no
longer needed. The adapter queries temporal_cloud_v1_approximate_backlog_count directly.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: internal/demo/README.md
+2-10Lines changed: 2 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -262,14 +262,6 @@ Stop the load generator (`Ctrl-C`) and watch the HPA scale back down as in-fligh
262
262
263
263
`approximate_backlog_count` measures tasks queued in Temporal but not yet started on a worker. Adding it as a second HPA metric means the HPA scales up on *arriving* work even before slots are full — important for bursty traffic.
264
264
265
-
>**Note:** Temporal Cloud emits `temporal_approximate_backlog_count` with a combined
266
-
>`worker_version="<worker-deployment-name>_<build-id>"` label that easily exceeds Kubernetes max label
267
-
> length of 63 characters. The recording rule in`prometheus-stack-values.yaml` uses `label_replace`
268
-
> to extract `temporal_worker_deployment_name` and `temporal_worker_build_id` as separate k8s-compatible
269
-
> labels, producing `temporal_backlog_count_by_version`. The HPA then selects on those labels — the same
270
-
> pair used by Phase 1. Temporal Cloud is in the process of rolling out the new separate labels, so this
271
-
> workaround is required until then.
272
-
273
265
**Step 1 — Create the Temporal Cloud credentials secret.**
274
266
275
267
Create a Temporal Cloud metrics API key (separate from the namespace API key) at Cloud UI → Settings → Observability → Generate API Key. Save it to `certs/metrics-api-key.txt`, then create the secret in the `monitoring` namespace:
You should see a result with `twd_name` and `build_id` labels. If the result is empty, wait15–30sfor the recording rule to evaluate.
293
+
You should see results with `temporal_worker_deployment_name` and `temporal_worker_build_id` labels. If the result is empty, wait10–15sfor the first scrape to complete.
0 commit comments