Set up metrics for Temporal Cloud
Temporal offers two distinct sources of metrics: Cloud Metrics and SDK Metrics. Each source provides different levels of granularity, filtering options, monitoring-tool integrations, and configuration.
- SDK metrics monitor individual Workers and your code's behavior from the perspective of your application.
- Cloud metrics monitor Temporal Cloud's behavior from the perspective of the Temporal Service.
When used together, Cloud and SDK metrics measure the health and performance of your full Temporal infrastructure, including the Temporal Cloud Service and user-supplied Temporal Workers.
Start with the OpenMetrics Quickstart to create a Service Account, generate an API key, and stream metrics into Datadog, Elastic, Grafana Cloud, New Relic, ClickStack, or self-hosted Prometheus in about 5 minutes.
Cloud Metrics
Cloud metrics for all Namespaces in your account are available from the OpenMetrics endpoint, a Prometheus-compatible scrapable endpoint at metrics.temporal.io.
Use the following rule of thumb when deciding which signal to rely on:
| Question | Primary signal |
|---|---|
| Is Temporal Cloud accepting and serving work normally? | Cloud metrics |
| Are Tasks backing up in a Task Queue? | Cloud metrics plus SDK Schedule-To-Start metrics |
| Are my Workers saturated, under-provisioned, or misconfigured? | SDK metrics |
| Is my application logic, downstream dependency, or Activity behavior unhealthy? | SDK metrics and traces |
For a Worker-focused view of how to combine these signals, see Monitor worker health.
- OpenMetrics overview - Getting started and key concepts
- Metrics integrations - Datadog, Grafana Cloud, New Relic, ClickStack, and more
- API reference - Endpoint specification and advanced configuration
- Metrics reference - Complete catalog of all
temporal_cloud_v1_*metrics
SDK Metrics
SDK metrics are emitted by your Workers and Clients. For setup instructions, see SDK metrics setup.