From a4257eff7767dc8ce8feebc4b3e9c21a37a570a5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Mon, 16 Dec 2024 13:17:38 +0100 Subject: [PATCH] Update 4290-logger-enabled.md --- oteps/logs/4290-logger-enabled.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/oteps/logs/4290-logger-enabled.md b/oteps/logs/4290-logger-enabled.md index f6e5e49e6cb..7ef39d28608 100644 --- a/oteps/logs/4290-logger-enabled.md +++ b/oteps/logs/4290-logger-enabled.md @@ -13,8 +13,8 @@ The consumers of OpenTelemetry clients want to: 2. Avoid allocating memory to store a log record, avoid performing computationally expensive operations and avoid exporting when emitting a log or event record is unnecessary. 3. Configure a minimum a log severity level on the SDK level. 4. Filter out log and event records when they are inside a span that has been sampled out (span is valid and has sampled flag of `false`). -5. Have **fine-grained** filtering control for logging pipelines without using an OpenTelemetry Collector (e.g. mobile devices, serverless, IoT). -6. **Efficiently** support high-performance logging destination like [Linux user_events](https://docs.kernel.org/trace/user_events.html) and [ETW (Event Tracing for Windows)](https://learn.microsoft.com/windows/win32/etw/about-event-tracing). +5. **Efficiently** support high-performance logging destination like [Linux user_events](https://docs.kernel.org/trace/user_events.html) and [ETW (Event Tracing for Windows)](https://learn.microsoft.com/windows/win32/etw/about-event-tracing). +6. Allow **fine-grained** filtering control for logging pipelines without using an OpenTelemetry Collector (e.g. mobile devices, serverless, IoT). Without a `Logger.Enabled` check in the OpenTelemetry Logs API and corresponding implementations in the SDK,