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: exporter/opentelemetry-exporter-prometheus-remote-write/example/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ data
14
14
*Users do not need to install Python as the app will be run in the Docker Container*
15
15
16
16
## Instructions
17
-
1. Run `docker-compose up -d` in the the `example/` directory
17
+
1. Run `docker-compose up -d` in the `example/` directory
18
18
19
19
The `-d` flag causes all services to run in detached mode and frees up your
20
20
terminal session. This also causes no logs to show up. Users can attach themselves to the service's logs manually using `docker logs ${CONTAINER_ID} --follow`
Copy file name to clipboardExpand all lines: instrumentation/opentelemetry-instrumentation-logging/src/opentelemetry/instrumentation/logging/constants.py
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@
18
18
_MODULE_DOC="""
19
19
The OpenTelemetry ``logging`` integration automatically injects tracing context into log statements.
20
20
21
-
The integration registers a custom log record factory with the the standard library logging module that automatically inject
21
+
The integration registers a custom log record factory with the standard library logging module that automatically inject
22
22
tracing context into log record objects. Optionally, the integration can also call ``logging.basicConfig()`` to set a logging
23
23
format with placeholders for span ID, trace ID and service name.
0 commit comments