Area(s)

area:feature-flag

What's missing?

In #3308 error.message was deprecated in feature flag semconv in favor of the domain-specific feature_flag.error.message. The argument was that error.message was not grounded in any specific concept like exception.message and that it caused confusion between error log bodies and error.message attributes.

After talking with @beeme1mr, I propose that in the feature flag semconv we remove use of error.type for the same reasons, and to be consistent with other attributes in the feature flag semconv. I believe the only reason this was not done in #3308 is because error.type is stable, but the feature flag semconv doc is not yet stable so our use of it should still be subject to change.

Describe the solution you'd like

• Remove error.type from model/feature-flags/events.yaml
• Add feature_flag.error.type to model/feature-flags/registry.yaml and model/feature-flags/events.yaml

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}