Updated monitoring-stack #91
Conversation
playbooks/files/grafana.yaml
Outdated
| type: prometheus | ||
| uid: prometheus | ||
| access: proxy | ||
| url: http://kube-prometheus-stack-1735-prometheus.monitoring.svc.cluster.local:9090 |
There was a problem hiding this comment.
I guess it will change but need to test
There was a problem hiding this comment.
Thank you for pointing this out.
Initially, I was facing problem while setting the URL, so I followed this recommendation, and it worked.
But yes, you're right, URL can change because of the suffix (1735). I used the --generate-name option while installing kube-prometheus-stack, as this option adds a unique suffix to the release name.
To avoid this, we can use a fixed release name "kube-prometheus-stack", instead of --generate-name. This will create a consistent service name: kube-prometheus-stack-prometheus
helm install kube-prometheus-stack --version {{ prometheus_stack }} prometheus-community/kube-prometheus-stack --create-namespace --namespace monitoring --values {{ ansible_user_dir }}/kube-prometheus-stack.values
With this, URL will always be:
http://kube-prometheus-stack-prometheus.monitoring:9090 as describe in this kube-prometheus-stack grafana datasource file also
I tried this approach, and it worked.
What this PR does / why we need it?
Install the Prometheus Operator and Grafana Operator instead of a standalone Prometheus and Grafana instance.
The standalone instances does not include important CRDs like servicemonitor ( prometheus-community/helm-charts#3010 ), that is needed to monitor user-defined applications without directly modifying the Prometheus configuration, also absence of these CRDs limits flexibility and stop us to migrate monitoring resources to production environment.
Changes:
This PR #2172 suggests including the Grafana Operator within the
kube-prometheus stackrather than Grafana instance, but the Prometheus community recommends disabling Grafana in the stack and installing Grafana Operator separately.