[Bug]: Errors are not captured in trace data

[chathurace]

Description

If an error occurs within a span, the corresponding span's state must be set to "Error" (status.code = 1). This is not done in the current implementation, which makes it impossible to track errors using trace analytics.

Steps to Reproduce

No response

Affected Version(s)

No response

OS, DB, other environment details and versions

No response

Related area

-> Observability

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[NipunaMadhushan]

@chathurace According to the API docs in opentelemetry-api, status code can be in three stages.

UNSET - 0
OK - 1
ERROR - 2

By default, it will be 0 since we haven't set the status of the span. If the status is ERROR, the status code will be 2.

Source - https://javadoc.io/doc/io.opentelemetry/opentelemetry-api/latest/io/opentelemetry/api/trace/StatusCode.html

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.