ID: 8309
Title: Fix authorization settings for seeing service in the user interface
Component: cmc
Level: 2
Class: Bug fix
Version: 1.2.7i4
The behaviour of the authorization setting <i>loose</i> for hosts has been
changed to be compatible with the behaviour Nagios has. If host authorization
is set to <i>loose</i> in the global settings of the Check_MK Micro Core, then
it is now suffient to be the contact of a host for seeing all of its service
- even if those services do have explicit <i>contacts</i> assigned. Formery
you needed to be an explicit contact if one had been set. In the case that
you just have contacts assigned to hosts nothing has changed.
The behaviour of the authorization setting <i>strict</i> has also changed.
If you are the explicit contact of service, but not of the host, then you
are allowed to see the service.
<b>Note</b>: This all has <b>no</b> impact on notifications. Nothing has
changed there.
ID: 8305
Title: Fixed segmentation fault of core in case of vanished object while check is running
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.2.7i3
In case you removed a host or service from the monitoring while a check was still
running the CMC would crash. This has been fixed. This bug had been introduced in
February.
ID: 8306
Title: Log stack trace in case of crash of CMC
Component: cmc
Level: 1
Class: New feature
Version: 1.2.7i3
This helps finding the exact reason for a (hopefully rare) crash of the CMC.
ID: 8307
Title: Fix error in agent bakery page if no agent for a certain has is existing
Component: WATO
Level: 1
Class: Bug fix
Version: 1.2.7i3
In case of an unclean state in the agents directory there are symbolic links
to non-existing agent configurations. This is e.g. the case if hosts had
been removed in certain Check_MK versions. This has been fixed.
ID: 8304
Title: New graphical frontend for metrics time graphs
Component: metrics
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.
A further advantage of the new system is, that in distributed setups no
reverse HTTP proxy is needed any longer. The data is being fetched via
Livestatus (up-to-date core is neccessary).
ID: 8302
Title: New page for downloading the baked monitoring agent of a host
Component: agents
Level: 2
Class: New feature
Version: 1.2.7i3
There is now a new page for every host where you can download it's Check_MK
agent. This page has one link for every supported operating system (as WATO
cannot know which agent package type you need).
Note: The download of baked monitoring agents is only possible for users
with the Adminitrator role per default. This is because agent may contain
confidential data such as passwords. But if you like you can allow normal
users either downloading agents for hosts where they are a contact for or
even for all agents.
ID: 8303
Title: Added new utility logdate, directly callable without path
Component: setup
Level: 1
Class: New feature
Version: 1.2.7i3
C+:
OM:logdate --help
Usage: logdate [-h|--help] [FILE1 FILE2 ...]
Reads log lines from stdin or from specified files and searches for
timestamps in the form [1443685694] (Unix epoch timestamp). Writes the
lines to standard output while replacing the timestamps by local times
in the format [2015-10-01 09:48:14].
Example:
logdate var/check_mk/core/history
C-:
ID: 8301
Title: cmcdump: New tool for offline mirroring satellite sites into a central site
Component: cmc
Level: 3
Class: New feature
Version: 1.2.7i3
The CMC now has a new replication mechanism for mirroring the state
of satellite monitoring sites into a central site. This is much like
<tt>livedump</tt> for the Nagios core but is much more powerful.
In order to setup this you need to call <tt>cmcdump -C > cmc.config</tt>
on the remote site and transfer that file to the central site into
<tt>etc/check_mk/conf.d/yourfile.mk</tt>. This will dump the configuration
of all hosts and services. Afterwards activate the updated configuration
with <tt>cmk -O</tt>. You need to repeat it from time to time so that
your central site is up-to-date.
In a much shorter interval (e.g. once per minute) you call <tt>cmcdump >
cmc.state</tt> on the same remote site. This can easily be done with a cron
job. That file you also transfer to the central site via any mechanism
you like (scp, http, rsync, ...). Over there read it into the core with:
C+:
OM:unixcat < cmc.state tmp/run/live
C-:
This will update the core's complete state of all hosts and services that
are contained in the dump. The transferred state will correctly reflect the
following variables:
LI:The actual state (PEND, OK, WARN, ...)
LI:The plugin output
LI:The long (multiline) plugin output
LI:The performance data
LI:Whether the object is flapping and the current level of flappiness
LI:The time of the last check execution
LI:The time of the last state change
LI:The check execution time
LI:The check latency
LI:The number of the current check attempt
LI:Whether the current state is hard or soft
LI:Whether a problem has been acknowledged
LI:Whether the object is currently in a scheduled downtime
In the central site this will almost - but not entirely - be handled
like a check execution. One difference is that no notifications will be
sent. But performance data is being processed graphs will be created. Also
the monitoring log is being updated and availability data can be processed.
Depending on our synchronization interval of the data transfer the latter
one might not be 100% precise however.
The tool <tt>cmcdump</tt> is in your path and can directly be executed.
Call <tt>cmcdump --help</tt> for details on how to call this tool.