- 2 minutes to read

What is a Nodinite Logging Agent?

Nodinite Log Agents deliver true end-to-end logging and event tracking for all your integration platforms. This page explains how Log Agents work, how they uniquely identify event sources, and how you can leverage them for advanced monitoring, troubleshooting, and business insight.

✅ Achieve end-to-end logging across all integration brokers, ESBs, and custom code
✅ Uniquely identify every event source for precise tracking
✅ Map Log Status Codes for actionable monitoring and business-friendly reporting
✅ Integrate with any system using flexible APIs and asynchronous pickup

The Logging feature of Nodinite includes one or more Log Agents that create Log Events from system integration brokers, ESBs, or custom code. Each Log Agent provides detailed event information, including payload and context, for complete visibility.

You can view and manage all Log Agents in the Overview.

graph LR subgraph "fal:fa-code-commit Nodinite" A[fal:fa-archive Log Agent ] --- broker[Integration Broker/ESB/Custom Code] A --- |Log Events| roNI[Nodinite Log API] end

Diagram: Log Agents connect your integration brokers and custom code to Nodinite's Log API for unified event tracking.

Unique Identification and Management

Each Log Agent uses a unique Id (Log Agent Value Id). Every Log Event from a Log Agent includes this identifier. Nodinite automatically creates the Log Agent entry during the first event, using the default name Not Set. Administrators should rename this to something descriptive, such as 'BizTalk 2016 - PROD' or 'iCore - Test', for clarity.

Log Status Codes

Each Log Agent may log events and messages with an optional status code. For more information, see the Log Status Codes user guide.

Troubleshooting

How do I add or manage Log Agents?
Manage Log Agent information using the Nodinite Web Client.

Where do Log Agents come from?
A Log Agent can be custom-built or provided by Nodinite. See Logging for more details.

Can I build my own Log Agent?
Yes! You can send Log Events directly to the Log API (not recommended) or create a JSON Log Event for the Pickup Service to fetch asynchronously (recommended). Every Log Event includes an identifier for the Log Agent.

Next Step

Add or manage Log Agents
Log Status Codes

Log Events
Log Views
List of Logging