ID: 0597
Title: dell_chassis_slots: new check to monitor the status of the blade slots of the Dell Poweredge Blade Servers
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i1
ID: 0596
Title: dell_chassis_status, dell_chassis_temp, dell_chassis_kvm, dell_chassis_io, dell_chassis_fans: new checks to monitor the overall status of various sections of the Dell Poweredge Chassis via CMC
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i1
ID: 0595
Title: dell_chassis_power, dell_chassis_powersupplies: new checks for Dell Poweredge Chassis Ppower consumption
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i1
These checks measure the overall power consumption of the chassis of the Dell Poweredge Blade Server
as well as the power consumption of the individual blade nodes as given by the Dell Chassis Management
Controller (CMC)
ID: 0144
Title: enterasys_cpu_util enterasys_powersupply: New Checks for CPU Utilization and Power Supplies on enterasys switches
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i1
ID: 0706
Title: EMC VNX: special agent can alternatively authenticate via security files
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i1
If you leave user name and password empty, the special agent tries to
authenticate against the EMC VNX device by Security Files.
These need to be created manually before using. Therefor run as
instance user (if using OMD) or Nagios user (if not using OMD)
a command like
<tt>naviseccli -AddUserSecurity -scope 0 -password PASSWORD -user USER</tt>
This creates <tt>SecuredCLISecurityFile.xml</tt> and
<tt>SecuredCLIXMLEncrypted.key</tt> in the home directory of the user
and these files are used then.
ID: 0733
Title: mem, solaris_mem: now able to configure amount of free memory
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i1
You can now configure the levels of free memory via WATO.
ID: 0749
Title: Allow to restrict visibility of events by their host contacts
Component: Event Console
Level: 2
Class: New Feature
Version: 1.2.5i1
The Event Console has now two new permissions:
<ol>
<li>See all events</li>
<li>See events not related to a known host</li>
</ol>
Both permissions default to <i>yes</i> in all roles. If you remove the <i>See all events</i>
permission then a user can only see events for hosts that either he is a monitoring contact for
or that are not known to the monitoring at all (i.e. no host with such a name or IP address
is configured as monitored host in your monitoring core). The visibility of the later
ones can be switched off with the second permission. The second permission is only relevant
if <i>See all events</i> is set to <i>no</i> - of course.
Furthermore you can now assign <i>Fallback Contact Groups</i> to an event. This
is done with a new rule option in the section <i>Outcome & Action</i>. As
soon as you assign contact groups these will be assumed for all hosts
that are not in the monitoring. That groups will be attached as an additional information
to each event created with that rule. These events will then be handled like as if the
host is known to the monitoring when it comes to the visibility.
ID: 0748
Title: Also custom views now have permissions
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.5i1
In that past only builtin views had permissions that you could disable in a
role and that way remove those views for certain users. Now this also works
for custom views - i.e. views that a user has created with a new unique name
and and that is published for other users.
Please note that regardless of a view's permission the owner of the view can
always see it. If you do not like this you can remove the permission for
creating custom views.
The default for new views is still that all roles have the permission for
this view.