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.

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

[editorial] Fix links: rename anchor id to event-data-model #4075

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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: 1 addition & 1 deletion specification/logs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -231,7 +231,7 @@ processor.

These are logs generated by various infrastructure components, such as
Kubernetes events (if you are wondering why events are discussed in the context
of logs see [Event API Data model](./event-api.md#data-model)). Like system logs, the
of logs see [Event API Data model](./event-api.md#event-data-model)). Like system logs, the
infrastructure logs lack a trace context and can be enriched by the resource
context - information about the node, pod, container, etc.

Expand Down
2 changes: 1 addition & 1 deletion specification/logs/event-sdk.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ All implementations of the OpenTelemetry API MUST provide an SDK.
## Overview

From OpenTelemetry's perspective LogRecords and Events are both represented
using the same [data model](./event-api.md#data-model). Therefore, the default
using the same [data model](./event-api.md#event-data-model). Therefore, the default
implementation of an Event SDK MUST generate events using the [Logs Data Model](./data-model.md).

The SDK MUST use the [Logs SDK](./sdk.md) to generate, process and export `LogRecord`s.
Expand Down
Loading