I deployed a jdbc_response probe on a Linux server and configured it. Successfully connected with the Postgresql server. After that when I tried to create a profile for a query request it's turning to down.
From the logs you can see that the jdbc probe was constantly restarting.
And this error is thrown:
[main, jdbc_response] (90) Configuration error, Config error at line 363frompg_stat_all_tables; missing '='
Controller: Max. restarts reached for probe 'jdbc_response' (command = <startup java>)
1. Check if the user has access to pg_stat_all_tables view.
Please test it by logging in as that user and running a select * from pg_stat_all_tables
PostgreSQL:
Download the latest version of PostgreSQL JDBC driver JAR file from
2. Restart the probe after storing the driver files in the jdbc_response probe installation directory.
3. Please set the controller and jdbc_response robe loglevel to 5 and logsize to 20000.
Deactivate the probe.
Activate the probe
4. Note that the jdbc_response probe does not support extended properties and only supports connection strings as follows:
jdbc:oracle:thin:@IP address:Port Number:Database Name
jdbc:oracle:thin:@database server name:Port Number:Database Name
Therefore it is not possible to connect using additional properties (such as alternate protocols, etc). TCP protocol is used by default, TCPS and others are not supported.
jdbc_response probe troubleshooting
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/bigdata-databases-and-storage/jdbc-response-java-database-connectivity-sql-queries-response-monitoring/jdbc-response-troubleshooting.html
5. Check the installation considerations here:
The jdbc_response probe, by default, installs the JDBC drivers for Microsoft SQL Server and Oracle databases.
To monitor other databases, the appropriate driver, as a JAR file, must be downloaded and stored on a system from where the probe can access it.
***The probe could start and continue running without restarting after removing the query that was causing the probe to be unstable - after examining the log files that show the error from the specific query***