If you suspect that Germain monitoring is not functioning properly and data is not being stored in the Germain database, you can verify if metrics are being stored in the database by following these steps:
Connect to the Germain database (Germain_DATAMART).
Execute one of the following queries based on your database type:
sqlCopy codeSELECT t.* FROM GENERIC_METRIC t WHERE t.timestamp BETWEEN (DATE_SUB(NOW(), INTERVAL 30 MINUTE)) AND NOW();
sqlCopy codeSELECT t.* FROM GENERIC_METRIC t WHERE t.timestamp >= sysdate - 30 / (24 * 60);
These queries will retrieve the metrics data from the GENERIC_METRIC table within the last 30 minutes (adjust the time range as needed).
If you see new data in the GENERIC_METRIC table, it indicates that metrics are being stored in the database. In this case, the issue may lie elsewhere, such as server-side errors or configuration problems. Review the storage-services.log file for any errors related to license expiration, license limit exceeded, or other relevant errors.
If you don't see any new data in the GENERIC_METRIC table, but the message queues (MQs) are receiving data (refer to Apache ActiveMQ Troubleshooting), then the problem likely exists on the server side. Check the storage-services.log file for any errors that may provide insights into the issue.
If the MQs are also not receiving data, review the logs of the Engines for any potential errors or issues that may be preventing the collection and storage of metrics data.
By examining the metrics data stored in the GENERIC_METRIC table and reviewing the appropriate logs, you can determine if Germain monitoring is successfully storing data in the database or identify any potential issues that need to be addressed.