- 2 minutes to read

Log Event

Achieve true end-to-end visibility for your integrations with Nodinite Log Events. This page explains how Log Events work, the benefits of synchronous and asynchronous logging, and how to leverage JSON-based events for robust, decoupled, and future-proof solutions.

What you'll find on this page:

✅ How Log Events enable end-to-end logging across any platform
✅ Synchronous vs. asynchronous logging patterns explained
✅ JSON-based Log Events for flexible, vendor-neutral integration
✅ Best practices for decoupled, reliable event delivery
✅ Context options and repository auto-mapping

Nodinite enables End-to-End Logging using either "out of the box" Log Agents or your own custom code. You can use both synchronous and asynchronous message exchange logging patterns to fit your architecture and business needs.

graph LR subgraph "Log Monitoring Agent Configuration" roMessageBroker[fal:fa-archive Nodinite Log Agents
BizTalk, Mule, Logic Apps, ...] roLogSink("fal:fa-bolt Custom Logging Solution") --> roId1["fal:fa-list Queue
fal:fa-folder Folder
..."] end subgraph "Web Server" roLogAPI(fal:fa-cloud-arrow-down Log API) roPS(fal:fa-truck-pickup Pickup Service)--> roLogAPI roId1 -.Log Event.-x roPS roLogSink --> |Log Event|roLogAPI roMessageBroker --> |Log Event| roLogAPI end

Architectural examples with synchronous and asynchronous logging.

We recommend the asynchronous logging pattern for maximum reliability and scalability.

What is a Log Event?

A Nodinite Log Event is a JSON object that represents a business or technical event. You can send Log Events directly to the REST-based Log API or persist them for the Pickup Service to fetch asynchronously. Asynchronous delivery means:

  • Your logging solutions have no dependency on the Log API (reboot/update whenever you like)
    • No need to implement custom retry logic
  • Improved concurrency and reliability—Pickup Service manages delivery and prevents overload
  • Flexible, decoupled architecture for future-proof integrations

A Log Event consists of:

  • Log Event (Mandatory) – Generic information about the event (e.g., time, message type, endpoint) – WHEN, HOW
  • Payload (Optional) – The business transaction data, usually XML, JSON, flat files like EDI/X12, or zip files, defined by a Message Types – WHAT
  • Context Properties (Optional) – Key-value pairs of arbitrary data (e.g., InvoiceId, CorrelationId) – WHAT
graph TD subgraph "Event" subgraph "Details" roED[fal:fa-bolt Event Details
LogDateTime = 2018-05-03 13:37:00+02:00
EndPoint = https://api.nodinite.com/...
MessageType=Invoice
...] end subgraph "Payload" ro[fal:fa-envelope Message
base64EncodedMessage] end subgraph "Context Properties" roKey[fal:fa-key Key Values
InvoiceNo = 123
CorrelationId=456
...] end end

The architectural layout of a Log Event

Models

The Log API includes details from the following Model entities:

How do I send Log Events using REST?

Follow the 'Log using REST' article to learn more about sending Log Events via REST.

Repository

Log Events can "auto-populate" the Repository Model with special content. This drastically reduces administration and automatically transfers know-how from developers to business and IT operations teams.

Important

You must enable the 'AllowRepositoryAutomapping' System Parameter for the Logging Service to honor the provided Repository Model related data.

Next Step

Log API
JSON Log Event
Context Options

Repository Model
Log Views
Log Agents
Endpoint Types
Endpoint Directions