Report runtime environment information in worker heartbeats - #3052
Open
Sushisource wants to merge 2 commits into
Open
Report runtime environment information in worker heartbeats#3052Sushisource wants to merge 2 commits into
Sushisource wants to merge 2 commits into
Conversation
Sushisource
marked this pull request as ready for review
September 1, 2026 21:49
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.
What was changed
Worker heartbeats now include an
EnvironmentInfomessage describing the JVM version, detected hosting environments (Docker, Kubernetes, AWS Lambda/ECS, Google Cloud Run/App Engine, Azure App Service/Functions/Container Apps), and the OS platform (Linux/macOS/Windows version, architecture, and Windows CRT).The information is attached to each worker's heartbeats until the server accepts one, then omitted.
HeartbeatManagertracks pending workers and clears them only after a successfulrecordWorkerHeartbeat.A new experimental
WorkflowClientOptions.Builder#setDisableWorkerEnvironmentInfoturns the reporting off.Why?
Port of Core's temporalio/sdk-rust#1457 so all SDKs report the same analytical information about the environments they run in.
Checklist
Closes N/A
How was this tested:
New unit tests in
WorkerEnvironmentInfoTestcover live detection, hosting-environment env vars, cgroup parsing, and Java version parsing.HeartbeatManagerTestgained cases for retry-until-accepted delivery and for omitting the environment when disabled.No.