From ec4a52a3436d1a624f80164ba4d6e2f677059569 Mon Sep 17 00:00:00 2001 From: Tyler Yahn Date: Tue, 27 Feb 2024 16:23:31 -0800 Subject: [PATCH] [editorial] Remove implementation detail from Logs Bridge API (#3884) --- CHANGELOG.md | 2 ++ specification/logs/bridge-api.md | 3 --- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 71aea8633a2..f40ac8223e3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -20,6 +20,8 @@ release. ### Logs +- Remove implementation detail from Logs Bridge API. + ([#3884](https://github.com/open-telemetry/opentelemetry-specification/pull/3884)) - Clarify that logs attributes are a superset of standard attributes. ([#3852](https://github.com/open-telemetry/opentelemetry-specification/pull/3852)) diff --git a/specification/logs/bridge-api.md b/specification/logs/bridge-api.md index a612f275a8c..610fa4862c7 100644 --- a/specification/logs/bridge-api.md +++ b/specification/logs/bridge-api.md @@ -46,9 +46,6 @@ graph TD `Logger`s can be accessed with a `LoggerProvider`. -In implementations of the API, the `LoggerProvider` is expected to be the stateful -object that holds any configuration. - Normally, the `LoggerProvider` is expected to be accessed from a central place. Thus, the API SHOULD provide a way to set/register and access a global default `LoggerProvider`.