Im taking a look at perf_monitor_rdbms_slow.csv and tracing back some long running statements.whilst the log file gives me plenty of information for query types, any entry that is a write type does not provide Operation Name or Operation Detail, which is making it rather hard to debug.
Is there any way to trace these back into the other logs to find the culprit ? For example is the thread-id in the log, used in the other logs ?
Discussion posts and replies are publicly visible
The thread id in perf_monitor_rdbms.csv and perf_monitor_rdbms_slow.csv is the java thread id that you can use to search for the thread details in a java thread dump.
If you want the sql generated by the write to data store or queryEntity functions then enable the hibernate debug loggers as described here https://docs.appian.com/suite/help/19.3/Logging.html#adding-database-integration-details.