Event Monitoring currently exposes the REQUEST_ID as a field:
- The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST_ID.
This detail could be extremely useful for tying together a transaction with its corresponding ApexLog, Event Monitoring, and Change Data Capture.
For instance, if there was an exception the message that is displayed to the user could include unique Request ID. That could then be used by someone providing support to directly find a corresponding ApexLog and/or EventLog entry.
This would need a method in Apex that returns the request ID string.