ID: 8011
Title: Complete German translation of GUI
Component: WATO
Level: 3
Class: New feature
Version: 1.2.5i1
The complete user interface of Multisite and WATO is now available in German language.
Every user can select either English or German as language. In a global setting you
can specify the default language.
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>