# Add asyncio monitoring hooks

**URL:** <https://discuss.python.org/t/add-asyncio-monitoring-hooks/26426>\
**Category:** Ideas\
**Tags:** asyncio\
**Created:** [May 2, 2023, 8:24pm UTC](https://discuss.python.org/t/add-asyncio-monitoring-hooks/26426 "2023-05-02T20:24:59Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![achimnol](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/achimnol/32/28061_2.png) [@achimnol](https://discuss.python.org/u/achimnol)\
**Post date:** [May 28, 2024, 11:28am UTC](https://discuss.python.org/t/add-asyncio-monitoring-hooks/26426/19 "2024-05-28T11:28:25Z")

</div>

Yet another raise-up:

> [@Measuring coroutine blocking time](https://discuss.python.org/t/measuring-coroutine-blocking-time/54399):
>
> I couldn’t find an easy way to measure how long an async coroutine blocks the event loop, so I rolled my own. I use this in conjunction with a lag monitor to keep track of event loop health and identify the next best targets for optimization. It’s difficult to maintain: every so often I come across a library that does something new that I haven’t accounted for. It breaks across different python versions sometimes too. I noticed that there are some coroutine time measurements in CPython. Is…

---

_[View the full topic](https://discuss.python.org/t/add-asyncio-monitoring-hooks/26426)._