In most cases, we are not interested in frequent messages like "Processor load is higher than 5". Brief pikes are always expected and normally do not indicate any serious problems.

Our original trigger is:

{host:system.cpu.load[all,avg1].last(0)}>5

How to make this trigger less sensitive?

Let's take advantage of a time period:

{host:system.cpu.load[all,avg1].min(600)}>5

The trigger will fire up if the processor...

I am very happy 1.6 is out. It seems to be a very successful release, which supports a number of highly anticipated features.

We have some issues with 1.6 though, all of them are being tracked and fixed in a very fast manner. There is a great chance that 1.6.1 will be ready within next week with all known problems fixed.

It's time to have some rest and start thinking about 1.8.

By the way, we are moving to a new office in October! More room to grow for ZABBIX...

The short of it is I have 2 applications I have to monitor. They are both proprietary and very difficult to work with in terms of getting data in and out. Another problem is that they tend to lock up so monitoring to see if the process is running isn't fool proof.

Since these are "critical" applications they fortunately have really good logging that is very verbose (70-100 lines to the log file every second). Unfortunately it tends to overwhelm Zabbix and push the limits....

ZABBIX already has a limited set of nice icons for the usage in maps. But I'd liked to have a more sophisticated set of icons and have startet on it.

Here are some examples of it:



The main goals I'd like to implement are the following:

• Different icons for each trigger state
• Differentiate generic and specific icons
• Indicator for the type of device
• Indicator for the OS
• Indicator for the manufactor

...

It is some suggestion for ubuntu users to move to new zabbix 1.6: new user or old ones.

for new user, intsll these packages by apt-get:

sudo apt-get install zabbix-agent zabbix-frontend-php zabbix-srver-mysql.

Now stop the running service:

/etc/init.d/zabbix_agent stop
/etc/init.d/zabbix_server stop

Then u should make the new zabbix and install them in another place:

./configure --prefix=/usr/local/zabbix...