Monitoring guide is broken #2192
Comments
|
Duplicate of #2150 |
|
To fix this we need to add each controller with its own key in the pod monitor. |
|
I can look at picking this up if it's no one else has it on their plate |
|
As for the Kubernetes API req duration, that's gone, we have to delete that graph see #1479 |
@Nalum that would be great, thank you! |
|
Ok now that scraping is sorted, we need to delete the Kubernetes API req duration graph to close this issue. |
grafjo
pushed a commit
to grafjo/flux2
that referenced
this issue
Dec 12, 2021
this release contains the prometheus operator in version 0.52.1 see fluxcd#2192 fluxcd#2193 for issues
grafjo
pushed a commit
to grafjo/flux2
that referenced
this issue
Dec 12, 2021
this release contains the prometheus operator in version 0.52.1 see fluxcd#2192 fluxcd#2193 for issues Signed-off-by: Johannes Graf <graf@synyx.de>
souleb
pushed a commit
to souleb/flux2
that referenced
this issue
Jul 10, 2023
this release contains the prometheus operator in version 0.52.1 see fluxcd#2192 fluxcd#2193 for issues Signed-off-by: Johannes Graf <graf@synyx.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
We're just doing an internal demo and we noticed that the Monitoring guide appears to be broken. The Flux Control Plane dashboard appears on the Grafana deployment as expected, but none of the pods match.
I have a customized version of the manifests from a fork, which could have introduced problems, but we had someone follow along with the instructions from https://fluxcd.io/docs/guides/monitoring/ and they had similar results. Metrics are not being collected from the Flux pods for some reason.
@Nalum found the issue that I was experiencing was not unique to my customized version. I have one custom pod and that pod was scraped successfully for some reason. His installation had zero customized pods and zero pods were scraped.
Steps to reproduce
Follow the monitoring guide. Notice that metrics are not being collected for the flux-system pods as expected.
Expected behavior
Expected to see that Flux control plane was being monitored and metrics are collected. As a double-check, I deleted all the pods in the cluster and allowed them to restart. It didn't change anything.
Screenshots and recordings
OS / Distro
MacOS 12.0.1 (Monterey)
Flux version
v0.24.0
Flux check
$ flux check
► checking prerequisites
✔ Kubernetes 1.21.7 >=1.19.0-0
► checking controllers
✔ helm-controller: deployment ready
► ghcr.io/fluxcd/helm-controller:v0.14.0
✔ image-automation-controller: deployment ready
► ghcr.io/fluxcd/image-automation-controller:v0.18.0
✔ image-reflector-controller: deployment ready
► ghcr.io/fluxcd/image-reflector-controller:v0.14.0
✔ kustomize-controller: deployment ready
► ghcr.io/fluxcd/kustomize-controller:v0.18.1
✔ notification-controller: deployment ready
► ghcr.io/fluxcd/notification-controller:v0.19.0
✔ source-controller: deployment ready
► ghcr.io/fluxcd/source-controller:v0.19.0
✔ all checks passed
Git provider
No response
Container Registry provider
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: