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

Emphasize that there is no user-facing Otel Logs API #3856

Merged
merged 7 commits into from
Feb 14, 2024
7 changes: 4 additions & 3 deletions content/en/docs/languages/java/instrumentation.md
Original file line number Diff line number Diff line change
Expand Up @@ -1190,9 +1190,10 @@ meter

## Logs

Logs are distinct from Metrics and Tracing in that there is no user-facing logs
API. Instead, there is tooling to bridge logs from existing popular log
frameworks (e.g. SLF4j, JUL, Logback, Log4j) into the OpenTelemetry ecosystem.
Logs are distinct from metrics and traces in that **there is no user-facing
OpenTelemetry logs API**. Instead, there is tooling to bridge logs from existing
popular log frameworks (e.g. SLF4j, JUL, Logback, Log4j) into the OpenTelemetry
ecosystem. For rationale behind this design decision, see [Logging specification](https://github.com/docs/specs/otel/logs/).
svrnm marked this conversation as resolved.
Show resolved Hide resolved

The two typical workflows discussed below each cater to different application
requirements.
Expand Down
Loading