Since three years, SAP IT uses SAP Advanced Event Mesh for internal projects . Over time, its usage has grown to more than 70 projects.
One of the use cases for SAP Advanced Event Mesh  is distributing s-user data to from the central S/4HANA system to a BTP app for further processing. As the event production and the event consumption is handled by two different groups, the issue was raised whether the event has reached the BTP app or not. We solved this by using one of SAP IT Dynatrace instances to store the trace data coming from AEM Advanced Event Mesh, so that both parties can verify whether an s-user creation, change or deletion has happened in the source system and whether this information has  been moved to SAP Advanced Event Mesh for consumption on a message queue.

First, we had to solve the problem how to store the S-USER ID as the a trace ID  as part of the event. As we did not find a standard way in the SAP NetWeaver Add-On for ERP nor could we use header attributes (e.g. Solace-User-Property- = ) which would have been part of the SAP Advanced Event Mesh rest endpoint call, we decided to add the S-User ID dynamically to the topic name of the event.

Next to the configuration steps on SAP Advanced Event Mesh (see blog: Configure SAP Integration Suite, Advanced Event Me… – SAP Community), an otel collector (https://open-telemetry.github.io/opentelemetry-helm-charts) needed to be deployed & configured on one of SAPs Kybernetes cluster which would read the open-telemetry queue configured on SAP Advanced Event Mesh and push it to the relevant Dynatrace instance for temporary storage .

Using the out of box search/display interface of Dynatrace, allows the support agent to query if an S-user event has already reached SAP Advanced Event Mesh  as well as if it has been consumed by the target application.