[ZBX-6409] Agent.ping with nodata() generate false Alert. Created: 2013 Mar 18 Updated: 2017 May 30 Resolved: 2013 Mar 18 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Agent (G) |
| Affects Version/s: | 2.0.5 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Major |
| Reporter: | Mudassir Zaidi | Assignee: | Unassigned |
| Resolution: | Won't fix | Votes: | 0 |
| Labels: | triggers | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Virtual Machine (VM): |
||
| Description |
|
Agent.Ping (Passive) item is configured on Zabbix Server (2.0.5) with update interval of 60 seconds. The trigger expression is {Hostname:agent.ping.nodata(3m)}=1 Once or twice in a day it generate false Alerts related to nodata for agent.ping. During this time, MySQL's slow query log file shows 20 to 100 sec query time (for rest of the time, MySQL statistics remains at optimum). Its a large scale deployment and false alerts related to Agent.ping nodata() really impacting the response to other alerts. Please suggest some solution. |
| Comments |
| Comment by richlv [ 2013 Mar 18 ] |
|
sounds like a performance issue, not a bug. |
| Comment by Nico MS [ 2016 Dec 07 ] |
|
It happens the same with version 3.2.1 with Windows agents only. It doesn't seem a performance issue because changing timeouts doesn't help either. In Zabbix 2.2 works correctly. I think exists a bad evalution ot the trigger because the agent.ping item is poolling correctly every minute. |