You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: troubleshoot/ingest/opentelemetry/edot-sdks/python/index.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,24 @@ As a first step, review the [supported technologies](elastic-otel-python://refer
25
25
26
26
Follow these recommended actions to make sure that EDOT Python is configured correctly.
27
27
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
+
28
46
### Debug and development modes
29
47
30
48
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