zabbix is useless: doesn't perform actions

[rokka]

I've played a couple of days with zabbix and I have to admit that the system is unreliable, badly documented and very hard configurable.

Just an example: there is an item to monitor postfix queue. It shows values BUT not the latest on the graph. Why???

Another example: you should you trigger state = problem to get warning and resolve messages. Try to find it in the documentation...

And more: actions dont' work. I didn't managed to figure out its logic. Here is the example:
item, trigger are defined; values and event are shown up in graph and history but actions is just silent...

Roman Naumenko,
Network Administrator,
Frontline Technologies

[Calimero]

Do the people in the "test" group have at least Read permission on the postfix host ?
What if you send notifications to yourself (zabbix super admin) ?

[simix]

Zabbix is useful and actions work

Yes, for me Zabbix is very useful and actions work fine.

[rokka]

Do the people in the "test" group have at least Read permission on the postfix host ?
What if you send notifications to yourself (zabbix super admin) ?

It doesn't send to superadmin either.

The user test has access to postfix servers.

It's all weird and what's frustrating is that there are no way to determine what causes absence of actions
(I mean the logic is buried in the web-interface, no logging available, no deployment documentation).

[Calimero]

Did you configure at least one media type ?
What if you create a simple Action (no filtering on trigger name, status or other parameters) ?

[rokka]

Did you configure at least one media type ?
What if you create a simple Action (no filtering on trigger name, status or other parameters) ?

Of course I've configured media.

I even managed to get this notification, BUT only for one host in the group.
Look at this: two server are the same, same configs and templates, same group.

Why does actions work for one host and the other one is silent?

host1 -> Linux_mail_server_template
host2 -> Linux_mail_server_template

postfix.trigger -> Linux_mail_server_template
postfix.item -> Linux_mail_server_template

proxy4 -> Linux_mail_server_template Monitored Available

proxy6 -> Linux_mail_server_template Monitored Available

User test gets messages when trigger fires for proxy6 BUT not for proxy4. Events are correct for both hosts.

[rokka]

can somebody confirm this: in action conditions a trigger from the real host (not from template) should be used?

[nms_user]

"confirm: trigger from the real host (not from template) should be used?"
Yep. Did the same error on our UPS-events. Never got a action (message) then.

[rokka]

"confirm: trigger from the real host (not from template) should be used?"
Yep. Did the same error on our UPS-events. Never got a action (message) then.

Thanks for the information
Well it show a great lack of functionality and I would say make zabbix pretty useless.

How else can you monitor particular event on many similar hosts?

It would be interesting ask developers about this

[tighep]

What we did was use the trigger description like instead of the trigger = logic. This works just fine, and is rather easy to setup. To call Zabbix useless is a very broad statement, and I'm sure more than one person would strongly disagree. I would say, more accurately, this is a instance where the learning curve is greater than in other areas.

http://www.zabbix.com/forum/showthread.php?t=12120&highlight=action+template

That thread discusses the same issue.

[rokka]

What we did was use the trigger description like instead of the trigger = logic. This works just fine, and is rather easy to setup. To call Zabbix useless is a very broad statement, and I'm sure more than one person would strongly disagree. I would say, more accurately, this is a instance where the learning curve is greater than in other areas.

http://www.zabbix.com/forum/showthread.php?t=12120&highlight=action+template

That thread discusses the same issue.

tighep, thanks a lot!

It's just what I've been looking for. Actually we managed to figure it out here by ourselves - but you are right, the learning curve is just too steep.

And this is not related to zabbix complicity but because is lack of deployment documentation.
Well, this is understandable since guys from zabbix want to make some money That's ok

Thanks again for everybody - it's resolved.