[ZBX-21773] Missing metrics in Proxy remote monitoring Created: 2022 Oct 17  Updated: 2022 Oct 24  Resolved: 2022 Oct 18

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P)
Affects Version/s: 6.0.9
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Karel Bělunek Assignee: Zabbix Support Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHEL8, standard Zabbix packages

Attachments: File proxy.json     File zabbix_proxy.conf    

 Description   

Steps to reproduce:

  1. Create host that monitors Zabbix 6.0.9 proxy using remote template.
  2. Wait for data, items "Remote Zabbix proxy: Utilization of data sender internal processes, in %" and "Remote Zabbix proxy: Utilization of heartbeat sender internal processes, in %" become unsupported

Result:
I tested JSON output from "Remote Zabbix proxy: Zabbix stats" master item (key zabbix[stats,\{$ZABBIX.PROXY.ADDRESS},\{$ZABBIX.PROXY.PORT}]) and it does not contains data for two forementined Items. Other items in template works well. The JSON content is attached to this ticket. The processes really exists on the proxy and works well, only they missing in remote monitoring JSON
Expected:

JSON master file contains missing metrics and everybody are happy.

 Comments   
Comment by Edgar Akhmetshin [ 2022 Oct 18 ]

Hello Karel,

Which mode of the Proxy is used? Active or Passive? Could you please show configuration file?

Data sender is used in Active mode only.

Regards,
Edgar

Comment by Karel Bělunek [ 2022 Oct 18 ]

Hello Edgar.

 

The proxy is in active mode, config file attached.

The problem afects all my 14 proxies (on each the "data sender" and "heartbeat sender" metric data are missing)

These proxies has been recentry upgraded from 5.0LTS to 6.0LTS using community.zabbix ansible and the selfmonitoring template has been downloaded from GITHUB for 6.0VERSION.

 

 

Comment by Karel Bělunek [ 2022 Oct 18 ]

DOh!

Sorry Edgar,

 

I have just realized that all my 14 proxies have misconfigured {$ZABBIX.PROXY.ADDRESS} macro that points to the Zabbix server itself (127.0.0.1) so instead of proxies I am monitoring central server. And central server does not have nor "data sender" nor "heartbeat sender" metrics

 

Sorry for spent time, I am closing the "issue"

 

Karel B.

Comment by Karel Bělunek [ 2022 Oct 18 ]

Problem has been caused by user misconfiguration on Zabbix Host level - the Zabbix itself works correctly

Generated at Wed Jul 09 12:56:00 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.