Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit c29c8bd

Browse files
committed
rephrase
1 parent 072b719 commit c29c8bd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

apm/apm-spans-traces/apm-errors.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ With Splunk APM error detection, you can isolate specific causes of errors in yo
1414
How Splunk APM detects error spans
1515
=========================================
1616

17-
Each :term:`span` in Splunk APM captures a single operation. Splunk APM considers a span to be an error span if the operation that the span captures results in an error. Splunk APM considers a span to be an error span when any of the following conditions are met:
17+
Each :term:`span` in Splunk APM captures a single operation. Splunk APM considers a span to be an error span if the operation that the span captures results in an error as defined by the following conditions:
1818

1919
* The ``otel.status_code`` field for the span is ``ERROR``. ``otel.status_code`` is set in the Splunk Distribution of the OpenTelemetry instrumentation using the native OTel field ``span.status``. ``span.status``, and subsequently ``otel.status_code``, are set based on either the HTTP status code or the gRPC status code.
2020

0 commit comments

Comments
 (0)