Issues fetching port item data through the Zabbix plugin for Grafana

Grafana Dashboards
1

Hello!

Here at the company, I have a Zabbix-Server 6.0 installed on a VM and a Grafana 10.4.5 on another VM using the Zabbix Plugin for Grafana in the latest version (4.5.2).

I have created some dashboards that are perfectly monitoring various items from my Zabbix-Server, but I am facing difficulties when trying to display in Grafana any item that monitors a port, for example, the item that monitors the status of the Zabbix-Proxy service on port 10051, which uses the key net.tcp.service[tcp,{$PORTA_1_1}]. All of them return “no data” in Grafana, even though the Zabbix-Server is collecting everything normally.

I have another VM with Grafana 7.2.0 and the plugin version 3.11.0, where the above situation does not occur. Everything works normally.

As an alternative, I created a script on the Zabbix Proxy machine that checks the status of the zabbix-proxy service and returns 0 (down) or 1 (up), and I configured a UserParameter to send the information to the Zabbix-Server. This way it works, and Grafana gets the value correctly.

Both items return the same value, in this case, 1 (integer), but one is “seen” by Grafana and the other is not.

I have already done various searches and tests, but I couldn’t find a solution other than the UserParameter.

Does anyone have any idea what I could do to fix this? Or if it might be some kind of plugin bug?

Thanks for the help!

2

I think there might be a version incompatibility between the plugin and the Zabbix Server, or between Grafana and the Zabbix Server. I tested with the same type of item using the same Grafana setup but with the Zabbix Server 6.4 that we finished setting up yesterday, and the collection worked perfectly. After conducting more tests, I’ll update the topic.

3

Guys, I’ve come to a conclusion from my tests.
Grafana (or the plugin) can’t fetch data when the item has a macro in its name.
Here are the tests I conducted:
Captura de tela 2024-07-12 105405

So, does anyone have any suggestions?
From what I’ve seen in my research, it’s probably an issue with the plugin, and we just have to wait for a new release with the fix, right?

I just wanted to know if anyone else had a similar issue or if it’s something specific to my environment.
Anyway, here’s the topic in case someone searches for it in the future.
Cheers!

4

Well, since I managed to work around the issue, I’ll close the topic. But at least there’s a record of the problem in case someone else encounters it.
I believe it is indeed related to the plugin, so let’s wait for an update to fix this.
Best regards.

5

I would post that question here

1 Like