Skip to main content

No project description provided

Project description

Monitored IO Loop

A production ready monitored IO loop for Python.
No more wondering why your event loop (or random pieces of your code) are suddenly popping up as slow in your monitoring.

GitHub Actions Workflow Status PyPI - Version PyPI - Python Version

Getting started

Installation

pip install monitored_ioloop  # For the default event loop
pip install monitored_ioloop[uvloop]  # For the the additional support of the uvloop event loop

Demo

📺 Play with the demo in sandbox

Usage

Asyncio event loop

from monitored_ioloop.monitored_asyncio import MonitoredAsyncIOEventLoopPolicy
from monitored_ioloop.monitoring import IoLoopMonitorState
import asyncio
import time


def monitor_callback(ioloop_state: IoLoopMonitorState) -> None:
    print(ioloop_state)


async def test_coroutine() -> None:
    time.sleep(2)


def main():
    asyncio.set_event_loop_policy(MonitoredAsyncIOEventLoopPolicy(monitor_callback))
    asyncio.run(test_coroutine())

Uvloop event loop

In order to use the uvloop event loop, please make sure to install monitored_ioloop[uvloop].
The usage is the same as the asyncio event loop, but with monitored_ioloop.monitored_uvloop.MonitoredUvloopEventLoopPolicy instead of the monitored_ioloop.monitored_asyncio.MonitoredAsyncIOEventLoopPolicy.

The monitor callback

The monitor callback will be called for every execution that the event loop initiates.
With every call you will receive an IoLoopMonitorState object that contains the following information:

  • callback_wall_time: Wall executing time of the callback.
  • loop_handles_count: The amount of handles (think about them as tasks) that the IO loop is currently handling.
  • loop_lag: The amount of time it took from the moment the task was added to the loop until it was executed.
  • callback_pretty_name: The pretty name of the callback that was executed
    Please Note: This is a best effort, the name of the callback may still be of little help, depending on the specific callback implementation.

Performance impact

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.
In summary the performance impact is negligible for most use cases.
You can find the more detailed information in the following README.md.

Usage examples

You can find examples projects showing potential use cases in the examples folder.
Currently there is only the fastapi with prometheus exporter example but more will be added in the future.

Roadmap

  • Add support for the amount of Handle's on the event loop
  • Add an examples folder
  • Add loop lag metric (Inspired from nodejs loop monitoring)
  • Add visibility into which Handle are making the event loop slower
  • Add easier integration with uvicorn
  • Add easier integration with popular monitoring tools like Prometheus

Credits

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

monitored_ioloop-0.0.13.tar.gz (6.6 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

monitored_ioloop-0.0.13-py3-none-any.whl (9.7 kB view details)

Uploaded Python 3

File details

Details for the file monitored_ioloop-0.0.13.tar.gz.

File metadata

  • Download URL: monitored_ioloop-0.0.13.tar.gz
  • Upload date:
  • Size: 6.6 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.12.8

File hashes

Hashes for monitored_ioloop-0.0.13.tar.gz
Algorithm Hash digest
SHA256 9d5f894013ed979c8efe6b414cc9faf5d566527caf5ab56e8fd8edc4529db3ef
MD5 68341f363d0211c8ab473dc6e76dc2f2
BLAKE2b-256 39ce0e79c2fb931f2eab0fa29a65d9775f749160ce49b5cdb87f835b417a662b

See more details on using hashes here.

Provenance

The following attestation bundles were made for monitored_ioloop-0.0.13.tar.gz:

Publisher: deployment.yaml on gnir-work/monitored-ioloop

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file monitored_ioloop-0.0.13-py3-none-any.whl.

File metadata

File hashes

Hashes for monitored_ioloop-0.0.13-py3-none-any.whl
Algorithm Hash digest
SHA256 2db3c27e05c8a6ef9a73e0369505f16d224d77a0cfcc44dfee2206b914216e29
MD5 6633f3dcf788066dfb65f8cafafd8ba8
BLAKE2b-256 1dd863b31302da8718bf4288c00387d9a23e2732b5f125b8f68e9c32d918e0f3

See more details on using hashes here.

Provenance

The following attestation bundles were made for monitored_ioloop-0.0.13-py3-none-any.whl:

Publisher: deployment.yaml on gnir-work/monitored-ioloop

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page