Envoy Proxy OpenTelemetry Assets

Envoy Proxy is a high-performance L3/L4/L7 network proxy for cloud-native applications, commonly deployed as an edge proxy, service mesh sidecar, or API gateway. This content pack provides Kibana dashboards, alert rules, and SLO templates for Envoy metrics ingested via the OpenTelemetry StatsD receiver, covering proxy health, downstream traffic and errors, upstream cluster status, memory, and TLS certificate expiry.

The Envoy Proxy OpenTelemetry assets have been tested with OpenTelemetry StatsD receiver v0.146.0 or later.

Envoy tested against:

• Envoy 1.28, 1.29, 1.30

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

Configure Envoy to emit StatsD metrics to the OpenTelemetry Collector. Add a StatsD stats sink to your Envoy bootstrap configuration and point it at the collector's StatsD receiver endpoint:

stats_sinks:
  - name: envoy.stat_sinks.statsd
    typed_config:
      "@type": type.googleapis.com/envoy.config.metrics.v3.StatsdSink
      tcp_cluster_name: statsd_exporter
		

You must also ensure the cluster statsd_exporter (or your chosen name) resolves to the host and port where the OpenTelemetry Collector's StatsD receiver is listening (default UDP port 8125). Envoy emits metrics in StatsD format; the collector aggregates and exports them to Elasticsearch.

Configure the OpenTelemetry Collector or Elastic Distribution of OpenTelemetry Collector (EDOT) with the StatsD receiver and the Elasticsearch exporter. The following example shows a minimal pipeline.

Placeholders:

• <ES_ENDPOINT> — Your Elasticsearch endpoint (e.g. https://my-deployment.es.us-central1.gcp.cloud.es.io:443).
• <ES_API_KEY> — API key or credential for authenticating to Elasticsearch. Prefer ${env:ES_API_KEY} and set the variable at runtime.

receivers:
  statsd:
    endpoint: 0.0.0.0:8125
    aggregation_interval: 60s

exporters:
  elasticsearch/otel:
    endpoints:
      - <ES_ENDPOINT>
    api_key: <ES_API_KEY>
    mapping:
      mode: otel

service:
  pipelines:
    metrics:
      receivers:
        - statsd
      exporters:
        - elasticsearch/otel
		

The StatsD receiver ingests metrics that Envoy emits in StatsD format. Metric names follow Envoy's hierarchical naming (e.g. envoy.cluster.<cluster_name>.upstream_cx_total, envoy.http.<stat_prefix>.downstream_rq_2xx). Refer to the StatsD receiver documentation for receiver configuration, and to Envoy's statistics documentation for metric semantics and naming.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.

← →

×

×

×