Skip to main content

Appendix D: Observability

This document describes conventions for extracting data from the OpenFeature SDK for use in telemetry signals. It primarily focuses on providing recommendations for mapping well-known fields in OpenFeature to OpenTelemetry feature-flag log records and other semantic conventions.

Evaluations

Flag evaluation telemetry comprises data resolved from the provider resolution (evaluation details and flag metadata) as well as metadata about the provider itself. This is particularly relevant to telemetry-related hooks.

Evaluation Details

The following describes how fields on the evaluation details are mapped to feature flag log records:

Log Record AttributeSource Field or Derived Value from Evaluation DetailsNotes
feature_flag.keyflag keySee: flag key
error.typeerror codeSee: error code
feature_flag.variantvariantSee: variant
feature_flag.evaluation.error.messageerror messageA human-readable error message associated with a failed evaluation. For programmatic purposes, refer to error code.
feature_flag.evaluation.reasonreasonSee: reason
feature_flag.evaluation.value.typeOne of "array", "boolean", "byte_array", "float", "int", "map", "null", "string" or "unknown", representing the type of the evaluation details' value fieldSee: reason

Note

The error.type and feature_flag.evaluation.reason enumerations use a lowercase "snake_case" convention (see OpenTelemetry feature-flag log records). OpenFeature error codes and resolution reasons should be transformed accordingly by integrations which include this data.

Flag Value

The flag value is required if the feature_flag.variant is not set (and optional otherwise), and is defined in a the event body:

Body FieldSource Field from Evaluation DetailsNotes
valuevalueThe type of the value field is undefined.

Flag Metadata

The following describes how keys in flag metadata are mapped to feature flag log records:

Log Record AttributeFlag Metadata KeyNotes
feature_flag.context.idcontextIdThe context identifier returned in the flag metadata uniquely identifies the subject of the flag evaluation. If not available, the targeting key should be used.
feature_flag.set.idflagSetIdA logical identifier for the flag set.
feature_flag.versionversionA version string (format unspecified) for the flag or flag set.

Note

Keys in flag metadata use the "camelCase" casing convention, while the OpenTelemetry standard uses a namespaced "snake_case" convention.

Provider Metadata

Log Record AttributeProvider Metadata FieldNotes
feature_flag.provider_namenameThe name of the provider as defined in the provider metadata, available in the hook context.