Event Directions

Unlock granular, end-to-end message tracking and filtering with Nodinite's Event Directions. This feature empowers both business and technical users to distinguish messages at every stage of integration, providing actionable insights and supporting compliance, troubleshooting, and business process optimization.

✅ Gain full visibility into message flow before and after each process step
✅ Filter and group Log Events by direction for precise business and technical analysis
✅ Empower self-service users with tailored Log Views
✅ Enhance compliance and troubleshooting with detailed event context

Helps you and your business filter Log Events so you can distinguish the same message before and after port/workflow processing

EventDirections is an optional numeric field in Log Events that qualifies the direction of a logged event. Use it to create fine-tuned, self-service Log Views for your business, enabling you to focus on the most relevant data at each integration point.

High-level design and implementation details

In any messaging process, multiple steps occur—some internal, some external. Event Directions let you pinpoint exactly where a message is in the process, such as:

• Message before decryption
• Message after decryption
• Message before encryption
• Message after encryption
• Message batch before a split
  • Messages after the split
• Flat file before being translated to XML (e.g., BizTalk, IBM IIB, or other brokers using flat file schemas on a Receive port)
• Flat file after being translated from XML (e.g., BizTalk, IBM IIB, or other brokers using flat file schemas on a Send port)
• Workflow/Orchestration inside a loop generating new messages

There are countless scenarios. The Event Direction property provides the Log Event with location semantics—such as before port, after port, inside workflow, or inside process—enabling true end-to-end logging and analysis.

How do I use Event Directions in a Log View?

From Log Views, you can search and group Log Events by the selected Event Direction.

Event Direction being used from within a Log View.

This feature allows you to hide internal events that may not be relevant to business users, focusing instead on what came in or went out (the net result). Conversely, developers can view every detail of the process.

Filtering Log Events by Event Direction for targeted analysis.

List of values to set the Event Direction for logged messages.

File transfer example

Illustration of Event Directions in a file transfer scenario.

API example

Illustration of Event Directions in an API integration scenario.

Combined Event Directions

From Log Views, you can search and group Log Events by combinations of Event Directions. This enables you to, for example, only see messages before and after processing for a given workflow (e.g., lines 1 and 5).

Valid combinations include:

Valid combinations of Event Directions available from within Log Views.

List of helpful values for use in Log Views.

Try it out yourself

To see the full list of values for your version, simply test the Log API.

 https://localhost/Nodinite/LogAPI/swagger/ui/index#/LogEvent/LogEvent_EventDirection

Replace https://localhost/Nodinite as appropriate for your Environment.

Event Direction collection from the Swagger documentation

Simply press the Try it out button:

To get the list of Event Directions, press the Try it out button.

Then, press the Execute button:

Execute the request to retrieve Event Directions from the API.

Here's an example of EventDirections from the Swagger definition.

Next Step

• Log Event
  • JSON Log Event
  • Context Options
• Endpoints
  • Endpoint Types
  • Endpoint Directions

Related Topics

Log Agents