Agents and modules generated by the plugin
The plugin will create an agent for each target database. That agent will contain the following modules
If engine_uptime is activated:
| restart_detection | It will be 0 if an unexpected restart has been detected, and 1 if this is not the case. When a server restarts unexpectedly, there may be an interruption in access to the database and potentially lost transactions or data not saved correctly. |
If query_stats is activated:
| queries: select | Number of SELECT queries. SELECT queries are used to retrieve data from the database. Monitoring SELECT queries allows you to assess query efficiency and index optimization. By identifying slow or inefficient SELECT queries, you can take steps to improve their performance, such as adding appropriate indexes, optimizing the queries, or adjusting server configuration. |
| queriers: update | Number of UPDATE queries. UPDATE queries are used to modify existing data in the database. Monitoring UPDATE queries is important to assess the frequency and efficiency of data updates. You can identify UPDATE queries that affect a large number of rows or have a significant impact on server performance. This allows you to optimize queries, review table structure, or take steps to reduce the load generated by updates. |
|
queries: delete |
Number of DELETE queries. DELETE queries are used to delete data from the database. Monitoring DELETE queries is useful for evaluating the frequency and efficiency of data deletions. You can identify DELETE queries that affect a large number of rows or that have a significant impact on server performance. This allows you to optimize queries, review table structure, or take steps to reduce the load generated by deletes. |
| queries: insert | Number of INSERT queries. INSERT queries are used to insert new data into the database. Monitoring INSERT queries allows you to assess the frequency and efficiency of data inserts. You can identify INSERT queries that are placing a high load on the server or could be causing performance issues. This allows you to optimize queries, review table structure, or consider lazy insert strategies to improve performance in high-concurrency environments. |
If analyze_connections is activated:
| session usage | Number of current connections with respect to the total of maximum connections. Monitoring session usage in SQL Server is important to optimize performance, identify blocking issues, improve security and auditing, and efficiently plan server resources. |
If cache_stats is enabled:
| allocated buffer cache |
Total memory space to store temporary data. The cache buffer is a critical part of memory management in PostgreSQL, as it stores data retrieved from tables and is used to reduce the need to constantly access disk storage. |
| backend user buffer cache | Memory space per user for quick access. Each user connection can have its own buffer cache to temporarily store the data it accesses. This can help reduce the need to access the shared cache buffer. |
| checkpoints buffer cache | Temporary memory to synchronize data with disk. The checkpoint buffer cache temporarily stores data related to the checkpoint process. A checkpoint is a point in time at which PostgreSQL ensures that modified data has been written to disk. |
| cleaned buffer cache | Space for unmodified data, reducing disk reads. Maintaining a buffer cache for clean data can help reduce the need to read data from disk storage, thereby improving the performance of database queries and operations. |
If fragmentation_ratio is activated:
| fragmentation ratio | The fragmentation ratio. The Fragmentation Ratio in |
The plugin will also create a module for each custom query defined in the configuration file.