- 3 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. Your users then search those events in Log Views, and the Logging Service stores them in the Log Databases.

You can view and manage all Log Agents in the Log Agents Overview. From there you can add new Log Agents, edit existing ones, delete, or restore Log Agents.

graph LR broker["fa:fa-sitemap Integration Broker,
ESB, or Custom Code"] subgraph "Nodinite" A["fa:fa-archive Log Agent"] roNI["fa:fa-cloud-arrow-down Log API"] LV["fa:fa-hard-drive Log Views"] end broker -->|"events"| A A -->|"Log Events with
Log Agent Value Id"| roNI roNI -->|"searchable in"| LV style broker fill:#9E59BB,color:#fff style A fill:#2678BD,color:#fff style roNI fill:#2678BD,color:#fff style LV fill:#3F827B,color:#fff

Diagram: Log Agents (blue) connect your integration brokers and custom code (purple, external) to the Nodinite Log API, and users search the result in Log Views (teal).

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; see Log Agent Value Id for how to choose and keep the Id. Administrators can also limit a Log View to selected Log Agents on its Data to search tab.

Log Status Codes

Each Log Agent may log events and messages with an optional status code. For more information, see the What is a Log Status Code? user guide. To configure Log Status Codes for your Log Agent, see Add or manage Log Status Codes.

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 Nodinite Pickup Log Events Service Logging Agent to fetch asynchronously (recommended). Every Log Event includes an identifier for the Log Agent.

Next Steps