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:

1. Enter the start and end date (quick select options and Time Interval Configuration available). The time zone is based on the local browser settings. All dates and times are stored in UTC in the Nodinite Log Database.
2. Enter the OrderId Search Field (various operators available by data type)
3. 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 user specified columns in the result.

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.

Example: Actions menu items available for a selected Log Event.

• View details
• View Message Body
• View message formatted as 'Name of the Stylesheet'
• Resend
• Download
• Search Fields

Tip

The With selected button provides powerful batch features.

View Details

Click 'View details' to open a new browser tab with advanced features.

Example: View details action button available for a selected Log Event.

Note

This option is available to members of the built-in Administrators Role.

A special feature only available here is the ability to Repair or Delete the Log Event. A hard delete is permanent and cannot be undone. A repair operation attempts to fix any issues with the Log Event, such as missing payloads or context data.

Repair

Click Repair to initiate a repair operation on the Log Event. To repair a Log Event, follow the steps below:

1. Edit the payload

2. Select transport type:

• File - SMB or local file system
• MSMQ - Microsoft Message Queuing
• ActiveMQ - Apache ActiveMQ (Uses the ResendWebhookSettings System Parameter for configuration)
• Webhook - HTTP Webhook (uses the ResendWebhookSettings System Parameter for configuration)

Tip

We recommend 'Webhook' as you can forward the message to virtually any other type of endpoint or system, including Azure Functions, Logic Apps, and API Management Services.
You must design, develop and test the receiving endpoint to handle the incoming message.

3. Add a Comment to the Log Event

Then, click 'Send and close' to submit the repair request. The system will attempt to resend the Log Event using the specified transport type.

Info

All repair attempts are logged for auditing purposes.

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.
  
  Example: Encoding options available when viewing a message body.

The following encoding options are available:

Important

Rendering a message with a different encoding may alter the original content.

• Search Field Wizard - Create or manage Search Fields.

Mime Mail to Text

💡Display Mime-encoded messages in a human-readable format.

With the 'Mime Mail to Text' encoding option, you can change the message presentation. For example, given the sample MIME-encoded message below, select the 'Mime Mail to Text' 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 base64-encoded part decodes to:

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' menu item to immediately resend the message to the Endpoint.

The operation can use instructions from System Parameter to resend the message even to another Endpoint compared to the one that was used in the original interchange. Review 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.

Q/A

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.

Tags are vital for organizing and categorizing Log Views, making it easier to locate and manage them. Tags can represent various attributes such as environment (e.g., Production, Staging), department (e.g., Sales, HR), or any other relevant classification that suits your organizational needs.

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}

Example: Search Field values not defined in the Log View are hidden.

Tip

You can use the ContextPropertiesFilters System Parameter to exclude sensitive data from being logged. >This feature also saves storage space and improves performance.

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.

Example: With selected menu items available for multiple selected Log Events.

• 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:

• Adding new Log Views
• Editing existing Log Views
• Deleting Log Views

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?