From 1c00b5ab25a92a7338792b9d1dc92350fa46d20f Mon Sep 17 00:00:00 2001 From: Liudmila Molkova Date: Fri, 10 Jan 2025 10:32:19 -0800 Subject: [PATCH] lint --- docs/exceptions/README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/exceptions/README.md b/docs/exceptions/README.md index cd88e566cd..a1dcf2e495 100644 --- a/docs/exceptions/README.md +++ b/docs/exceptions/README.md @@ -21,9 +21,10 @@ Semantic conventions for Exceptions are defined for the following signals: When an instrumented operation fails with an exception, instrumentation SHOULD record this exception as a [span event](exceptions-spans.md) or a [log record](exceptions-logs.md). -Recording exceptions on spans SHOULD be accompanied by +Recording exceptions on spans SHOULD be accompanied by: + - setting span status to `ERROR` -- setting [`error.type`](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/attributes-registry/error.md#error-type) +- setting [`error.type`](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/attributes-registry/error.md#error-type) attribute Refer to the [Recording errors](/docs/general/recording-errors.md) document for additional details on how to record errors across different signals.