ID: 14054
Title: crash_reporting: Add agent_output to section crash report
Component: Reporting & Availability
Level: 1
Class: New feature
Version: 2.2.0i1
Section crashes now have an agent output which can be viewed,
downloaded and submitted in a crash report.
ID: 14418
Title: Changes in rendering functions used in legacy check API
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
This werk might be incompatible only for users with custom check plugins in the
legacy check API. The following rendering functions in the legacy check API have
been changed. In case you are negatively affected by these changes, we strongly
recommend to migrate to the new API (see <a href="https://checkmk.com/blog/migrating-check-plug-ins-to-checkmk-2-0">this blog post</a> for help and further references).
LI: <tt>get_age_human_readable</tt>: Changes in rendering format only, no API changes.
LI: <tt>get_bytes_human_readable</tt>: SI and IEC prefixes are now used consistently, see
also werk #14417. Furthermore, the value for the <tt>base</tt> argument must now be either 1,000
or 1,024, any other value results in a <tt>ValueError</tt>. Finally, the argument <tt>precision</tt>
is now ignored. Instead, the number of decimal places is set automatically.
LI: <tt>get_nic_speed_human_readable</tt>: Changes in rendering format only, no API changes.
LI: <tt>get_percent_human_readable</tt>: The argument <tt>scientific_notation</tt> is now ignored.
Hence, values are not rendered in scientific notation any more. Furthermore, percentages are
always rendered with two decimal places, except for very small values.
LI: <tt>get_number_with_precision</tt>: No unit prefixes are added any more to the rendered
value. Instead, the value is displayed as is with the specified number of decimal places. Hence,
the argument <tt>base</tt> is now ignored. Furthermore, the arguments <tt>drop_zeroes</tt> and
<tt>zero_non_decimal</tt> are also ignored.
ID: 14417
Title: Service outputs: Render byte-related units using consistent SI/IEC prefixes
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
There are two options for rendering a raw value in bytes as a human-readable number:
LI: SI unit prefixes, where the base factor is 1,000 and the unit prefixes are
k, M, G, etc. For example, 1,500 B would be rendered as 1.5 kB.
LI: IEC unit prefixes, where the base factor is 1,024 and the unit prefixes are
Ki, Mi, Gi, etc. For example, 1,500 B would be rendered as 1.46 KiB.
Before this werk, Checkmk mixed up these two systems when rendering service
outputs by using a base factor of 1,024 in combination with SI unit prefixes.
After this werk, Checkmk renders byte-related units in service outputs consistenly:
LI: When displaying e.g. "1.23 MB" in a service output, the underlying value in
bytes is 1.23 * 1000^2 B.
LI: When displaying e.g. "14.7 KiB" in a service output, the underlying value in
bytes is 14.7 * 1024 B.
ID: 14415
Title: Graphs & dashboard elements: Render byte-related units using consistent SI/IEC prefixes
Component: metrics
Level: 1
Class: Bug fix
Version: 2.2.0i1
There are two options for rendering a raw value in bytes as a human-readable number:
LI: SI unit prefixes, where the base factor is 1,000 and the unit prefixes are
k, M, G, etc. For example, 1,500 B would be rendered as 1.5 kB.
LI: IEC unit prefixes, where the base factor is 1,024 and the unit prefixes are
Ki, Mi, Gi, etc. For example, 1,500 B would be rendered as 1.46 KiB.
Before this werk, Checkmk mixed up these two systems when rendering graphs and
dashboard elements by using a base factor of 1,024 in combination with SI unit
prefixes. After this werk, Checkmk consistently uses IEC prefixes instead of the
mixup mentioned above. Hence, numerical values will remain unchanged, but the
displayed units will change from kB, MB, GB, ... to KiB, MiB, GiB, ... .
Furthermore, as a result of this werk, there are now check plugins which
report a given value using (consistent) SI unit prefixes but visualize the same
value in a graph using IEC unit prefixes. While this is of course not optimal,
we prefer this intermediate state over the state before this werk (inconsistent
SI unit prefixes with mixed up base factors).
ID: 14395
Title: allow custom notification events for pagerduty testing
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.2.0i1
To test pagerduty notification you can now use CUSTOM commands as documented.
ID: 14332
Title: Fix title of Forecast graphs
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
If new Forecast graphs were saved with the option "Save & go to Forecast graph"
or existing graphs were edited via "Edit model", the defined titel was
overwritten with "HOSTNAME - SERVICEDESCRIPTION".
We are sorry but existing Forecast graphs have to be saved again with the
intended title.
ID: 13989
Title: Timesyncd check plugin can now handle large time offsets
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The timesyncd check plugin was unable to handle offsets that were displayed
with units other than seconds, milliseconds, or microseconds.
For example, an offset such as 5h 10min 12s would produce an error.
This incompleteness in the check plugin is now fixed and all the units systemd.time is
able to produce at the time of writing this werk can be handled effectively.
See also https://man7.org/linux/man-pages/man7/systemd.time.7.html
ID: 14327
Title: Prevent use of builtin snapin IDs for custom snapins
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
Custom sidebar snapins could be created with IDs like "tactical_overview",
leading to multiple problems while rendering the snapins in the sidebar.
You will now get an error message if such ID is used for custom sidebar
snapins.
ID: 13924
Title: Dashboard element 'Alert statistics': Apply context filters and rename
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
The 'Alert statistics' dashboard element is renamed to 'Alert overview' for a higher naming consistency among comparable dashboard elements. Also the context filters for this element are fixed and now applicable.