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: README.md
+3-1
Original file line number
Diff line number
Diff line change
@@ -51,6 +51,8 @@ With every call you will receive an [IoLoopMonitorState](monitored_ioloop/monito
51
51
-`callback_wall_time`: Wall executing time of the callback.
52
52
-`loop_handles_count`: The amount of handles (think about them as tasks) that the IO loop is currently handling.
53
53
-`loop_lag`: The amount of time it took from the moment the task was added to the loop until it was executed.
54
+
-`callback_pretty_name`: The pretty name of the callback that was executed
55
+
__Please Note__: This is a best effort, the name of the callback may still be of little help, depending on the specific callback implementation.
54
56
55
57
## Performance impact
56
58
As many of you might be concerned about the performance impact of this library, I have run some benchmarks to measure the performance impact of this library.
@@ -66,7 +68,7 @@ Currently there is only the [fastapi with prometheus exporter example](examples/
66
68
-[x] Add support for the amount of `Handle`'s on the event loop
67
69
-[x] Add an examples folder
68
70
-[x] Add loop lag metric (Inspired from nodejs loop monitoring)
69
-
-[] Add visibility into which `Handle` are making the event loop slower
71
+
-[x] Add visibility into which `Handle` are making the event loop slower
70
72
-[ ] Add easier integration with `uvicorn`
71
73
-[ ] Add easier integration with popular monitoring tools like Prometheus
0 commit comments