Áú»¢¶Ä²©

This is the documentation page for an unsupported version of Áú»¢¶Ä²©.
Is this not what you were looking for? Switch to the current version or choose one from the drop-down menu.

11 What's new in Áú»¢¶Ä²© 1.8.9

11.1 Frontend improvements

Improved performance for event acknowledging.

11.1.1 Updated translations

  • Brazilian Portuguese

11.2 Supported PostgreSQL version changes

  • Support for PostgreSQL 9.1 was added
  • PostgreSQL support changed from 7.0.2 and later to 7.4 and later.

11.3 Áú»¢¶Ä²© daemon improvements

11.3.1 Áú»¢¶Ä²© server improvements

11.3.1.1 Improved log messages

Áú»¢¶Ä²© server log messages about failed checks have been improved. Previously, if a check failed, Áú»¢¶Ä²© server would log messages, similar to these:

Áú»¢¶Ä²© host [monitored host]: first network error, wait for 15 seconds
       Áú»¢¶Ä²© host [monitored host]: another network error, wait for 15 seconds

After 3 failures like these, host would be disabled and a message logged:

Disabling Áú»¢¶Ä²© host [monitored host]

If a host then became available, a log message would say:

Enabling Áú»¢¶Ä²© host [monitored host]

Starting with Áú»¢¶Ä²© 1.8.9, this has been improved. First, messages now tell which specific item key failed, thus allowing to see whether the problem happens with multiple items or just one:

Áú»¢¶Ä²© agent item [proc.num[sshd]] on host [monitored host] failed: another network error, wait for 15 seconds
       Áú»¢¶Ä²© agent item [system.cpu.load] on host [monitored host] failed: another network error, wait for 15 seconds

Additionally, for all failures item type is logged as well (in this case, Áú»¢¶Ä²© agent).

If a host is determined to be unavailable and then available, messages are a bit more verbose now and also include check type:

temporarily disabling Áú»¢¶Ä²© agent checks on host [monitored host]: host unavailable
       enabling Áú»¢¶Ä²© agent checks on host [monitored host]: host became available

And a new message has been introduced if host responds after one or two failures (this was not logged before at all):

resuming Áú»¢¶Ä²© agent checks on host [monitored host]: connection restored

These changes should allow for much easier debugging of connectivity or configuration issues - for example, if all problems on a host would be associated with a user parameter, it would most likely be a performance problem with the executed command.

11.3.1.2 Acknowledge synchronisation in distributed mode

Starting with Áú»¢¶Ä²© 1.8.9 acknowledge status will be fully synchronised from child nodes to master node.

11.3.1.3 Performance improvements

Áú»¢¶Ä²© server performance was improved in some edge cases by skipping value updating for disabled or removed items.

11.3.1.4 Waiting for database to appear upon startup

Starting with Áú»¢¶Ä²© 1.8.9, upon startup Áú»¢¶Ä²© daemons will wait for database to be available. This will help with case when database is started by bootup process before Áú»¢¶Ä²© daemons, but takes long time to become ready.

11.3.2 Áú»¢¶Ä²© agent improvements

Áú»¢¶Ä²© agent daemon performance on AIX was improved by only collecting perfstat data if it is requested.