LogoLogo
CommunitySupport PortalYouTubeStart a free trial
OE (Celonis)
  • Welcome
  • Commerce Engine
  • Orchestration Engine
  • API Documentation
  • Release Notes
  • Changelog
OE (Celonis)
  • Orchestration Engine
  • Getting Started
    • What is OE?
      • What are the benefits?
      • Use Cases
    • Provisioning
    • Understanding Make
    • OE Learning Trails
      • Setting up a First Digital Process
      • Adding a Conditional Step in a Digital Process
  • Management Dashboard
    • Accessing OE
    • Orchestration Center
    • Forms
    • KPIs and Analytics
    • Rulestore
    • Events
      • Event Registry
      • Event Log
      • Cloud Events in OE (Celonis)
      • Events Authentication and Configuration
      • Working with Event Data (Celonis)
    • Admin
      • Users and Roles
      • Integration with Celonis
      • Make Team
      • Task Inbox and Tasks
  • Digital Processes
    • Digital Processes Dashboard
    • Digital Processes Example
    • Working with Digital Processes
      • Digital Process Components
      • Creating a Digital Process
      • Editing a Digital Process
      • Testing a Digital Process
      • Conditional Process Runs
      • OE Make Modules
      • Configuring a Connection between OE and Make Modules
      • Setting a Trigger to Wake Up a Paused Digital Process (Celonis)
      • Cloning of Make Scenarios in OE Digital Processes
    • Data Flow between OE and Celonis
      • Retrieving Data from Celonis
      • Sending Data from OE to Celonis (Celonis)
      • Sending Form Submission Data from OE to Celonis (Celonis)
      • Sending Forms Magic Links Data from OE to Celonis (Celonis)
    • Process Context
    • Datastore
    • Versioning
    • Data Retention Policy
  • Troubleshooting
    • Firewall Allowlisting
    • Digital Processes Debugger
    • Generating a HAR File with Logs
    • FAQ
      • Receiving Alerts for Scenario Errors
      • Make Scenario Not Valid in OE
      • Digital Processes Blocked by Scenario Errors
      • Invalid Digital Processes
Powered by GitBook
LogoLogo

Resources

  • Emporix.com
  • Developer Policy
  • Terms of Use

Find us

  • LinkedIn

© 2025 Emporix. All Rights Reserved.

On this page

Was this helpful?

Export as PDF
  1. Management Dashboard
  2. Events

Event Log

Track and monitor operations happening in OE.

PreviousEvent RegistryNextCloud Events in OE (Celonis)

Last updated 9 days ago

Was this helpful?

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.

  • 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.

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

Event Registry