From 61038e48b149f74912f1e274280c18ffc76cf5fd Mon Sep 17 00:00:00 2001 From: David Ashpole Date: Tue, 2 Aug 2022 19:09:00 +0000 Subject: [PATCH] update wording, update short_name example, and remove prefix --- semantic_conventions/scope/scope.yaml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/semantic_conventions/scope/scope.yaml b/semantic_conventions/scope/scope.yaml index af0e84602ec..1f80f8a16ab 100644 --- a/semantic_conventions/scope/scope.yaml +++ b/semantic_conventions/scope/scope.yaml @@ -1,6 +1,7 @@ groups: - id: scope - prefix: scope + prefix: + type: scope brief: > Scope attributes attributes: @@ -12,5 +13,6 @@ groups: characters, and generally consist of a single word. It is not required to be globally unique, but should be unique enough to make it very unlikely to collide with other short names. An example use is as the [namespace](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#metric-naming-and-namespaces) - (prefix) for OpenMetrics metric names. - examples: ['mylibrary', 'otelhttp'] + (prefix) for OpenMetrics metric names. It is recommended for the short_name to be + related to the name of the scope. + examples: ['mylibrary', 'otelmacaron']