New concept of definition of trigger actions in beta5

[disparo]

Guys, it really sucks!

A heap of text... It's really difficult to explore this page on gprs connection.

And absolutely no filtering possibility neither by host, nor group!

What about turning back of previous style of action configuration or making ability to choose between old or new scheme?

[disparo]

PS :

much more flexible definition of trigger actions in one screen.

if i defined about 350 trigger's actions and all of it displays on one page, which flexibility we're talking about?

[Alexei]

I agree that the page may not be very friendly if one has plenty of already defined actions. Some filtering must be provided. However use of macros can greatly reduce number of actions. Don't define actions one per each trigger. Define them one per host or even per host group.

[ruckus37]

Mabye have only alerts sent to your gprs connection! browsing any webpage even google takes it's time on a 56k line, do not expect extreme wonders from zabbix! Try to look at avents sent to a mailbox with a gprs connection otherwise a 3g connection.

Guys, it really sucks! is an imature way of trying to solve a problem!!!! zabbix owns

[disparo]

However use of macros can greatly reduce number of actions. Don't define actions one per each trigger. Define them one per host or even per host group.

So... I need to monitor checksum of log-files for a subject of service crash.

I have such triggers on all hosts of my platform, but it is necessary to see host's name in subject of each letter to know which host in down exactly! How can i do it?

And... During editing of defined action it's impossible to remove conditions defined. It's a bug, i guess...

And i think it will be a great idea for me to roll back to beta4... Beta5 is too poor, unfortunately

[Alexei]

I have such triggers on all hosts of my platform, but it is necessary to see host's name in subject of each letter to know which host in down exactly! How can i do it?

Use macro {HOSTNAME} or {IPADDRESS}.