Charm should auto detect the grafana-api-url
Bug #1952962 reported by
Alexander Balderson
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ceph Dashboard Charm |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
When the charm is already related to grafana, it should be able to ask the grafana unit for its api-url.
Generally a user can know the url before the deployment of LMA/ceph-dashboard by using the fqdn for grafana via maas, but it would be nice to not have to configure this option for deployment.
| Changed in charm-ceph-dashboard: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
Revision history for this message
| Liam Young (gnuoy) wrote | #1 |
To post a comment you must log in.
The charm did originally retrieve the grafana api from the its relation with the grafana charm. However, the grafana charm is related to the ceph-dashboard via its website relation ( https:/
Originally the ceph-dashboard assumed that grafana had been correctly configured to use https and automatically set the grafana url to be https but this felt wrong so it is left as a config option that needs to be set manually.
If the above is fixed then the grafana-api-url should still remain as an optional charm configuration option in case the operator needs to set it manually. Since the grafana-api-url manages how the users browser connects to grafana not how the ceph dashboard connects its quite possible for a user to need to access via an external proxy.