ID: 3214
Title: Removing SNMP checks for non SNMP hosts and agent based checks for non agent hosts
Component: Core & Setup
Level: 2
Class: Bug Fix
Version: 1.2.9i1
When changing the agent type of a host, for example from Agent to SNMP, vice versa or
from Agent+SNMP to only SNMP it could happen that former discovered services of now
disabled protocols were left assigned to a host leading to still contacting the host
with the disabled protocol. This could only be solved by rediscovering the services
of this host.
This has now been changed to disable the services right after next restart/reload of
the core after changing the agent type.
ID: 3169
Title: Permission/Contact group settings for new hosts did show folder options
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.7i4
When creating a new host in WATO the section <i>Permissions</i> would show
settings that are meant for folders. This has been fixed (when editing an
existing host the correct options were displayed).
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: 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: 2934
Title: all temperature checks rewritten to use the shared temperature api
Component: Checks & Agents
Level: 3
Class: New Feature
Version: 1.2.7i4
Over 100 checks were touched in this update. For most of these
checks it won't be necessary to re-inventorize but once you do,
item names on many checks will change.
Service descriptions have also been normalized but to ease the
transition from existing setups, the old service description will
continue to show on existing installations.
If you have an existing installation and would like to switch to
the new service descriptions you can toggle them in:
Global Settings->Execution of checks->Use new service descriptions
Finally, all temperature checks can now be configured through the
same rule (called "Temperature", who would've thunk) and support the
same features (like configurable unit, support for trend computations,
upper and lower thersholds and so on).
Unfortunately this means that most existing rules for temperature
checks will no longer be applied and disappear from the
Host&Service Parameter list.
Please make sure you carry over all important temperature rules!
You can still see the now deprecated rules through the
button "Deprecated Rulesets" in Host&Service Parameters.
ID: 2902
Title: Hosts can now be added by regular network scans of configured IP ranges
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i4
For each WATO folder a new attribute <i>Network Scan</i> can now be configured.
This network scan will ping all IP addresses in all configured IP ranges in the
configured interval for new reachable hosts / IP addresses.
When such a network scan of a folder discovers a new host, the discovery mechanism
tries to resolve the host name via DNS. If found, it uses the DNS name as hostname.
Otherwise the IP address will be used as host name. Then it will be created as new
host and added to this folder.
Hosts found by the network scan are added as disabled host. You can enable monitoring
of these hosts by setting the <i>Criticality</i> host tag of this host to another
value. Additionally you may want to configure other attributes like the agent type
of this host before adding it to your regular monitoring.
If you want to exclude a found host from your monitoring, add the IP address to the
list of excluded IP addresses and then delete the found host from this folder.
The result of a network scan is written to the <i>Last Scan Result<i> attribute
of a folder. So if you like to know when the last scan for a folder was performed,
take a look at that folders properties.
If you experience issues with the network scan, take a look at the log of the Web GUI
(<tt>var/log/web.log</tt>).
ID: 2826
Title: Disabled BI Aggregations no longer causing crashes when using "Precompile aggregations on demand"
Component: BI
Level: 2
Class: Bug Fix
Version: 1.2.7i4
This fixes the error <i>AttributeError: class DISABLED has no attribute 'lower'</i>, which is shown in
the BI sidebar snapin or written to the file <i>~/var/log/web.log</i>.
Because of this bug most of the aggregation views were empty.
ID: 2882
Title: Reorganize BI configuration into packs, add contacts and permissions
Component: BI
Level: 2
Class: New Feature
Version: 1.2.7i4
The WATO module for configuring Business Intelligence (BI) has been
reorganized. The configuration is now split up into <b>Packs</b>. This has
been made for two reasons:
LI:It makes the configuration of large BI environments easier
LI:It allows to delegate BI configuration to normal users
Each pack contains rules and aggregations. A rule or aggregation in one pack
<b>can</b> refer to rules in another pack.
Each BI pack can have a list of contact groups. A new permission has been
introduced: <i>Business Intelligence Rules and Aggregations</i>. Per default
this is set for normal users. It allows a normal user to configure rules
and aggregations in a BI pack if that user is in one of the listed contact
groups of that pack.
A pack can have the checkbox <i>Allow all users to refer to rules contained
in this pack</i> set. That way a user can use rule from a pack where he is
not a contact for. So the admin can put some basic rules there that can be
used but not changed by other.
Your existing BI configuration will automatically be converted the next
time you use the WATO Bi modul. All existing rules and aggregations will
be put in to one BI pack with the name <i>Default Pack</i>.
ID: 2900
Title: Bulk Host import can now handle CSV files including several host attributes
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i4
The Bulk Host Import feature of WATO could be used for importing a list of host names
before. But more complex imports like adding hosts together with a collection of initial
attributes was not possible.
The import has now been extended that one can upload whole CSV files or paste the contents
of a CSV file into a form. Then, after the upload, a preview page is displayed to configure
the parameters how to parse the CSV file and which column to assign to which host attribute.