ID: 8544
Title: Fixed broken "default grahs" having negative values
Component: metrics
Level: 1
Class: Bug fix
Version: 1.4.0i1
Graph values which have no value specification and thus are rendered
with the default rendering method without unit etc. lead to broken
graphs when the values were negative. This fixes a regression introduced
with 1.2.8p6.
ID: 8541
Title: Service check timeouts can now be configured individually for services
Component: cmc
Level: 2
Class: New feature
Version: 1.4.0i1
It is a good idea to keep the service check timeout values as low as possible. All past versions
could only configure this option globally. So if you had only some services needing a higher
execution time, you had to increase this global value for all your services.
Now you can use the rule set "Service check timeout (Microcore)" to control this timeout per
service. It will override the globally configured option for all matching services.
ID: 8537
Title: Fixed possible exception when deleting a host via WATO
Component: WATO
Level: 1
Class: Bug fix
Version: 1.4.0i1
This could happen when the agent bakerys agent directory is not existant.
ID: 8538
Title: Make graph data resolution visible in the graphs
Component: metrics
Level: 1
Class: Bug fix
Version: 1.4.0i1
It was not transparent to the users which data resolution the graphs are calculated and rendered with.
The step of the graphs is now rendered to the top right of the graphs, next to the time specification
to make this transparent.
ID: 8539
Title: Made consolidation of values transparent to the user
Component: metrics
Level: 2
Class: Bug fix
Version: 1.4.0i1
When showing graphs of larger time ranges, the graphs are normally based on
aggregated values, which means multiple measured values are consolidated to
a single value.
For example, when a graph is based on the "max" aggregation function, like
nearly all graphs are by default, the values in the Average column are not
the real average values of the shown time, but the average values of the
max values in the step of the graph. The step of the graph is now shown on
the top right of the graph.
To clarify this: If you look at a 7 day graph, you have a step of 30 minutes.
If the service is being checked in a 1 minute interval, the graph is based on
the maximum of 30 single values of each 30 minutes step.
So your average values are the 7 day average of the 30 minute maximum values.
This is obviously not what most users would expect, but we would have to fetch
3 times more data per graph to get the real average and the real min values
for each graph. The graphs are already producing a lot of load and we try
to keep the impact low, so we decided to make the calculation transparent and
changable by the user.
If you have a max graph, the min and average columns are slightly grayed out
to visualize the situation. If you hover on the titles, you get a description
about it. Now you can click on the columns titles to change the aggregation
function the graph is based on.
ID: 8540
Title: cmk-update-agent: Fixed exception at end of registration when using auth secret
Component: agents
Level: 1
Class: Bug fix
Version: 1.4.0i1
ID: 8535
Title: cmk-update-agent: Fixed not using configured CA certificates]
Component: agents
Level: 1
Class: Bug fix
Version: 1.4.0i1
cmk-update-agent could fail when using HTTPs with configured CA certificates.
The error message was:
Exception: Cannot fetch deployment URL via curl: Peer certificate cannot be authenticated with known CA certificates
This was caused by missing links in /var/lib/check_mk_agent/cas which can be
created with "c_hash /var/lib/check_mk_agent/cas".