Skip to content

Clarify that it is allowed to directly use Logs API #4438

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

Merged
merged 2 commits into from
Mar 10, 2025
Merged

Clarify that it is allowed to directly use Logs API #4438

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b38a517
Clarify that it is allowed to directly use Logs API
pellared Mar 3, 2025
5a4fe4b
Update PR number
pellared Mar 3, 2025
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 @@ -23,6 +23,8 @@ release.

- Clarify STDOUT exporter format is unspecified.
([#4418](https://github.com/open-telemetry/opentelemetry-specification/pull/4418))
- Clarify that it is allowed to directly use Logs API.
([#4438](https://github.com/open-telemetry/opentelemetry-specification/pull/4438))

### Baggage

Expand Down
15 changes: 8 additions & 7 deletions specification/logs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,13 +144,14 @@ Given the above state of the logging space we took the following approach:
translate them to OpenTelemetry log data model.

- OpenTelemetry defines a Logs API
for [emitting LogRecords](./api.md#emit-a-logrecord). Application developers are
NOT encouraged to call this API directly. It is provided for library authors
to build [log appender](../glossary.md#log-appender--bridge), which use
the API to bridge between existing logging libraries and the OpenTelemetry log
data model. Existing logging libraries generally provide a much richer set of
features than what is defined in OpenTelemetry. It is NOT a goal of
OpenTelemetry to ship a feature-rich logging library.
for [emitting LogRecords](./api.md#emit-a-logrecord). It is provided for
library authors to build [log appender](../glossary.md#log-appender--bridge),
which use the API to bridge between existing logging libraries and the
OpenTelemetry log data model. Existing logging libraries generally provide
a much richer set of features than what is defined in OpenTelemetry.
It is NOT a goal of OpenTelemetry to ship a feature-rich logging library.
Yet, the Logs API can also be used directly if one prefers to couple the code
to it instead of using a bridged logging library.

- OpenTelemetry defines an [SDK](./sdk.md) implementation of the [API](./api.md),
which enables configuration of [processing](./sdk.md#logrecordprocessor)
Expand Down