Comment 1 for bug 1952962

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://git.launchpad.net/charm-grafana/tree/src/metadata.yaml#n19 ). This relations uses the http interface which does not support telling the client which protocol to use (http or https). ceph-dashboard requires that grafana be using https (otherwise iframes do not work as its a mix of http and 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.