client_python
client_python copied to clipboard
Prometheus instrumentation library for Python applications
When using prometheus client in multiprocess mode as in the docs example, metric description always says `Multiprocess metric`: ``` # HELP inprogress_requests Multiprocess metric # TYPE inprogress_requests gauge inprogress_requests 0.0...
My use case is fairly simple: I'm looking for a Prometheus client in Python because I'm going to be doing some queries, e.g. (a picture is worth a thousand words,...
When the multiprocess environemnt is not properly set-up (missing environment variable) and mark_process_dead is called, the method raises an error on path.join() because the path is None which may be...
Just a small cleanup: only 3.9+ is supported, so it looks fine to switch to `functools.wraps`.
Current Prometheus client_python does support basic auth towards pushgateway but it doesn't support TLS as well as authentication towards prometheus server. Is there any plan to support it? Will it...
I'd like `count_exceptions` to add the error type as a label so I can track what errors are occurring against what endpoints for my application. I'd like to do this...
It'd be awesome if client_python was type hinted, as that would allow downstream consumers to typecheck their API calls (one has to explicitly `# type: ignore` the import right now)....
Is there a way to define a default, global prefix for all metrics? For example instead of: `python_gc_objects_collected_total` I'd like to add the prefix `myproject_`: `myproject_python_gc_objects_collected_total` I'm currently doing it...
It's useful to be able to apply a label across all metrics, for example when using a multi-processing framework to apply a label for worker ID to all metrics (including...
It's useful to be able to apply a label across all metrics, for example when using a multi-processing framework to apply a label for worker ID to all metrics (including...