Default metrics pipeline

When you follow the get started guide, the default metrics pipeline is set up automatically for you.

1. 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
   

2. 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.

   • gloo-platform chart
   • Legacy charts

   helm upgrade --install gloo-platform gloo-platform/gloo-platform \
      --namespace gloo-mesh \
      --version $GLOO_VERSION \
      --values gloo-gateway.yaml \
      --set common.cluster=$MGMT_CLUSTER \
      --set licensing.glooMeshLicenseKey=$GLOO_MESH_LICENSE_KEY \
      --set prometheus.enabled=true
   

   If you installed Gloo Mesh using the gloo-mesh-enterpise, gloo-mesh-agent, and other included Helm charts, or by using meshctl version 2.2 or earlier, these Helm charts are considered legacy. Migrate your legacy installation to the new gloo-platform Helm chart.

   helm upgrade --install gloo-mgmt gloo-mesh-enterprise/gloo-mesh-enterprise \
      --namespace gloo-mesh \
      --version $GLOO_VERSION \
      --values values-mgmt-plane-env.yaml \
      --set glooMeshLicenseKey=${GLOO_MESH_LICENSE_KEY} \
      --set global.cluster=$MGMT_CLUSTER \
      --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. For more information, see Get your Helm chart values in the upgrade guide.

3. Open the Prometheus UI.