From 1608f92cf08119f9aec237c910b200d1317ec696 Mon Sep 17 00:00:00 2001 From: Tigran Najaryan Date: Mon, 29 May 2023 10:54:45 -0400 Subject: [PATCH] Clarify uniqueness of Scope attribute keys We use exact same wording as we already have for LogRecord, Span, etc. --- opentelemetry/proto/common/v1/common.proto | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/opentelemetry/proto/common/v1/common.proto b/opentelemetry/proto/common/v1/common.proto index d233677c1..ff8a21a1f 100644 --- a/opentelemetry/proto/common/v1/common.proto +++ b/opentelemetry/proto/common/v1/common.proto @@ -72,6 +72,10 @@ message InstrumentationScope { // An empty instrumentation scope name means the name is unknown. string name = 1; string version = 2; + + // Additional attributes that describe the scope. [Optional]. + // Attribute keys MUST be unique (it is not allowed to have more than one + // attribute with the same key). repeated KeyValue attributes = 3; uint32 dropped_attributes_count = 4; }