Overview
The mod_wsgi-telemetry package provides an external telemetry ingester and live UI for the mod_wsgi Apache module. With the WSGITelemetryService directive enabled in Apache, each mod_wsgi process (daemon-mode worker or embedded-mode Apache child) emits per-interval binary datagrams summarising its throughput, latency distribution, capacity utilisation, CPU and memory consumption, and any active slow requests. The ingester receives those datagrams over a local UNIX socket, aggregates them across every reporting process, and serves a browser-based live UI together with a curses terminal monitor for hosts where opening a browser is impractical.
The package is distributed separately from mod_wsgi itself so that an installation using the operating-system mod_wsgi package, or any other manually-configured Apache, can use the telemetry pipeline without adopting the PyPi mod_wsgi or mod_wsgi-express packages.
The ingester is intended to run co-located with the Apache instance it observes: the transport is a local UNIX datagram socket, and the UI binds to the loopback interface by default. For remote access, either an SSH tunnel or an authenticated reverse proxy is recommended.
Once installed, launch the ingester with:
mod_wsgi-telemetry serve
It binds unix:/tmp/mod_wsgi-telemetry.sock for incoming datagrams and serves the browser UI on http://127.0.0.1:8888/ by default. A mod_wsgi-telemetry top subcommand provides a curses-based terminal monitor for the same data.
For the full configuration reference, including the WSGITelemetryService, WSGITelemetryOptions and WSGISlowRequests Apache directives, the matching mod_wsgi-express options, socket-permission handling for multi-user deployments, and the remote-access patterns, see the External Telemetry Service page in the mod_wsgi documentation site at https://www.modwsgi.org.
This package is still being iterated on. The directive set, option names, wire format and ingester CLI may change in a future release; pair an ingester release with the matching mod_wsgi release until the pipeline stabilises.
Metadata
Release files for mod-wsgi-telemetry 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mod_wsgi_telemetry-1.1.0.tar.gz | 158.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mod_wsgi_telemetry-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 316.1 kB
Release files / mod_wsgi_telemetry-1.1.0.tar.gz
| Download URL | mod_wsgi_telemetry-1.1.0.tar.gz |
|---|---|
| Size | 158.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f36e2d0098cf63e6973f442704639b48aa23072aafb2839463b04999a669a8c4
|
|
BLAKE2b-256 checksum How to use checksums |
1fcae6f1da0db951dced55872fa618e40df753baba59decbdb57baec179b1492
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency logRelease files / mod_wsgi_telemetry-1.1.0-py3-none-any.whl
| Download URL | mod_wsgi_telemetry-1.1.0-py3-none-any.whl |
|---|---|
| Size | 157.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11014f3eeee53cdc853520d72150f9cd42d28e8635325185a4518ddb64d81262
|
|
BLAKE2b-256 checksum How to use checksums |
4762779e408fe9e70a9313847fa517cd35ea57baef20a6f3a9c3811f17e4887a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency log