From 379de21dfde620b06343aa223661ec22c9cf9f0a Mon Sep 17 00:00:00 2001 From: Christian Simon Date: Tue, 10 Dec 2024 13:57:30 +0000 Subject: [PATCH] fix(docs): Make sure helm Grafana example works as expected. (#3753) The problem with the grafana helm is that we don't have the profiling port exposed as part of the containerPorts of the container. So I had to reuse/abuse the gossip-tcp port in order to get it to be scraped. It also was using the wrong annotation of "pyroscope.grafana.com" instead of "profiles.grafana.com". Fixes #3523 (cherry picked from commit 6045daac6c70d48e4393acf7259d028ea246072b) --- docs/sources/deploy-kubernetes/helm.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/sources/deploy-kubernetes/helm.md b/docs/sources/deploy-kubernetes/helm.md index 4565a017d4..33bcc802b5 100644 --- a/docs/sources/deploy-kubernetes/helm.md +++ b/docs/sources/deploy-kubernetes/helm.md @@ -128,9 +128,13 @@ Use a custom namespace so that you don't have to overwrite the default namespace --set env.GF_AUTH_ANONYMOUS_ORG_ROLE=Admin \ --set env.GF_DIAGNOSTICS_PROFILING_ENABLED=true \ --set env.GF_DIAGNOSTICS_PROFILING_ADDR=0.0.0.0 \ - --set env.GF_DIAGNOSTICS_PROFILING_PORT=6060 \ - --set-string 'podAnnotations.pyroscope\.grafana\.com/scrape=true' \ - --set-string 'podAnnotations.pyroscope\.grafana\.com/port=6060' + --set env.GF_DIAGNOSTICS_PROFILING_PORT=9094 \ + --set-string 'podAnnotations.profiles\.grafana\.com/cpu\.scrape=true' \ + --set-string 'podAnnotations.profiles\.grafana\.com/cpu\.port=9094' \ + --set-string 'podAnnotations.profiles\.grafana\.com/memory\.scrape=true' \ + --set-string 'podAnnotations.profiles\.grafana\.com/memory\.port=9094' \ + --set-string 'podAnnotations.profiles\.grafana\.com/goroutine\.scrape=true' \ + --set-string 'podAnnotations.profiles\.grafana\.com/goroutine\.port=9094' ``` For details, see [Deploy Grafana on Kubernetes](/docs/grafana/latest/setup-grafana/installation/kubernetes/).