Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 9115d7d

Browse files
authored
Merge pull request #1436 from splunk/repo-sync
Pulling refs/heads/main into main
2 parents 74483d7 + 2d5720c commit 9115d7d

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

gdi/get-data-in/application/nodejs/troubleshooting/common-nodejs-troubleshooting.rst

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Activate diagnostic logging
2626

2727
Diagnostic logs can help you troubleshoot instrumentation issues.
2828

29-
To output instrumentation logs to the console, set the ``OTEL_LOG_LEVEL`` environment variable to ``debug``.
29+
To output instrumentation logs to the console, set the ``OTEL_LOG_LEVEL`` environment variable to ``debug`` in the same scope where the application is running. For example, ``OTEL_LOG_LEVEL=<level> node start.js``. Don't add it to the .env file, as it's loaded later.
3030

3131
You can also activate debug logging programmatically by setting the ``logLevel`` argument. For example:
3232

@@ -60,7 +60,9 @@ To deactivate debug logging in your code, call ``setLogger()`` as in the followi
6060
Activate debug metrics
6161
---------------------------------
6262

63-
You can activate internal debug metrics by setting the ``SPLUNK_DEBUG_METRICS_ENABLED`` environment variable to true. For more information, see :ref:`nodejs-otel-debug-metrics`.
63+
You can activate internal debug metrics by setting the ``SPLUNK_DEBUG_METRICS_ENABLED`` environment variable to ``true`` in the same scope where the application is running. For example, ``SPLUNK_DEBUG_METRICS_ENABLED=true node start.js``. Don't add it to the .env file, as it's loaded later.
64+
65+
For more information, see :ref:`nodejs-otel-debug-metrics`.
6466

6567
.. _nodejs-trace-exporter-issues:
6668

0 commit comments

Comments
 (0)