From b036ba30b207c79c06d0661ff139bc370443dd5f Mon Sep 17 00:00:00 2001 From: "allen.k1m" Date: Sat, 23 Dec 2023 23:29:40 +0900 Subject: [PATCH] modified lint results --- .../opentelemetry-instrumentation-asyncio/README.rst | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/instrumentation/opentelemetry-instrumentation-asyncio/README.rst b/instrumentation/opentelemetry-instrumentation-asyncio/README.rst index e23b2412fc..1a94a0c223 100644 --- a/instrumentation/opentelemetry-instrumentation-asyncio/README.rst +++ b/instrumentation/opentelemetry-instrumentation-asyncio/README.rst @@ -15,17 +15,20 @@ The metric for coroutine, future, is generated even if there is no setting to ge Set the name of the coroutine you want to trace. ------------------------------------------------- -.. code:: +.. code:: bash + export OTEL_PYTHON_ASYNCIO_COROUTINE_NAMES_TO_TRACE=coro_name,coro_name2,coro_name3 If you want to keep track of which function to use in the to_thread function of asyncio, set the name of the function. ------------------------------------------------------------------------------------------------------------------------ -.. code:: +.. code:: bash + export OTEL_PYTHON_ASYNCIO_TO_THREAD_FUNCTION_NAMES_TO_TRACE=func_name,func_name2,func_name3 For future, set it up like this ----------------------------------------------- -.. code:: +.. code:: bash + export OTEL_PYTHON_ASYNCIO_FUTURE_TRACE_ENABLED=true Run instrumented application @@ -122,6 +125,6 @@ Installation References ---------- -* `OpenTelemetry asyncio/ Tracing /.html>`_ +* `OpenTelemetry asyncio/ Tracing `_ * `OpenTelemetry Project `_ * `OpenTelemetry Python Examples `_