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
AsyncioInstrumentor: Tracing Requests Made by the Asyncio Library
10
10
11
-
Primary Use Case:
12
-
-----------------
13
-
1. Performance and Error Monitoring:
14
-
The AsyncioInstrumentor tool offers significant advantages for developers and system administrators. It's designed to monitor real-time performance bottlenecks and catch exceptions within specific asynchronous tasks.
15
11
16
-
When It's Not Ideal to Use AsyncioInstrumentor:
17
-
------------------------------------------------
18
-
1. Frameworks with Built-in Instrumentation:
19
-
If you're utilizing a framework like aiohttp that already includes built-in instrumentation, you might not need this library. In such cases, leveraging the built-in tools of the framework is generally more beneficial than using external ones like AsyncioInstrumentor.
12
+
The opentelemetry-instrumentation-asycnio package allows tracing asyncio applications.
13
+
The metric for coroutine, future, is generated even if there is no setting to generate a span.
20
14
21
-
2. Libraries Lacking Instrumentation:
22
-
Should you employ a library that isn't inherently instrumented, AsyncioInstrumentor can step in to fill that gap.
23
15
24
-
3. Concerns about Overhead:
25
-
Tracing each task and future consistently can lead to added overhead. As a best practice, it's wise to enable tracing only when crucial, especially during the development stage.
0 commit comments