# Pandora AzurePostgresql # Introduction **Ver.** 23-08-2022 Plugin with which to monitor an azure postgresql data server. **Type:** Server plug-in # Compatibility matrix
**Systems where tested** | CentOS 7, Fedora, rocky linux |
**Systems where it should work** | Any linux system |
**Parámetro** | **Descripción** |
--timespan | In hours (optional), last time period, can be used in a custom run to display data from a time period (optional). |
--metric | Metric name for custom execution (optional). |
--granularity | In minutes combined with timespan it will show you the data in intervals (optional). |
--name\_module | To choose the name of the module in a custom run (optional). |
--tentacle\_port | Tentacle port Default 41121(optional) |
--tentacle\_address | Ip of the tentacle server to send the data (optional) |
--agent\_name | To name the agent that will contain the modules, by default: "Azure SQL" (optional). |
--prefix\_module | To prefix the modules in case you want to differentiate them from other executions (optional). |
--conf | Path of the conf file with the queries (required) |
-g,--group | Pandora FMS target group (optional) |
--data\_dir | Pandora FMS data directory. By default it is /var/spool/pandora/data\_in/ (optional) |
--as\_agent\_plugin | It is optional, if you want the plugin to be an agent plugin and put the modules in the pandora agent, execute this with a 1 (optional) |
Remember that the recommended path for the use of the server plugins is: /usr/share/pandora\_server/util/plugin/
And in parameters of the plugin we will introduce these followed by the macro "\_field<N>\_", the obligatory one for it to work is --conf.Although it is not mandatory, it is highly recommended the use of the --agent\_name parameter, since it allows us to customize the name of the agent that will contain the modules created for each customized query. It is also advisable to use the --prefix\_module parameter, because this will allow us to assign a prefix to the modules, which can be useful to recognize them faster and differentiate them if we create several executions for different databases.
**--CONF** [](https://pandorafms.com/guides/public/uploads/images/gallery/2022-06/image-1656438528074.png) Once this is done, we will click on "create". Once this is done, the only thing left to do is to call it, so we will go to some agent's view and create an add-in module: [](https://pandorafms.com/guides/public/uploads/images/gallery/2022-03/image-1646741530197.png) We will give it a name and in the section "plugin" we will put the one we have just configured. Once this is done, click on create. If the module is shown with 1, it means that it is running correctly. # Modules generated by the plugin The plugin will create an agent with the name we have set with the --agent\_name parameter. [](https://pandorafms.com/guides/public/uploads/images/gallery/2022-08/image-1661255594501.png) And it will create the following modules:cpu_percent |
memory_percent |
io_consumption_percent |
storage_percent |
storage_used |
storage_limit |
serverlog_storage_percent |
serverlog_storage_usage |
serverlog_storage_limit |
active_connections |
connections_failed |
backup_storage_used |
network_bytes_egress |
network_bytes_ingress |
pg_replica_log_delay_in_seconds |
pg_replica_log_delay_in_bytes |