Skip to content
You are viewing the documentation for Solo Enterprise for Istio, formerly known as Gloo Mesh (OSS APIs).

Observability

Page as Markdown
Review built-in and optional observability tools to monitor the health of your sidecar mesh.
Solo UI

Solo UI
 
The Solo UI provides an at-a-glance view of the configuration, health, and traffic in your Istio environment. Key features include a visual service graph with live metrics, a resource overview for all Istio and Kubernetes resources across your clusters, and global service visibility in multicluster setups.
To get started, launch and explore the Solo UI.
Request traces
 
You can configure Istio to send request traces to an external Jaeger instance to observe traffic in your mesh. To get started, enable request traces.
Metrics
 
The Solo UI includes a built-in telemetry pipeline that scrapes Istio metrics from istiod, ztunnel, and waypoint proxy pods, and stores them in ClickHouse. The Solo UI reads directly from ClickHouse to power the service graph and metrics views. You can also connect Grafana to ClickHouse to build custom dashboards, or query ClickHouse directly.
For the list of default metrics collected, see Metrics. For information on querying ClickHouse or connecting Grafana, see ClickHouse data store.
When reviewing metrics for the ambient data path, keep the following in mind.
  • Metrics are per proxy, such as a ztunnel, sidecar, or waypoint. The client is any workload that has Istio ambient data plane mode or is sidecar-injected. For example, a metric might show that a specific client is failing to reach the workload endpoints behind that ztunnel.
  • Both the source reporter and the destination reporter in ztunnel emit metrics. When a request fails, only the source reporter reports metrics; the destination reporter does not. In failed requests, fields such as destination_app and destination_cluster appear as unknown. To determine the intended destination of a failed request, enable tracing.
  • Endpoint health is per-ztunnel. The health status of all endpoints that the ztunnel serves is available in metrics for that ztunnel. For more information, check out ztunnel outlier detection.
  • The response_flags field in the metric indicates the type of failure (for example, CONNECT).
Access logs
 
Leverage the default Envoy access log collector to record logs for the Istio ingress gateway and Istio-enabled workloads in your service mesh. You can then review these logs to troubleshoot issues as needed, or scrape these logs to view them in your platform logging system.
To get started, enable the default Envoy access log collector in your Istio installation.
SecurityUpgrade