From 4544f21b5f0f3e05409f56501813fb405d58abd4 Mon Sep 17 00:00:00 2001 From: Tigran Najaryan Date: Wed, 12 Apr 2023 13:22:18 -0400 Subject: [PATCH] Clarify "Emit a LogRecord" API We discussed in Log SIG today and the current was unclear since it could be interpreted as API taking LogRecord as an input. This is not the case. The effect of making this API call is to emit a LogRecord to the pipeline, but the API does not take a LogRecord as an input. The input parameters are described in a subsequent paragraph. --- specification/logs/bridge-api.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/specification/logs/bridge-api.md b/specification/logs/bridge-api.md index 2a51cedf69b..37222cc413f 100644 --- a/specification/logs/bridge-api.md +++ b/specification/logs/bridge-api.md @@ -115,9 +115,7 @@ The `Logger` MUST provide functions to: #### Emit a LogRecord -`LogRecord`s encapsulate the fields identified in the [`LogRecord` -data model](data-model.md#log-and-event-record-definition) and are emitted to the processing pipeline using -this API. +The effect of calling this API is to emit a `LogRecord` to the processing pipeline. The API MUST accept the following parameters: