ID: 8429
Title: Fix exception 'format' on RRD creation of you have created RRD rules with the previous version
Component: metrics
Level: 2
Class: Bug fix
Version: 1.4.0i1
If you had created some rules for RRD configuration of hosts or services
then you would run into an exception with missing <tt>'format'</tt>. This
has been fixed.
ID: 8428
Title: mk_oracle: force section "instance" to be always the first one when baking agent
Component: agents
Level: 2
Class: Bug fix
Version: 1.4.0i1
This is neccessary, because in this section the version of the database is detected.
Otherwise the plugin fails to execute the queries correctly.
ID: 8422
Title: Fix deadlock in CMC when creating lots of RRDs at once
Component: metrics
Level: 2
Class: Bug fix
Version: 1.4.0i1
This could e.g. happen if you add many hosts and services to the monitoring
at once. The CMC would then stuck in a dead lock with the RRD creation
helper process. This has been fixed.
ID: 8421
Title: Fix baking of Windows agent in case of installing custom files
Component: agents
Level: 2
Class: Bug fix
Version: 1.4.0i1
Thanks to Hardy Düttmann!
ID: 8400
Title: Fixed PDF export for service detail views: added missing graphs
Component: Reporting & Availability
Level: 2
Class: New feature
Version: 1.4.0i1
This still works only for services with at most 2 or 3 graphs. The cell that
is containing the graphs cannot include a page break.
ID: 8395
Title: Use one RRD file per service as default now for new installations
Component: metrics
Level: 2
Class: New feature
Version: 1.2.7i4
If you create a new site then per default now two rules are created that
switch to the new RRD format per default. Only one RRD file per service will
be created. This save IO operations and bandwidth.
Existing sites are not affected. You can switch to single RRDs by creating
rules in <i>Configuration of RRD databases of hosts</i> and <i>Configuration
of RRD databases of services</i> for that purpose. After that run <tt>cmk
--convert-rrds</tt> for migrating existing RRDs.
ID: 8396
Title: When adding views to reports the currently selected filters are now honored
Component: Reporting & Availability
Level: 2
Class: Bug fix
Version: 1.2.7i4
This means that if you have modified some filters in a view and add that view
to a report these filters are now being saved in the report as well. So the
view in the report has exactly the same object selection.