Checkmk werks level2 March 2015

checkmk-werks-lvl2@lists.checkmk.com

5 participants
14 discussions

Check_MK Werk 0973: Renaming of hosts via WATO

by Mathias Kettner

ID: 0973 Title: Renaming of hosts via WATO Component: WATO Level: 2 Class: New Feature Version: 1.2.5i3 WATO has now a new function <i>Rename Host</i>. You will find a button with that name in the Properties of a host. It allows a renaming of an existing host. Before you can use that feature you need to have all changes activated, so nothing is pending. Renaming a host is a complex precedure that will not only rename the host in WATO, but also in: <ul> <li>all rules from <i>Host & Service Parameters</i></li> <li>cluster's node definitions</li> <li>a host's parent definitions</li> <li>Business Intelligence rules</li> <li>notification rules (both rule based and flexible notifications)</li> <li>internal Check_MK data like caches and performance counters</li> <li>auto-disovered services of the host</li> <li>logfile information of logwatch plugin</li> <li>stored SNMP walks</li> <li>RR databases with performance data</li> <li>RRD updates in journal of RRD Cache</li> <li>spool files of PNP4Nagios</li> <li>NagVis maps</li> <li>monitoring history entries (events and availability)</li> <li>the current monitoring state (including ackowledgements and downtimes)</li> </ul> Please note that renaming of a host involves a temporary stop of the monitoring core. This is neccessary in order to avoid situation where the old and the new name of a host is being used at the same time.

8 years, 9 months

Check_MK Werk 1903: mk_oracle: Remote Monitoring of Oracle Databases

by Bruhns＠mathias-kettner.de

ID: 1903 Title: mk_oracle: Remote Monitoring of Oracle Databases Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.7i1 mk_oracle got a major improvement in monitoring Oracle Databases. This new option allows monitoring a database from another host with a running check_mk_agent. H2: Requirements You need an Oracle Client from Oracle to use this feauture. The Oracle Instant Client with SQLPlus is a required minimum. You could use an existing Oracle installation as environment for mk_oracle as well. The plugin sends the data with piggyback. Please keep in mind, that the agent from the host with mk_oracle is responsible for the piggyback data. If you put the Check_MK check in downtime you'll put all other database checks from mk_oracle in a downtime as well. H2: Configuration You need an Oracle Client. If ORACLE_HOME is not set in the login shell of root, you need to add the ORACLE_HOME variable to mk_oracle.mk. Add the following lines to <tt>mk_oracle.cfg</tt>. The path is an example for the RPM Instant Client from Oracle for 64bit. <tt>ORACLE_HOME=/usr/lib/oracle/11.2/client64</tt> <tt>REMOTE_INSTANCE_1_omd110=check_mk:check_mk:::::XE:11.2</tt> <tt>REMOTE_INSTANCE_2_omd110=check_mk:check_mk:::::XE2:11.2</tt> Definition of a REMOTE_INSTANCE: <tt>REMOTE_INSTANCE_<Number>_<piggyback Hostname>=<Configuration String></tt> The definition of the database connection is as follows. <tt><username>:<password>:<sysdba>:<port>:<Database hostname>:<reserved for future use>:<ORACLE_SID>:<ORACLE-Release></tt> Notes regarding <tt>REMOTE_INSTANCE_x</tt> You need to make sure, that the name of the variable including the hostname is unique for every database in <tt>mk_oracle.cfg</tt>. Only 3 '_' are allowed in front of the piggyback hostname. Otherwise the plugin won't work correctly. The Oracle Release must be 9.2, 10.1, 10.2, 11.1, 11.2 or 12.1. No other values are allowed. Don't forget to use the testmode before starting the inventory on the monitoring host. More details could be found on the documentation at Check_MK: https://mathias-kettner.de/checkmk_oracle.html The testmode is compatible with the remote mode. Details with an example are shown in the documentation. H2: Incompatible change: The compatibility against old sqlplus.sh has been removed. Please remove an exiting sqlplus.sh and configure the <tt>mk_oracle.cfg</tt>. This change is a requirement for the new remote monitoring option and the only reason for this change. There is nothing to do when <tr>sqlplus.sh</tr> was not used before this Werk.

9 years, 5 months

Check_MK Werk 2154: Interface-Checks: Separate traffic thresholds for in and out are now possible

by Lars Michelsen

ID: 2154 Title: Interface-Checks: Separate traffic thresholds for in and out are now possible Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.7i1 It is now possible to configure separate bandwidth thresholds for the interface checks on the traffic directions. Instead of configuring "In/Out" at once, you can choose only a single traffic direction to specify the levels for.

9 years, 5 months

Check_MK Werk 2061: DB2 monitoring: Additional checks for AIX (and presumably linux)

by Andreas Boesl

ID: 2061 Title: DB2 monitoring: Additional checks for AIX (and presumably linux) Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.7i1 This werk introduces the new agent plugin mk_db2.aix which can be installed on aix systems in the agents plugins directories. It is very likely that it runs on linux systems as well. It is able to run queries over multiple DB2 instances. The plugin output is processed by the following new checks <table> <tr><th>Check</th><th>Description</th><th>Limits configurable</th></tr> <tr><td>db2_backup</td><td>Time since last database backup</td><td>X</td></tr> <tr><td>db2_bp_hitratios</td><td>Bufferpool Hitratios</td><td></td></tr> <tr><td>db2_connections</td><td>Number of database connections</td><td>X</td></tr> <tr><td>db2_counters</td><td>Deadlocks and Lockwaits per Second</td><td>X</td></tr> <tr><td>db2_logsize</td><td>Size and growth of database logfile</td>X<td></td></tr> <tr><td>db2_tablespaces</td><td>Size and growth of tablespaces</td>X<td></td></tr> <tr><td>db2_sort_overflow</td><td>Percentual sort overflow</td><td>X</td></tr> <tr><td>db2_version</td><td>Displays DB2 version</td><td></td></tr> </table>

9 years, 5 months

Check_MK Werk 2104: aix_if: new agent section and check

by Goetz Golla

ID: 2104 Title: aix_if: new agent section and check Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.7i1 This aix check_mk_agent has a new section aix_if extracting more information about network interfaces than the previous lnx_if section. A new interface check for AIX named aix_if has also been created given more useful information. As long as you do not replace the check_mk_agent on your AIX systems, nothing will change. When you replace the agent with the new one, you will have to redo the service discovery. Interfaces will reappear with the same service description, but with more information about the NIC.

9 years, 5 months

Check_MK Werk 2137: diskstat: new implementation of Linux Disk IO check

by Mathias Kettner

ID: 2137 Title: diskstat: new implementation of Linux Disk IO check Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.7i1 The <tt>diskstat</tt> check for Linux has been reimplemented from scratch. It now gets much more specific metrics information like average wait time, IO queue length, latency, IOs per seconds und more. Six graphs are being created. Note: this check is new parametrized by a new rule set in WATO. You need to redo your configuration of this check, sorry. Also if you have a very old legacy setup with two seperate checks for read and write, you also need to rediscover. These checks are not longer supported.

9 years, 5 months

Check_MK Werk 2057: New checks for postgreSQL monitoring

by Andreas Boesl

ID: 2057 Title: New checks for postgreSQL monitoring Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.7i1 With this update the agent plugin <i>mk_postgres</i> now reports additional information, which will be processed by these new checks: <table> <tr><th>Check</th><th>Description</th><th>Limit configurable</th></tr> <tr><td>postgres_bloat</td><td>Shows size of table and index bloat</td><td>X</td></tr> <tr><td>postgres_conn_time</td><td>Time to connect to database</td><td></td></tr> <tr><td>postgres_connections</td><td>Number of connections to database</td><td>X</td></tr> <tr><td>postgres_locks</td><td>Number of ShareAccess and ExclusiveLocks</td><td>X</td></tr> <tr><td>postgres_query_duration</td><td>Displays longest running query</td><td></td></tr> <tr><td>postgres_stats</td><td>Time of last VACUUM and ANALYZE</td><td>X</td></tr> <tr><td>postgres_version</td><td>Displays PostgreSQL version</td><td></td></tr> </table> Note: You have to update the agent plugin <i>mk_postgres</i> on the target host.

9 years, 5 months

Check_MK Werk 2136: Unify headers of Host/Service rules, EC rules and notification rules

by Mathias Kettner

ID: 2136 Title: Unify headers of Host/Service rules, EC rules and notification rules Component: WATO Level: 2 Class: New Feature Version: 1.2.7i1 All three types of rules now have a common header with description, command and documentation URL. The section has been renamed from <i>General Properties</i> or <i>Additional options</i> to <i>Rule Properties</i>. In the host and service rules the existing comment information is being used as description if the description is empty. This is in order to be compatible with the existing configuration where no description field existed.

9 years, 6 months

Check_MK Werk 2100: if64: check can now impose limits on the number of outgoing and incoming non-unicast packets per second

by Goetz Golla

ID: 2100 Title: if64: check can now impose limits on the number of outgoing and incoming non-unicast packets per second Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.7i1

9 years, 6 months

Check_MK Werk 2041: Notification Spooler can now handle incoming and outgoing persistent TCP connections

by Mathias Kettner

ID: 2041 Title: Notification Spooler can now handle incoming and outgoing persistent TCP connections Component: Notifications Level: 2 Class: New Feature Version: 1.2.7i1 The Check_MK Notification Spooler (<tt>mknotifyd</tt>) has completely been rewritten. It now: <ul> <li>uses persistent TCP connections instead of connecting for each notifiction</li> <li>can use outgoing TCP connections for <i>receiving</i> notifictions</li> <li>can handle an arbitrary number of parallel connctions</li> <li>monitors connections with heart beats</li> <li>is being monitored by two new checks for the general state and for each connection</li> </ul> The global configuration for the spooler has changed. Your existing settings are still supported but have vanished from WATO. As soon as you create a new configuration that will override your legacy configuration. The new checks that monitor the spooler require an update of the Check_MK Agent for Linux on the Check_MK server. It needs OMD based installaions paths. All spoolers will automatically be discovered. The new checks are <tt>mknotifyd</tt> and <tt>mknotifyd.connection</tt>. The spooler write messages into <tt>var/log/mknotifyd.log</tt>. There are three log levels, which can be configured in the global settings of the spooler. We propose starting with the highest log level. Also a file <tt>var/log/mknotifyd.log</tt> is being written every 20 seconds. It shows the state of the spooler and its connections. This is being used for the monitoring of the spooler.

9 years, 6 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2 March 2015