Launch the UI

The Gloo UI is served from the gloo-mesh-ui service on port 8090. When you have access to the management cluster, you can launch the Gloo UI from your local machine. You can connect by using the meshctl or kubectl CLIs.

  1. Open the Gloo UI. The Gloo UI is served from the gloo-mesh-ui service on port 8090. You can connect by using the meshctl or kubectl CLIs.

  2. Optional: If authentication is enabled, sign in.
  3. Review the dashboard.

Home

View the health and performance of your Gloo Mesh Enterprise components and Istio workloads by using the Dashboard.

Dashboard

The Dashboard page presents an at-a-glance look at the health of workspaces and clusters that make up your Gloo setup.

In the Workspaces and Clusters panes, you can review a count of the healthy resources, sort by, or search by name for your resources. You can review top-level details about each resource in the resource cards. For more information about workspaces and registered clusters, see the Setup docs.

Figure: Overview page in the Gloo UI
Figure: Overview page in the Gloo UI

Resources

Find an overview of resources that are deployed in your cluster and use the filter options in the Gloo UI to find the resource that you need.

Solo

View the Gloo resources in your Gloo Mesh Enterprise environment, such as policies, workspaces, and route tables. Use the Filter by options to filter the list by resource type. To view the YAML configuration for a resource, click View YAML.

Figure: Solo resources page

Istio

View the Istio resources in your Gloo Mesh Enterprise environment, such as virtual services, gateways, or Istio operators. Use the Filter by options to filter the list by Istio resource type. To view the YAML configuration for a resource, click View YAML.

Figure: Istio resources page

Gateway API

View all Kubernetes Gateway API resources in your environment. For more information, see the Kubernetes Gateway API guide in the Istio documentation.

Kubernetes

View all Kubernetes resources in your cluster, such as services, service accounts, secrets, or cluster roles. Use the Filter by options to filter the list by Kubernetes resource type. To view the YAML configuration for a resource, click View YAML.

Figure: Resources page

Observability

The Gloo UI consumes telemetry data from Prometheus and Jaeger and visualizes this data in the Observability section.

Graph

The Gloo UI includes a Graph page to visualize the network traffic that reaches your service mesh. The graph is based on Prometheus metrics that are collected with the Gloo telemetry pipeline.

Review the following sections to learn more about the Graph layout.

Layout settings

From the footer toolbar, click Layout Settings. Toggle on or off the following settings.

Figure: Graph UI layout settings

Header, filter, and footer toolbars for navigation

Legend

From the footer toolbar, click Show Legend.

Node Types describes the icons that are used for the application “nodes” of the graph. For example, a node might be a Kubernetes service, Istio gateway, external service, or an attached virtual machine (VM). (Note that nodes represent your apps, not Kubernetes compute nodes.)

Node States and Edges show whether a service’s traffic behaves normally or not, as indicated by a color or icon.

Color or iconStateDescription
BlueNormalThe node sends and responds to traffic as expected.
RedDangerThe node has some sort of failure. For example, a policy might be applied to a route that blocks traffic to a service.
YellowWarnThe node has some sort of degraded traffic. For example, a policy might be applied to a route that rate limits traffic to a service. Most of the requests are successful, but some are not.
GrayIdleThe node does not yet accept or send traffic. For example, the deployment might be pending.
Dashed, black lineL7The traffic between nodes is sent over Layer 7 (application). For this traffic, you can apply L7 HTTP/HTTPS Gloo Mesh and Gloo Mesh Gateway policies.
Solid, navy lineL4The traffic between nodes is sent over Layer 4 (transport). You cannot apply Gloo Mesh Enterprise or Gloo Mesh Gateway policies to Layer 4 traffic as these products operate on Layer 7.
Colorful trianglesFailure, Healthy, Degraded, or IdleThe connection is in a state of failure, healthy, degraded, or idle, depending on the color. Try describing the resources in your cluster to troubleshoot further.
Blue lock iconmTLS appliedService isolation is enabled for the traffic, with communication secured via mTLS. You can change service isolation settings via an access policy for a specific destination, or for the entire workspace via the workspace settings.
Istio iconEnforced by IstioThe traffic connection is enforced by Istio, which indicates that you use Gloo Mesh, or Gloo Mesh Gateway for gateway-only connections.
Figure: Graph UI legend

Networking views

Tracing

Gloo Mesh Enterprise integrates with Jaeger as the tracing platform. Jaeger is an open source tool that helps you follow the path of a request as it is forwarded between microservices. The chain of events and interactions are then captured by the Gloo telemetry pipeline and visualized in the Jaeger UI that is embedded on the Tracing page of the Gloo UI. You can use this data to troubleshoot issues in your microservices and identify bottlenecks.

To access the Jaeger UI through the Gloo UI, you must enable tracing in the Gloo telemetry pipeline and instrument your apps to collect traces. If you have an existing Jaeger instance that you want to use to visualize traces, you can configure the Gloo UI to embed the UI of your Jaeger instance. For more information, see Add Istio request traces.

Figure: Tracing UI
Figure: Tracing UI

Logs

You can use the Gloo UI log viewer to see the logs of Gloo components, such as the Gloo management server, the Gloo telemetry collector agent, or the Gloo UI. These logs can help you monitor the health of your Gloo components and troubleshoot issues.

To view logs, use the log viewer filter options to select the cluster, Gloo component, pod name, and, if applicable, the container that you want to check the logs for. You can also use the search capability to find logs that match a specific search term, or download the logs so that you can share them with your team.

Figure: Logs UI
Figure: Logs UI