OpenTelemetry — Export MonPG Metrics as OTLP
Push MonPG's metrics into your existing observability stack (Honeycomb, Lightstep, etc.).
If you already have an observability platform that consumes OTLP, MonPG can fan out its metrics there so DB stats live next to your service metrics. One pane, no tab-juggling.
What it does
Every MonPG organization can configure an OTLP exporter. When set, every collection cycle's metrics also get pushed to your OTLP endpoint with consistent attribute tags: monpg.org_id, monpg.server_id, monpg.server_name, db.system=postgresql, cloud.provider. This is in addition to the data MonPG keeps in ClickHouse — you don't lose access to the MonPG UI when you turn this on.
Configure
Settings → Integrations → OpenTelemetry → Add exporter. Endpoint goes in (something like https://api.honeycomb.io:443), auth headers (Honeycomb wants x-honeycomb-team: <your-key>; other vendors look similar), pick gRPC or HTTP for the wire protocol, and add any resource attributes you want stamped on every span — most teams set at least service.name=postgres-prod so it shows up sensibly in their existing service catalog.
Tested vendors
We've validated end-to-end against Honeycomb, Lightstep (now ServiceNow Cloud Observability), New Relic via its OTLP endpoint, Datadog via the Datadog Agent's OTLP receiver, and a self-hosted Tempo collector. Anything OTLP-compliant should work — those are just the ones we've personally tested.
What's exported
Per-server metrics from MonPG's catalog at the cycle interval. Query-level metrics are aggregated to the top-N by total_time rather than emitting every queryid we've ever seen — the cardinality would explode otherwise. If you need per-query series in your OTLP backend specifically, that's a paid add-on under Enterprise; the default works for most.