[ZBXNEXT-3249] Make documentation more clear for Internal Checks (not supported by proxy) Created: 2016 Apr 18  Updated: 2016 Jul 11  Resolved: 2016 Jul 11

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Documentation (D)
Affects Version/s: 2.2.10
Fix Version/s: None

Type: Change Request Priority: Trivial
Reporter: James Sperry Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: documentation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

While troubleshooting an error on our zabbix server for internal items, I realized that "(not supported by proxy)" actually means that the zabbix server should not be monitored by a proxy.

I was getting the error "Invalid second parameter"

Initially I thought the data for those items could not be collected when monitoring a proxy, so it would be pointless to add those items to a zabbix proxy template.

This assumption was incorrect.

If you could update the documentation more clear here:
https://www.zabbix.com/documentation/2.2/manual/config/items/itemtypes/internal

(also all other versions)

Something like "The Zabbix Server must not be monitored by a proxy in order to get the data." or something along those lines.

I think this would clear up some confusion. In searching for a solution, I found a few forum posts that asked similar questions as to why it was returning "Invalid second parameter"

 Comments   
Comment by richlv [ 2016 Apr 18 ]

it actually means that this item does not collect data about the proxy - there are items that do

Comment by James Sperry [ 2016 Apr 18 ]

Yeah, that's what I thought too. But it was giving me an error when my Zabbix server was being monitored by a proxy.
I switched the server to be monitored by itself and all those items started collecting data.

I switched it back to be monitored by a proxy and the items went unsupported again.

4340:20160418:112522.190 item "<my zabbix server name>:zabbix[process,"proxy poller",avg,busy]" became not supported: Invalid second parameter

Comment by richlv [ 2016 Apr 18 ]

yes - when you assign a host to be monitored through a proxy, all internal items are monitored on the proxy, not the server

Comment by James Sperry [ 2016 Apr 18 ]

That wasn't clear in the documentation. It would be nice if there was a statement outlining these details.

Please point me in the right spot if it was already documented, I didn't see it on the page that was listed in my initial description.

Comment by Aleksandrs Saveljevs [ 2016 Apr 20 ]

It says the following at the top of the page:

Internal checks are calculated either by Zabbix server or by Zabbix proxy, depending on whether the host is monitored by a proxy or not.

Comment by James Sperry [ 2016 Apr 20 ]

I saw that, but it wasn't clear to me that if you want to gather data for items labeled "(not supported by proxy)" then that host must NOT be monitored by a proxy.

This ticket was created as a suggestion; I didn't find the documentation clear enough and had to experiment to find the solution. I was just hoping to spell it out more clearly to avoid future confusion for anyone that ran into the issue that I have.

I don't want to push to hard if you feel this is documented enough, just thought I'd throw it out there.

Thanks.

Comment by Aleksandrs Saveljevs [ 2016 May 02 ]

martins-v, please see whether there is anything we can improve.

Comment by Martins Valkovskis [ 2016 Jul 08 ]

The introductory part of:

has been expanded with more explicit information now.

Thanks for taking the time to report.

Comment by James Sperry [ 2016 Jul 08 ]

Awesome. I think this is great. I say close this ticket now

Thanks.

Generated at Sat Apr 27 06:50:27 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.