ID: 8010
Title: New option for sending performance data to graphite
Component: cmc
Level: 2
Class: New feature
Version: 1.2.5i1
The Micro Core has now a new option (to be configured in the global
settings via WATO) for sending the performance data (in addition) to an
already existing Graphite installation. Simple enter hostname/IP-addresse
and port number of your Graphite carbon line receiver (usually port 2003)
and activate your changes. Optionally you can specify a prefix to be added
to the variable names in graphite. That way you can put all of your graphs
into a subfolder in Graphite.
ID: 8004
Title: Implement service freshness checking
Component: cmc
Level: 2
Class: New feature
Version: 1.2.5i1
The CMC now supports freshness checking for passive services. This means
that the WATO option <i>Check freshness</i> in the rule set <i>Classical
active and passive Nagios checks</i> now also works for the CMC.
ID: 4026
Title: mk_logwatch: plugin now also supports windows
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.5.0i1
The mk_logwatch plugin is no longer restricted to windows.
It now runs as a frozen python binary under windows, which requires no extra python installation.
The plugin reads its configuration from the config/logwatch.cfg file.
The syntax of the windows and linux logwatch.cfg is identical.
The plugin may be configured through the WATO agent bakery with the rule "Text logfiles (Linux, Windows)".
The former rule "Text logfiles (Windows)" still works, but is considered as deprecated.
Keep in mind, there is difference in regex pattern matching.
The legacy windows logwatch always did a case insenstive match.
The new mk_logwatch.exe now also checks case sensitive, just like the linux plugin.
ID: 4380
Title: Raw Edition: Fixed broken views that contain graphs
Component: Multisite
Level: 2
Class: Bug Fix
Version: 1.5.0i1
An error message "KeyError ('graph_render_options')" was displayed
on all views that are used to display graphs.
ID: 4204
Title: Prevent password completion for all WATO rule where passwords are being specified
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.5.0i1
Most browsers try to autofill password input fields in forms.
While this is useful in most times it is very nasty in WATO
rules where passwords are being configured. This not only
destroys existing passwords when loading and saving a rule. It
also renders the {{view in plaintext}} button useless.
This has been fixed for all browsers.
ID: 8655
Title: Changing global setting for alert handler event types is now effective
Component: Alert Handlers
Level: 2
Class: Bug Fix
Version: 1.4.0b2
The bug was that changing the global setting for the handled event types
would not be activated by {{Activate Changes}}. The configuration for the
core was not generated newly until some other settings was changed also.
This has been fixed.
ID: 4023
Title: WATO Web API: Now able to add/edit/delete htpasswd users
Component: WATO
Level: 2
Class: New Feature
Version: 1.4.0i4
New functions for the WATO Web-API have been introduced.
You can now manage htpasswd users with automation calls.
The following (not very fleshed out) examples provide a quick overview.
A more elaborate version will be written later on in our official manual.
<pre>
Common url prefix:
http://localhost/heute/check_mk/webapi.py?_username=automation&_secret=1122...
To get a list of all supported attributes, you'll need to have a look in the actual config files
~/etc/check_mk/conf.d/wato/contacts.mk
~/etc/check_mk/multisite.d/wato/users.mk
Add users:
curl {common_prefix}&action=add_users -d 'request={"users": {"klaus": {"alias": "mr. klaus", "password": "1234", "contactgroups": ["all"]}}}'
Edit users:
curl {common_prefix}&action=edit_users -d 'request={"users": {"klaus": {"set_attributes": {"alias": "mr. santa"}, "unset_attributes": ["contactgroups"]}}}'
Delete users:
curl {common_prefix}&action=delete_users -d 'request={"users": ["klaus", "guest12", "guest2332"]}'
</pre>
ID: 4320
Title: Distributed: Master site has now also site specific global settings
Component: WATO
Level: 2
Class: New Feature
Version: 1.4.0i4
It is now possible to configure site specific global settings for the central
master site in distributed setups. In previous versions it was difficult to
set a configuration setting (like the number of check helpers) for the master
site and another value for the remote sites. You had to set the configuration
setting for each site individually which could be a problem when having a lot
of remote sites.
With this change the "Global settings" can now be handled as default
configuration settings for all sites while the site specific settings can be
configured on the site specific globals page which can be opened from the
distributed configuration page.
So you can now easily set a individual setting for the master site and leave
the configuration for the slave sites at the global defaults.
ID: 4319
Title: Reworked the service discovery dialog
Component: WATO
Level: 2
Class: New Feature
Version: 1.4.0i4
The service discovery dialog of hosts has completely been reworked. It has been changed
to be more user friendly and make bulk actions more comfortable.
We have reduced the number of columns, moved the action icons to the first columns and made
the checkboxes for bulk actions optional. Each table has now it's own bulk actions. These
actions are performed on all rows of the table by default. If you enabled the checkboxes,
the actions are performed on the selected rows. The full scan button is now an action button
like the other actions.
Actions on that page will now make you stay on the page to see the result of your action.
The disabling of services is now totally done via the "disabled services" ruleset. For each
host a host specific rule is added to this ruleset for setting the disabled services you
choose in the service discovery dialog. If you have global rules that disable services and
choose to enable that service via the service discovery dialog, a "enable" rule is created
for the selected service.
This means the service discovery page creates up to two rules in "disabled services" for each
host, one positive and one negative rule. These rules have the description
"Discovery rule of '[hostname]'".
ID: 8304
Title: New graphical frontend for metrics time graphs
Component: Metrics System
Level: 3
Class: New Feature
Version: 1.2.7i3
The Check_MK Enterprise Edition has now a new graphical user frontend for
displaying metrics time graphs. Instead of using pixeled PNG images it makes
use of interactive vector graphics using HTML 5. These graphs do not only
look better. They allow you to:
LI:Zoom horitontally using your mouse wheel
LI:Zoom vertically by dragging points up and down
LI:Scroll horizontally (into past and future) by dragging points left and right
LI:Resize a graph using the right bottom corner
If more than one graph is being displayed on the same HTML page then any zoom
or shift in time will be synchronzed to <b>all</b> graphs on the same page.
Also the reporting uses the new graphing engine and replaces the embedded
pixel images by real vector graphics.