-
Notifications
You must be signed in to change notification settings - Fork 23
Fix Grafana project metrics dashboard [2025.1] #1848
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
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.
Summary of Changes
Hello @Alex-Welsh, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request addresses and resolves issues with the Grafana project metrics dashboard. It updates the Prometheus Libvirt exporter version and modifies the dashboard's JSON configuration to align with the new exporter's metrics and Grafana's updated schema, ensuring accurate and functional project monitoring.
Highlights
- Prometheus Libvirt Exporter Update: The
prometheus_libvirt_exporter
image tags were updated to a newer version (v2.2.0), which introduced changes in metric names requiring dashboard adjustments. - Grafana Dashboard Configuration Updates: The
grafana_project_dashboard.json
file was extensively modified to adapt to the new exporter's metric names (e.g.,libvirt_domain_info_meta
tolibvirt_domain_openstack_info
,project_uuid
toproject_id
,flavor
toflavor_name
). - Grafana Schema and Panel Enhancements: The dashboard's
schemaVersion
was updated, and various panel display options were adjusted or added (e.g.,legend
configuration,maxVizHeight
,barWidthFactor
,hideZeros
), improving the dashboard's functionality and appearance. - Dashboard Title Adjustments: Panel titles for CPU, Memory, and Disk utilization were updated from "per instance" to "per project" to better reflect the aggregated data.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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.
Code Review
This pull request fixes the Grafana project metrics dashboard by updating it to be compatible with a newer version of the Prometheus Libvirt exporter. The changes involve updating Prometheus queries to use new metric and label names, adjusting panel configurations for a newer Grafana version, and adding a release note. The changes are generally correct and improve the dashboard. I've identified a couple of minor issues with legend formatting on two of the panels, which I've detailed in the comments.
etc/kayobe/kolla/config/grafana/dashboards/openstack/grafana_project_dashboard.json
Outdated
Show resolved
Hide resolved
etc/kayobe/kolla/config/grafana/dashboards/openstack/grafana_project_dashboard.json
Outdated
Show resolved
Hide resolved
1d4325f
to
caf59ab
Compare
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.
Works in my AIO< cheers @Alex-Welsh
See also #1843