From 1041faadbefde59360bed28c9be6e55f20d247e3 Mon Sep 17 00:00:00 2001 From: Luca Belluccini Date: Fri, 12 Jul 2024 16:03:46 +0200 Subject: [PATCH] [DOCS] Clarify error capturing Clarify we collect the exceptions passed to a `logger.error`, not the message of the `logger.error`. --- docs/logs.asciidoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/logs.asciidoc b/docs/logs.asciidoc index 53c5564525..f0abf66468 100644 --- a/docs/logs.asciidoc +++ b/docs/logs.asciidoc @@ -77,6 +77,10 @@ As a result, when an exception is reported to the logger: - An `error.id` is generated and injected into logger MDC for the duration of the logger invocation - Logger output will contain the `error.id` if the log format allows it (plaintext still requires some configuration) +Please note we capture the exception, not the message passed to the `logger.error`. + +To collect the message passed to the `logger.error`, you would need to ingest the logs of the application (see {apm-guide-ref}/log-correlation.html[Log correlation]). + [float] [[log-sending]] === Log sending (experimental)