From 9aad9d2d5d1b780597339411d15dabb86c3708da Mon Sep 17 00:00:00 2001 From: Michael Beemer Date: Tue, 12 Jul 2022 21:26:47 -0400 Subject: [PATCH] Add intro section --- specification/trace/semantic_conventions/feature-flags.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/specification/trace/semantic_conventions/feature-flags.md b/specification/trace/semantic_conventions/feature-flags.md index 7fa490cedaa..d37a4d622ad 100644 --- a/specification/trace/semantic_conventions/feature-flags.md +++ b/specification/trace/semantic_conventions/feature-flags.md @@ -2,9 +2,12 @@ **Status**: [Experimental](../../document-status.md) +This document describes how a feature flag evaluation can be represented as a span in +OpenTelemetry. The span can be used to determine the impact a feature has on a request. + **Span kind:** MUST always be `INTERNAL`. -The **span name** MUST be of the format ` ` provided that +The **span name** SHOULD be of the format ` ` provided that `feature_flag.provider_name` is available. If `feature_flag.provider_name` is not available, the span SHOULD be named `Feature Flag `.