>
> Alternately publish
> all metrics to prometheus with fsid label then you can auto-filter
> based on the fsid of the ceph cluster since fsid is unique.
>
This is exactly something that we are looking into as we are looking into
providing
the support for multi-cluster monitoring and management
In my case I'm adding a label that is unique to each ceph cluster and
then can filter on that. In my ceph dashboard in grafana I've added a
pull-down list to check each different ceph cluster.
You need a way for me to configure what labels to filter on so I can
match it up with how I
>
> We have 4 ceph clusters going into the same prometheus instance.
>
Just curious, In the prometheus, if you want to see the details for a
single cluster, how's it done through query?
For reference, these are the queries that we are currently using now.
USEDCAPACITY =
Ok, so I tried the new ceph dashboard by "set-prometheus-api-host"
(note "host" and not "url") and it returns the wrong data. We have 4
ceph clusters going into the same prometheus instance. How does it
know which data to pull? Do I need to pass a promql query?
The capacity widget at the
Ah yeah, probably that's why the utilization charts are empty because it
relies on
the prometheus info.
And I raised a PR to disable the new dashboard in quincy.
https://github.com/ceph/ceph/pull/54250
Regards,
Nizam
On Mon, Oct 30, 2023 at 6:09 PM Matthew Darwin wrote:
> Hello,
>
> We're not
Hello,
We're not using prometheus within ceph (ceph dashboards show in our
grafana which is hosted elsewhere). The old dashboard showed the
metrics fine, so not sure why in a patch release we would need to make
configuration changes to get the same metrics Agree it should be
off by
Hi Matthew,
Is the prometheus configured in the cluster? And also the
PROMETHUEUS_API_URL is set? You can set it manually by ceph dashboard
set-prometheus-api-url .
You can switch to the old Dashboard by switching the feature toggle in the
dashboard. `ceph dashboard feature disable dashboard`
