From 38e4c981655481a7d2df4a13c4a838b998b39422 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Tue, 10 Dec 2024 13:42:04 +0100 Subject: [PATCH] Update 4290-logger-enabled.md --- oteps/logs/4290-logger-enabled.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/oteps/logs/4290-logger-enabled.md b/oteps/logs/4290-logger-enabled.md index eb2a428a7a4..d3172c2fdf2 100644 --- a/oteps/logs/4290-logger-enabled.md +++ b/oteps/logs/4290-logger-enabled.md @@ -8,7 +8,7 @@ The consumers of OpenTelemetry clients want to: 2. Avoid performing computationally expensive operations and exporting when emitting a log or event record is unencessary. 3. Control a minmium a log serverity level on the SDK level. 4. Filter out log and event records when they are not inside a recording span. -5. Have fine-grained control of logging pipelines without using an OpenTelemetry Collector (e.g. mobile devices, serverless, IoT). +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 destionation like user_events and ETW. 7. Add sampling for logging.