Skip to content

Commit 8487495

Browse files
committed
add link to crates
1 parent 0cdf9c7 commit 8487495

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

docs/design/logs.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,9 @@ graph TD
8484

8585
## Logs API
8686

87+
Logs API is part of the [opentelemetry](https://crates.io/crates/opentelemetry)
88+
crate.
89+
8790
The OTel Logs API is not intended for direct end-user usage. Instead, it is
8891
designed for appender/bridge authors to integrate existing logging libraries
8992
with OpenTelemetry. However, there is nothing preventing it from being used by
@@ -120,6 +123,9 @@ Users or vendors can also provide alternative SDK implementations.
120123

121124
## Logs SDK
122125

126+
Logs SDK is part of the
127+
[opentelemetry_sdk](https://crates.io/crates/opentelemetry_sdk) crate.
128+
123129
The OpenTelemetry Logs SDK provides an OTel specification-compliant
124130
implementation of the Logs API, handling log processing and export.
125131

@@ -249,9 +255,9 @@ include:
249255

250256
## `tracing` Log Appender
251257

252-
The `tracing` appender bridges `tracing` logs (events) to OpenTelemetry. Logs
253-
emitted via `tracing` macros (`info!`, `warn!`, etc.) are forwarded to
254-
OpenTelemetry through this integration.
258+
The `tracing` appender bridges `tracing` logs to OpenTelemetry. Logs emitted via
259+
`tracing` macros (`info!`, `warn!`, etc.) are forwarded to OpenTelemetry through
260+
this integration.
255261

256262
- `tracing` is designed for high performance, using *layers* or *subscribers* to
257263
handle emitted logs (events).

0 commit comments

Comments
 (0)