Architecture
BMC PATROL for PostgreSQL enables you to monitor local or remote database instances .
A typical architecture for BMC PATROL for PostgreSQLis as follows:
Local monitoring
UNIX remote monitoring
Windows remote monitoring
Data collection details
- In local monitoring, BMC PATROL for PostgreSQL starts a JAVA process. This JAVA process runs local queries from a PostgreSQL database to produce a list of instances and databases.
- For remote monitoring, the JAVA process identifies where the remote server is running. Based on the operating system, the Java process creates a remote client connection. For Unix, the remote connection is an SSH channel. For Windows, the remote client connection is an SSH or WMI channel. The same process logic applies as local monitoring.
- In the first inventory poll, the JAVA process discovers the PostgreSQL system (databases and table spaces) and creates the discovery tree for PATROL.
- After the discovery is complete, the JAVA collector starts collecting availability for the PostgreSQL instances, databases and partitions. The default availability poll cycle is 1 minute. The java process also starts to collect data performance, with a 5 minute poll interval. All of the poll cycles are configurable.
BMC PATROL for PostgreSQL collector details
The following table lists different BMC PATROL for PostgreSQL collectors and explains how they work:
Collectors | Description |
|---|---|
ConfigurationManager | Runs every 15 sec (default) and is responsible for checking if there was any change in the pconfig area. |
ChannelListener | Responsible for opening a channel and starts a Java process and to listen to the java channel for incoming data. |
AutoDiscovery | Run force discovery |
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*