ID: 11078
Title: Dynamic configuration: Add connector plugin API
Component: DCD
Level: 2
Class: New feature
Version: 1.7.0i1
The Dynamic configuration is now loading plugins that are located below
the path <tt>local/lib/check_mk/cee/dcd/plugins/connectors/</tt>.
You can find a minimal example connector implementation it in your site at
<tt>lib/check_mk/cee/dcd/plugins/connectors/example_connector.py</tt>. You may
use this as base for your own connectors. To enable this connector, you need to
copy it to the plugin directory mentioned above and uncomment the registry
registration lines in the plugin (See TODO).
To be able to configure connections based on this connector in the GUI, you
also need to deploy a GUI plugin. An example can be found in your site at
<tt>lib/check_mk/gui/cee/plugins/wato/example_dcd_connector.py</tt>. This
needs to be placed in the WATO plugin directory of your site. You also need to
uncomment the registry registration line in the plugin (See TODO).
ID: 11078
Title: Dynamic configuration: Add connector plugin API
Component: DCD
Level: 2
Class: New feature
Version: 1.7.0i1
The Dynamic configuration is now loading plugins that are located below
the path <tt>local/lib/check_mk/cee/dcd/plugins/connectors/</tt>.
You can find a minimal example connector implementation it in your site at
<tt>lib/check_mk/cee/dcd/plugins/connectors/example_connector.py</tt>. You may
use this as base for your own connectors. To enable this connector, you need to
copy it to the plugin directory mentioned above and uncomment the registry
registration lines in the plugin (See TODO).
To be able to configure connections based on this connector in the GUI, you
also need to deploy a GUI plugin. An example can be found in your site at
<tt>lib/check_mk/gui/cee/plugins/wato/example_dcd_connector.py</tt>. This
needs to be placed in the WATO plugin directory of your site. You also need to
uncomment the registry registration line in the plugin (See TODO).
ID: 11080
Title: Port Checkmk to Python 3
Component: Core & setup
Level: 3
Class: New feature
Version: 1.7.0i1
Most of Checkmk is written in Python. We have been developing on Python 2 for
over 10 years now and are now taking the big step of porting Checkmk to Python
3 with Checkmk 1.7.
This is a very big change in the software which has cost us a lot of time. But
this step is necessary to continue to develop Checkmk efficiently and safely.
In the past, Python 2.7 with all necessary 3rd party modules have been shipped
in Checkmk for a long time. This Python 2.7 will no longer be shipped with
Checkmk 1.7. Instead we now ship Python 3.8 with all necessary 3rd party
modules.
This is especially important if you use your own plugins or scripts. You have
to consider the following things.
If you have a script that is called directly from a cronjob or the core, e.g. a
notification script, you have often used the shebang "#!/usr/bin/env python" in
the past. By doing so, you have used the Python 2.7 that we shipped. Since this
no longer exists, "python" of the operating system is used without further
adaptation. This can be a Python 2.7, it depends on your system.
We recommend changing the shebang to "#!/usr/bin/env python3". This will allow
you to use the Python that comes with Checkmk again.
After you have done this, you may need to adjust some things in your scripts to
change your code from Python 2 to 3. We will publish more information about the
conversion of plugins and scripts soon.
ID: 11124
Title: Arista BGP check plugin
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
Generates service info from basic BGP information provided via SNMP (LocalAddr, LocalIdentifier,
RemoteAs, RemoteIdentifier, AdminStatus, (Peer)State, LastErrorReceivedText). Check is always OK
and has no parameters.
ID: 11078
Title: Dynamic configuration: Add connector plugin API
Component: DCD
Level: 2
Class: New feature
Version: 1.7.0i1
The Dynamic configuration is now loading plugins that are located below
the path <tt>local/lib/check_mk/cee/dcd/plugins/connectors/</tt>.
You can find a minimal example connector implementation it in your site at
<tt>lib/check_mk/cee/dcd/plugins/connectors/example_connector.py</tt>. You may
use this as base for your own connectors. To enable this connector, you need to
copy it to the plugin directory mentioned above and uncomment the registry
registration lines in the plugin (See TODO).
To be able to configure connections based on this connector in the GUI, you
also need to deploy a GUI plugin. An example can be found in your site at
<tt>lib/check_mk/gui/cee/plugins/wato/example_dcd_connector.py</tt>. This
needs to be placed in the WATO plugin directory of your site. You also need to
uncomment the registry registration line in the plugin (See TODO).
ID: 11119
Title: Proxmox: add disk usage check
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
This check is OK when disk usage is below a configurable set of levels or if no levels have
been set. It shows the available and used disk space.
ID: 11098
Title: Proxmox: add VM backup status check
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
This check makes sure every VM has a recent backup. The information is taken from log entries
collected by the agent via API since Proxmox does not provide us with backup status (yet?).
The check plugin optionally checks against existence and age of the last backup and shows some
additional info like date, size and bandwidth.
ID: 11121
Title: Proxmox: add node info check
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
This check is OK when a given Proxmox node's `status` and it's subscription 'status' match the
given configured values, WARN otherwise. It shows the node status, subscription status, Proxmox
version and number of hosted VMs.
ID: 11120
Title: Proxmox: add mem usage check
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
This check is OK when memory usage is below a configurable set of levels or if no levels have
been set. It shows the available and used memory.
ID: 11122
Title: Proxmox: add VM info check
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
This check is OK when a given Proxmox VM's {status} matches a configured value, WARN otherwise.
It shows {vmid} (e.g. "101"), {status} (e.g. "running"), {type} ("lxc" or "qemu") and {host} values
returned by the API for the given VM.