Note: Observability features are available only in enterprise Gloo
No special configuration is needed to use the instance of Grafana that ships by default with Gloo. Find the deployment and port-forward to it:
~ > kubectl -n gloo-system get deployment glooe-grafana NAME READY UP-TO-DATE AVAILABLE AGE glooe-grafana 1/1 1 1 34h ~ > kubectl port-forward deployment/glooe-grafana 3000 Forwarding from 127.0.0.1:3000 -> 3000 Forwarding from [::1]:3000 -> 3000
Grafana can now be viewed at
The admin user/password combo that the default installation of Grafana starts up with is controlled by the helm values
grafana.adminPassword, which are set to
admin/admin by default.
These are read into the
observability pod’s env from the secret
~ > kubectl -n gloo-system get secret glooe-observability-secrets -o yaml apiVersion: v1 data: # by default, these are both the base64 encoded string "admin" GRAFANA_PASSWORD: YWRtaW4= GRAFANA_USERNAME: YWRtaW4= kind: Secret ...
If you create an API key in Grafana, you can make the pod use it instead of basic auth by setting the key
GRAFANA_API_KEY in that same secret and then restarting the
observability pod. If an API key is present, the pod will prefer to use that over any username/password combo that may be set.
If you’d like Gloo to talk to your pre-existing instance of Grafana, there are a few helm values that you’ll need to set at install time. See the code snippet below for the bare minimum, but in general you’ll need to set several values in the
observability.customGrafana object; see a complete list of those fields here
helm install ... \ --set grafana.defaultInstallationEnabled=false \ --set observability.customGrafana.enabled=true # the first --set ensures that the default deployment of Grafana is not created # the second --set tells Gloo to expect to find configuration related to your own Grafana instance