Loading

Temporal (OpenTelemetry)
Version 0.1.0 (View all)
Managed integration release status
Subscription level
What's this?		 Basic
Developed by
What's this?		 Elastic
Minimum Kibana version(s) 9.5.0
Important - Managed integrations on Elastic Cloud Hosted

You can use this integration as an Elastic Managed integration on Elastic Cloud Hosted deployments running this version or later.

The Temporal (OpenTelemetry) integration v0.1.0 is in technical preview

To use pre-release integrations, go to the Integrations page in Kibana, scroll down, and toggle on the Display beta integrations option.

Collect operational metrics from Temporal Cloud using the Temporal (OpenTelemetry) integration.

This integration scrapes Temporal Cloud OpenMetrics using the Prometheus (OTel) Input Package into the Cloud Metrics data stream (temporal.cloud_metrics.otel): workflow lifecycle, task queues and polling, service latency and errors, namespace limits and throttles, schedules, and replication lag.

Metrics are stored with native OTel schema — no field renaming or custom mapping is applied.

Requirement Details
Temporal Cloud Account with permission to create a Service Account
API key role Service Account with Metrics Read-Only account-level role
Elastic Stack 9.5.0+
Input package prometheus_input_otel (installed automatically as a dependency)

  1. Create a Temporal Cloud API key:

    • Sign in to Temporal Cloud as an Account Owner or Global Admin
    • Go to Settings → Service Accounts → create a Service Account with the Metrics Read-Only role
    • Generate an API key for that Service Account and store it securely

  2. Add the integration in Kibana:

    • Go to Management → Integrations → search for "Temporal (OpenTelemetry)"
    • Click Add Temporal (OpenTelemetry)
    • Fill in:
      • Temporal Cloud Metrics Endpoint: metrics.temporal.io:443 (default)
      • Metrics Path: /v1/metrics (optionally append ?namespaces=<namespace> to filter)
      • Temporal Cloud API Key: paste the Metrics Read-Only API key

  3. Verify data:

    • Discover filter data_stream.dataset: "temporal.cloud_metrics.otel"

Metrics are scraped from:

GET https://metrics.temporal.io/v1/metrics
Authorization: Bearer <API_KEY>

Temporal Cloud aggregates metrics in one-minute windows. Each scrape returns only the most recently completed window — configure Elastic to retain history. Honor scrape timestamps (honor_timestamps: true, enabled by default).

See the Temporal Cloud OpenMetrics documentation and metrics reference for the full catalog.

Category Prefix / examples
Workflow lifecycle temporal_cloud_v1_workflow_success_count, *_failed_count, *_timeout_count, schedule-to-close latency percentiles
Activity lifecycle temporal_cloud_v1_activity_success_count, *_fail_count, activity latency percentiles
Task queues / polling temporal_cloud_v1_approximate_backlog_count, *_poll_success_count, *_poll_timeout_count, *_no_poller_tasks_count
Service / frontend temporal_cloud_v1_service_request_count, *_service_error_count, *_service_latency_p99
Limits / capacity temporal_cloud_v1_action_limit, *_operations_limit, *_poller_limit, *_provisioned_capacity_tru_count
Schedules temporal_cloud_v1_schedule_action_success_count, *_schedule_rate_limited_count
Replication temporal_cloud_v1_replication_lag_p50, *_p95, *_p99

All metrics are stored under the metrics.* field namespace with their original OpenMetrics names.

Changelog
Version Details Minimum Kibana version
0.1.0 Enhancement (View pull request)
Initial release of the Temporal Cloud OTel integration (cloud_metrics data stream).		 9.5.0