Update Ceph module to support new API #7723
Assignees
Labels
candidate
Candidate to be added to the current iteration
enhancement
Metricbeat
Metricbeat
module
Team:Integrations
Label for the Integrations team
Team:Services
(Deprecated) Label for the former Integrations-Services team
v7.7.0
Comments
andresrc
added
[zube]: Backlog
Team:Services
|
If we want to switch to If we agree to switch to Prometheus endpoint, I need some guidance on deprecating existing implementation |
10 tasks
|
|
|
The existing implementation should be still valid for older versions of Ceph. Newer versions that have ceph-mgr could be handled by a separate metricset.
My recommendation would be to use native APIs wherever possible. |
|
It seems that we responded in the same time... according to what we discussed offline, let's try to stick to native APIs as Prometheus module is not enabled by default. |
|
After talking more with @mtojek about this, it seems that the right way would be to use the mgr's |
|
@sorantis Here are some of them:/mon:/osd: /pool: /server: I'm afraid it might be hard for end-user to conclude the cluster health state and available storage. Apart from that, there is one resource that gives you a valid (but also too deep) information is /perf: Here is a sample: |
|
Just updating the thread. We had a discussion with @sorantis and will go with Sample call/output: |
|
I'm working on the following metricsets (metricset ~ ceph command): mgr_cluster_health ~ The |
This was referenced Feb 8, 2020
|
Module updated to use new API. PRs merged. Resolving. |
|
Hi @mtojek : I'm looking at the cherry-pick for #16254 and I can't find the changes for the mgr_osd_disk. All the other metricset are present except for the mgr_osd_disk. should we fall back to osd_df? |
Hi! It's renamed to |
|
Thank you @mtojek. I must have missed this comment :). |
|
Hi folks, just for you to know: at Ceph project we're planning to deprecate soon the The alternatives would either be the fine-grained Ceph Dashboard REST API (more of a management API, so probably not the best for you) or the Prometheus exporter (which gives you all the metrics in a single shot). |
|
@epuertat thanks for letting us know. We did consider Prometheus exporter earlier, but decided to stick to the native API capabilities. We'll need to revisit this. Which release are you planning to remove the restful API from? |
3 tasks
|
@sorantis: v17 (codenamed Quincy) to be released by first half of 2022. Please let us know if you need any guidance on this. |
|
@epuertat good to know. Any plans to support Prometheus endpoint natively? AFAIK today the user will have to manually enable the exporter via |
|
@sorantis, no plans to change that. The Prometheus exporter is embedded inside a Ceph service. It's probably the reference 'metrics agent' for the Ceph project (others are less maintained, like influx, telegraf, zabbix, ...). The main downside I see there is that it only supports plain-text HTTP, but if you really need HTTPS, it wouldn't be that hard to get that change in [ceph-dashboard sample HTTPS Cherrypy config]. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ceph-rest-apiis replaced byceph-mgrin newer releases http://docs.ceph.com/docs/luminous/mgr/restful/# See #7661 (comment) for additional details.The text was updated successfully, but these errors were encountered: