From 195e6aca8e0abb3b0a0333e5a5a81d896b043bb8 Mon Sep 17 00:00:00 2001 From: Andre Wanlin Date: Thu, 17 Jul 2025 12:16:53 -0500 Subject: [PATCH] Adjustments based on feedback Signed-off-by: Andre Wanlin --- docs/tutorials/setup-opentelemetry.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/tutorials/setup-opentelemetry.md b/docs/tutorials/setup-opentelemetry.md index 44795b3da3..4803933736 100644 --- a/docs/tutorials/setup-opentelemetry.md +++ b/docs/tutorials/setup-opentelemetry.md @@ -45,7 +45,8 @@ if (isMainThread) { const prometheusExporter = new PrometheusExporter(); // We post the traces to localhost:4318/v1/traces const otlpTraceExporter = new OTLPTraceExporter({ - url: 'http://localhost:4318/v1/traces', // This is the most common URL to work with Jaeger but you may need to adjust this for your needs + // Default Jaeger URL trace endpoint. + url: 'http://localhost:4318/v1/traces', }); const sdk = new NodeSDK({ metricReader: prometheusExporter, @@ -131,7 +132,9 @@ const { diag, DiagConsoleLogger, DiagLogLevel } = require('@opentelemetry/api'); diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.DEBUG); ``` -This will then output a very large volume of details to the logs, we don't recommend shipping this in production, which you can then look at to help get a better idea of why something may not be working as expected. +This will then add OpenTelemetry debug logs that you can then look at to help get a better idea of why something may not be working as expected. + +We don't recommend shipping this in production because of the log density. ## Production Setup