UI graph

If you do not see any data in the Gloo UI graph, review the following steps to debug the metrics pipeline and the Gloo UI deployment.

1. If you see a No visible data message in the UI, traffic might not be visible as nodes might went idle. Go to the Graph Layouts settings and toggle on Idle Nodes.

   

   

2. If you see a No Graph data found message in the UI, no traffic was detected in the timeframe that you selected. Try changing the timeframe and adjust any filters that you added.

   

   

3. If you use Istio versions 1.27.7, 1.28.4, 1.29.0 or later, and you install the Solo Enterprise for Istio management plane into a namespace other than gloo-mesh, you must allow that namespace by listing it in the DEBUG_ENDPOINT_AUTH_ALLOWED_NAMESPACES environment variable of your istiod installation. For more information, see the release notes.

4. If you still do not see any data, ensure that traffic metrics are captured for your requests by using the built-in Prometheus server.

   1. Enable port-forwarding of the Prometheus server deployment.

      kubectl --context $MGMT_CONTEXT port-forward -n gloo-mesh deploy/prometheus-server 9090

   2. Open the Prometheus Graph.

      open http://localhost:9090/graph

   3. In the Prometheus expression browser, search for metrics, such as istio_requests_total, gloo_gateway_upstream_rq, and istio_tcp_connections_opened_total and verify that your requests are captured in metrics. If you get an Empty query result, follow the steps in Monitor the health of receivers, exporters, and processors to verify that metrics are being scraped by the Gloo collector agents and sent to the telemetry gateway.

   4. Open the scraping endpoints that are configured for the Prometheus server.

      open http://localhost:9090/targets

   5. Check for a green UP state, such as in the following figure.

      

      

5. If you confirmed that your requests are captured in Prometheus, enable verbose logging for the UI.

   You can edit the Gloo UI deployment to enable verbose logging. Note that this setting is overwritten during upgrades.

   1. Edit the Gloo UI deployment.

      kubectl edit deployment gloo-mesh-ui -n gloo-mesh  --context $MGMT_CONTEXT

   2. In the spec.containers.args section, enable verbose logging.

      ...
      spec:
        containers:
        - args:   
          - --verbose=true
      ...

   3. Get the logs of the Gloo UI pod and look for any error messages or warnings.

      kubectl logs <gloo-ui-pod> -n gloo-mesh --context $MGMT_CONTEXT

   To keep verbose logging enabled between upgrades, update your Helm values file.

   1. Get the Helm values of your current installation.

      helm get values gloo-platform --kube-context $MGMT_CONTEXT -n gloo-mesh -o yaml > gloo.yaml
      open gloo.yaml

   2. Add the following values to enable verbose logging.

      
      glooUi:
        enabled: true
        verbose: true

   3. Upgrade your installation.

      helm upgrade -i gloo-platform gloo-platform/gloo-platform \
      --kube-context $MGMT_CONTEXT \
      --namespace gloo-mesh \
      --version $GLOO_VERSION \
      --values gloo.yaml

   4. Get the logs of the Gloo UI pod and look for any error messages or warnings.

      kubectl logs <gloo-ui-pod> -n gloo-mesh --context $MGMT_CONTEXT

6. If you cannot find the root cause for data not showing up in the Gloo UI Graph, gather a Gloo UI dump and open a ticket with Solo Support.

   1. Open the Gloo UI.

      meshctl dashboard --kubecontext $MGMT_CONTEXT

   2. In your web browser, open the console. You can typically access the console when you inspect the web page and navigate to the Network tab.

   3. In the console, enter the following command to get a Gloo UI dump.

      window.__DUMP_SWR_CACHE__();

   4. Enter a name for your Gloo UI dump and click Ok.

   5. Follow the steps to submit a support request.