Navigation :

Debug the Gloo 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. Note that the steps vary depending on the metrics pipeline that you set up during your installation.

Enable port-forwarding of the Prometheus server deployment.

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

Open the scraping endpoints that are configured for the Prometheus server.
```
open http://localhost:9090/targets
```
Check for a green UP state, such as in the following figure.

Figure: Example of green UP state.
Check the following query: http://localhost:9090/graph?g0.expr=istio_requests_total&g0.tab=1&g0.stacked=0&g0.range_input=1h.

If you get an Empty query result from the previous step, debug your metrics pipeline.

Gloo telemetry pipeline
Legacy metrics pipeline

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.

Open the management server dashboard.
```
meshctl proxy
```
In your browser, connect to http://localhost:9091/metrics.
Search for the istio_requests_total metric.
If the search returns no results, debug the Gloo agents.

If you see data returned, check the Prometheus queries.

Get your current Helm values for the management cluster. Change the release name as needed.

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

Delete the first line that contains USER-SUPPLIED VALUES:, and save the file.

Upgrade your Helm release in the management cluster. Include the --set common.verbose=true flag.

helm upgrade gloo-platform gloo-platform/gloo-platform \
   --kube-context $MGMT_CONTEXT \
   --namespace gloo-mesh \
   --version $UPGRADE_VERSION \
   -f mgmt-server.yaml \
   --set common.cluster=$MGMT_CLUSTER \
   --set licensing.glooGatewayLicenseKey=$GLOO_GATEWAY_LICENSE_KEY \
   --set common.verbose=true

Check the logs of the gloo-mesh-ui pod. To view logs recorded since a relative duration such as 5s, 2m, or 3h, you can specify the --since <duration> flag.

meshctl logs ui --kubecontext $MGMT_CONTEXT [--since DURATION]

The logs resemble the following example.

{"level":"debug","ts":1650923640.6589358,"logger":"prometheus-source","caller":"prom/range.go:59","msg":"executing query 
sum(
  increase(
    istio_requests_total{
      workload_id=~\".+.bookinfo-experiments.cluster1|.+.gloo-mesh.cluster1|.+.bookinfo.cluster1|.+.bookinfo-demo.cluster1|.+.bookinfo.cluster2|.+.bookinfo-security.cluster2\",
      destination_workload_id=~\".+..+..+\",
      response_code=~\"[2-3].*\",
      reporter=\"source\",
      # Exclude data from outside the mesh
      workload_id!=\"unknown.unknown.unknown\",
    }[15m]
  )
  ) by (
  workload_id,
  destination_workload_id,
  )
: "}

Review the Prometheus queries for the Gloo UI Graph.
```
open http://localhost:9090/graph
```