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 UI deployment.
If you see a No visible data message in the UI, traffic might not be visible because nodes went idle. Go to the Graph Layouts settings and toggle on Idle Nodes.


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.


- 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 theDEBUG_ENDPOINT_AUTH_ALLOWED_NAMESPACESenvironment variable of your istiod installation. For more information, see the release notes. If you still do not see any data, ensure that traffic metrics are captured for your requests by using the built-in Prometheus server.
Enable port-forwarding of the Prometheus server deployment.
kubectl --context ${context1} port-forward -n gloo-mesh deploy/prometheus-server 9090Open the Prometheus Graph.
open http://localhost:9090/graphIn the Prometheus expression browser, search for metrics, such as
istio_requests_total,gloo_gateway_upstream_rq, andistio_tcp_connections_opened_totaland verify that your requests are captured in metrics. If you get anEmpty query result, follow the steps in Monitor the health of receivers, exporters, and processors to verify that metrics are being scraped by the collector agents and sent to the telemetry gateway.Open the scraping endpoints that are configured for the Prometheus server.
open http://localhost:9090/targetsCheck for a green UP state, such as in the following figure.

Figure: Example of green **UP** state. 
Figure: Example of green **UP** state.
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.
Edit the UI deployment.
kubectl edit deployment gloo-mesh-ui -n gloo-mesh --context ${context1}In the
spec.containers.argssection, enable verbose logging.... spec: containers: - args: - --verbose=true ...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 ${context1}
To keep verbose logging enabled between upgrades, update your Helm values file. 4. Get the Helm values of your current installation.
sh helm get values gloo-platform --kube-context ${context1} -n gloo-mesh -o yaml > gloo.yaml open gloo.yamlAdd the following values to enable verbose logging.
glooUi: enabled: true verbose: trueUpgrade your installation.
helm upgrade -i gloo-platform gloo-platform/gloo-platform \ --kube-context ${context1} \ --namespace gloo-mesh \ --version $GLOO_VERSION \ --values gloo.yamlGet the logs of the Gloo UI pod and look for any error messages or warnings.
kubectl logs <gloo-ui-pod> -n gloo-mesh --context ${context1}
If you cannot find the root cause for data not showing up in the UI Graph, gather a Gloo UI dump and open a ticket with Solo Support.
- Open the Gloo UI. You can connect by using the
meshctlorkubectlCLIs.- meshctl: For more information, see the CLI documentation.
meshctl dashboard --kube-context ${context1} - kubectl:
- Port-forward the
gloo-mesh-uiservice on 8090.kubectl port-forward -n gloo-mesh --context ${context1} svc/gloo-mesh-ui 8090:8090 - Open your browser and connect to http://localhost:8090.
- Port-forward the
- meshctl: For more information, see the CLI documentation.
- 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.
- In the console, enter the following command to get a Gloo UI dump.
window.__DUMP_SWR_CACHE__(); - Enter a name for your Gloo UI dump and click Ok.
- Follow the steps to submit a support request.
- Open the Gloo UI. You can connect by using the