From 659eb8b38333f50983de7405552693792e58c848 Mon Sep 17 00:00:00 2001 From: Ted Young Date: Tue, 15 Oct 2024 08:23:19 -0700 Subject: [PATCH] remove log instrumentation header --- specification/logs/bridge-api.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/specification/logs/bridge-api.md b/specification/logs/bridge-api.md index 80101451aab..621a53db20c 100644 --- a/specification/logs/bridge-api.md +++ b/specification/logs/bridge-api.md @@ -17,7 +17,6 @@ - [Logger operations](#logger-operations) - [Emit a LogRecord](#emit-a-logrecord) - [Enabled](#enabled) - - [Logs Instrumentation API](#logs-instrumentation-api) - [Emit Event](#emit-event) - [Optional and required parameters](#optional-and-required-parameters) - [Concurrency requirements](#concurrency-requirements) @@ -148,15 +147,10 @@ SHOULD be documented that instrumentation authors needs to call this API each time they [emit a LogRecord](#emit-a-logrecord) to ensure they have the most up-to-date response. -## Logs Instrumentation API +#### Emit Event **Status**: [Development](../document-status.md) -This set of API functions will provide the capabilities needed to emit a -`LogRecord` as is currently provided by [Events API](./event-api.md). - -#### Emit Event - Events are OpenTelemetry's standardized semantic formatting for LogRecords. Beyond the structure provided by the LogRecord data model, it is helpful for logs to have a common format within that structure. When OpenTelemetry