# Add asyncio monitoring hooks **URL:** \ **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:** 6
**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 23, 2024, 3:17pm UTC](https://discuss.python.org/t/add-asyncio-monitoring-hooks/26426/6 "2024-05-23T15:17:23Z")
> [@Server-oriented task scope design](https://discuss.python.org/t/server-oriented-task-scope-design/53903/2): > > So, I think we need to break down the issue to a set of more approachable tasks. There are two big directions: Implementing the intrinsic “task scope” entirely in the stdlib asyncio (e.g., an option to TaskGroup as some suggested, refactoring TaskGroup into TaskScope and TaskContext, etc.) Splitting out the “task scope” implementation as a 3rd-party library after adding minimal supporting facilities in the stdlib asyncio Practically, the second approach would sound better and be more useful … There is another use case for fine-grained asyncio hooks to implement “task scope” to structure asyncio server applications. Also, please have a look at [aiomonitor](https://github.com/aio-libs/aiomonitor). > **[\[PyCon APAC 2023\] Improving Debuggability of Complex Asyncio Applications](https://speakerdeck.com/achimnol/pycon-apac-2023-improving-debuggability-of-complex-asyncio-applications)** --- _[View the full topic](https://discuss.python.org/t/add-asyncio-monitoring-hooks/26426)._