ID: 3449
Title: The host alias can now be used in BI aggregates
Component: BI
Level: 2
Class: New Feature
Version: 1.2.9i1
When matching for hosts in BI aggregations it is now possible to match
hosts with regular expressions by their host alias instead of the host name.
Additionally it is now possible to use the host alias in the titles of the
aggregations.
Instead of using $1$ for matchin the host name or the host alias, you can now
use the variables $HOSTNAME$ or $HOSTALIAS$ to use them in your BI rules.
ID: 3388
Title: Event Console can now process SNMPv3 traps
Component: Event Console
Level: 2
Class: New Feature
Version: 1.2.9i1
The Event Console can now process SNMPv3 traps send with SNMPv3. To be able to receive
the traps, you will have to configure the SNMPv3 credentials to be used for decrypting
the received traps. This can be done in the Event Console configuration using the
option <i>Credentials for processing SNMPv3 traps</i>.
For each sending server you need to configure the credentials and the systems engine ID
which is normally generated automatically by the SNMP device. Some devices also support
setting engine IDs on your own. However, the SNMPv3 specification requires that each
SNMP device has it's own unique engine ID. To be able to decrypt the traps you need to
configure this engine ID together with the other SNMPv3 credentials for each trap sending
device.
ID: 3418
Title: Do not send host notifications if a service group is required
Component: Notifications
Level: 2
Class: Bug Fix
Version: 1.2.9i1
If you set a match condition on the service groups then for host notifications
this condition was ignored. But a host cannot be in any service group so now
if you use this condition then the rule will never match for host notifications.
This should be the way that you expect this.
ID: 3386
Title: AIX agent: Cached local scripts / plugins need to be configured in seconds
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.9i1
When using cached executin of local scripts or agent plugins (putting scripts
in subdirectories named like the execution interval) with the AIX agent, the
directory names were interpreted as minutes which was not consistent with the
other agents.
This has now been changed to be consistently interpreted as seconds. You will
have to rename your directories to the current name multiplied with 60 to
execute the plugins again in the expected interval.
ID: 3027
Title: mtr (Matt's traceroute): New agent plugin
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.9i1
mtr combines the functionality of the traceroute and ping programs in a single network diagnostic tool.
For further information have a look at the mtr manpage.
This plugin collects data for every hop to the destination address and creates a plethora
of performance values for round trip average, package loss and standard deviation.
Keep in mind that services for this new check require quite a large amount of RRD space, due to
the large number of performance values. Roughly ~23MB for 10 network hops to a target destination.
ID: 3396
Title: Change default setting of Precompile aggregations on demand to ON now
Component: BI
Level: 2
Class: New Feature
Version: 1.2.9i1
The global setting {{Precompile aggregations on demand}} improves the
performance of BI in case where not all aggregations are needed at once. This
is especially true for the case of single-host aggregations. This setting
now exists for a long time and we have finally regarded that feature as
stable enough in order to make it the default.
We might remove the setting from WATO totally in future.
ID: 3395
Title: Fix performance issue when many BI aggregations are active
Component: Multisite
Level: 2
Class: Bug Fix
Version: 1.2.9i1
If you have created 1000 or more aggregations and show a view with many
hosts or services than you could get massive performance and memory problems
in your Apache process. The reason is the computation of the BI icon in the
drop down menus of hosts and services. This was only done in order to
check the visibility of the menu itself. The menu is now always visible
and thus the computation is not longer neccessary.
ID: 3394
Title: Availability: Annotations can now be used to reclassify the scheduled downtime status
Component: Reporting & Availability
Level: 2
Class: New Feature
Version: 1.2.9i1
The availability computation of hosts and services now allows to use the
existing {{Annotations}} in order to reclassify the annotated periods as
having been in scheduled downtime or even as not having been in scheduled
downtime. That way you can fix your figures in case one has forgotten to enter
a scheduled downtime in the past or in the case that scheduled downtimes
were just used in order to disable notifications (but the breakdown was in
fact real and not scheduled).
Availability of BI aggregations currently does not support annotations or any
reclassifications. Neither does it honor reclassifications in the underlying
host and service history.
ID: 3328
Title: Default cloned views to be not public
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.9i1
If you create a view as a clone from an existing view than the new view
defaults <b>not</b> to be public. Previously the public-flag was cloned
as well. That could lead into trouble by an admin overriding the views of
others by that way.