Skip to content

[temporal] make it GA (1.0.0) - #21998

Merged
stefans-elastic merged 3 commits into
elastic:mainfrom
stefans-elastic:temporal_ga
Oct 16, 2026
Merged

stefans-elastic merged 3 commits into
elastic:mainfrom
stefans-elastic:temporal_ga

Conversation

@stefans-elastic

@stefans-elastic stefans-elastic commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Proposed commit message

WHAT: Bump temporal 0.4.1 → 1.0.0 to mark the Temporal (OpenTelemetry) integration as GA, and change its requires.content dependency on temporal_otel from 0.2.0 to 1.0.0.

WHY: The integration is ready to move out of technical preview. Installing temporal should pull in the GA temporal_otel content package.

Fleet resolves content dependencies from the package registry, so installing temporal with the 1.0.0 pin fails until temporal_otel 1.0.0 is published.

Merge after #21997 is merged and temporal_otel 1.0.0 is available in the registry. Re-run CI at that point.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.

Related issues

How to test this PR

Agentless can't be tested on a local stack. It needs a QA serverless project created with an override that allows installing custom agentless integrations.

  1. In QA cloud (https://console.qa.cld.elstc.co/home), go to Organization → API keys, generate a new API key and create the project:

    export API_KEY="your-api-key"
    
    curl -XPOST https://console.qa.cld.elstc.co/api/v1/serverless/projects/observability \
      -H "Authorization: ApiKey $API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "name": "my-integration-test-project",
        "region_id": "gcp-us-central1",
        "overrides": {"channel": "testing"}
      }'
    
  2. In the serverless project, go to Admin and settings → API keys, generate a new key and, in the same shell, install the packages (temporal_otel first):

    export ELASTIC_PACKAGE_KIBANA_HOST=<host, visible in the URL>
    export ELASTIC_PACKAGE_ELASTICSEARCH_HOST=<same host with "kb" replaced by "es">
    export ELASTIC_PACKAGE_ELASTICSEARCH_API_KEY=<generated API key>
    (cd packages/temporal_otel && elastic-package install)
    (cd packages/temporal && elastic-package install)
    

    If Fleet rejects the upload with Cannot upload a package whose name already exists in the package registry, install renamed copies instead (for example temporal_otel_test and temporal_test, with requires.content and the dashboard ID prefix updated to match).

  3. Add the Temporal integration in agentless mode with a Temporal Cloud API key that has the Metrics Read-Only role, generate workflow activity in the namespace, and open the [Temporal OTel] Cloud Metrics dashboard.

Testing done

Tested on a QA serverless project with renamed copies of both 1.0.0 packages (temporal_otel_test, temporal_test) and an agentless policy scraping metrics.temporal.io:443:

  • both packages installed; the content package installed its dashboard, 7 alerting rule templates and 3 SLO templates;
  • the agentless agent came online and metrics arrived in metrics-temporal.cloud_metrics.otel-default;
  • load from omes (workflow_with_single_noop_activity) plus a small worker that deliberately fails workflows and activities, times out activities and workflows, and starts workflows on a task queue with no pollers; a batch of workflows was also terminated;
  • all 36 ES|QL panels of the dashboard return data. Temporal Cloud only emits throttling, resource-exhausted and frontend service error series when those conditions occur, so service_request_throttled_count, resource_exhausted_error_count and service_error_count were filled with synthetic documents for that check.

Known limitation (not changed by this PR): the metric fields aren't declared in the package, so they are mapped on first sight. On a namespace where a failure type has never happened (for example no throttling or no timeouts), the ES|QL panels that use that metric show Unknown column errors until the first such series is ingested.

Screenshots

[Temporal OTel] Cloud Metrics on the QA project with both 1.0.0 packages installed, for the steady part of the test load (12-minute window). The throttled requests, resource-exhausted errors and frontend service error panels show synthetic data (see "Testing done").

Overview, Latency & Traffic temporal-otel-1-overview-latency-traffic
Saturation & Capacity temporal-otel-2-saturation-capacity
Errors & Failures temporal-otel-3-errors-failures

Full dashboard in a single image

🤖 Generated with Claude Code

@stefans-elastic stefans-elastic added enhancement New feature or request Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations] Integration:temporal Temporal (OpenTelemetry) labels Oct 14, 2026
@stefans-elastic
stefans-elastic requested a review from a team as a code owner October 14, 2026 11:21
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

✅ All changelog entries have the correct PR link.

@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

💚 Build Succeeded

History

@mergify

mergify Bot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again.

@stefans-elastic
stefans-elastic merged commit 12c4d64 into elastic:main Oct 16, 2026
14 checks passed
@stefans-elastic
stefans-elastic deleted the temporal_ga branch October 16, 2026 07:32
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Package temporal - 1.0.0 containing this change is available at https://epr.elastic.co/package/temporal/1.0.0/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request Integration:temporal Temporal (OpenTelemetry) Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

⌂ 换网址