Skip to content

[DO NOT MERGE] [Trace] Deprecate Record Exception API in favor of using Logs API #4825

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pellared wants to merge 8 commits into
base: main
Choose a base branch
from
+7 −3
Open

[DO NOT MERGE] [Trace] Deprecate Record Exception API in favor of using Logs API #4825

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
7d6bf5b
[Trace] Deprecate Record Exception API in favor of using Logs
pellared Jan 7, 2026
9a6e58d
Update link reference in changelog
pellared Jan 7, 2026
25a45f0
Remove confusing paragraph
pellared Jan 7, 2026
99fb865
Update specification/trace/exceptions.md
pellared Jan 7, 2026
6ba12cb
Update CHANGELOG.md
pellared Jan 7, 2026
35d64db
Merge branch 'main' into dep-span-events
pellared Jan 29, 2026
eb0510b
Merge branch 'main' into dep-span-events
pellared Feb 17, 2026
118e39e
Merge branch 'main' into dep-span-events
pellared Mar 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ release.

### Traces

- Deprecate Record Exception API in favor of using Events.
([#4825](https://github.com/open-telemetry/opentelemetry-specification/pull/4825))
- Add normative language to the Tracing API/SDK spec concurrency requirements.
([#4887](https://github.com/open-telemetry/opentelemetry-specification/pull/4887))

Expand Down
2 changes: 2 additions & 0 deletions specification/trace/api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -683,6 +683,8 @@ in the scope of this requirement and recommendation.

#### Record Exception

**Status**: [Deprecated](../document-status.md)

To facilitate recording an exception languages SHOULD provide a
`RecordException` method if the language uses exceptions.
This is a specialized variant of [`AddEvent`](#add-events),
Expand Down
6 changes: 3 additions & 3 deletions specification/trace/exceptions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
# Exceptions

**Status**: [Stable](../document-status.md), Unless otherwise specified.
**Status**: [Deprecated](../document-status.md), follow the
[semantic conventions for recording exceptions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/recording-errors.md#recording-exceptions)
instead.

This document defines how to record exceptions and their attributes.

Expand All @@ -19,8 +21,6 @@ to be set to ERROR.

The name of the event MUST be `"exception"`.

**Status**: [Development](../document-status.md) - Refer to the [Recording Errors](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/recording-errors.md) document for the details on how to report errors across signals.

A typical template for an auto-instrumentation implementing this semantic convention
using an [API-provided `recordException` method](api.md#record-exception)
could look like this (pseudo-Java):
Expand Down
Loading