ID: 0103
Title: services: Fixed bug with service inventory defined in main.mk
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.3i8
There was an error message while inventory when using main.mk based config.
ID: 0018
Title: New option for displaying a legend for the colors used in the timeline
Component: Reporting & Availability
Level: 1
Class: New Feature
Version: 1.2.3i7
The availability has now a new labelling option <i>Display legend for timeline</i>. If this is
enabled and a timeline is being displayed, then at the end of the page a small legend is shown,
which explains all of the possible colors in the timeline.
ID: 0085
Title: brocade_mlx: now handles more different module states
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.3i7
If a module in a Brocade MLX device reports status configured/stacking or
blocked for full height card the check now returns WARN and a meaningful
message (instead of UNKNOWN before)
ID: 0017
Title: local: New state type P for state computation based on perfdata
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.3i7
The section <tt><<<local>>></tt> now allows a new state
marker <tt>P</tt> (next to <tt>0</tt>, <tt>1</tt>, <tt>2</tt> and <tt>3</tt>).
When setting this marker, the check plugin computes the state according to the
levels contained in the performance data. Take the following example:
F+:
<<<local>>>
P Environment temp=30;28;35|humidity=33;40:60;35:70;0;100 This is a text
F-:
The check will first check the variable <tt>temp</tt>. It's current value
is <tt>30</tt>. The levels are at <tt>28</tt> and <tt>35</tt> for warning and
critical, resp. Because 30 is greater then 28 this will trigger a warning.
The second performance value <tt>humidity</tt> has both lower and upper
levels for warning and critical - separated by a colon. The
current value is 33, which is lower than the lower critical level
of <tt>35</tt>. This will make this variable und thus the total check critical.
H2:Notes
<ul>
<li>It is allowed to use fractional values like <tt>35.12</tt>.</li>
<li>If the current value exactly matches a level, the <i>better</i> state is being used. This
is not consistent with the usual levels in Check_MK checks, but is neccessary if you want
to have just one single value to be OK.</li>
<li>When using <tt>P</tt> then the current values of all variables are appended to the plugin output.
If you want you can omit the your additional text at all in that case.</li>
<li>When you use <tt>P</tt> and do not supply performance data or do not supply levels, the
status will always be <b>OK</b>.</li>
</ul>
Example for a <tt>local</tt> line without a text:
F+:
<<<local>>>
P Environment temp=30;28;35|humidity=33;40:60;35:70;0;100
F-:
The output will be:
C+:
Environment CRIT - temp 30.0 > 28.0(!), humidity 33.0 < 35.0(!!)
C-:
ID: 0016
Title: Linux+Windows agent: allow spooling plugin outputs via files
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.3i7
The Windows and Linux agent now have a new feature for sending the contents of
files as a part of the agent output. This is useful for generating monitoring
data asychronously, e.g. by a cron job.
Simply let the job create or update a file in the directory
<tt>/etc/check_mk/spool</tt> (Linux) or in the subdirection <tt>spool</tt>
of the agent directory (Windows). If that directory is missing, simply
create it. The agent will then add the contents of all files contained in
that directory to its output. You can use any filename you like. Just files
beginning with a dot are ignored. This is an easy way to have applications
on the host drop monitoring data into Check_MK. Especially conveniant is
using a local <tt><<<local>>></tt> section here.
If you prefix the file name with a number (e.g. <tt>600MyOutput</tt>
or <tt>3600_app_data.txt</tt>) then that number is interpreted as a
number of seconds. If the last modification of the file is older than
that number, it will be ignored. This will usually set the corresponding
services in the monitoring to <b>UNKNOWN</b>. That way you can make sure
that you will be alarmed if no fresh monitoring data is available.
Here is an example for a spool file using a [check_local|<tt>local</tt>] section:
F+:C:\Program Files\Check_MK\spool\600_foobar.txt
<<<local>>>
0 Service_FOO V=1 This Check is OK
1 Bar_Service - This is WARNING and has no performance data
2 NotGood V=120;50;100;0;1000 A critical check
F-:
ID: 0016
Title: Linux+Windows agent: allow spooling plugin outputs via files
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.3i7
The Windows and Linux agent now have a new feature for sending the contents of
files as a part of the agent output. This is useful for generating monitoring
data asychronously, e.g. by a cron job.
Simply let the job create or update a file in the directory
<tt>/etc/check_mk/spool</tt> (Linux) or in the subdirection <tt>spool</tt>
of the agent directory (Windows). If that directory is missing, simply
create it. The agent will then add the contents of all files contained in
that directory to its output. You can use any filename you like. Just files
beginning with a dot are ignored. This is an easy way to have applications
on the host drop monitoring data into Check_MK. Especially conveniant is
using a local <tt><<<local>>></tt> section here.
If you prefix the file name with a number (e.g. <tt>600MyOutput</tt>
or <tt>3600_app_data.txt</tt>) then that number is interpreted as a
number of seconds. If the last modification of the file is older than
that number, it will be ignored. This will usually set the corresponding
services in the monitoring to <b>UNKNOWN</b>. That way you can make sure
that you will be alarmed if no fresh monitoring data is available.
ID: 0238
Title: vsphere monitoring: new option to skip placeholder vms in agent output
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.3i7
When using a Site Recovery Manager (SRM) some of the virtualmachines are only
used as fallback. The new agent_vsphere option -p allows to suppress any output
regarding placeholder vms.
Right now this option only works when querying a host system.
Placeholder vms are identified by not having an assigned VirtualDisk Device.
The option is also configurable via the WATO rule "Check state of VMWare ESX via vSphere"
ID: 0237
Title: tsm_sessions: fixed invalid check output during backups
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.3i7
The check was unable to handle agent data where no client_name was set.
This could happen during a backup process.
ID: 0015
Title: Fixed summary computation in availability when grouping is used
Component: Reporting & Availability
Level: 1
Class: Bug Fix
Version: 1.2.3i7
In the availability view the summary line was computed wrong in cased
you had more than one group (e.g. by grouping after the service
group). That has been fixed.