What is a Log View?
Nodinite Log Views empower your business with secure, self-service access to business transactions and integration events. This page explains how Log Views streamline monitoring, enable rapid troubleshooting, and provide advanced search and audit capabilities for your integration landscape.
✅ Empower users with secure, self-service access to business data
✅ Advanced search and filtering with Search Fields and roles
✅ Full audit trail for compliance and traceability
✅ Rapid troubleshooting with download, resend, and formatting options
✅ Access historical data from any number of Log Databases
✅ Use a Time Interval Configuration to cap the lookback period for performance and usability
Get started now: See the Add or Manage Log View user guide.
A Nodinite Log View gives business users secure, self-service access to selected data. Log data is captured using a Log Agent or the Asynchronous Logging pattern. All user operations—downloading, peeking at payloads, and more—are audited for compliance and traceability.
Use Nodinite Log Views to Find Business Transactions
The Nodinite Administrator creates Log Views for selected Roles. For example, you can enable business users to quickly find orders by OrderId.
Example: Log View filtered by OrderId.
First, the authenticated user selects a Log View and specifies the following scoping properties:
- Enter the start and end date (quick select options and Time Interval Configuration available)
- Enter the OrderId Search Field (various operators available by data type)
- Search for Log Events. Results appear in a paged list. You can re-order columns using the Display Field Configuration.
Example: Search results in a Log View with custom columns.
Interact with Log Events
With results in hand, you can explore and take further action. Click the Actions button to open the sub-menu. Options depend on your permissions.
Menu items in the Actions button.
- View details
- View Message Body
- View message formatted as 'Name of the Stylesheet'
- Resend
- Download
- Search Fields
The With selected button provides powerful batch features.
View Details
Click 'View details' to open a new browser tab with advanced features.
This option is available to members of the built-in Administrators Role.
View Message Body
Click View message body to open a modal displaying the message payload in its original format. The modal provides details such as size, position, and selection, similar to popular file editors.
The view message body option is available to users with permission to view the message body.
Example: A logged message in its raw format.
On the modal, advanced options are available depending on your permissions and role membership:
- Download - Download the message.
- Open in a new window - Open the message in a separate window.
- Word wrap - Toggle word-wrap for easier reading.
- Pretty print - Beautify the message for readability.
- Show hidden characters - Display hidden characters (e.g., whitespace, tab) with special markings. New 6.0
- Linebreak marker - Insert line breaks at specified content. Reload the payload to revert changes. Especially useful for reading EDIFACT/X12 messages. New 6.0
- Encoding - Re-render the message with the selected encoding.
The following encoding options are available:
Encoding option | Comment |
---|---|
ASCII | Render the message in ASCII format |
Base64 Decode | Decode a base64 encoded message |
Base64 Encode | Encode the message |
EBCDIC (IBM307) | Render the message in EBCDIC format |
ISO-8859-1 | Render the message in ISO-8859-1 format |
Mime Mail to Text | Convert a Mime encoded message |
None (Binary) | |
UTF-16 | Render the message in UTF-16 format |
UTF-8 (Default) | Render the message in UTF-8 format |
Windows-1251 | Render the message in Windows-1252 format |
Important
Rendering with a different encoding may result in data loss.
- Search Field Wizard - Create or manage Search Fields.
Mime Mail to Text
With the Mime encoding option, you can change the message presentation. For example, given the sample MIME-encoded message below, select the Mime encoding option to view the base64-encoded part in a decoded format.
MIME-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-Transfer-Encoding: Base64
Content-ID: {749803BA-3A65-4A8F-1337-65125988BBF3}
Content-Description: body
Tm9kaW5pdGUgaGFzIGl0IGFsbCE=
The result looks like this:
Nodinite has it all!
View Message Formatted as 'Name of the Stylesheet'
Click View message formatted as... to open a modal with the message payload styled using a stylesheet.
Note
This option is available to users with permission to view messages using stylesheets.
Resend
Click Resend to immediately resend the message to the Endpoint. See the Context Options user guide for details.
Note
This option is available to users with permission to resend messages.
Download
Click Download to save the message locally.
Note
This option is available to all users with permission to view the message body.
Search Fields
System Administrators can add Search Fields to Log Views. These can be:
- Search Fields
- Built-in properties from a Log Event
Processing State
The Processing State search field is set during the processing and re-indexing of Log Events, managed by the Nodinite Logging Service.
Example: Different Processing States of a Nodinite Log Event.
State | Description |
---|---|
Reindexing | When a re-index operation is issued, all affected Log Events are set to Reindexing. These records are processed and then assigned another Processing State. This operation may take time. |
Unprocessed | When a Log Event is stored, the state is Unprocessed. These records are processed and then assigned another Processing State. |
Counted | Set during processing when a Log Event is missing both a payload (Body) and Context (key-value collection). |
Processed | Indicates successful processing of the Log Event. |
Completed with Warnings | A problem occurred finding values for Search Field Expressions during processing. Review Search Fields configuration. Consider using optional if data is not always present. |
Failed | A problem occurred processing the Log Event. This may be due to payload size limits (MessageProcessingMaxBodySize). Contact support if processing fails for other reasons. |
Q/A
# | Topic |
---|---|
What is the origin of logged events? | |
What data is available to the end-user? |
What is the Origin of Logged Events?
Nodinite logging and archiving features are designed to replace BAM in BizTalk. Today, Nodinite is a feature-rich platform supporting a wide range of systems integration solutions. Platforms with built-in tracking, like BizTalk Server and IBM Integration Bus, have plug-and-play Log Agents. Other platforms and custom-built solutions use the Asynchronous Logging pattern, avoiding vendor lock-in and supporting a flexible logging strategy.
Diagram: Integration platforms and Log Agents connect to Nodinite Log API
Tags
Use the Nodinite Tags feature to efficiently manage numerous Log Views.
What Data is Available to the End-User?
As a Nodinite Administrator, you can set filter rules to control what data is displayed in Log Views. Payloads can be transformed using XSLT or Liquid with the Nodinite Stylesheets.
Hiding values for search fields not defined in the Log View: New 5.4
Values are hidden for Search Fields not included in the Log View.
What Systems Integration Does the Logged Message Belong To?
A Nodinite Log Event can be linked to a Service belonging to a System. An Integration is defined as a set of linked Services. This connection can be set manually or as part of your logging strategy; see Repository Binding for details.
Example: Repository Model showing Log Event to Integration mapping.
When the Log Event is tied to a log point (Transport Contract), use the Landscape button to see where in the flow the event belongs. When you open the Landscape, the associated Service blinks for a few seconds.
With Selected
Use the With selected button to perform operations on multiple messages at once.
Select one or more messages; the content in the 'With selected' button changes according to your selection.
- Save as .zip with original filenames
- Save as .zip (files in zip package get unique names)
- Resend
- Reindex
- Export events
- Diff message body New 6.0
Available if exactly two Log Events are selected.
- Comment
- Remove selected events
Example: Difference between two selected Log Events in a Nodinite Log View.
Manage Log Views
A Nodinite Administrator can manage Log Views by:
See the Log Views - Overview user guide for a list of manageable Log Views.
Next Step
Administration
How to Add or manage Search Fields
How to Add or manage Log Views
Related Topics
Expression Type Plugins are used in Search Fields
- What are Search Fields?
- What are Search Field Expressions?
- What are Message Types?
- What are Tags?