Note: Available only for new signups after the 31 March, 2026 release. If you signed up earlier, refer to the existing ITAM documentation.

PostgreSQL database discovery is designed specifically for *nix targets. It retrieves comprehensive instance details, connection information, and schema data. By automating this process, you ensure that your inventory remains current with the latest database configurations and active service instances across your network.

Minimum permissions requirements 

For the discovery process to return detailed information about your database instance, the database user must have access to the following system tables and functions:

• pg_database (table)

• pg_tablespace (table)

• pg_stat_activity (table)

• inet_server_addr() (function)

Set up a PostgreSQL Discovery job

Follow these steps to establish a connection to your PostgreSQL environment and configure a discovery job.

1. Go to Admin > Asset Management > Scan and discover and click the Discovery Jobs tab.

2. Select Hypervisors/*nix/win Autodiscovery from the list of discovery jobs and click Add new.

3. Select *nix job type as your target platform..
   

4. Enable the Collect database server information toggle.

5. Fill out both sets of credentials:

   • Database Username / Password(s): Credentials to authenticate to the Oracle database.

   • Discovery Target(s) Credential(s): Credentials to authenticate to the host server.

Note: You can enter multiple credentials in a preferred order. The job tries each credential in order and stops at the first successful authentication. Subsequent runs start with the last successful credential.

6. Click Save.

7. Click Run Now on the job details page to test the connection.

View discovery results

Locate and analyze the details of your discovered Oracle instances through the application components.

Application components

View the high level service details and dependency maps for your environment.

1. Navigate to Applications > Application Components.

2. Search for Postgres to filter the list.
   

3. Click a database name to view its specific details. You can access Server Instances,  Dependency Chart, Impact Chart, or Impact List.