AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    You can monitor any version of PostgreSQL with Database Visibility. 

    Connection Details

    SectionFieldDescription
    Create New CollectorDatabase TypeThe database type that you want to monitor.
    AgentThe Database Agent that manages the collector.
    Collector NameThe name you want to identify the collector by.
    Connection DetailsHostname or IP AddressThe hostname or IP address of the machine that your database is running on.
    Listener PortThe TCP/IP address of the port on which your database communicates with the Database Agent.
    Custom JDBC Connection StringThe JDBC connection string generated by the database agent, for example, jdbc:db2://. You can also specify a custom connection string, which is useful for setting custom authentication options.
    Username and PasswordUsernameThe name of the user who is connecting to and monitoring the database through the Database Agent. The user should have the permissions described in User Permissions for IBM DB2 LUW.
    PasswordThe password of the user who is connecting to and monitoring the database through the Database Agent.
    CyberArkClick to enable CyberArk for database username and password. When CyberArk is enabled, information about Application, Safe, Folder, and Object is required to fetch the username and password for your database. To use CyberArk with Database Visibility, you must download the JavaPasswordSDK.jar file from the CyberArk web site and rename the file to cyberark-sdk-9.5.jar. Then, you must copy the JAR file to the lib directory of the database agent zip file. 
    Advanced OptionsSub-Collectors

    Click to monitor multiple database instances in a consolidated view, and aggregate metrics of multiple databases. To monitor a custom cluster, you can add additional hostname or IP address, and port details for each sub-collector. You can add up to a total of 29 sub-collectors. Thereby, 30 databases can be monitored in a custom cluster. In addition to the licenses consumed by the main collector, each sub-collector consumes one or more licenses, depending on the database type.

    Note

    • All connection parameters other than the hostname or IP address, and port details of the sub-collector are the same as the main collector. If you want to specify different parameters for the sub–collectors, while creating or editing the collector configuration, you can do that only via the Create Collector API.

    • You cannot convert a custom cluster collector to a standalone collector. If you want to monitor a standalone database, delete the entire custom cluster collector and create a fresh standalone collector. However, note that deleting the custom cluster collector will delete all its historical data.
    Connection PropertiesClick to add a new JDBC connection property or edit an existing property for relational databases.
    EnterpriseDBClick if your PostrgreSQL database installation is an EnterpriseDB distribution. 
    Exclude DatabasesThe databases that you want to exclude, separated by commas. 
    Monitor Operating SystemSee this page for more details, Configure the Database Agent to Monitor Server Hardware.

    User Permissions for PostgreSQL

    The monitoring user must either have a role of superuser or be granted access to the pg_stat_activity table using the technique described below. 

     The following script allows you to create a SECURITY DEFINER function that is owned by the superuser, and runs the query you want, thus allowing non-superusers to see the contents of pg_stat_activity by calling the get_sa() function and pg_stat_statements by calling the get_querystats( ) function respectively. The script must be executed by the superuser.

    CREATE FUNCTION get_sa() RETURNS SETOF pg_stat_activity AS
    $$ SELECT * FROM pg_catalog.pg_stat_activity; $$
    LANGUAGE sql
    VOLATILE
    SECURITY DEFINER;
     
    CREATE VIEW pg_stat_activity_allusers AS SELECT * FROM get_sa();
     
    GRANT SELECT ON pg_stat_activity_allusers TO public;
    CREATE FUNCTION get_querystats() RETURNS SETOF pg_stat_statements AS
    $$ SELECT * FROM pg_stat_statements; $$
    LANGUAGE sql
    VOLATILE
    SECURITY DEFINER;
    CREATE VIEW pg_stat_statements_allusers AS SELECT * FROM get_querystats();
    GRANT SELECT ON pg_stat_statements_allusers TO public;

    The monitoring user must also be able to connect remotely to the PostgreSQL instance from the AppDynamics for Databases machine. 


    • No labels