Add or Manage a Nodinite Log Agent
Info
In this user guide, you will learn how to add and manage a Nodinite Log Agents.
Tip
New to Log Agents? Start with these conceptual guides:
- What is a Log Agent? - Understand end-to-end logging and event tracking
- What is a Log Status Code? - Learn about status code mapping and visual process tracking
- Log Agents Overview - View and manage all Log Agents in your landscape
Add or manage Log Agent configurations
- Either Manage (click on one Log Agent in the Log Agents Overview) or Add a new Log Agent (click on the Add Log Agent button)
| From the Log Agents Overview | From Add or Manage Log Agent page |
|---|---|
![]() |
![]() |
Enter the following details
Name - The user-friendly name for this Log Agent Configuration (Required)
Description - user-friendly description of the Log Agent Configuration (Optional)
Web Site - Link to remote documentation (Optional)
Log Agent Value Id - Unique Id (Required field) - Once set, this value must not change!
Name
The user-friendly name the of the Log Agent. This name appears in the Log Agents Overview and throughout Nodinite. For example:
- BizTalk 2016 - Prod
- iCore - Test
- Azure Logic Apps (North Europe)
- ...
Log Agent Value Id
Log Agent Value Id is the unique positive integer value for this specific Log Agent configuration. This identifier is included in every Log Event from this Log Agent. Learn more about unique identification in Log Agents. For example:
- 1
- 42
- 1337
Description
The Description property has the user-friendly information about this Log Agent configuration.
Web Site
Can be a link (URL) to some internal, or external documentation. (optional)
Add or manage Log Status Codes
The Logging feature of Nodinite provides a way of adding human-readable texts for Log Status Codes. Review the "What is a Log Status Code" user guide if you are unfamiliar with this topic. You can view all configured Status Codes in the Log Agents Overview.
You can add any number of Log Status Codes

In the Edit dialogue, you can manage the collection of Log Status Code.

Since a Log Status Code can mean different things depending on for example integration broker (BizTalk, IBM Integration Bus, Mule, ...) the Log Status code is defined per Log Agent. These Status Codes enable visual process tracking in BPM and rapid troubleshooting with Search Field Links.

Click the Edit button to manage Log Status Codes for the selected Log Agent.
The following properties can be set:
| Mandatory | Property | Description |
|---|---|---|
| Status Type | Select one of the predefined Status Type values (None, Information, Success, Warning, Error). See What is a Log Status Code? for detailed explanations of each status type. | |
| Log Status | The numeric code logged in the Log Event by custom code or by any of the Log Agents. This number will be mapped to the human-readable Description. | |
| Description | A user-friendly description to display for this Log Status Code. This text appears in Log Views and throughout Nodinite. | |
| Web Site | Link to external or internal documentation for this specific status code (optional) |
Save
You must click 'Save' or 'Save and close' for changes to persist. The new settings/thresholds are evaluated on the next synchronization.

Here's an example of the Save options.
Next Step
- BizTalk - Use the built-in tracking feature and/or use custom Pipeline Components
- BizTalk has special support, see more here
- Log4Net Appender - Enable logging from log4net applications by adding the DLL:s and a new appender to the
app.configfile - MuleSoft Anypoint Logging - Uses Log4J Appender framework for Logger and Business Events (code) or the Mule ESB - Custom Connector
- Log Api - Enable Logging from your code (e.g. C# and Java)
- VB6/COM/VBScript - Enable Logging from VB6/VBScript code
Related Topics
Understanding Log Agents:
What is a Log Agent? - End-to-end logging and event tracking concepts
What is a Log Status Code? - Visual process tracking and rapid troubleshooting
Log Agents Overview - View, filter, and manage all Log Agents
Core Services:
Logging Service - Processes (indexing) the logged messages
Log Views - Manage User access to events and messages across platform
Log Databases - Keep as much data as you like


