discovr
HTTP service discovery for Prometheus, backed by cloud provider APIs.
discovr exposes one endpoint per provider that returns your running instances in the
http_sd_config format, so Prometheus can
scrape them without a static target list. Provider credentials are never stored: Prometheus passes
them per request as a bearer token, and discovr forwards them to the provider API.
Supported providers:
| Provider | Endpoint | Credentials |
|---|---|---|
| cloudscale.ch | GET /v1/cloudscale-ch |
API token |
| Exoscale | GET /v1/exoscale |
<key>:<secret> |
| CloudStack | GET /v1/cloudstack |
<key>:<secret> |
Targets are returned on port 9100 (the Prometheus
node_exporter default). Instance metadata is exposed
as __meta_<provider>_* labels; use Prometheus relabel_configs to keep the ones you want.
Install
With uv:
uv tool install discovr-ngine
discovr --host 0.0.0.0 --port 8000
Or with the container image:
docker run --rm -p 8000:8000 ghcr.io/ngine-io/discovr:latest
Interactive API docs are then served at http://localhost:8000/.
Configure
All settings are optional and read from the environment or a local .env file.
| Variable | Default | Description |
|---|---|---|
APP_NAME |
Clouds Service Discovery API |
Title shown in the API docs. |
URL_PREFIX |
(empty) | Path prefix, e.g. /api when running behind a reverse proxy. |
HOST |
127.0.0.1 |
Address to bind to. |
PORT |
8000 |
Port to bind to. |
LOG_LEVEL |
INFO |
One of DEBUG, INFO, WARNING, ERROR. |
Use with Prometheus
scrape_configs:
- job_name: cloudscale.ch nodes
http_sd_configs:
- url: "http://discovr:8000/v1/cloudscale-ch"
authorization:
type: Bearer
credentials: <your-cloudscale-api-token>
discovr has no authentication of its own — the bearer token is the provider credential. Run it on
a trusted network, or put it behind a reverse proxy that terminates TLS and restricts access. Use a read-only API token of your provider if possible.
A runnable Prometheus setup is in sample/:
docker compose up
Develop
uv sync # create the virtualenv and install everything
uv run discovr --reload
uv run pytest
uv run ruff check .
uv run ruff format .
License
Metadata
Release files for discovr-ngine 0.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 | |
|---|---|---|---|
| discovr_ngine-0.1.0.tar.gz | 72.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| discovr_ngine-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.5 kB
Release files / discovr_ngine-0.1.0.tar.gz
| Download URL | discovr_ngine-0.1.0.tar.gz |
|---|---|
| Size | 72.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fe4f7c5ad8d163a283818f1b431c181ec0dcc269d0c3ace6bd1f46240a22d1a
|
|
BLAKE2b-256 checksum How to use checksums |
e7b6ac5df6b68741078ec544680ddb958201c9ce0ffaabf4f955c5b599951f1f
|
| 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 Aug 25, 2026.
Transparency logRelease files / discovr_ngine-0.1.0-py3-none-any.whl
| Download URL | discovr_ngine-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8818a8095987a5e5d5c4bad0c3db70bfd99c21487dfcf349c192072028612631
|
|
BLAKE2b-256 checksum How to use checksums |
e747762af624781633c0bd3905ba4506c5f36ef0f0eba49587b53305fe5456f9
|
| 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 Aug 25, 2026.
Transparency log