This guide describes how to get started with Gloo Mesh Enterprise's out of the box metrics suite.

Gloo Mesh Enterprise is required for this feature.
This feature currently only supports Istio meshes.

Before you begin

This guide assumes the following:

Environment Prerequisites


Each managed Istio control plane must be installed with the following configuration in the IstioOperator manifest.

kind: IstioOperator
  name: example-istiooperator
  namespace: istio-system
        address: enterprise-agent.gloo-mesh:9977
        # needed for annotating Gloo Mesh cluster name on envoy requests (i.e. access logs, metrics)
        GLOO_MESH_CLUSTER_NAME: ${gloo-mesh-registered-cluster-name}
      # needed for annotating istio metrics with cluster
        clusterName: ${gloo-mesh-registered-cluster-name}

The envoyMetricsService config ensures that all Envoy proxies are configured to emit their metrics to the Enterprise Agent, which acts as an Envoy metrics service sink. The Enterprise Agents then forward all received metrics to Enterprise Networking, where metrics across all managed clusters are centralized.

The multiCluster config enables Istio collected metrics to be annotated with the Gloo Mesh registered cluster name. This allows for proper attribution of metrics in multicluster environments, and is particularly important for attributing requests that cross cluster boundaries.

Gloo Mesh Enterprise

When installing Gloo Mesh Enterprise, the metricsBackend.prometheus.enabled Helm value must be set to true. This can be done by providing the following argument to Helm install, --set metricsBackend.prometheus.enabled=true.

This configures Gloo Mesh to install a Prometheus server which comes preconfigured to scrape the centralized metrics from the Enterprise Networking metrics endpoint.

After installation of the Gloo Mesh management plane into cluster-1, you should see the following deployments:

gloo-mesh      enterprise-networking-69d74c9744-8nlkd               1/1     Running   0          23m
gloo-mesh      prometheus-server-68b58c79f8-rlq54                   2/2     Running   0          23m


Generate Traffic

Before any meaningful metrics are collected, traffic has to be generated in the system.

Port forward the productpage deployment (the productpage workload is convenient because it makes requests to the other workloads, but any workload of your choice will suffice).

kubectl -n bookinfo port-forward deploy/productpage-v1 9080

Then using a utility like hey, send requests to that destination:

# send 1 request per second
hey -z 1h -c 1 -q 1 http://localhost:9080/productpage\?u\=normal

Note that you may need to wait a few minutes before the metrics are returned from the Gloo Mesh API discussed below. The metrics need time to propagate from the Enovy proxies to the Gloo Mesh server, and for the Prometheus server to scrape the data from Gloo Mesh.

Enterprise Networking Metrics Scrape Endpoint

The Enterprise Networking deployment exposes its aggregated metrics through an HTTP endpoint at /metrics, formatted as Prometheus metrics. You can view them with the following commands:

# port-forward enterprise networking
kubectl -n gloo-mesh port-forward deploy/enterprise-networking 8080

# request metrics
curl localhost:8080/metrics

These metrics can be consumed by any custom Prometheus server.

Prometheus UI

The Prometheus server comes with a builtin UI suitable for basic metrics querying. You can view it with the following commands:

# port forward prometheus server
kubectl -n gloo-mesh port-forward deploy/prometheus-server 9090

Then open localhost:9090 in your browser of choice. Here is a simple promql query to get you started with navigating the collected metrics. This query fetches the istio_requests_total metric (which counts the total number of requests) emitted by the productpage-v1.bookinfo.cluster-1 workload's Envoy proxy. You can read more about PromQL in the official documentation.

) by (

Enterprise Networking Metrics Retrieval Endpoint

Enterprise Networking also exposes endpoints for retrieving metrics through an API that models the service graph as a set of nodes and edges. A node is a workload in the network that is capable of sending traffic, receiving traffic, or both. An edge consists of a source and target node, representing metrics for requests originating at the source node and targeting the target node.

The /v0/observability/metrics/node endpoint returns metrics by node, and the /v0/observability/metrics/edge returns metrics by edge.

Here are some example queries, assuming that Enterprise Networking is port forwarded to 8080:

This request returns all incoming and outgoing requests for the productpage-v1 deployment, collecting metrics samples spanning the last 5 minutes with a sample for each minute.

curl -XPOST --data '{
  "nodeSelectors": [

        "workloadRef": {
          "name": "productpage-v1",
          "namespace": "bookinfo",
          "clusterName": "cluster-1"

  "window": "300s", "step": "60s"
}' "localhost:8080/v0/observability/metrics/node?pretty"

This request returns all requests originating from productpage-v1 and targeting details-v1:

curl -XPOST --data '{
         "source": {
         "target": {
}' "localhost:8080/v0/observability/metrics/edge?pretty"

For full documentation on the access log retrieval endpoint, see the Swagger specification.