# Measuring Temporal Workflow health with OpenTelemetry and Parseable

DevFeed: [Measuring Temporal Workflow health with OpenTelemetry and Parseable](<https://devfeed.tech/articles/measuring-temporal-workflow-health-with-opentelemetry-and-parseable-119223.md>)

Original publisher: [Read original article](<https://temporal.io/blog/measuring-temporal-workflow-health-with-opentelemetry-and-parseable>)

Author: Praveen K B

Published: 2026-11-05T00:00:00Z

Content type: article

Language: en

Sources: [Temporal](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>)

Tags: [alert](<https://devfeed.tech/tags/alert.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [community](<https://devfeed.tech/tags/community.md>), [correlation](<https://devfeed.tech/tags/correlation.md>), [custom](<https://devfeed.tech/tags/custom.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [delay](<https://devfeed.tech/tags/delay.md>), [health](<https://devfeed.tech/tags/health.md>), [onboarding](<https://devfeed.tech/tags/onboarding.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [queue](<https://devfeed.tech/tags/queue.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [temporal](<https://devfeed.tech/tags/temporal.md>), [time](<https://devfeed.tech/tags/time.md>), [worker](<https://devfeed.tech/tags/worker.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

## AI overview

The excerpt describes combining Temporal SDK metrics with Parseable lifecycle records and traces to explain Workflow duration beyond a simple Completed status. In a controlled Temporal Cloud onboarding run, verifyIdentity failed twice and succeeded on its third attempt; Parseable preserved each attempt and the Workflow's domain milestones. Metrics help locate Task Queue waiting and Worker slot pressure, while lifecycle records expose attempt status and duration, and traces show timing and parent-child relationships. The guidance pairs Schedule-to-Start latency with slot availability, host utilization, and poller behavior; it also tracks backlog age, retries, and Workflow Run duration. It recommends low-cardinality labels for dashboards and retaining execution IDs for targeted investigation. Backlog values are approximate, and the validation was not a production benchmark.

## Source excerpt

A customer can complete onboarding and still be unhappy with the experience. A Workflow's Completed status tells you it finished, but not where it spent its time. Onboarding might have taken five minutes or 50 because an Activity waited for a Worker, an identity provider timed out, or a Task Queue received Tasks faster than Workers could process them. We built a simple onboarding Workflow that runs on Workers connected to Temporal Cloud and sent its telemetry to Parseable.