Dumping CommitDebug information when latency spike?

We are facing situation when we have sudden spikes in the p99.9 latency of commits and we would like to investigate a bit more. I looked at CommitDebug information roughly doing the delta of the timestamp of message with location CommitProxyServer.commitBatch.AfterReportRawCommittedVersion which should be more or less the last message - message with location CommitProxyServer.commitBatch.Before but it seems because of sampling I’m only getting message that somewhat show the average value maybe p90 once in a while.
I’m wondering if there is a way to trigger the generation of message if the overall latency of the transaction was >Xms