Event Log

Track and monitor operations happening in OE.

Event logs are records that track important actions and incidents in a system or network, like errors or user activities. They help to monitor the system by providing details on when, where, and what happened.

In the OE Event Log main view, you can check records of all the events that were received for your digital processes. You can search the results with the Request ID for which the event occurred. You can also see when the data was received and whether the call was successful.

Request ID - it's an identifier of the signal sent to OE to start a digital process, for example: req_NkMdGRM1paSsrootCUhf. You can find the Request ID in the debug mode in the Webhook logs of the trigger:

To see more detailed logs, select the event you're interested in.

Then you can see a popup window with details including:

• ID - it's the ce-id that is sent in a request, it represents the unique identifier for the event instance.

• Source - information about where the event occurred, for example: emporix/oe.

• Type - event name, it can be checked in the Event Registry, for example: order.stock.checked.

• Time - timestamp showing when the event occurred, for example: 2024-04-29T13:48:13.992+00:00

• Instance ID - ID of the digital process instance where the event occurred, for example: 01HQRB60P23FQ5DV8X8SPH4NED-01H7YP07GX9TFBK2S0RRRT11WY-01HWN1SXGG90FP1M6HWWZ9Y5JR.

• Scenario - the name of the Make scenario for which the event is configured and where it occurred, for example: Send Quote (1343). The copy button copies the scenario link.

  When you click the scenario link in the logs, it opens the scenario in Make.

• Scenario Run ID - the ID of a specific scenario execution where logs are stored, for example: abb589c4c9cd4cdbbe428f949d3d980a.

  When you click on the run ID link, it opens the logs of a specific scenario execution in Make.

• HMAC - details of the keyed-Hash Message Authentication Code secret.

• ce-specversion - the version of the CloudEvents specification with which the event is compliant, for example: 1:0.

• User-agent - Emporix Orchestration/production

• Payload - event payload details, for example:

  
  "root":{
      "globalAvailabilty":[
          0:{
          "id":"15536937"
          "globalStock":40
          "orderedAmount":1
          }
          1:{
          "id":"20635992"
          "globalStock":12
          "orderedAmount":1
          }
      ]
  }

Logs details also allow to get all of the event information in a CURL format, use the Copy as CURL for that.