ID: 0266
Title: windows_agent: now supports mrpe include files
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i1
This version introduces the mrpe configuration option <tt>include</tt>.
With this option you can define addiontal include files and the user domain in
which include files should be executed.
F+:check_mk.ini
[mrpe]
# Run classical Nagios plugins. The word before the command
# line is the service description for Nagios. Use backslashes
# in Windows-paths.
check = Dummy mrpe\check_crit
check = IP_Configuration mrpe\check_ipconfig 1.2.3.4
check = Whatever c:\myplugins\check_whatever -w 10 -c 20
# Additional mrpe configs
# The include files can be changed during the runtime
include \\ab = C:\includes\ab_mrpe.cfg
include \\NT-AUTORITÄT\SYSTEM = C:\includes\system_mrpe.cfg
# If you omit the user the file is executed with the current user
include = C:\includes\default.cfg
F-:
The syntax in the mrpe include file is the same as in the mrpe section, with the exception
that you cannot add further includes in a include file. There is also no need to define a <tt>[mrpe]</tt>
section in an included file. You just need to define the <tt>check</tt> lines here.
F+:ab_mrpe.cfg
check = Dummy mrpe\check_crit
check = IP_Configuration mrpe\check_ipconfig 1.2.3.4
F-:
<b>Important:</b> Keep in mind that the agent needs the permission to run
scripts as other user. Internally it uses the windows command <tt>runas /User:</tt>
which prompts for a password if agent has no permission to change to this user.<br>
In this case the check_mk agent will get stuck!
ID: 0684
Title: New notification variables NOTIFY_LASTSERVICEOK and NOTIFY_LASTHOSTUP
Component: Notifications
Level: 1
Class: New Feature
Version: 1.2.5i1
These two variables have been added to <tt>check_mk_templates.cfg</tt>.
ID: 0683
Title: New column painter for the last time a service was OK
Component: Multisite
Level: 1
Class: New Feature
Version: 1.2.5i1
This information is displayed in the details of a service.
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>.
ID: 0682
Title: Allow overriding of active checks by more specific rule
Component: Core & Setup
Level: 1
Class: Bug Fix
Version: 1.2.5i1
If you define an active Check via WATO in the main folder and then
want to override this check in a subfolder, that was not possible
up to now. Now if you define an active check <b>with the same
type and service description</b> by a more specific rule, then
that rule will override the more general ones (i.e. those
coming later).
ID: 0681
Title: Display correct year for availability range for last month in january
Component: Reporting & Availability
Level: 1
Class: Bug Fix
Version: 1.2.5i1
ID: 0680
Title: Do not allow spaces in host names in event simulator
Component: Event Console
Level: 1
Class: Bug Fix
Version: 1.2.5i1
Spaces are not allowed because that breaks the syslog message format.