Navigation :

Open the UI

Open the Prometheus UI to start analyzing metrics for your Gloo environment.

Check if the Prometheus server is running in your Gloo management cluster.
```
kubectl get pods -n gloo-mesh --context $MGMT_CONTEXT | grep prometheus 
```
Example output:
```
prometheus-server-647b488bb-wxlzh        2/2     Running   0          66m
```
- If no Prometheus server is set up in your management cluster, you can enable the Prometheus server by upgrading your Helm chart with the following command.
```
helm upgrade --install gloo-platform gloo-platform/gloo-platform \
   --namespace gloo-mesh \
   --version $GLOO_VERSION \
   --values gloo-gateway-single.yaml \
   --set common.cluster=${MGMT_CLUSTER} \
   --kube-context=${MGMT_CONTEXT} \
   --set licensing.glooGatewayLicenseKey=$GLOO_GATEWAY_LICENSE_KEY \
   --set prometheus.enabled=true
```
  Make sure to include your Helm values when you upgrade either as a configuration file in the –values flag or with –set flags. Otherwise, any previous custom values that you set might be overwritten. In single cluster setups, this might mean that your Gloo agent and ingress gateways are removed. To get your current values, such as for a release named gloo-platform, you can run helm get values gloo-platform -n gloo-mesh > gloo-gateway-single.yaml. For more information, see Get your Helm chart values in the upgrade guide.
Open the Prometheus expression browser.
- meshctl
- kubectl
For more information, see the CLI documentation.
```
meshctl proxy prometheus --kubecontext $MGMT_CONTEXT
```
Port-forward the prometheus-server deployment on 9091.
```
kubectl -n gloo-mesh --context $MGMT_CONTEXT port-forward deploy/prometheus-server 9091
```
Access the metrics endpoint.

View metrics and alerts

Refer to the following links to see the metrics and alerts that are available to you: