From db270876d116d273bb0d94b66175ef4ca257a3c7 Mon Sep 17 00:00:00 2001 From: Liudmila Molkova Date: Thu, 2 Jan 2025 17:32:52 -0800 Subject: [PATCH] Fix indentation in OTEP 4333 note section --- oteps/4333-recording-exceptions-on-logs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/oteps/4333-recording-exceptions-on-logs.md b/oteps/4333-recording-exceptions-on-logs.md index 2bb3626b5e3..4bf38272ed0 100644 --- a/oteps/4333-recording-exceptions-on-logs.md +++ b/oteps/4333-recording-exceptions-on-logs.md @@ -66,9 +66,9 @@ this OTEP proposes to record exception stack traces on logs with `Error` or high 2. Instrumentations for incoming requests, message processing, background job execution, or others that wrap user code and usually create local root spans, should record logs for unhandled exceptions with `Error` severity. - > [!NOTE] - > - > Only top-level instrumentations (native and non-native) should record exceptions at `Error` (or higher) severity. + > [!NOTE] + > + > Only top-level instrumentations (native and non-native) should record exceptions at `Error` (or higher) severity. Some runtimes provide global exception handler that can be used to log exceptions. Priority should be given to the instrumentation point where the operation context is available.