Skip to content

ssh: record the serverless environment version in tunnel telemetry - #7265

Draft
anton-107 wants to merge 1 commit into
mainfrom
deco-28307-ssh-telemetry-environment-version
Draft

anton-107 wants to merge 1 commit into
mainfrom
deco-28307-ssh-telemetry-environment-version

Conversation

@anton-107

@anton-107 anton-107 commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Changes

Add environment_version to the ssh tunnel telemetry event. It holds the serverless environment version the server job is submitted with: the --environment-version value or the default. It is unset for dedicated clusters and for a custom base environment. The job submit path and the event now read the value from one helper.

The proto field is added in databricks-eng/universe#2938156. Ingestion drops unknown fields, so the two can land in either order.

Why

The tunnel's default is still environment 4. Moving it to 5 is planned once the REPL sandbox port forwarding reaches every region (DECO-28307). The event has no environment field today, so neither opt-in adoption nor the effect of the flip can be measured.

Tests

  • A unit test covers the event mapping (default, explicit, dedicated, base environment).
  • go test ./acceptance -run TestAccept/ssh passes, and the submitted environment_version is unchanged.

This pull request and its description were written by Isaac.

The CLI default is still environment 4, and moving it to 5 is planned
once the driver's sandbox port forwarding reaches every region. The
tunnel event has no environment field today, so neither opt-in adoption
nor the effect of the flip can be measured.

Send the environment version the server job is submitted with. The
submit path and the event now read it from one helper, so the two cannot
drift. Dedicated clusters and custom base environments leave it unset.

The matching proto field lands in universe separately; ingestion drops
the field until then.

Co-authored-by: Isaac <no-reply@databricks.com>
@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

Integration test report

Commit: 14c8e8e

Run: 41083815513

Env ✅​pass 🙈​skip Time
✅​ aws linux-2core-8gb 281 15 5:17
✅​ aws-windows-latest-4core-16gb 283 13 6:16
✅​ azure linux-2core-8gb 280 15 5:25
✅​ azure-windows-latest-4core-16gb 282 13 5:46
✅​ gcp linux-2core-8gb 281 15 5:26
✅​ gcp-windows-latest-4core-16gb 283 13 5:40
Top 6 slowest tests (at least 2 minutes):
duration env testname
6:08 aws-windows-latest-4core-16gb TestAccept
5:39 azure-windows-latest-4core-16gb TestAccept
5:32 gcp-windows-latest-4core-16gb TestAccept
3:56 azure linux-2core-8gb TestAccept
3:45 gcp linux-2core-8gb TestAccept
3:43 aws linux-2core-8gb TestAccept

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants