ISDB-Exporter

Linux

Windows

The ISDB-Exporter provides the metrics of the INUBIT REST interface for versions lower than version 7.4.0.50. It can act as a generic DB connector to measure the database availability from the perspective of the application server. It can therefore also process specialist data from the DB and provide it as a metric (e.g. number of incoming messages per minute). Data and statistics can be extracted from databases, but functions can also be triggered.For example, the number of incoming messages per minute).

Data and statistics can be extracted from databases, but functions can also be triggered. The exporter also measures the runtimes of the individual statements so that information about the availability and performance of the database can be determined and mapped in VIMON.

From version 7.4.0.50, INUBIT itself also offers Prometheus metrics via the REST Metrics interface, e.g. information about running, faulty and waiting processes in the queue manager, maintenance mode, etc. Only this method should be used to determine the INUBIT data!

The ISDB Exporter is still used, but then only as a database exporter!

Behaviour

Initialization

The configuration is read in when the exporter is started. The entry inubit can occur 0 to 1x and is triggered once for each query before the statements are executed.

All statements refer to the previously defined database. Several databases with associated statements can therefore be defined.

At startup, queries are then built for all database entries.

During a query, the connections are used or rebuilt if necessary.

INUBIT queries

The exporter behaves towards INUBIT like a workbench and requests an update of the QueueManager from the Process Engine. Only after this does INUBIT write its QueueManager data to the LOG tables in the database.

Therefore, the ISDB exporter can then connect to the database and evaluate the QueueManager tables for status, user groups, etc.

While INUBIT performs this evaluation and persistence of the processes, no other user/process can access the QueueManager. Therefore, using the QueueManager with an active ISDB exporter on this ProcessEngine can lead to strange displays.

Database queries

All queries (statement) are separated in executionGroups. All queries within a executionGroup are executed in parallel.

The `executionGroups in turn are executed sequentially.

Setup

The ISDB-Exporter uses JDBC to communicate with the database. All drivers that are under vimon/drivers are included for this purpose.

Configuration

The configuration is under vimon/config/isdb_exporter/isdb_exporter.conf.

If INUBIT is not to be queried via this exporter, the inubit block can be omitted.

The required blocks are then:

1..n database each with
- 1..n statement

The statements can return

either a numerical value
or
several values line by line (which must then be in a column with the name value!) and Labels in other columns.
In the second case, a Prometheus metric is generated for each row, with value as the value and the other columns as Labels.