Skip to content

fix(semconv): declare the SDK's failure_reason key - #117

Merged
duynhne merged 1 commit into
mainfrom
feat/semconv-failure-reason
Oct 2, 2026
Merged

duynhne merged 1 commit into
mainfrom
feat/semconv-failure-reason

Conversation

@duynhne

@duynhne duynhne commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

What

Temporal Go SDK 1.49 (order-service#233, checkout-service#95) adds a failure_reason attribute to temporal_activity_execution_failed. Today the value is always ActivityError; later SDK releases will add more values.

The registry did not declare the key. The release audit's conformance row C22 (Weaver registry live-check, ADR-076) therefore failed on local-stack with 153 violations. All of them are missing_attribute: Attribute 'failure_reason' does not exist in the registry, and all are on that one metric.

Change

  • attributes-bare.yaml: declare failure_reason (string, development, example ActivityError).
  • metrics-vendor.yaml: reference it from metric.temporal_activity_execution_failed.

Checks

  • make semconv-check: no after_resolution policy violation.
  • make semconv-generated-check: the generated Go constants and docs are unchanged.
  • make semconv-lockstep: registry upstream v1.41.0 = obsx semconv v1.41.0.

After merge, the G4 release audit reruns from scratch, C22 included.

Temporal Go SDK 1.49 adds a failure_reason attribute to
temporal_activity_execution_failed. The registry did not declare it, so
the local-stack conformance row (C22, Weaver live-check) failed with 153
missing_attribute violations, all on that one metric, once order and
checkout moved to SDK 1.49.

Declare failure_reason as a bare key and reference it from the metric.
The value is ActivityError today; the SDK will add more reasons later.
@sonarqubecloud

sonarqubecloud Bot commented Oct 2, 2026

Copy link
Copy Markdown

@duynhne
duynhne merged commit 08cde01 into main Oct 2, 2026
12 checks passed
@duynhne
duynhne deleted the feat/semconv-failure-reason branch October 2, 2026 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant