From 4c195fe6f24ab51b0c41e5263e68ed43ace7f4c0 Mon Sep 17 00:00:00 2001 From: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com> Date: Wed, 24 Jan 2024 13:52:53 -0500 Subject: [PATCH 1/6] Emphasize that there is no user-facing Otel Logs API --- content/en/docs/languages/java/instrumentation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/languages/java/instrumentation.md b/content/en/docs/languages/java/instrumentation.md index 7391a1576ffa..c9316ee4af44 100644 --- a/content/en/docs/languages/java/instrumentation.md +++ b/content/en/docs/languages/java/instrumentation.md @@ -1185,8 +1185,8 @@ 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 +Logs are distinct from Metrics and Tracing 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. The two typical workflows discussed below each cater to different application From 2edb8b446f9abf81c0e6fe1accc5eaa150c3c484 Mon Sep 17 00:00:00 2001 From: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Date: Wed, 24 Jan 2024 18:57:00 +0000 Subject: [PATCH 2/6] Results from /fix:format --- content/en/docs/languages/java/instrumentation.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/en/docs/languages/java/instrumentation.md b/content/en/docs/languages/java/instrumentation.md index c9316ee4af44..e7939ad8ac85 100644 --- a/content/en/docs/languages/java/instrumentation.md +++ b/content/en/docs/languages/java/instrumentation.md @@ -1185,9 +1185,10 @@ meter ## Logs -Logs are distinct from Metrics and Tracing 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. +Logs are distinct from Metrics and Tracing 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. The two typical workflows discussed below each cater to different application requirements. From f7c19051f8555469b65b4f30cc965cdd1aa52bf7 Mon Sep 17 00:00:00 2001 From: Fabrizio Ferri-Benedetti Date: Thu, 1 Feb 2024 10:45:32 +0100 Subject: [PATCH 3/6] Update content/en/docs/languages/java/instrumentation.md --- content/en/docs/languages/java/instrumentation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/languages/java/instrumentation.md b/content/en/docs/languages/java/instrumentation.md index e7939ad8ac85..95f512badbf4 100644 --- a/content/en/docs/languages/java/instrumentation.md +++ b/content/en/docs/languages/java/instrumentation.md @@ -1185,7 +1185,7 @@ meter ## Logs -Logs are distinct from Metrics and Tracing in that **there is no user-facing +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. From 4d5f20f9335d1a0d8120a0d4f98251cba1d1a412 Mon Sep 17 00:00:00 2001 From: Severin Neumann Date: Wed, 14 Feb 2024 12:05:39 +0100 Subject: [PATCH 4/6] Update content/en/docs/languages/java/instrumentation.md --- content/en/docs/languages/java/instrumentation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/languages/java/instrumentation.md b/content/en/docs/languages/java/instrumentation.md index 95f512badbf4..04ec79c4035f 100644 --- a/content/en/docs/languages/java/instrumentation.md +++ b/content/en/docs/languages/java/instrumentation.md @@ -1188,7 +1188,7 @@ meter 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. +ecosystem. For rationale behind this design decision, see [Logging specification](https://github.com/docs/specs/otel/logs/). The two typical workflows discussed below each cater to different application requirements. From 72443030f67cb18c4e23a479e686364e610e6f75 Mon Sep 17 00:00:00 2001 From: Severin Neumann Date: Wed, 14 Feb 2024 12:09:34 +0100 Subject: [PATCH 5/6] Update content/en/docs/languages/java/instrumentation.md --- content/en/docs/languages/java/instrumentation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/languages/java/instrumentation.md b/content/en/docs/languages/java/instrumentation.md index 22ab5b915fbb..09419a487a4f 100644 --- a/content/en/docs/languages/java/instrumentation.md +++ b/content/en/docs/languages/java/instrumentation.md @@ -1193,7 +1193,7 @@ meter 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/). +ecosystem. For rationale behind this design decision, see [Logging specification](/docs/specs/otel/logs/). The two typical workflows discussed below each cater to different application requirements. From 06778f5ba36d6992d3bb6fe7e18b0c2a9fefff42 Mon Sep 17 00:00:00 2001 From: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Date: Wed, 14 Feb 2024 11:16:33 +0000 Subject: [PATCH 6/6] Results from /fix:all --- content/en/docs/languages/java/instrumentation.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/languages/java/instrumentation.md b/content/en/docs/languages/java/instrumentation.md index 09419a487a4f..85a266311493 100644 --- a/content/en/docs/languages/java/instrumentation.md +++ b/content/en/docs/languages/java/instrumentation.md @@ -1193,7 +1193,8 @@ meter 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](/docs/specs/otel/logs/). +ecosystem. For rationale behind this design decision, see +[Logging specification](/docs/specs/otel/logs/). The two typical workflows discussed below each cater to different application requirements.