• The integration can manage critical/recovery failure alerts for the following two scenarios when the user activates App Failure Notifications in the settings:
    • Connectivity Exception
    • Authentication Exception
  • PostgreSQL Cluster will send any duplicate/repeat failure alert notification for every 6 hours.
  • PostgreSQL Cluster cannot control monitoring pause/resume actions based on above alerts. Metrics can be used to monitor PostgreSql Cluster resources and can generate alerts based on the threshold values.
  • We have provided 5432 as default Port value for connecting postgresql DB. Also, the default postgresDatabaseName is populated as “postgres”. Users can modify this value from application configuration page at any point of time if requires. Component level thresholds can be configured on each resource level.
  • No support of showing activity logs.
  • The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
  • Latest snapshot metric support from gateway version 14.0.0.
  • This application supports both Classic Gateway and NextGen Gateway.

Troubleshooting

Before troubleshooting, ensure all prerequisites prerequisites are met.

If PostgreSQL Cluster integrations fail to discover or monitor, troubleshoot using the following steps:

  • Check if any alerts have been generation on PostgreSQL Cluster, the gateway, or in vprobe.
  • If there is an error or alert related to the end device connectivity or authentication, try checking the reachability of the end device from the gateway with the following commands:
    • to ping the IP address provided in the configuration: {ping <IP Address>}
    • to try telnet: {telnet <IP Adress> <Port>}
    • to try ssh to the end device from the gateway {ssh <username>@<node IP Address>}
    • To run an ssh command and DB command:

      • Prepare the request payload by using below sample request:

        { “apiVersion”: “debug/v1”, “module”: “Debug”, “app”: “postgresql-cluster”, “action”: “Reachability”, “payload”: { “ipAddressOrHostName”: “”, “protocol”: “https”, “port”: 443, “requestPath”: “”,

        “version”:“v1”,

        “requestMethod”:"<get/post>", “userName”: “”, “password”: “” } }

      • Encode the request payload to base64

      • Log in to the gateway concole and connect to the GCLI terminal using the below command: {## gcli}

      • Run the command using the previously generated base64 encoded string {## sdkappdebug <base64 encoded string>}