- 2 minutes to read

What is a Logging Agent?

The Logging feature of Nodinite includes one or more Log Agents that creates Log Events from one or more integration brokers or custom code with information about events and optional payload/context.

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

Each Log Agent is uniquely identified by unique Id (Log Agent Value Id) and Log Events always has this information element embedded. On the very first logged event, the Log Agent entry will be automatically created if it does not already exist. The name will be Not Set by default. This name should be changed by an Administrator to a more user-friendly name describing the type of source, for example 'BizTalk 2016 - PROD' or 'iCore - Test'

Log Status Codes

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


How do I add or Manage Log Agents?

Information about the Log Agent can be managed in the Web Client of Nodinite.

Where does Log Agents originate from?

A Log Agent is either custom built by you or provided by Nodinite, review Logging for additional details.

Can I build my own Log Agent?

Yes, your missions is that you either send the Log Events directly to the Log API (note recommended) or create a JSON formatted object that the Pickup Service fetches asynchronously (recommended).

Next Step

Add or manage Log Agents
Log Status Codes

Log Events
Log Views
List of Logging