Discovery

This plugin can be integrated with Pandora FMS Discovery.

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

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

The following minimum data will be requested for each task:

PostgreSQL target strings: List of PostgreSQL targets to be monitored by the task. It will be a comma or line separated list. Each target database can be defined with the format IP:PORT or IP.
User: User of connection to the target databases.
Password: Password of the specified user.

You can also adjust the task configuration to customize the desired monitoring:

Max threads: To optimize execution time, multiple threads can be configured to monitor the task agents. Keep in mind that setting up multiple threads can increase the CPU usage of the task.
Target agent: List of target agents for the PostgreSQL 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 lines. The position of the names in the list should match the position of the PostgreSQL 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.
Scan databases: If activated, the different databases of each PostgreSQL target will be monitored.
Create agent per database: If activated, a different agent will be created for each database of each PostgreSQL target. Database monitoring needs to be enabled for it to work.
Custom database agent prefix: Text included as a prefix for the names that will be generated for the individual agents for each database of each PostgreSQL target. It is useful to locate the agents generated by the task or distinguish them from others.
Check engine uptime: If activated, it will monitor the uptime of the objectives.
Retrieve query statistics: If enabled, it will monitor query statistics.
Analyze connections: If activated, it will monitor the connections.
Calculate fragmentation ratio: If activated it will monitor the fragmentation ratio statistics.
Retrieve cache statistics: If enabled, it will monitor cache statistics.
Execute custom queries: If activated, it will allow you to execute custom queries to each PostgreSQL target and each database.
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.

Tasks that are not completed successfully will have an execution summary recording the errors that occurred.