Discovery

This plugin can be integrated with Pandora FMS Discovery.

To do this, you must load the ".disco" package that you can download from the Pandora FMS library:

Once loaded, DB2 environments can be monitored by creating Discovery tasks from the Management > Discovery > Applications section.

For each task, the following minimum data will be requested:

DB2 target string: List of DB2 targets to be monitored by the task. It will be a list separated by commas or by lines. Each target database can be defined with the format IP:PORT/SID or IP/SID.
User: Connection user to the target databases.
Password: Password of the indicated user.

Task settings can also be adjusted to customize the desired monitoring:

Max threads: To optimize the execution time, multiple threads can be configured to monitor the agents of the task. Keep in mind that setting up multiple threads can increase the CPU usage of the task.
Target agent: List of target agents for the DB2 targets to monitor. That is, the names with which the agents of each objective defined in the task will be generated. It will be a list separated by commas or by lines. The position of the names in the list must match the position of the DB2 targets in your list, that is, the first name will be used for the first target and so on. If the list is separated by lines, blank lines will be ignored. If an agent name is not specified for a target, its IP or FQDN will be used as the agent name.
Custom module prefix: Text included as a prefix for all generated module names. It is useful to locate the modules generated by the task or distinguish them from others.
Get database summary: If activated, it will monitor the summary of the databases.
Check transactional log utilization: If enabled, it will monitor the use of the transactional log.
Get number of connections: If activated, it will monitor the connections.
Check DB size: If activated, it will monitor the size of the databases.
Retrieve cache statistics: If enabled, it will monitor cache statistics.
Execute custom queries: If enabled, it will allow executing custom queries to each DB2 target.
Custom queries: Configuration block to define the custom queries to be executed. Each query will generate a new module for each agent in the task.

Tasks that are successfully completed will have an execution summary with the following information:

Total agents: Total agents generated by the task.
Targets up: Total number of targets to which it has been possible to connect.
Targets down: Total number of targets to which it has not been possible to connect.

The tasks that are not completed successfully will have an execution summary recording the errors produced.