Monitor GET using Grafana Cloud
Note
Monitoring with Grafana Cloud is required for all GET installations. Professional services will assist you in configuring monitoring for your GET installation.
Metamonitoring for GET is handled by the Grafana k8s-monitoring
Helm chart (>=v2.1). Using Grafana Alloy to collect metrics and logs.
Before you begin
- Helm v3+
- Supported Kubernetes cluster: EKS, AKS, and GKE.
- Existing GET deployment in Kubernetes.
- Grafana Cloud account for metrics/logs storage
Steps
- Add the Grafana Helm Chart, or update if already added. This will be using the K8s-Monitoring-Helm and the
values.yml
file will be to set parameters in the Helm chart.
helm repo add grafana https://grafana.github.io/helm-charts
helm repo update
- Generate
values.yml
.
cluster:
name: enterprise-traces # Name of the cluster, this will populate the cluster label
integrations:
tempo:
instances:
- name: "enterprise-traces" # This is the name for the instance label that will be reported.
namespaces:
- enterprise-traces # This is the namespace that will be searched for tempo instances, change this accordingly
metrics:
enabled: true
portName: prom-metrics
logs:
enabled: true
labelSelectors:
app.kubernetes.io/name: tempo
alloy:
name: "alloy-enterprise"
destinations:
- name: "enterprise-metrics"
type: prometheus
url: "<url>" # URL for prometheus, this can be found under your Grafana Cloud account and should look similiar to "https://prometheus-us-central1.grafana.net/api/prom/push"
auth:
type: basic
username: "<username>" # Username for Grafana Cloud Prometheus
password: "<password>" # Password for Grafana Cloud Prometheus
- name: "enterprise-logs"
type: loki
url: "<url>" # URL for loki, this can be found under your grafana cloud account and should look similiar to "https://logs-prod-us-central1.grafana.net/loki/api/v1/push"
auth:
type: basic
username: "<username>" # Username for Grafana Cloud Loki
password: "<password>" # Password for Grafana Cloud Loki
alloy-metrics:
enabled: true
podLogs:
enabled: true
gatherMethod: kubernetesApi
namespaces: [enterprise-traces] # Set to namespace
collector: alloy-singleton
alloy-singleton:
enabled: true
alloy-metrics:
enabled: true # This will send Grafana Alloy metrics to ensure the monitoring is working properly.
- Install the Helm chart using the following command to create a daemonset that grabs Tempo logs:
helm install k8s-monitoring grafana/k8s-monitoring \
--namespace monitoring \
--create-namespace \
-f values.yml
- View Logs and Metrics
Log into Grafana Cloud. Select metrics drilldown and select cluster=<cluster.name>
where cluster.name is the name specified in the values.yml. Do the same for logs drilldown.