ID: 8095
Title: Agent bakery now creates .tar.gz files as an alternative for RPM and DEB
Component: agents
Level: 2
Class: New feature
Version: 1.2.6b1
The tarballs are not meant for direct use in the first place. But they are
conventiant of you want to extract some of the baked files with your
own scripts.
ID: 8092
Title: Bake generic and vanilla agent
Component: agents
Level: 2
Class: New feature
Version: 1.2.6b1
The agent bakery used to always create a so called <i>Generic agent</i>. That was
an agent with a default configuration.
Now the bakery per default creates two - possible identical - agents: The <i>Vanilla</i>-agent is
what had been the generic agent. It is an agent without any plugins and with the default
configuration. The <i>Generic</i> agent is an agent with all rulesets being applied that do
not have any positive restrictions. It is the agent for a generic host, i.e. a host that
has no tags and no name. All rules that do not require certain tags to be <i>set</i> or
do require the host to have a certain name are being used. This allows you to create a proper
agent without creating any host at the first place.
ID: 8093
Title: New option for expiration of acknowledgements
Component: cmc
Level: 2
Class: New feature
Version: 1.2.6b1
Acknowledgements can now optionally expire. Multisite has been extended
by an option to set a timespan when acknowledging problems. At the end
of this timespan the acknowledgement is automatically removed and
a log entry created in <tt>cmc.log</tt>. You can see an expiration in the
details views about the comments of a host or service.
Expiration of acknowledgements mean something like "This should be
repaired within time X". In combination with periodic notifications
these acknowledgements will in effect stop the notifications for the
configured while.
ID: 8089
Title: Fix instant reports in views with a context (e.g. one Services of one Host)
Component: Reporting & Availability
Level: 2
Class: Bug fix
Version: 1.2.6b1
In non-global views the instant reports showed always empty tables. This was
due to an invalid set single-context and is now fixed.
ID: 8090
Title: Report scheduler - automatically email reports on a regular base
Component: Reporting & Availability
Level: 3
Class: New feature
Version: 1.2.6b1
The new reporting scheduler allows users to have reports emailed at
regular intervals. The scheduler is available for admins and normal
users. Normal users can only mail reports to themselves.
Currently the schedule can be daily, weekly or monthly, where you
can configure the time of day and the relative day in the week
or month.
The scheduler allows to specify contexts for reports that need
a context. For example you can use the shipped example report
<i>Report of host</i> and specify the host to report about
directly in the scheduler.
ID: 8088
Title: Fix problem with Smart PING packets not being sent (Out of Buffer Space)
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.5i6
This problem has been fixed by splitting up the <tt>icmphelper</tt> into
a <tt>icmpsender</tt> and a <tt>icmpreceiver</tt>. Both processes now do
not need to do any <tt>select()</tt>. The pcap-library can thus be used
in a standard way. Previously it could happen that it did not see all
packets.
ID: 8078
Title: All Linux agent plugins now supported by agent bakery - except ORACLE
Component: agents
Level: 3
Class: New feature
Version: 1.2.5i6
The new agent bakery now supports all official Check_MK agent plugins
for the Linux agent - in the variants RPM and DEB. The only exception
are the ORACLE agent plugins since these are currently being rewritten.
As soon as they are finished, they also will be supported.
ID: 8076
Title: New option cmk --rrd-convert for convertig existing RRDs
Component: config
Level: 2
Class: New feature
Version: 1.2.5i6
This new commanline option for the <tt>cmk</tt> tool will change exising
RRD databases to match the configuration that is done via the WATO rulesets
<i>Configuration of RRD databases of hosts</i> and <i>Configuration of RRD
databases of services</i>. Otherwise changes in these rules applied only on
new RRDs.
You can restrict the conversion to one or several hosts:
C+:
OM:cmk -v --convert-rrds myhost1 myhost2
myhost1:
HOST
- rta....uptodate
- pl....uptodate
- rtmax....uptodate
- rtmin....uptodate
Postfix Queue
- length....uptodate
- size....uptodate
CPU utilization
- user....converted, 376 KB -> 40 KB
- system....converted, 376 KB -> 40 KB
- wait....converted, 376 KB -> 40 KB
[...]
C-:
If you do not specify any hostname, then <b>all</b> RRDs will
be converted.
<b>Note:</b> this new option uses a completely new feature of the RRDTool,
which has been sponsored by Mathias Kettner: RRDTool can now change the
internal structure of RRDs on-the-fly. That way it is now for example possible
to change the range of time or precision that data is being kept.
<b>Note 2:</b> this feature uses an <b>experimental</b> version of
RRDTool. Please make a backup of your RRDs before trying this out.
ID: 8077
Title: New option --split-rrds for --rrd-convert, converts PNP storage type
Component: config
Level: 2
Class: New feature
Version: 1.2.5i6
Check_MK has now a new builtin function for converting legacy-style PNP RRDs
from storage type <tt>SINGLE</tt>, which had been the default for many years,
to <tt>MULTIPLE</tt>, which is the current default since about three years.
<tt>SINGLE</tt> means that all metrics of one host or service are stored
in a single round robin database, whereas with <tt>MULTIPLE</tt> each RRD
does contain only one single datasource.
Performance tests have revealed that - other then one might guess -
<tt>MULTIPLE</tt> is not significantly slower. But it has the advantage
that new datasources can be added on the fly. This is often needed when new
versions of Check_MK introduce new metrics. For that reason Check_MK only
fully supports storage type <tt>MULTIPLE</tt>. When using the Check_MK
Micro Core then you <b>have</b> to convert to <tt>MULTIPLE</tt>, if you do
not want to loose your historic metrics, because the CMC does not support
<tt>SINGLE</tt> at all.
Converting RRDs - essentially splitting them up - can be done with PNP4Nagios'
shipped utility <tt>lib/pnp4nagios/rrd_convert.pl</tt>, but that is a bit
clumsy to use and very slow. If you have thousands of hosts the conversion
can take many days.
For that reason Check_MK now can do the splitting into multiple RRDs during the
process of the RRD conversion. This is not only simpler for you. It is also
much faster because it uses the native C code of the recent RRDTool. This
is how to do the conversion. We assume that you are using Nagios as your
monitoring core:
<ol>
<li>Make a backup of the directory <tt>var/pnp4nagios/perfdata</tt>.</li>
<li>Stop the <tt>npcd</tt>. This avoids RRD updates while the conversion is in progress:
C+:
OM:omd stop npcd
C-:
</li>
<li>Start the conversion. The option <tt>-v</tt> selects verbose output:
C+:
OM:cmk -v --convert-rrds --split-rrds
C-:
</li>
<li>Edit the file <tt>etc/pnp4nagios/process_perfdata.cfg</tt> and
change the storage type:
F+:etc/pnp4nagios/process_perfdata.cfg
RRD_STORAGE_TYPE = MULTIPLE
F-:
</li>
<li>Start the <tt>npcd</tt> again:
C+:
OM:omd start npcd
C-:
</li>
</ol>
<b>Notes:</b>
<ul>
<li>You can specify host names as arguments to <tt>cmk --convert-rrds</tt>. The conversion
will then only be done for these hosts. But when you start <tt>ncpd</tt> again and only
some of the hosts are being converted, then hosts that do not match the storage type
in <tt>process_perfdata.cfg</tt> will loose their RRD data.</li>
<li>The splitting and the conversion to the RRD configuration that is setup via WATO
with the rulesets <i>Configuration of RRD databases of hosts</i> and
<i>Configuration of RRD databases of services</i> will be done at the same time. There
is no way to just split. But the <i>Default</i> configuration of PNP4Nagios and of
WATO for the RRDs is the same, so if you have changed neither, you essentiall will
just split.</li>
<li>Check_MK will <b>not create any backups of any files!</b> Failed modifications, unlucky RRD
configuration and software bugs can lead to data loss. Make sure you have a backup.</li>
</ul>
ID: 8074
Title: Avoid delaying notifications for WARN/CRIT changes during periodic notifications
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.5i6
When you use period notifications and have a hard state change e.g. from WARN to CRIT
then the notification for this state change would be delayed until the next periodic
notification.
This has been fixed. Any non-OK state change will now immediately be notified.
Furthermore any first notification delay will <b>not</b> be applied in that case.