Versio.io can import, historize and process monitoring data from Check_MK.
You can find the configuration option in Versio.io at
Environment settings > OneImporter > Configurations > Check_MK.
Here you can edit all existing configurations, create new configurations or delete existing configurations.
To add a new configuration enter a
Name for your importer and an
Entity suffix (default:
-check-mk) to clearly identify your Check_MK entities.
Note that the
Entity suffix is fixed and cannot be changed afterwards.
Add to proceed to the configuration.
To edit an existing configurations click the arrow on the left of your importer name to expand the configuration options.
Following configuration options are available:
|Name||Meaningful name||Add the word "Check_MK" to identify importer when viewing the logs|
|Active||Option to activate and deactivate the configuration. Data is only imported if the configuration is activated.|
|Server URL||Check_MK server URL to get data from|
|Version||Select relevant Check_MK version|
|Username||User name for Check_MK access|
|Secret||Password for Check_MK access||See paragraph below for secret generation in Check_MK|
|Entities||Select all required entities|
|Executing OneImporter||Select a Versio.io OneImporter to import the data based on the importer configuration.||Requires installed OneImporter: Installation instruction|
|Schedule time (cron format)||Determine the frequency of imports in CRON format||Learn more about CRON format: https://en.wikipedia.org/wiki/Cron|
Table: Check_MK configuration parameters
The following image is an example of a Check_MK configuration:
Figure: Example of a Versio.io Check_MK configuration
A user with an automation secret (similar to a token) for the Hetzner Cloud integration is required to access the Check_MK API.
Check_MK offers the concept of the automation user. These users are intended exclusively for remote control and do not permit normal GUI logins. Authorisation is achieved using specific variables in the URL.
An automation user is created like a normal user, but receives an automation secret instead of a password. This can be defined manually or can be generated automatically with the randomising die.
Just like a normal user, an automation user has a role and can also be a contact. With these you can thus restrict its permissions and visibility of hosts and services as required.
When opening websites automatically, you enter the following additional variables in the URL:
- _username the automation user's ID
- _secret the user's Automation secret
The Versio.io OneImporter imports Check_MK data based on a specific configuration into entities with a suffix defined by you (default:
-check-mk). To view the imported instances in Versio.io, select 'Asset & Configuration Repository → Instance Viewer'. There you can select your specific instance and click it for a detailed view in the instance history viewer.
The following image is an example of imported Check_MK data:
Figure: Overview of Versio.io Check_MK instance (left) and topology of related instances (right)