ID: 15289
Title: mk_oracle: Revert werk 15559, use tnsping when available
Component: agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
<a href="https://checkmk.com/werk/15559">Werk 15559</a> removed the invocation
of <tt>tnsping</tt>.
<tt>tnsping</tt> was used to check if the tns-alias could be reached. If it
could not be reached via <tt>tnsping</tt>, hostname and port is used to connect
to the database.
With <a href="https://checkmk.com/werk/15559">Werk 15559</a> the invocation of
<tt>tnsping</tt> was completely removed. tns-alias was always used. This lead
to problems with different configurations of <tt>mk_oracle</tt>.
This change introduces a check if the <tt>tnsping</tt> binary is available.
If the binary is available, the logic of <tt>mk_oracle</tt> before Werk 15559
is restored. If the binary is not available, it is assumed that the tns-alias
can be reached.
ID: 15972
Title: Activate changes: Performance improvement in very large distributed setups
Component: Setup
Level: 1
Class: New feature
Version: 2.3.0b1
The speed at which changes are distributed to remote sites and activated when in a distributed setup with hundreds of sites has been improved.
This is mainly due to improved parallelization, which means that more sites can perform their activation at the same time.
ID: 15910
Title: agent_aws: DNSName not available in load balancer info
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0p8
The agent_aws special agent used to crash when the DNSName was not available in the load balancer information.
This happened for Gateway Load Balancers. These load balancers will now be skipped.
ID: 16091
Title: Local checks: Show metric values in service summary only if WARN/CRIT
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Before this werk, local check services always showed all metric values in the service summary. As of
this werk, only metric values which result in a <i>WARN</i> or a <i>CRIT</i> are shown in the
service summary. All other metric values are instead shown in the service details.
Hence, if the <a href="https://docs.checkmk.com/latest/en/localchecks.html#dynamic_state">P</a>
state is used, metric values are displayed in the service summary if the violate the thresholds.
Without the P state, metric values are always displayed in the service details.
ID: 16089
Title: etherbox_smoke: Fix default behaviour and remove predictive levels option
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
The check plugin <tt>etherbox_smoke</tt> monitors smoke sensors of Etherboxes.
<a href="https://checkmk.com/werk/14664">Werk 14664</a> introduced configurable levels for this
plugin. However, this accidentally changed the default behaviour of the plugin. Before werk 14664,
the plugin reported <i>OK</i> if no smoke was detected and <i>CRIT</i> otherwise. With werk 14664,
by default, the plugin always reported <i>CRIT</i>, even if no smoke was detected.
As of this werk, the old default behaviour is restored. Furthermore, a new configuration option is
added. Users now have two alternatives for configuring the behaviour of the plugin: Users can either
specify two monitoring states for the two cases "smoke detected" and "no smoke detected", or,
alternatively, users can specify <i>WARN</i> and <i>CRIT</i> thresholds on the smoke level.
Finally, this werk removes the option to configure predictive levels for this check plugin, which
was also added by werk 14664. Using this option lead to a crash. Already existing configurations
will automatically be migrated to the default behaviour mentioned above.
ID: 16090
Title: etherbox_voltage: No default thresholds and remove predictive levels option
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
The check plugin <tt>etherbox_voltage</tt> monitors voltage sensors of Etherboxes. By default, the
plugin reported <i>CRIT</i> for any non-zero voltage reading. As of this werk, the new default
behaviour is to apply no thresholds. Users can configure custom thresholds, as before.
Furthermore, this werk removes the option to configure predictive levels for this check plugin,
which lead to a crash. Already existing configurations will automatically be migrated to the new
default behaviour (no thresholds).
ID: 16023
Title: Use oracledb over cx_Oracle module for Oracle DB in check_sql
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
The python module cx_Oracle is replaced by <a href="https://oracle.github.io/python-oracledb/">oracledb</a> to support Python 3.11 for Oracle database checks with the check_sql active check.
In order to use the check_sql with an Oracle DB it is now necessary to install the oracledb python package with:
C+:
python3 -m pip install oracledb --upgrade
C-:
ID: 15940
Title: Fix result view of host and service label search
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0p8
If you searched for host or service labels in the Monitor search or Quicksearch
snapin, the results were listed correctly but on enter, the view showed all
hosts or services.
ID: 15259
Title: Fixed periodic service notification interval
Component: Setup
Level: 2
Class: Bug fix
Version: 2.3.0b1
Because of a regression in 2.2, the periodic notification interval of a host
was used for all of its services, too, overriding any rules for the given
services. This has been fixed, the periodic service notification interval
rules work as expected again.
ID: 15939
Title: Fix possible "Internal Server Error" on save of changes
Component: Setup
Level: 1
Class: Bug fix
Version: 2.3.0b1
After update of the werkzeug module we have seen different users facing
problems while saving changes in, e.g. Business Intelligence, Dynamic host
management and Agent deployment rules. The save action always lead to an
"Internal Server Error".
Reason was a new introduced limit of the mentioned module causing this error
while saving very large formulars. So this could also occur on various other
pages.