Skip to content
FlagLint

OpenTelemetry

Optional post-migration integration — not generated by FlagLint. FlagLint does not install OpenTelemetry dependencies, register hooks, configure collectors, or emit runtime feature-flag telemetry.

Official references:

Boundary

Section titled “Boundary”

LaunchDarkly can remain the underlying provider through its OpenFeature provider integration. OpenFeature becomes the application-facing evaluation API, and OpenFeature hooks provide a consistent place for application teams to add instrumentation.

After registration, a hook can observe evaluations performed through the configured OpenFeature client within that application boundary.

Current Semantic Convention

Section titled “Current Semantic Convention”

OpenTelemetry feature-flag semantic conventions are currently Development status and may change.

The current convention defines feature-flag evaluation as an event:

feature_flag.evaluation

Current attribute names include:

feature_flag.key
feature_flag.provider.name
feature_flag.result.variant
feature_flag.result.value
feature_flag.result.reason

Teams may correlate evaluation events with traces in their observability system, but should follow the current OpenTelemetry specification when implementing instrumentation.

Privacy Guidance

Section titled “Privacy Guidance”

Prefer an approved variant identifier where available. Avoid exporting sensitive evaluation context or unrestricted flag-result values. Follow your organization’s data-handling controls and the current OpenTelemetry specification.

Feedback

Section titled “Feedback”