Zabbix 1.8 problem with count()

[jean]

Hello,

Before in Zabbix 1.6.*,

this item : net.tcp.port[ldap.domain.com, 389] with this trigger {Linux_t:net.tcp.port[ldap.domain.com, 389].count(600,0,"eq")}>1 was working great.

But now, with Zabbix 1.8, this item are always up, but in the history all value are equal at 1.

Could yo help me please.

[robertmcox]

I confirm the same behavior. I'm using a trigger like this:

({Template_Windows_Symantec_BackupExec:service_sta te[BackupExecAgentAccelerator].count(180,0,"gt")}>5) & ({Template_Windows_Symantec_BackupExec:service_sta te[BackupExecAgentAccelerator].last(0)}#255)

Worked great in 1.6.6. The objective is to allow for the service to be restarted without triggering an event. (Veritas sucks and has to be restarted frequently)

[robertmcox]

There's always more than 1 way to skin a cat...as a workaround, I changed my trigged to:

({Template_Windows_Symantec_BackupExec:service_sta te[BackupExecAgentAccelerator].count(#5,0)}<1) & ({Template_Windows_Symantec_BackupExec:service_sta te[BackupExecAgentAccelerator].last(0)}#255)

[MClark00]

Is there any workaround to this which is time-based? I want to put in a warning trigger which alerts me if data has not been received from a 'Zabbix Trapper' item in the last 30 minutes, and I don't think that can be done by counting the number of data points.

[richlv]

1. original issue has been fixed in 1.8.1 - https://support.zabbix.com/browse/ZBX-1497
2. for time based missing data see nodata() function in the manual