New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
helm: Add example dashboards as chart options #23794
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! I'll ping some folks more familiar with the Grafana integration to also take a look at this.
Since you copied the Dashboards from examples
- I think it would make sense to remove them there and update the docs to the new Helm chart options instead. Otherwise we would have to maintain two copies of the dashboards in the tree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since you copied the Dashboards from examples - I think it would make sense to remove them there and update the docs to the new Helm chart options instead. Otherwise we would have to maintain two copies of the dashboards in the tree.
+1, I don't how files in examples
are used (are there any scripts or docs depending on them?), but maintaining two copies of each dashboard should be avoidable.
I'm not sure what's the quality of these "example" dashboards, @tommyp1ckles might have more input on that. If a dashboard is included in a Helm chart, I would expect it to be well-thought with prod usage in mind, not just a dump of metrics. I know such dashboards for Cilium exist, but I'm not sure if that's the case for these examples.
Also a housekeeping note: I left a longer comment in the referenced issue (#21921), but this PR seems to be more directly relevant for another one: #20354
install/kubernetes/cilium/templates/cilium-agent/dashboards-configmap.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! The change looks good to me.
The quality of these dashboards is an open question, but if better dashboards exist they can be commited separately. Same about the dashboards duplication (it seems that hubble-l7-http-metrics-by-workload.json
is already in both places, so this PR is not introducing duplication; but it should be resolved, especially if the examples are actually used my some scripts or docs).
Would dropping soft links in the examples directory work for now? That would preserve the paths for evaluation by folks who use them. PR updated with links |
@jcpunk One more thing, when you update the Helm values you need to update the Helm values docs too:
I think that would be it, can you commit the generated docs changes? I hope switching to symlinks in |
.... I've got to be doing something wrong here:
|
nope, my typo, |
Any guesses on:
I've given you merge rights to my repo if my local system is just too wonky.... |
@jcpunk I don't know, |
I think I got it to run... the files changed at least. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me now.
There are some more dashboards in a Grafana mixin btw: https://github.com/grafana/jsonnet-libs/tree/master/cilium-enterprise-mixin/dashboards The dashboards here should be updated too at some point, but not necessarily in this PR.
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I've left some more feedback
/test Job 'Cilium-PR-K8s-1.25-kernel-4.19' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! One last typo
Updated and rebased |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Some more documentation nits, and then this should be good to go I think!
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
/test |
Seems like there are still some issues with the generated code: https://github.com/cilium/cilium/actions/runs/4294347264/jobs/7484211056
|
I think I've got it sorted... |
/test |
The issue seems to persist unfortunately. Locally, I can fix it via |
That is strange... I've run that by hand and hopefully that helps. |
Looks good now! |
/test Job 'Cilium-PR-K8s-1.16-kernel-4.19' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment |
@tommyp1ckles Ping for review |
They appear similar to the other Isovalent dashboards here: https://grafana.com/orgs/isovalent/dashboards. Not 100% sure what the relationship is. Overall they're ok, for basic use cases but some obvious flaws jump out (same issues as the linked ones):
Anyway, changes LGTM 🙏 |
I'm marking this ready to merge. There are a newer test suites which weren't part of the branch when this PR was opened, so those can be ignored. The other test failures are unrelated:
|
@jcpunk I think there is a bug in this PR. There is
While the dashboard are in files/cilium-agent/dashboards. Could you fix this? |
#24733 opened |
With this patch, helm users can enable reporting on their clusters with example grafana dashboards.
These dashboards were copied from
examples/kubernetes/addons/prometheus/files/grafana-dashboards/
Fixes: #21921