From 7d7a75b600ede8eb305376939c749dc95eb53bb2 Mon Sep 17 00:00:00 2001 From: Dan Jaglowski Date: Thu, 21 Nov 2024 10:57:20 -0500 Subject: [PATCH] Add section about instrementation scope --- docs/rfcs/component-universal-telemetry.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/rfcs/component-universal-telemetry.md b/docs/rfcs/component-universal-telemetry.md index a628ad65fd08..1f4e63a70dac 100644 --- a/docs/rfcs/component-universal-telemetry.md +++ b/docs/rfcs/component-universal-telemetry.md @@ -72,6 +72,12 @@ the mechanism. Currently, that package is `service/internal/graph`, but this may ascribed to individual component packages, both because the instrumentation scope is intended to describe the origin of the telemetry, and because no mechanism is presently identified which would allow us to determine the characteristics of a component-specific scope. +### Instrumentation Scope + +All telemetry described in this RFC should include a scope name which corresponds to the package which implements the telemetry. If the +package is internal, then the scope name should be that of the module which contains the package. For example, +`go.opentelemetry.io/service` should be used instead of `go.opentelemetry.io/service/internal/graph`. + ### Auto-Instrumented Metrics There are two straightforward measurements that can be made on any pdata: