[ZBX-5376] Discovery seems limited to 8 parallel checks Created: 2012 Jul 27  Updated: 2017 May 30  Resolved: 2012 Aug 06

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D)
Affects Version/s: None
Fix Version/s: 2.0.0

Type: Incident report Priority: Major
Reporter: Raymond Kuiper Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: discovery, networkdiscovery
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS 6.3, MySQL


 Description   

When configuring Discovery rules, I was able to at least add 12 checks.
However, the server doesn't seem to handle more than 8 checks.
This is the maximum amount of checks I see in the monitoring screen for the discovery.

Also, the event monitoring does not list anything for the checks that don't show up.
Subsequently, actions using these checks are not performed.

It seems to me a hard limit of 8 checks per discovery rule is defined.
If that is the case, the frontend should limit the amount of checks that can be defined in a rule.
Otherwise the limit should be removed or raised to the amount that is defined in the frontend (if any).

 Comments   
Comment by Alexei Vladishev [ 2012 Jul 27 ]

Zabbix displays checks discovered for at least one host. If a check is not discovered (for example, no SSH running) for all of your hosts, it will not be displayed at all.

Are you sure there are at least 9 discovered services?

Comment by Raymond Kuiper [ 2012 Jul 28 ]

Hi alex,

Thanks for looking into this.
All the checks I'm missing are tcp port checks.
I know for certain these ports are open. I've verified the ability of the zabbix server to connect to these ports via a nmap scan run on the zabbix server. Other tcp port checks for the same hosts are being found by the discovery rule.

Before going home today, i reduced the number of checks in the discovery rule (I left the missing ones active) to see if Zabbix will now pick thes missing checks up.

I'll post the result of this test on monday.

Regards,

Raymond

Comment by Raymond Kuiper [ 2012 Jul 30 ]

Hi Alex,

After some more testing, I see I've misinterpreted nmap's output, the port is being filtered.
Zabbix is behaving as expected.

Sorry to have bothered you with this, I'll close the ticket.

Comment by Raymond Kuiper [ 2012 Jul 30 ]

Misinterpreted output, not a bug

Comment by richlv [ 2012 Jul 31 ]

let's use this chance to document that

Comment by richlv [ 2012 Jul 31 ]

added a new & page with a note at http://www.zabbix.com/documentation/2.0/manual/web_interface/frontend_sections/monitoring/discovery

Comment by richlv [ 2014 Apr 08 ]

also created a new feature request to show all services always : ZBXNEXT-2244

Generated at Sat Apr 27 03:45:17 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.