MySQL Infrastructure Agent not reporting MySQL metrics and throwing below exception:
9/29/20 10:01:59 AM CDT [ERROR] [IntroscopeAgent.DBMonitor]
java.sql.SQLSyntaxErrorException: (conn=13762) Table 'performance_schema.global_variables' doesn't exist
at org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.get(ExceptionMapper.java:243)
at org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.getException(ExceptionMapper.java:164)
at org.mariadb.jdbc.MariaDbStatement.executeExceptionEpilogue(MariaDbStatement.java:258)
at org.mariadb.jdbc.MariaDbStatement.executeInternal(MariaDbStatement.java:349)
at org.mariadb.jdbc.MariaDbStatement.executeQuery(MariaDbStatement.java:595)
at com.ca.agent.extensions.dbmon.commands.DBMonExecuteQueryCommand.fireAndUpdateMetric(DBMonExecuteQueryCommand.java:158)
at com.ca.agent.extensions.dbmon.commands.DBMonExecuteQueryCommand.execute(DBMonExecuteQueryCommand.java:123)
at com.ca.agent.extensions.dbmon.DBMonChain.run(DBMonChain.java:66)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.sql.SQLException: Table 'performance_schema.global_variables' doesn't exist
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.readErrorPacket(AbstractQueryProtocol.java:1599)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.readPacket(AbstractQueryProtocol.java:1461)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.getResult(AbstractQueryProtocol.java:1424)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.executeQuery(AbstractQueryProtocol.java:178)
at org.mariadb.jdbc.MariaDbStatement.executeInternal(MariaDbStatement.java:343)
... 7 more
DX Application Performance Management MySql SaaS Agent.
MySQL 8.x release.
This happens due to the incompatibility of MySql database, make sure that you are trying to monitor MySQL database 8.x which is supported by Broadcom.
Any other MySql that you try to monitor, you will see the exception reported in this knowledge article.