- 7 minutes to read

What is the Log Status Code?

Nodinite Log Status Codes provide meaningful, actionable event tracking for all your integrations. This page explains how Log Status Codes work, how to map numeric codes to user-friendly states, and how to leverage them for advanced search, grouping, and monitoring.

✅ Visual process tracking - BPM steps inherit colors from Log Status Codes for instant process health visibility
✅ Rapid troubleshooting - Search Field Links on Log Status Codes enable one-click navigation to related systems
✅ Clear state mapping - Map numeric codes to user-friendly states (Success, Warning, Error)
✅ Advanced filtering - Search, group, and filter events by Log Status Code in Log Views
✅ End-to-end tracking - Track status across all integration platforms and custom solutions
✅ Business intelligence - Status codes power BPM milestone tracking and Non-Events monitoring

Logged Events can have a Log Status Code set to represent the state of the Log Event. The Events are logged from any of the Log Agents.

The Log Status Code is a crucial element in logging and monitoring. It represents the state of the event and is set for all logged events from any Nodinite Log Agents and custom coded solutions. Your understanding and management of these codes are key to efficient operations.

Since the Log Status Code is a number, it may be hard for end-users to understand its semantics. Nodinite lets you map these codes into meaningful textual representations, making it easy for users to interpret the status of logged events.

graph LR subgraph "fa:fa-bolt Log Event" A[fa:fa-code-commit Logging Agent 1] -->|unique collection| B(Log Status Codes) C[fa:fa-code-commit Logging Agent 2] -->|unique collection| D(Log Status Codes) end

Diagram: Each Logging Agent can have its own unique collection of Log Status Codes in Nodinite.

To further emphasize the meaning behind the Log Status Code, Nodinite is configured with a Status Type. The following image shows the different options available:
Status Type Entries
Here's an example of Log Status Types.

A user may search, Group, and filter according to selected Log Status Codes:
Search by Log Status Code
Example Log View where the User searched by Log Status Code.

Log Events matching the Log Status Code are displayed in Log Views coloured accordingly.

Examples:

  • 0 from the BizTalk Log Agent can mean 'Message successfully transmitted' - Ok
  • 76 from custom Log Agent can mean 'Invoice successfully created' - Ok
  • 401 from a custom Web Api can mean 'Bad Request' - Error
  • -16 from a custom Log4Net Appender Log Agent can mean 'Missing due date' - Warning

A Log Status Code has one of the following states:

State Description
None Not set or unknown
Information Informational event
Success Message was successfully processed
Warning Unexpected but not invalid state
Error Error/fatal condition

The Log Status Codes are unique for each Log Agent.

Visual Process Tracking with BPM

Log Status Codes power visual process health in Business Process Models (BPM).

When you use Business Process Modeling (BPM) to track end-to-end business processes, each step in your BPM inherits its color from the Log Status Code of the most recent event:

  • Success (Green) - Step completed successfully
  • Warning (Yellow) - Step completed with warnings or unexpected conditions
  • Error (Red) - Step failed or encountered a fatal condition
  • Information (Blue) - Informational events or in-progress steps
  • None (Gray) - No events logged yet for this step

This visual status inheritance provides instant process health visibility across your entire integration landscape. Business users and operations teams can see at a glance:

  • Which business processes are running smoothly (green)
  • Which require attention (yellow)
  • Which have failed and need immediate action (red)

BPM with Status Colors
Example: BPM process view showing steps colored by Log Status Code state—enabling instant health assessment.

Tip

When designing BPM processes, ensure your logging agents and custom code set meaningful Log Status Codes at each milestone. This enables automatic, real-time visual process tracking without additional configuration.

Navigate instantly from errors to related systems using Search Field Links.

When a Log Event has an Error or Warning status code, Nodinite enables rapid troubleshooting through Search Field Links. These links allow you to:

  1. Click directly from an error event in a Log View or BPM
  2. Navigate to related events in other systems using shared business identifiers (Order IDs, Invoice Numbers, Customer IDs)
  3. Trace transactions end-to-end across your integration landscape

Example Troubleshooting Workflow:

  1. BPM shows a red (Error) status in the "Payment Processing" step
  2. User clicks on the error event to view details
  3. User clicks a Search Field Link on the "OrderId" field
  4. Nodinite instantly displays all related events across all systems (ERP, CRM, payment gateway) with the same OrderId
  5. User identifies the root cause (invalid credit card) and takes corrective action

This eliminates hours of manual log correlation and system navigation.

Important

Search Field Links require properly configured Search Fields

To enable rapid troubleshooting with Search Field Links:

  1. Message Types - Define business transaction types for all systems
  2. Search Field Expressions - Configure extraction of business identifiers (Order IDs, Customer IDs, etc.)
  3. Search Fields - Create Search Fields with Links enabled
  4. Log Status Codes - Set meaningful status codes at each integration point

With this foundation, users can navigate from any error directly to correlated events across your entire integration landscape—regardless of platform or technology.

You must be part of the Administrators role to configure Log Status Codes.

SeriLog

The Log Status Code in Nodinite can be automatically set when logging using the SeriLog framework by providing an EventId (new EventId(1337, "SomeLog")). If you do not provide the EventId, the Nodinite Log Status Code on the Log Event is None.

State Mapped log level in Microsoft.Extensions.Logging New 7.x
None _logger.LogTrace("Foo {message}", "Bar");
_logger.LogDebug("Foo {message}", "Bar");
_logger.LogInformation("Foo {message}", "Bar");
_logger.LogWarning("Foo {message}", "Bar");
_logger.LogError("Foo {message}", "Bar");
_logger.LogCritical("Foo {message}", "Bar");
The code to inject an EventID is not provided
Information _logger.LogTrace(new EventId(1337, "SomeLog"), "Foo {message}", "Bar");
_logger.LogDebug(new EventId(1337, "SomeLog"), "Foo {message}", "Bar");
Success _logger.LogInformation(new EventId(1337, "SomeLog"), "Foo {message}", "Bar");
Warning _logger.LogWarning(new EventId(1337, "SomeLog"), "Foo {message}", "Bar");
Error _logger.LogError(new EventId(1337, "SomeLog"), "Foo {message}", "Bar");
_logger.LogCritical(new EventId(1337, "SomeLog"), "Foo {message}", "Bar");

If you log using the following code snippet:

_logger.LogError("Foo {message} {LogStatusCode}", "Bar", 1337);

The Nodinite Log Event will have a Log Status Code set to 1337 with the Information state.

Next Step

Complete your Log Status Code configuration to enable visual tracking and rapid troubleshooting:

  1. Add or manage Log Status Code - Map numeric codes to meaningful states
  2. Message Types - Define business transaction types (prerequisite for Search Fields)
  3. Search Field Expressions - Configure extraction of business identifiers
  4. Search Fields - Create Search Fields with Links enabled for rapid navigation
  5. BPM - Design Business Process Models that inherit status colors
  6. Add or manage Log View - Create Log Views for searching and filtering by status

Visual Process Tracking:

  • BPM - Business Process Models inherit colors from Log Status Codes
  • Log Views - Search, filter, and group events by Log Status Code
  • Stylesheets - Transform technical data into user-friendly formats

Rapid Troubleshooting:

Configuration & Access:

Standards & Integration: