ID: 3150
Title: fixed helpers failing to start and high cpu load when an unparsable local check is installed
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i1
When python fails to parse a check file (local or shipped), the check_mk helpers would produce an
erro message and exit. check_mk would then restart the helper, repeating the process infinitely
which left check_mk in a non-working state, causing high cpu load and quickly growing the cmc.log.
This only occurs when installing syntactically broken checks so most users shouldn't be affected.
ID: 3689
Title: brocade_fcport: now monitors BBcredit zero stats and the number of encoding error or disparity error inside frames received
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.4.0i1
ID: 3687
Title: Hostname translation for piggybacked host: now it's possible to enter any number of regular expressions within this ruleset
Component: WATO
Level: 1
Class: New Feature
Version: 1.4.0i1
Please note: You can add any number of expressions which are executed succesively until the first match.
ID: 3657
Title: Custom host attributes can now be configured
Component: WATO
Level: 1
Class: New Feature
Version: 1.4.0i1
It is now possible to declare custom host attributes (just like for users). By default the
custom attributes are just fields in the configuration GUI which you can use to store
host related values in.
Each of the attributes can be configured to be exported as custom variable to the
monitoring core. In case you do this for a custom attribute, the variable will be available
in the monitoring GUI, in notifications and via raw livestatus for your scripts or 3rd party
tools.
If you create a custom variable "my_custom_variable", it will result in a custom variable
"_MY_CUSTOM_VARIABLE" in the monitoring core.
ID: 3148
Title: fixed Edit View/Dashlet Dialogs offering non-sensical filter choices
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.4.0i1
This is actually two separate but similar bugfixes:
When editing a dashlet that represented a view, the search/context filter offered all possible
filter choices even when they made no sense for the data visualised.
Also, when editing a aggregation group view (and potentially other views), the filter list
offered the same filter option (aggregation group) twice, with different semantics, causing
exceptions if either one of these options was used.