# Parameters and configuration **Parameters**
--conf | Path to the configuration file. |
--target\_databases | Path to the configuration file containing the database targets. |
--target\_agents | Path to the configuration file containing the agent targets. |
--custom\_queries | Path to the configuration file containing custom queries. |
The standard installation of instant client 19.8 is done in the /usr/lib/oracle/19.8/client64/lib path.
**List of target databases (--target\_databases)**: The content of the file should be a list of target databases, with each database separated by commas or lines. The format for a database can be any of the following: ``` ip/sid ip:puerto/sid ip:puerto/service_name ``` If the port is not specified, the default TCP port 1521 will be used for connecting to the target. Example: ``` 172.17.0.3:1521/FREEPDB1 ``` Each line in the file should represent a separate target database using one of these formats. This file is used to specify the databases that the plugin should monitor. **List of target agents (--target\_agents):** The content of the file should be a list of agent names, with each agent separated by commas or lines. These agent names will be used to associate the information from each target database with the corresponding specified agent name, instead of letting the plugin generate agent names automatically. The position of each agent name in the list should match the position of the target database in its own list. In other words, the name for the first target database should be the first name in this list, considering that blank lines are ignored. Example: ``` agente1,,agente3 agente4 agente5,agente6,agente7,,agente9 ``` **Custom queries (--custom\_queries)** A module must be introduced for each custom query that is intended to be monitored. The modules must follow a structure, which is as follows: ``` check_begin --> Module opening label name --> Module name description --> Description of the module. operation --> Operation type datatype --> Module type min_warning --> Configuration of the minimum warning threshold max_warning --> Configuration of the maximum warning threshold str_warning --> Warning string configuration warning_inverse --> Activate the inverse interval with 1 for warning threshold min_critical --> Setting the minimum critical threshold max_critical --> Setting the maximum critical threshold str_critical --> Critical string configuration critical_inverse --> Activate inverse interval with 1 for critical threshold module_interval --> This interval is calculated as a multiplier of the agent interval. target --> Custom query target_databases --> Database agents in which the module will be created check_end --> Module closing tag ``` Example: ``` check_begin name Select 1 description Number of invalid objects operation value datatype generic_data min_warning 5 target SELECT 1 FROM dual target_databases all check_end check_begin name NumeroConexiones description Number of connections operation value datatype generic_data min_warning 5 target SELECT COUNT(*) AS NumeroConexiones FROM v$session; target_databases pandora check_end check_begin name NumeroRegistros.files_table description Invalid objects (detail) operation full datatype generic_data target SELECT COUNT(*) AS NumeroRegistros FROM files; target_databases pandora check_end ```