ID: 2929
Title: Show all metrics of a service in a nicely formatted table in the service details
Component: Multisite
Level: 1
Class: New Feature
Version: 1.2.7i4
ID: 2941
Title: tinkerforge, tinkerforge.ambient, tinkerforge.humidity, tinkerforge.motion, tinkerforge.temperature: new checks to monitor tinkerforge sensors
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
Tinkerforge is a manufacturer of buildings blocks (include many sensor blocks) that can be combined
and assembled freely. The assembled devices can be connected to via usb, ethernet or wifi.
The current range of checks supports the blocks (so called bricklets) included in the
"Server Room Monitoring"-kit:
- Ambient Light sensor
- Humidity sensor
- Motion sensor
- Temperature sensor
- Master brick
The plugin can also be configured to display sensor readings on the integrated 7-segment display.
ID: 3038
Title: Fixed invalid error message when creating service group assignment rule without having service groups
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.7i4
ID: 3036
Title: Bulk discovery steps are now timing out short before HTTP request timeout
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.7i4
The bulk discovery could cause stability issues by consuming too much resources on
the monitoring server. This could be caused in case the single discovery steps take
longer than the configured timeout of the web server service the Check_MK GUI. In
case a request (discovery step) took longer than the request timeout, the browser
request was timing out and the next discovery step was started while the former
discovery process of Check_MK was still running. If this happened multiple times,
like several hundret times, this could consume all system memory and causing a lot
of CPU load which may result in an unstable monitoring server. Only a restart of
the whole sites web server could fix this situation.
ID: 3037
Title: Terminate datasource programs when check timeout occurs
Component: Core & Setup
Level: 2
Class: Bug Fix
Version: 1.2.7i4
When using datasource programs, e.g. for checking by SSH, the Check_MK
process could be terminated by a reached timeout leaving the launched
subprocesses open. This might have caused in processes being too long
open, running and consuming resources.
The datasource program process and it's sub processes are now cleaned
up when a check timeout occures.
ID: 2986
Title: Event Console: Text elements of events are now correctly quoted in shell scripts
Component: Event Console
Level: 1
Class: Bug Fix
Version: 1.2.7i4
Text elements (message, comment, contact, etc.) of an event may contain <i>'</i> and <i>"</i>.
The previous event console had troubles evaluating these event. Some shell scripts even got stuck..
For example: <tt>TEXT=my"text</tt><br>
Shell script: <tt>echo $TEXT$ > /tmp/mylog</tt><br>
The actual command looks like <tt>echo my"text > /tmp/mylog</tt><br> -> broken command.
ID: 2928
Title: Fix display of rule set Do hardware/software Inventory
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.7i4
When you selected one of the two options for setting the state then
this was correctly saved but not correctly displayed in the rule table
nor when editing the rule again. This has been fixed.
ID: 2457
Title: mssql_counters.sqlstats: New check to monitor several rates from the SQL statistics object
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
ID: 2985
Title: MongoDB: Introduced agent plugin and some checks
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
After installing the mk_mongodb agent plugin on the target system, the following new
checks are available:
<table>
<tr><th>Check</th><th>Description</th></tr>
<tr> <td>mongodb_asserts</td><td>Monitors the rate of various assert types<td> </tr>
<tr> <td>mongodb_connections</td><td>Monitors the number of connections</td> </tr>
<tr> <td>mongodb_collections</td><td>Monitors the collection size</td> </tr>
<tr> <td>mongodb_counters</td><td>Monitors the number of MongoDB operations</td> </tr>
<tr> <td>mongodb_flushing</td><td>Monitors the flush time</td> </tr>
<tr> <td>mongodb_locks</td><td>Monitors the number of locks</td> </tr>
<tr> <td>mongodb_mem</td><td>Monitors the resident, virtual and mapped memory</td> </tr>
<tr> <td>mongodb_replica</td><td>Show replica information </td> </tr>
<tr> <td>mongodb_instance</td><td>Shows instance information</td> </tr>
</table>
Note:
If the MongoDB is running as a replica set most of the agent sections are sent to
a piggyback host named after the replication set. You can find the replica name
in the agent output under <<<<{replicaname}&gr;&gr;&gr;&gr;.
So you need to create a host named {replicaname} and execute a service discovery.<br>
Reason:<br>
A MongoDB replica set consists of n-Hosts. All of these hosts have the mk_mongodb plugin installed.
There is a primary host in this replica set which sends the complete plugin information.
The secondary and arbiter hosts will only send a subset of this data.
Since the primary host might change over time, we cannot put all discovered services on
the current primary host. If the host changes to secondary mode later on, all services
would be gone.