Repository navigation
[temporal] make it GA (1.0.0) - #21998
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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. |
Contributor
|
✅ All changelog entries have the correct PR link. |
💚 Build Succeeded
History
|
ishleenk17
approved these changes
Oct 16, 2026
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. |
Contributor
|
Package temporal - 1.0.0 containing this change is available at https://epr.elastic.co/package/temporal/1.0.0/ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
WHAT: Bump
temporal0.4.1 → 1.0.0 to mark the Temporal (OpenTelemetry) integration as GA, and change itsrequires.contentdependency ontemporal_otelfrom 0.2.0 to 1.0.0.WHY: The integration is ready to move out of technical preview. Installing
temporalshould pull in the GAtemporal_otelcontent package.Fleet resolves content dependencies from the package registry, so installing
temporalwith the 1.0.0 pin fails untiltemporal_otel1.0.0 is published.Merge after #21997 is merged and
temporal_otel1.0.0 is available in the registry. Re-run CI at that point.Checklist
changelog.ymlfile.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.
In QA cloud (https://console.qa.cld.elstc.co/home), go to Organization → API keys, generate a new API key and create the project:
In the serverless project, go to Admin and settings → API keys, generate a new key and, in the same shell, install the packages (
temporal_otelfirst):If Fleet rejects the upload with
Cannot upload a package whose name already exists in the package registry, install renamed copies instead (for exampletemporal_otel_testandtemporal_test, withrequires.contentand the dashboard ID prefix updated to match).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 scrapingmetrics.temporal.io:443:metrics-temporal.cloud_metrics.otel-default;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;service_request_throttled_count,resource_exhausted_error_countandservice_error_countwere 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 columnerrors until the first such series is ingested.Screenshots
[Temporal OTel] Cloud Metricson 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
Saturation & Capacity
Errors & Failures
Full dashboard in a single image
🤖 Generated with Claude Code