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.
✅ Achieve true end-to-end tracking and monitoring across all integration platforms
✅ Map numeric status codes to clear, descriptive states for business users
✅ Search, group, and filter events by Log Status Code in Log Views
✅ Integrate with popular brokers, ESBs, and custom solutions
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.
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:
Here's an example of Log Status Types.
A user may search, Group, and filter according to selected Log Status Codes:
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.
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.