OTLP

OTLP (OpenTelemetry push)

Argus is backend-agnostic at the core; the OTLP adapter pushes the same neutral registry to an OpenTelemetry collector, in addition to the Prometheus pull endpoint. Set otlp_endpoint to enable it; install the extra:

pip install "argus-dpy[otlp]"

Argus(bot, otlp_endpoint="http://collector:4317")

OTLP push is outbound-only: it needs no inbound port, so it's the simplest way to get metrics off a Docker bot panel (Pterodactyl, PebbleHost, Railway) where you can't expose /metrics. See Hosting on bot panels.

Mapping (adapters/otlp.py)

Neutral kind	OpenTelemetry
counter	Counter.add(amount, attributes)
histogram	Histogram.record(value, attributes)
scrape-time gauge	create_observable_gauge(callbacks=[...]) reading the neutral callback at export
info	observable gauge of constant 1 carrying the info as attributes

Labels become OTel attributes (including cluster). Gauges stay pull-based: the observable gauge's callback invokes the neutral gauge callback at export time, so invariant 4 holds across both backends.

Wiring

When otlp_endpoint is set, the cog builds an OTLPAdapter and attaches it to the registry alongside the Prometheus adapter, so every inc/observe/set_info fans out to both. opentelemetry is imported lazily inside _build_meter, so the adapter (and its tests, via an injected meter) work without the dependency installed.

The adapter builds a MeterProvider with a PeriodicExportingMetricReader wrapping OTLPMetricExporter(endpoint=...). Standard OTel env vars (OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_METRIC_EXPORT_INTERVAL, …) apply. The gRPC exporter is the default; the HTTP exporter variant lives at opentelemetry.exporter.otlp.proto.http.

Datadog and friends

Reach Datadog (and most vendors) through their OTLP intake rather than a bespoke client; no core changes are needed.