Integration · Web & proxy

Envoy

Cluster health, upstream RTT, retry budget.

What gets collected

The admin endpoint /stats/prometheus. xDS observability is supported via an ALS sink.

Requirements

  • Envoy admin :9901
  • /stats/prometheus
  • ALS sink (optional)

Key metrics

Collected out of the box. Every metric is available in dashboards, alerts and PromQL.

envoy.cluster.healthenvoy.upstream.rttenvoy.retry.budgetenvoy.downstream.5xxenvoy.conn.active

Setup steps

  1. 1admin.address: 0.0.0.0:9901
  2. 2stats_sinks with the unimoni grpc endpoint

After install

  • · Metrics show up on the dashboard within 15-30 seconds
  • · Integration labels flow into filters automatically
  • · Dashboard presets for common metrics are available in the editor
More in the docs
Envoy
Open the guide →

Frequently asked questions

What does Unimoni collect from Envoy?
Cluster health, upstream RTT, retry budget. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across Envoy and everything else in one place.
How long does it take to connect Envoy?
Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
What access does the Envoy integration need?
Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
Is Envoy monitoring available self-hosted and on the free plan?
Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.

Similar integrations