Comment 3 for bug 1929262

After updating and rebooting an entire cloud, I see that there's an issue with client.prometheus-ceph-exporter using an old client with the insecure global_id reclaim.

Adding prometheus-ceph-exporter charm to this bug.

Ultimately, if all you see is that client alerting in 'ceph health detail' such as:
$ sudo ceph health detail
HEALTH_WARN client is using insecure global_id reclaim; mons are allowing insecure global_id reclaim
[WRN] AUTH_INSECURE_GLOBAL_ID_RECLAIM: client is using insecure global_id reclaim
    client.prometheus-ceph-exporter at v1:10.0.0.123:0/2623829913 is using insecure global_id reclaim
[WRN] AUTH_INSECURE_GLOBAL_ID_RECLAIM_ALLOWED: mons are allowing insecure global_id reclaim
    mon.juju-e75ae8-5-lxd-0 has auth_allow_insecure_global_id_reclaim set to true
    mon.juju-e75ae8-4-lxd-0 has auth_allow_insecure_global_id_reclaim set to true
    mon.juju-e75ae8-3-lxd-0 has auth_allow_insecure_global_id_reclaim set to true

I suggest adding relation between prometheus:target and ceph-mon:prometheus to start capturing ceph stats from ceph-mon directly, and then removing application prometheus-ceph-exporter and then running the command:

    ceph config set mon auth_allow_insecure_global_id_reclaim false

lp#1912557 is tracking the need to add dashboards compatible with ceph-mon's built-in exporter for grafana to display the new data.