Skip to content

Commit 4095822

Browse files
xrmxtheletterf
andauthored
edot-sdks/python: document OTEL_LOG_LEVEL in troubleshoot (#3311)
Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
1 parent 7cc3933 commit 4095822

File tree

1 file changed

+18
-0
lines changed
  • troubleshoot/ingest/opentelemetry/edot-sdks/python

1 file changed

+18
-0
lines changed

troubleshoot/ingest/opentelemetry/edot-sdks/python/index.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,24 @@ As a first step, review the [supported technologies](elastic-otel-python://refer
2525

2626
Follow these recommended actions to make sure that EDOT Python is configured correctly.
2727

28+
### EDOT Logging level
29+
30+
```{applies_to}
31+
product:
32+
edot_python: ga 1.9.0
33+
```
34+
35+
You can change the default verbosity of both EDOT Python and OpenTelemetry Python SDK code with `OTEL_LOG_LEVEL`, see [configuration](elastic-otel-python://reference/edot-python/configuration.md#differences-from-opentelemetry-python) for the possible values.
36+
37+
### Log configuration
38+
39+
```{applies_to}
40+
product:
41+
edot_python: ga 1.9.0
42+
```
43+
44+
EDOT Python would print its configuration at startup when `OTEL_LOG_LEVEL` is set to `info` or a more verbose logging level.
45+
2846
### Debug and development modes
2947

3048
Most frameworks support a debug mode. This mode is intended for non-production environments and provides detailed error messages and logging of potentially sensitive data. Turning on instrumentation in debug mode is not advised and might pose privacy and security issues in recording sensitive data.

0 commit comments

Comments
 (0)