Bug #53505
open
mgr/dashboard: grafana data source hardcoded for iframe panels
Added by James Page over 2 years ago.
Updated over 1 year ago.
Description
Description of problem¶
https://github.com/ceph/ceph/commit/527f76005cb3
The name of the datasource for grafana sourced dashboards is passed as a parameter; however there is no way to change the name of the datasource being used from the Ceph MGR dashboard side so unless the datasource name matches, grafana based panels at empty.
Environment¶
ceph version string: ceph version 16.2.6 (ee28fb57e47e9f88813e24bbf4c14496ca299d31) pacific (stable)- Platform (OS/distro/release): Ubuntu 20.04
- Cluster details (nodes, monitors, OSDs):
How reproducible¶
Ceph deployed using Juju charms including the Ceph dashboard and Grafana.
Actual results¶
Grafana iframe displayed but with no data (as datasource name != Dashboard1)
Expected results¶
Grafana iframe displayed with data.
- Category set to Monitoring
- Status changed from New to Triaged
- Source set to Community (user)
Hi James,
There are multiple ways to work around this:
- One is renaming the datasource in your Grafana instance to Dashboard1. Is there any reason not to try this one?
- The other one is letting users customize this, but we want to avoid adding more tunables to Ceph, especially for integrations when the other component already provides a way to deal with it.
Can you please share your thoughts on this?
- Status changed from Triaged to In Progress
- Pull request ID set to 44150
Hello, I want to help with this task. How to proceed
Ngwa Sedrick Meh wrote:
Hello, I want to help with this task. How to proceed
Hi Sedrick, I suggested you another task instead (https://tracker.ceph.com/issues/54206 ). Let me know what you think about it.
Hi Ernesto
Ernesto Puerta wrote:
There are multiple ways to work around this:
- One is renaming the datasource in your Grafana instance to Dashboard1. Is there any reason not to try this one?
- The other one is letting users customize this, but we want to avoid adding more tunables to Ceph, especially for integrations when the other component already provides a way to deal with it.
Can you please share your thoughts on this?
I'd prefer to see a configuration option that allows deployers to set the name of the data source - this seems something that is completely deployment specific depending on configuration tools used.
Also available in: Atom
PDF