Discussion thread for official Zabbix Template Ceph

[iwik.sk]

I was searching how to monitor ceph in proxmox and found two ways.
First is zabbix module in ceph, seems to be working, but in documentation it is marked as deprecated.
Other option is zabbix-agent2 working using rest module and this template - but this is no win either - rest module in ceph is also deprecated - and it is not mentioned here in thread!

https://tracker.ceph.com/issues/68803#note-5

https://github.com/ceph/ceph/commit/96ec7badb8534b812bbcae20eb411304900c0d0c

https://support.zabbix.com/si/jira.issueviews:issue-html/ZBXNEXT-9402/ZBXNEXT-9402.html

[tompaah]

I have the exact same problem as this post from 2024

https://www.zabbix.com/forum/zabbix-help/495011-ceph-by-zabbix-agent-2-empty-result

All checks done by zabbix_get or the Zabbix server return

ZBX_NOTSUPPORTED: Empty result

except ceph.ping that returns

0

.

There really isn't much help in the zabbix_agent2.log, this is about what it says at loglevel=5

2026/01/21 15:12:13.710861 received passive check request from "{\"request\":\"passive checks\",\"data\":[{\"key\":\"ceph.ping[https://cephdash.mydomain:443,user,pass\",\"timeout\":30}]}": "10.0.0.210"
2026/01/21 15:12:13.710946 [1] adding new request for key: 'ceph.ping[https://cephdash.mydomain:443,user,pass]'
2026/01/21 15:12:13.710956 [1] created direct exporter task for plugin 'Ceph' itemid:0 key 'ceph.ping[https://cephdash.mydomain:443,user,pass]'
2026/01/21 15:12:13.711000 executing direct exporter task for key 'ceph.ping[https://cephdash.mydomain:443,user,pass]'
2026/01/21 15:12:13.719131 executed direct exporter task for key 'ceph.ping[[https://cephdash.mydomain:443 user pass]'

The /etc/zabbix/zabbix_agent2.d/plugins.d/ceph.conf contains

Plugins.Ceph.InsecureSkipVerify=true
Plugins.Ceph.KeepAlive=300
Plugins.Ceph.Timeout=30

I have verified that the Ceph API works by using a REST client (Insomnia) directly to it, using the same URI and authentication I try with Zabbix.
It is able to authenticate and pull data successfully with the REST client.

Requests to the Ceph API go through a proxy server so I can see what requests the Zabbix Ceph module is trying to do. Here's what it sends

10.0.0.210 - user [22/Jan/2026:17:03:33 +0100] "POST /request?wait=1 HTTP/1.1" 404 137 "-" "zbx_monitor"

Note that the request is to an URL "/request?wait=1", this is not a valid URL at the Ceph API.
Correct requests should be done to the "/api" endpoint, like what the log says when I'm authenticating and listing cephfs instances with Insomnia

192.168.1.22 - - [22/Jan/2026:17:07:10 +0100] "POST /api/auth HTTP/1.1" 201 1351 "-" "insomnia/12.2.0"
192.168.1.22 - - [22/Jan/2026:17:07:04 +0100] "GET /api/cephfs HTTP/1.1" 200 2356 "-" "insomnia/12.2.0"

Using Ceph 20.2.0 and Zabbix 7.4.6.

EDIT:
Okay so I finally found the problem, it's the incompatibility with Zabbix Agent2 and current versions of Ceph, where Ceph removed a function that was long announced to be deprecated. There is no solution to this except to wait for a new release (8) of the Agent2.

https://support.zabbix.com/si/jira.issueviews:issue-html/ZBXNEXT-9402/ZBXNEXT-9402.html