From 81bb7e06ac1068da4ac27fbfce40097f46588d63 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Mon, 16 Dec 2024 16:35:51 +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 a65f376cb1e..aabb6c67f05 100644 --- a/oteps/logs/4290-logger-enabled.md +++ b/oteps/logs/4290-logger-enabled.md @@ -159,7 +159,7 @@ Moreover, both (5) and (6) use cases are coupled to log record processing, therefore it seems more straighforward to extend `LogRecordProcessor`. There was a [proposal](https://github.com/open-telemetry/opentelemetry-specification/issues/4207#issuecomment-2354859647) -to add a seperate `LogRecordFilterer` abstraction. +to add a separate `LogRecordFilterer` abstraction. However, it does not looks well-suited for (5) use case and also would not give a lot flexibility for (6) use case.