…rometheus#1138)

* fix: Use `asyncio.new_event_loop()` to create event loop for tests

Replace the use of `asyncio.get_event_loop()` with more appropriate
`asyncio.new_event_loop()` to create event loops for testing.
The former used to be a wrapper that either returned the currently
running event loop or created a new one, but the latter behavior was
deprecated and removed in Python 3.14.  Since the tests are always run
in a synchronous context, and they always run the obtained event loop
to completion, just always create a new event loop.

Fixes prometheus#1137

Signed-off-by: Michał Górny <mgorny@gentoo.org>

* fix: Remove obsolete asgiref pin

Remove the `asgiref` pin linked to prometheus#1020.  I can't reproduce the issue
anymore with the current `asgiref` versions, and the pin actually
breaks the tests with the `asyncio` event loop fixes.

Signed-off-by: Michał Górny <mgorny@gentoo.org>

---------

Signed-off-by: Michał Górny <mgorny@gentoo.org>

Signed-off-by: Ruslan Kuprieiev <kupruser@gmail.com>

Signed-off-by: Chris Marchbanks <csmarchbanks@gmail.com>

* Always run the asgi tests

Since the client now requires a minimum of Python 3.9, we don't need to
have this feature gate in place any more

Signed-off-by: Lexi Robinson <lexi@lexi.org.uk>

* Add an AIOHTTP exporter

Unfortunately the AIOHTTP library doesn't support ASGI and apparently
has no plans to do so which makes the ASGI exporter not suitable for
anyone using it to run their python server.

Where possible this commit follows the existing ASGI implementation and
runs the same tests for consistency.

Signed-off-by: Lexi Robinson <lexi@lexi.org.uk>

---------

Signed-off-by: Lexi Robinson <lexi@lexi.org.uk>

* Add remove_matching() method for metric label deletion

Signed-off-by: Hazel <hazel@hazel.localdomain>

* Rename function name, and the parameter's name

Signed-off-by: Hazel <hazel@hazel.localdomain>

* Make remove_by_labels() consistent with remove(): return None

Signed-off-by: Hazel <hazel@hazel.localdomain>

---------

Signed-off-by: Hazel <hazel@hazel.localdomain>
Co-authored-by: Hazel <hazel@hazel.localdomain>

* Add Python version 3.14 to CircleCI config

Signed-off-by: Naoyuki Sano <nsano@ae.em-net.ne.jp>

* Update tox.ini

Signed-off-by: Naoyuki Sano <nsano@ae.em-net.ne.jp>

* Add support for Python 3.14 in pyproject.toml

Signed-off-by: Naoyuki Sano <nsano@ae.em-net.ne.jp>

* Update pyproject.toml

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Naoyuki Sano <nsano@ae.em-net.ne.jp>

---------

Signed-off-by: Naoyuki Sano <nsano@ae.em-net.ne.jp>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

…us#1035) (prometheus#1146)

* fix(multiprocess): avoid double-building child metric names (prometheus#1035)

Signed-off-by: hazel-shen <mail@hazel.style>

* test: ensure child metrics retain parent namespace/subsystem/unit

Signed-off-by: hazel-shen <mail@hazel.style>

---------

Signed-off-by: hazel-shen <mail@hazel.style>

…heus#1148)

The OpenMetrics exposition format requires that samples for a given
Metric (i.e. metric name and label set) are not interleaved, but the way
that the multi-process collector handled accumulating histogram metrics
could end up interleaving them.  Restructure it slightly to guarantee
that all the samples for a given Metric are kept together.

Fixes: prometheus#1147

Signed-off-by: Colin Watson <cjwatson@debian.org>

* Turn Collector into a Protocol

We require Python >= 3.9 now, so there's no reason to avoid this any
more.

Signed-off-by: Colin Watson <cjwatson@debian.org>

* Relax registry type annotations for exposition

Anything with a suitable `collect` method will do: for instance, it's
sometimes useful to be able to define a class whose `collect` method
yields all metrics from a registry whose names have a given prefix, and
such a class doesn't need to inherit from `CollectorRegistry`.

Signed-off-by: Colin Watson <cjwatson@debian.org>

---------

Signed-off-by: Colin Watson <cjwatson@debian.org>

* feat(): Added compression support in pushgateway

Signed-off-by: ritesh-avesha <ritesh@aveshasystems.com>

* fix(): Incorporated changes for PR review comments

Signed-off-by: ritesh-avesha <ritesh@aveshasystems.com>

* fix(): Incorporated changes for PR review comments, lint issues

Signed-off-by: ritesh-avesha <ritesh@aveshasystems.com>

* fix(): lint issues

Signed-off-by: ritesh-avesha <ritesh@aveshasystems.com>

---------

Signed-off-by: ritesh-avesha <ritesh@aveshasystems.com>

Signed-off-by: Julie Rymer <rymerjulie.pro@gmail.com>

Signed-off-by: Chris Marchbanks <csmarchbanks@gmail.com>

`registry` does not exists in prometheus_client.registry, as that causes
an ImportError the test was skipped in the 3.9 scenario.

Signed-off-by: Jelle van der Waa <jelle@vdwaa.nl>

Signed-off-by: Chris Marchbanks <csmarchbanks@gmail.com>

* Migrate to Github Actions
* Pin github actions versions

---------

Signed-off-by: Chris Marchbanks <csmarchbanks@gmail.com>

Add server.server_close() call to shutdown example to properly
release the port. Without this call, attempting to restart the
server on the same port results in "Address already in use" error.

Fixes prometheus#1068

Signed-off-by: Varun Chawla <varun_6april@hotmail.com>

Use base64 encoding for grouping key values containing spaces,
similar to how values with slashes are handled. This prevents
spaces from being converted to '+' signs by quote_plus().

Fixes prometheus#1064

Signed-off-by: Varun Chawla <varun_6april@hotmail.com>

* Support MultiProcessCollector in RestrictedRegistry.

This change makes it so that the RestrictedRegistry will always attempt to collect metrics from a collector for which it couldn’t find any metrics name. Although this can be used generally, this is meant to be used with MultiProcessCollector.

This changes the current behavior of the code but should be somehow safe as it enables filtering in case where it was not working previously. If this is an issue, an alternative approach with an explicit flag could be used (set either in the MultiProcessCollector or in the registry).

The intent here is to allow collecting a subset of metrics from production fastapi servers (running in multiprocess mode). So not having to change the library usage in these servers is advantageous to have filtering work out-of-the-box with this change.

Signed-off-by: Mathias Kende <mathias.kende@mistral.ai>

* Make the new support for collectors without names be explicit.

This adds a parameters to the constructor of CollectorRegistry to allow that new behavior rather than make it be the default.

Signed-off-by: Mathias Kende <mathias.kende@mistral.ai>

* Fix comments

Signed-off-by: Mathias Kende <mathias.kende@mistral.ai>

---------

Signed-off-by: Mathias Kende <mathias.kende@mistral.ai>