You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: source worker.id telemetry from the deployment friendlyId (#78)
* feat(supervisor,cli): source worker.id telemetry from the deployment friendlyId
The runner stamps the OTel worker.id from TRIGGER_DEPLOYMENT_ID, which the
supervisor may set to an opaque token. Have the supervisor also pass the plain
friendlyId in TRIGGER_DEPLOYMENT_FRIENDLY_ID, and have the runner prefer it for
the telemetry worker.id (falling back to TRIGGER_DEPLOYMENT_ID for older
supervisors). The auth header keeps using TRIGGER_DEPLOYMENT_ID unchanged. New
deploys then report a stable deployment id in telemetry with no decode -
including to customers' own external exporters.
Refs TRI-11974
* fix(cli): redact TRIGGER_DEPLOYMENT_ID from managed run debug logs
Deployed task telemetry now reports the deployment identifier (e.g. `deployment_abc123`) in the `worker.id` attribute, instead of an opaque internal value. Upgrade to get the readable identifier in your own OpenTelemetry exporters.
0 commit comments