ID: 0708
Title: ntp, ntp.peers: avoid DNS lookups in NTP queries and avoid timeouts
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.5i1
The ntpq queries in the various Unix agents now call ntpq with the option
-n. This avoids DNS lookups. Note: the ntp.peers check will then display
IP addresses instead of host names. That check will fail if you do not
have fixed IP addresses.
ID: 0700
Title: arcserve_backup: new check for status of backups in an Arcserve Backup Server
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i1
ID: 0273
Title: Fixed exceptions when modifying / cloning views
Component: Multisite
Level: 2
Class: Bug Fix
Version: 1.2.5i1
This werk fixes several view related problems<br>
<ul>
<li>Modified views no longer vanish in the "Views" sidebar snapin</li>
<li>Fixed attribute inheritance of views</li>
<li>Changing a views name no longer causes exception in the view editor</li>
<li>Nagstamon and dashboard views are now hidden for real</li>
</ul>
ID: 0687
Title: New summary page with all settings of a host
Component: WATO
Level: 3
Class: New Feature
Version: 1.2.5i1
In WATO there is now a new summary page for each host, called <i>Settings
host host...</i>. In this page you can see all of the host's settings that are
determined by rules (via <i>Host & Service Parameters</i>). You will only
see the current setting of each paramter, but also whether it is determined
by one or more matching rules or whether it is the factory default value.
A click brings you directly to the according rule set or even rule. This all
makes it much simpler to get an overview over all <i>effective</i> settings
of a host and also gives you a fast access to each setting.
ID: 0574
Title: if64: check now supports clustering
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i1
If you have a cluster of two or more hosts, and the check is configured
as a clustered service for an interface, the interface with the highest
output traffic is considered the active interface, and only this interface
is monitored and assigned to the cluster. The check denotes from which node
the interface data is taken.
ID: 0268
Title: wato inventory: fixed missing services
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.5i1
If a host had more inventorized services than they were specified in
the global option "Limit the number of rows shown in tables" specified,
the excess services got ignored.
ID: 0265
Title: mpre_include: new local check, allows to include further mrpe configurations
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i1
H1:<b class=new>1.2.5</b> Additional MRPE local check with new features
This version brings the new local check <tt>mrpe_include</tt> where you can
configure additional include files for mrpe and under which user context
the commands of these files are run. It allows non-root users to add additional
mrpe commands without modifying the <tt>mrpe.cfg</tt> file.
You can assign include files to users and define in which user context the commands
should be executed.
This check is configured with the configuration
file <tt>mrpe_include.cfg</tt>. In a default installation this file is located
within the Check_MK config directory under <tt>/etc/check_mk/mrpe_include.cfg</tt>.
The <tt>mrpe_include.cfg</tt> does not contain the new mrpe commands,
though a user name followed by a include path.
Here is an example:
F+:/etc/check_mk/mrpe_include.cfg
# Execute as user ab
ab /etc/check_mk/mrpe_ab_commands.cfg
# Execute as user lm
lm /etc/other/mrpe_lm.cfg
# Execute with no user context change
- /etc/mrpe_default.cfg
F-:
Each line consists of two parameters, the user followed by the include file.
Each command within the include file is executed as this user.
If you do not want to change the user context (default is root), you can set the user to <tt>-</tt>.
The included files have the same configuration syntax as the <tt>mrpe.cfg</tt>.