- 9 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 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

Walkthrough: on the Log Agent Contoso Shipping Platform - Test, change the Log Status Code 500 from Error to Warning with a new description and save; the card shows an orange flag (7.12)
Mapping a code: 500 becomes a Warning with a business-friendly text. See Add or manage Log Status Codes.

Understanding Log Status Codes

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.

You can view and manage all Log Agents and their Status Codes in the Log Agents Overview. To configure Status Codes for a specific Log Agent, see Add or manage Log Status Codes.

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 Events" A["fa:fa-code-commit Logging Agent 1"] -->|"unique collection"| B("fa:fa-flag Log Status Codes
0 = Success") C["fa:fa-code-commit Logging Agent 2"] -->|"unique collection"| D("fa:fa-flag Log Status Codes
0 = Error") end style A fill:#2678BD,color:#fff style C fill:#2678BD,color:#fff style B fill:#E47528,color:#fff style D fill:#E47528,color:#fff

Diagram: Each Logging Agent (blue) has its own collection of Log Status Codes (orange), so the same number can mean different things for different Log Agents.

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 dropdown with None, Information, Success, Warning, and Error, each with its Id 0 to 4 (7.12)
The five Status Types a Log Status Code can map to, with their Ids 0 (None) to 4 (Error).

A user may search, Group, and filter according to selected Log Status Codes:
Log View search criteria with Log Status Code Not In 0
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

Status Type Values

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. When configuring Status Codes, you map numeric codes to these predefined status types.

Automatic creation from incoming events

The Logging Service creates or updates a Log Status Code only when the Log Event carries these Context properties:

Context property Required Becomes
ExtendedProperties/1.0#LogLevel Yes The Status Type, by name: None, Information, Success, Warning, or Error (case-insensitive)
ExtendedProperties/1.0#EventDescription No The Description; when it's missing, the Description is set to empty
ExtendedProperties/1.0#LogStatus No The code; without it, the event's LogStatus is used

An event without LogLevel creates nothing; its code then shows only as a number.

Walkthrough: a Log Event posted to the Log API with LogStatus 409, LogLevel Warning, and EventDescription Shipment already booked adds the code 409 = Warning to the Log Agent within seconds (7.12)
The event's Context sets the code: 409 = Warning, Shipment already booked, appears on the Log Agent within seconds.

The LogStatusCodeAutoSyncPolicy System Parameter (Nodinite 7.5.24 and later) decides what happens, globally or per Message Type (keys may use * wildcards). The default is {"default":"Upsert","messageTypes":{}}.

Policy Missing code Existing code
Upsert (default) Created Overwritten: the event's Status Type and Description replace yours, and a disabled code is enabled again
CreateMissingOnly Created Never changed; a conflict writes a Warning to the Log Audits ("Ignored LogStatusCode auto-sync …")
Disabled Not created Never changed

Warning

With Upsert, an edit you make in Add or manage Log Status Codes lasts only until the next event that carries a LogLevel for that code. Set CreateMissingOnly when administrators maintain the texts by hand.

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 Viewer with every step of one Order-to-Cash order colored by its Log Status Code, here all successful (7.12)
Example: BPM process view showing steps colored by Log Status Code state—enabling instant health assessment. In this order every step succeeded; a failed step would show red.

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, in the Log Agents Overview.

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 Steps

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