Overview
Gloo Mesh Enterprise comes with several observability tools that help you monitor the health of Gloo, Istio, and Cilium components and the workloads in your cluster.
Gloo Mesh Enterprise health
View the configuration and status of Gloo custom resources, such as the Istio lifecycle manager. You can also view the health of the clusters that are registered with the Gloo management server. To monitor the health of your Gloo Mesh Enterprise components, such as the Gloo management server or Gloo telemetry collector agent, use the Gloo UI log viewer to view, filter, search, or download logs for these components.
Use the Prometheus expression browser to run PromQL queries to analyze and aggregate Gloo Mesh Enterprise metrics. To view metrics that are collected by default, see Gloo management server metrics. To view the alerts that are automatically set up for you, see Alerts.
Quickly see critical metrics and alerts for Gloo Mesh Enterprise components and processes, such as connected workload clusters, Gloo resources that could not be translated, the translation and reconciliation time, or the resource consumption of the Gloo management server and agent pods.
Ingress gateway
View the componts of your gateway setup and the Gloo resources that you applied to them, such as route tables and policies. To monitor the traffic to your gateway, you can access the Gloo UI Graph.
The Gloo telemetry pipeline collects Istio metrics from the ingress gateway proxy and exposes those metrics so that the built-in Prometheus server can scrape them. To view the metrics that are collected by default, see Istio proxy metrics. You can access these metrics by running PromQL queries in the Prometheus expression browser. To find example queries that you can run, see Ingress gateway queries.
You can enable request tracing for the ingress gateway and add these traces to the Gloo telemetry pipeline so that they can be forwarded to the built-in or a custom Jaeger instance. For more information about how to set up tracing, and how to enable Jaeger, see Add Istio request traces.
Leverage the default Envoy access log collector to record logs for the apps that send requests to the Istio ingress gateway. You can review these logs to troubleshoot issues as-needed, or scrape these logs to view them in your larger platform logging system.
Service mesh
View your service mesh workloads and the Gloo resources that you applied to them, such as route tables and policies. To monitor the traffic to your service mesh workloads, you can access the Gloo UI Graph.
The Gloo telemetry pipeline collects Istio metrics from the Istio-enabled workloads and exposes those metrics so that the built-in Prometheus server can scrape them. To view the metrics that are collected by default, see Istio proxy metrics. You can access these metrics by running PromQL queries in the Prometheus expression browser. To find example queries that you can run, see Service mesh workload queries.
You can enable request tracing for Istio-enabled workloads and add these traces to the Gloo telemetry pipeline so that they can be forwarded to the built-in or a custom Jaeger instance. For more information about how to set up tracing, and how to enable Jaeger, see Add Istio request traces.
Leverage the default Envoy access log collector to record logs for the apps that send requests to Istio-enabled workloads in your service mesh. You can review these logs to troubleshoot issues as-needed, or scrape these logs to view them in your larger platform logging system.
Cilium agent and network communication
View health information for the Cilium agent and Cilium network policies that you applied to your workloads. To monitor the traffic to your workloads, such the number of packets that were successfully routed to your app or dropped, you can access the Gloo UI Graph.
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. You can customize the Gloo telemetry pipeline and enable additional Cilium, Hubble, and eBPF-specific metrics that you can query in Prometheus. For more information, see Add Cilium metrics. To find example queries that you can run, see Cilium queries.
Quickly view the health of the Cilium agent and Cilium endpoints that the agent monitors, memory and CPU consumption of eBPF maps, the number of system calls, and any network traffic that is accepted or rejected by Cilium network policies.
meshctl hubble observe command
If your cluster uses the Cilium CNI image that is provided by Solo, you can configure the Gloo telemetry pipeline to collect and expose Hubble network flows for Cilium workloads in your cluster. Then, you can use the meshctl hubble observe command to gain visibility into network and app protocol flows, such as individual TCP connections, DNS queries, or HTTP requests.