Unable to View Diagnostics for Failed Flows/Integrations in Adeptia

Issue:

Diagnostics for failed process flows and integrations were not visible in the Adeptia.

Root Cause:

The log4j.rootLogger property is set to DEBUG, which creates too many logs. This causes:

• A high number of logs, making it difficult for the database to handle.

• Failover log files to be created instead of logs being stored in the database.

• The au_transactionlog table to remain empty, so diagnostics do not appear.

Solution:

Change the log4j.rootLogger property from DEBUG to ERROR. This reduces the number of logs, allowing them to be stored properly in the au_transactionlog table. Once this change is made, diagnostics start appearing in the GUI.

Recommendation:

If diagnostics are not visible, check the logging level in log4j.properties. Setting it to ERROR helps reduce excessive logging and ensures that logs are saved correctly in the database.