Discovery

This plugin can be integrated with Pandora FMS Discovery.

To do this, you should load the ".disco" package, which you can download from the Pandora FMS library.

Once loaded, you can monitor Microsoft SQL Server environments by creating Discovery tasks from the Management > Discovery > Applications.

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

Microsoft SQL Server target string: A list of Microsoft SQL Server targets to be monitored by the task. It will be a comma-separated or newline-separated list. Each target database can be defined in the format IP:PORT\INSTANCE, IP:PORT, IP\INSTANCE, or IP.

If you want to monitor specific databases of an instance, you must specify them with "|" and separate each database with ";".

Example :
```
172.17.0.4:1433\DEVENV|pandora;testing;model
```
If you want to monitor all the databases of an instance, but discard some, you must specify “!” before the “|”.

Example:
```
172.17.0.4:1433\DEVENV!|pandora;testing;model
```
User: The connection user for the target databases.
Password: The password for the specified user.

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

Max threads: To optimize execution time, you can configure multiple threads to monitor the task's agents. Keep in mind that configuring multiple threads may increase the CPU usage of the task.
Target agent: List of target agents for the Microsoft SQL Server targets to be monitored. These are the names under which agents for each defined target in the task will be generated. It should be a comma-separated or newline-separated list. The position of the names in the list should match the position of the Microsoft SQL Server targets in their list, meaning 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 no agent name is 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's useful for locating modules generated by the task or distinguishing them from others.
Entities list path : Entities list path, by default : "/tmp/mssql_entities_list.txt"
Scan databases: Activate to monitor the databases of the instances.
Create agent per database: Activate to create an agent for each monitored database.

Retrieve logs statistics: If enabled, it will monitor log statistics.
Monitor active users: If enabled, it will monitor active users.
Retrieve transactions statistics: If enabled, it will monitor transaction statistics.
Monitor filegroups space: If enabled, it will monitor filegroup space usage.
Monitor user reserved space: If enabled, it will monitor user reserved space.
Monitor backups: If enabled, it will monitor backup status.
Check engine uptime: If enabled, it will monitor engine/instance uptime.
Retrieve query statistics: If enabled, it will monitor query statistics.
Analyze connections: If enabled, it will monitor connections.
Monitor long queries: If enabled, it will monitor long-running queries.
Monitor latch requests: If enabled, it will monitor latch requests.
Monitor full scans: If enabled, it will monitor executed full scans.
Count databases: If enabled, it will monitor the number of databases.
Retrieve memory statistics: If enabled, it will monitor memory statistics.
Retrieve locks statistics: If enabled, it will monitor lock statistics.
Check engine performance: If enabled, it will monitor engine/instance performance.
Retrieve buffer statistics: If enabled, it will monitor buffer statistics.
Retrieve users information: If enabled, it will monitor user information.
Retrieve Cluster State: If enabled, it will monitor the cluster state.

Rename default modules: If enabled, it will allow renaming the default modules.
Modules names: Configuration block to define the names of the default modules.
Execute custom queries: If enabled, it will allow executing custom queries on each Microsoft SQL Server target.
Custom queries: Configuration block to define the custom queries to be executed. Each query will generate a new module for each task agent.

Successfully completed tasks will have an execution summary with the following information:

Tasks that do not complete successfully will have an execution summary that records the errors encountered.