If your cluster uses the Cilium CNI image that is provided by Solo, a few Cilium metrics are collected by default and can be accessed by using the expression browser of the built-in Prometheus server.

To collect more metrics, you can enable the filter/cilium processor on the Gloo telemetry collector agent that is built in to the Gloo telemetry pipeline. This processor collects the following metrics:

  • Cilium and Hubble: By default, all Cilium and Hubble metrics are collected. For an overview of metrics that are collected, see the Cilium documentation.
  • Additional eBPF metrics: The following metrics are collected for traffic that is sent or received by the workloads in your cluster. Note that you must use a Solo distribution of the Cilium image to receive these metrics.
    • ebpf_solo_io_num_conn: The number of connections between workloads.
    • ebpf_solo_io_bytes_sent: The number of bytes that were sent for each workload.
    • ebpf_solo_io_bytes_recv: The number of bytes that were received for each workload.
    • ebpf_solo_io_http_responses: The number of HTTP responses for each workload.

Add all Cilium and Hubble metrics

Enable the filter/cilium processor in the Gloo telemetry pipeline to collect Cilium-specific metrics. All metrics are exposed on the Gloo telemetry collector agent where they can be scraped by the built-in Prometheus. You can view these metrics by using the Prometheus expression browser.

Customize the Cilium metrics collection

Instead of enabling all Hubble and Cilium metrics that the Cilium agent emits, you can customize the Cilium processor and include only the metrics that you want to collect. All metrics are exposed on the Gloo telemetry collector agent where they can be scraped by the built-in Prometheus. You can view these metrics by using the Prometheus expression browser.