ID: 5470
Title: Make the number of rrdcached write threads configurable.
Component: WATO
Level: 1
Class: New feature
Version: 1.5.0i2
Thanks to Matthias Hähnel for this patch!
ID: 5568
Title: Fixed breaking report elements when reloading edit page
Component: Reporting & Availability
Level: 1
Class: Bug fix
Version: 1.5.0i2
When opening a report element for editing which e.g. has a context configured
and reloading the page multiple times, the conditions may be modified which
leads to issues when trying to save the element.
e.g. a service could change from "Check_MK" to "{'service': u'Check_MK'}".
ID: 5469
Title: Fixed acknowledgement notifications when RBN is disabled
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.5.0i2
When an ACKNOWLEDGE_{HOST,SVC}_PROBLEM command is issued to the core (via
the GUI or via Livestatus) and rule-based notifications are disabled, the
CMC segfaulted. This has been fixed.
ID: 5567
Title: Scheduled reports can now be stored in the site
Component: Reporting & Availability
Level: 2
Class: New feature
Version: 1.5.0i2
Instead of sending an email with the created report in the scheduled
interval it is now possible to store the just created reports locally
in the site.
This feature is configured in the configuration of the schedule. You
can now choose the action <i>Store locally</i> instead of
<i>Send via Email</i> and configure different action specific things
after this.
Each user allowed to use the report scheduler can open the page
"Scheduler > Stored reports" to view and open all stored reports
available to the user.
All reports are stored below <tt>~/var/check_mk/reports/archive/</tt>.
In the first directory below the base directory each user that creates
such stored reports gets a directory. All stored reports of this user
are saved below this directory. In case the user configures a schedule
to publish the resulting PDFs to other users, the reports are stored
in the <tt>public</tt> sub directory. A schedule can be configured
to store the report either directly in these directories or in a
hierarchy of subdirectories below these parent directories.
You can configure stored reports to be deleted after a given time.
ID: 5352
Title: agent_hivemanager_ng/hivemanager_ng_devices: new special agent and check
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i1
Add the special agent agent_hivemanager_ng and the corresponding check
hivemanager_ng_devices. Together they can be used to monitor devices
in the Aerohive HiveManager NG cloud.
Setup of the special agent is possible via the WATO rule "Aerohive
HiveManager NG". For each device one check is created. The devices
can be configured via the WATO rule "HiveManager NG Devices".
ID: 5480
Title: bdt_tape_info, bdt_tape_status, bdtms_tape_info, bdtms_tape_module, bdtms_tape_status: new checks to monitor tape libraries
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i2
This werk adds new checks for tape libraries that can be monitored based on
the BDTMIB and BDT-MS-MIB mibs. They are used for example in Fujitsu Eternus
LT40 and Fujitsu Eternus LT260 devices, respectively.
ID: 5523
Title: df: Make filesystem types ignored during discovery configurable via WATO
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i2
Previously, the only way to influence the filesystem types to be ignored was by
setting a config variable manually in a file, which would affect the behaviour
globally. Now, this can be configured by a rule, allowing to include e.g. tmpfs
only for certain hosts. Individual mountpoints can also be configured to be
discovered regardless of filesystem type.
ID: 5481
Title: Host-specific Check_MK agent TCP connect timeouts
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i2
The time for TCP connect timeouts of the Check_MK agent
can now be defined on a per-host-basis using the WATO
ruleset "Agent TCP connect timeout".