Skip to content
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

Jump to bottom

[editorial] Remove use of Object-Oriented term class in log signal #3882

Merged
merged 2 commits into from
Feb 15, 2024
Merged

[editorial] Remove use of Object-Oriented term class in log signal #3882

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
653155c
Remove use of class term in log signal
MrAlias Feb 15, 2024
953d2da
Add changelog entry
MrAlias Feb 15, 2024
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 @@ -26,6 +26,8 @@ release.
([#3827](https://github.com/open-telemetry/opentelemetry-specification/pull/3827))
- Deconstruct number scalar type to double and signed integer.
([#3854](https://github.com/open-telemetry/opentelemetry-specification/pull/3854))
- Remove use of Object-Oriented term `class` in log signal.
([#3882](https://github.com/open-telemetry/opentelemetry-specification/pull/3882))

### Resource

Expand Down
4 changes: 2 additions & 2 deletions specification/logs/bridge-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,10 +30,10 @@ library authors to build
which use this API to bridge between existing logging libraries and the
OpenTelemetry log data model.</b>

The Logs Bridge API consist of these main classes:
The Logs Bridge API consist of these main components:

* [LoggerProvider](#loggerprovider) is the entry point of the API. It provides access to `Logger`s.
* [Logger](#logger) is the class responsible for emitting logs as
* [Logger](#logger) is responsible for emitting logs as
[LogRecords](./data-model.md#log-and-event-record-definition).

```mermaid
Expand Down
4 changes: 2 additions & 2 deletions specification/logs/noop.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,8 @@ so that no telemetry is produced and computation resources are minimized.

All language implementations of OpenTelemetry MUST provide a No-Op.

The [Logs Bridge API](./bridge-api.md) defines classes with various operations.
All No-Op classes MUST NOT hold configuration or operational state. All No-op
The [Logs Bridge API](./bridge-api.md) defines components with various operations.
All No-Op components MUST NOT hold configuration or operational state. All No-op
operations MUST accept all defined parameters, MUST NOT validate any arguments
received, and MUST NOT return any non-empty error or log any message.

Expand Down
Loading