ID: 11879
Title: ntp: Parametrize discovery via WATO
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
This werk only affects users who have configured the NTP service discovery manually via mk
file.
The discovery of the "NTP Peer <item>" and "NTP Time" service has been configurable only via
the config variable <tt>ntp_inventory_mode</tt>. This variable is no longer valid.
To configure the service discovery please use in the new discovery rule "NTP Discovery".
If you do not configure a WATO rule, the plugin will fall back to its default behaviour,
which is to discover a summary service.
ID: 11719
Title: Levels for packet rates for network interface checks
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Previously, the error, multicast and broadcast WARN/CRIT levels
specified within the ruleset "Network interfaces and switch ports" were not
applied correctly. I.e., all levels were interpreted as percentual
levels, regardless of whether they had been specified as absolute or percentual
levels.
This behavior is fixed with this werk.
Additionally, the forms for error, multicast and broadcast levels now
yield a unified structure, that allows the specification of independent levels
for the in and out directions.
ID: 11720
Title: Cleanup graphs and check output for network interface checks
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
All graphs showing average metrics (e.g. "In_avg15" for the 15-minutes average
value of incoming traffic) have been removed from all interface services, as
the underlying value is only needed for evaluation of average-based warn/crit
levels and the graph adds no additional information to the normal output.
All displayed graphs now show the absolute value of the corresponding
rate, independent of the type of the specified warn/crit levels (percentual, absolute).
This had not been the case for errors, multicast and broadcast graphs.
All available packet rates, i.e. unicast, non-unicast, multicast, broadcast,
errors, discards, are now displayed in the detailed service output. The values will be shown
as percetual or absolute values, depending on the type of the underlying warn/crit levels,
with the absolute value being the default, if no levels are specified. Please note that
for error levels, there is a default of warn:0.01% and crit:0.001%, therefore,
the error rates will be displayed in percent by default. If averaging is activated for
the packet rate levels, the corresponding average value will be displayed instead.
Finally, the bandwidth graph has been moved up to the top of the displayed graphs.
ID: 11777
Title: Reordered inventory of VMware ESX clusters
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The inventory table below Software>Applications>Vmwareesx had a clumsy layout
and did not represent topology constraints of VMware clusters.
This change introduces a Cluster->(Datacenter, Hostsystems, VMs) relationship.
ID: 11897
Title: Fix misc regressions with Piggyback configuration
Component: Setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
In some cases, the core helpers would not parse the
Piggyback configuration for a Host correctly.
This has been fixed.
ID: 11714
Title: Openlog: logfile was not displayed
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Openlog did not display the logfile with the Error:<br>
<b>Logfile does not exist</b><br>
The log data retrieved via Livestatus was not decoded properly.
Thats why no data was found for this logfile.
ID: 11523
Title: mk_oracle: Fixed problems with multiple ORACLE_HOME entries on Grid setups
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
A Oracle Grid setup may contain more than one {{ORACLE_HOME}} entries. Until
now {{mk_oracle}} was not aware, that this could be the case and took all of
them. Now only the first entry will be considered.
ID: 11779
Title: Rename Proxmox Checks and Agent to Proxmox VE in order to prevent naming conflicts
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Names of agent and checks for Proxmox VE have been prefixed with 'proxmox' only. In order to
prevent future problems names of checks, agent, rules etc have been renamed to 'proxmox_ve' or
'Proxmox VE' respectively.
ID: 11830
Title: <tt>timesyncd</tt>: increase default thresholds for last synchronisation
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The check plugin <tt>timesyncd</tt> monitors the synchronization of linux hosts
with time servers. One of the monitored quantities is the time passed since the
last synchronization with the time server. Up to now, the corresponding default
thresholds were set to 1h (WARN) and 2h (CRIT). However, practice has shown that
1:30h (WARN) and 2h (CRIT) are more suitable, therefore, with this werk, we
change the defaults to these values. Note that this does not affect any user-
defined levels (ruleset "Systemd Timesyncd time synchronisation", option
"Allowed duration since last synchronisation").
ID: 11351
Title: Clear search query also on-click
Component: Setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
The last typed search query was already cleared if the results were selected with arrow keys and followed by enter or if directly pressed enter.
Now, they are also cleared when a result is selected by a mouse click.