"Unknown" status in host map

[Murilex]

Devs, please let *Unknown* feature be optional on maps....

I really support this suggestion. It's very annoying see "unknown" triggers stats on maps.

[gospodin.horoshiy]

IMHO, frontend hack would be better....

[maxlock]

I've got rid of the issue for now by performing the following sql

update triggers set status=1 where status=0 and value=2;

However I wouldn't recommend this approach.

-Max

[gospodin.horoshiy]

Devs, please let *Unknown* feature be optional on maps....

[maxlock]

We're seeing the same problem here, and would love a solution. We've got templated hosts, and when disabling all the triggers that are unknown we still get this problem saying there are a number of unknown triggers. I've checked one in particular and I've got current data for the item it depends on?! this is a real pain.

-Cheers Max.

[Zaniwoop]

Almost solved.

I had the same problem and yes, I did have triggers that were "not supported".

I have removed them and in most cases this has solved the problem. However, there are some hosts that still report a number (2 - 18) of unknowns.
All remaining triggers have (latest) data, so they should be happy.

Is there anyway to find out what triggers are still unknown?

Zabbix 1.8.1 on Centos 5.4 (64 bit)

[imarinkovic]

[solved]

Ok,

I found the answer.

The "unknown" status appear by triggers that don't have any item associated (ie: disabled items)

Disabling this triggers to, removes "unknown" statuses

Example:

Trigger: Low number of free inodes on maggie volume /usr
--> In my case, this item was disabled, but no the trigger.

best regards

[brian]

Same problem here:

http://www.zabbix.com/forum/showthread.php?t=15250

[imarinkovic]

In the map section, all hosts appears as "Unknown", but the polling of data is working ok. If a trigger condition is reached, the icon in the map show the problem.

Version 1.8

Any idea?