What is a Log View?

Nodinite Log Views give your business secure, self-service access to business transactions and integration events. This page explains what a Log View is, what an administrator controls in it, and which actions it gives your users.

• ✅ 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
• ✅ Inspect grouped Log Views as runtime diagrams for faster cross-system troubleshooting
• ✅ Rapid troubleshooting with repair, resend, download, and formatting options
• ✅ Search any number of Log Databases, with a Time Interval Configuration capping the lookback period

Get started now: See the Add or Manage Log View guide. End users learn to search in Working with Log Views.

Log data arrives through a Log Agent or the Asynchronous Logging pattern and the Log API. Administrators assign Log Views to Roles with granular permissions for viewing, downloading, and resending messages, and every user operation is audited.

Use Nodinite Log Views to Find Business Transactions

The Nodinite Administrator creates Log Views for selected Roles. For example, you can enable the finance team to quickly find orders by order number.

Example: a Log View that finds orders by order number and groups the results by Application interchange id.

Users pick a date range (capped by the Time Interval Configuration; stored in UTC, shown in browser time), enter values in your Search Fields, and search Log Events across the Log Databases. Columns come from the Display result tab and the user's Display Field Configuration. End-user steps: How to perform a Search and Find an order by Order Id.

Example: an expanded group lists the Log Events of one order interchange.

Inspect grouped runtime flow

When a Log View is grouped by one business transaction or interchange, users can open its events as a runtime diagram in Participants mode (Services, Contracts) or Systems mode (Systems), best with Architecture Diagrams in place. See the user guide and the design guidance.

Interact with Log Events

With results in hand, users click the Actions button to open the sub-menu. Options depend on the permissions you grant on the Log View's Roles; the end-user walkthrough is in View Log Event Details.

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

Every user with access to the Log View can open View details. What they can do there, such as reading the message body, resending, or repairing, follows the Permission Set for Log Views of their Role; Repair and resubmit needs both the Resend and Repair permissions.

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.

Under Message Type, the page shows the Encoding the message is read with, that is, its resolved encoding. ^{New 7.11}

The Encoding line under Message Type, here UTF-8 (without BOM), taken from the Message Type Hello.World.File/1.0.

The View details page also has a Download menu: Download saves the original message, and Download converted to saves it in the encoding you pick. See Download. ^{New 7.11}

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 ResubmitContextValuesForActiveMQ System Parameter to select which context properties are attached as message properties)
   • Webhook - HTTP endpoints you define in the ResendWebhookSettings System Parameter

   Tip

   We recommend the Webhook target: it forwards the message to almost any system, such as Azure Functions, Logic Apps, or API Management. You build and test the receiving endpoint.

3. Fill in the transport settings, and choose the Encoding the message is written in: ^{New 7.11}

   • Use original encoding (default) – the encoding the message originally arrived in.
   • Use the encoding configured in the editor – the encoding selected in the editor's dropdown in step 1.

   This choice is separate from the Message Type and Endpoint encoding.

   
   The Encoding options in step 3; the arrow points to the editor's encoding dropdown that the second option uses.

4. Add a Comment to the Log Event

   Tip

   If this Log View is used by a Non-Events monitor, you can use a controlled comment value (for example Ignore: or FIXED) to include or exclude selected events in the monitored result set. See Tip: Clear alerts using comments in a Log View.

Then, click 'Send and close' to resend the Log Event with the selected transport type.

Info

All repair attempts are logged for auditing purposes.

The AllowResubmit and AllowRepair System Parameters switch Resend and Repair on or off for the whole installation (both are true by default). Repair only works while AllowResubmit is true.

View Message Body

Click 'View message body' to open a modal with the payload in its original format, showing size, position, and selection like a file editor.

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 original message, byte for byte.

• Download converted to - Download the message converted to a target encoding you choose. ^{New 7.11}

• 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} With a with BOM encoding selected, a leading byte order mark shows as a red BOM marker. ^{New 7.11}

  
  A message read as UTF-8 (with BOM) with Show hidden characters on.

• 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. From 7.11, the dropdown opens on the message's resolved encoding, and its tooltip says where that came from, such as From the Message Type. ^{New 7.11}

  
  The encoding dropdown preset to UTF-8 (without BOM), with a tooltip naming the Message Type as the source.

The dropdown offers every supported encoding, including UTF-8 (with BOM) and one Base64 Decode into … option per encoding (earlier versions had a single Base64 Decode, now Base64 Decode into UTF-8 (without BOM)), plus Base64 Encode, Mime Mail to Text, and None (Binary).

Important

Rendering a message with a different encoding changes only what you see. The stored message is not changed.

• Search Field Wizard - Create or manage Search Fields. The wizard's Encoding dropdown opens on the message's resolved encoding. ^{New 7.11}

Mime Mail to Text

The 'Mime Mail to Text' encoding option shows MIME-encoded messages in readable form. For the sample below, it decodes the base64-encoded part.

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. From 7.11, Nodinite converts the body from its resolved encoding to UTF-8 before inserting it into the stylesheet, so characters such as Å and é display correctly. ^{New 7.11}

Note

Needs View Transformed; see Permission Set for Log Views.

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 to another Endpoint than the one 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, with its original bytes and encoding.

When a receiving system needs another encoding, for example Windows-1252 instead of UTF-8, use Download converted to: the download-converted button in View message body, or the Download menu on the View details page. Pick UTF-8 or UTF-16 (with or without BOM), ASCII, Windows-1252, ISO-8859-1, or EBCDIC (IBM037). Nodinite reads the message with its resolved encoding and saves it in the target. The Web API download operation takes the target as a parameter. ^{New 7.11}

The Download menu on the View details page.

Note

This option is available to all users with permission to view the message body.

Search Fields

Administrators add Search Fields to Log Views on the Search criteria tab. These can be:

• Search Fields - Custom fields extracted from message payloads and context using Search Field Expressions
• Built-in properties from a Log Event - Standard properties like timestamps, correlation IDs, Log Status Codes

Important

Search Fields require Message Types. A Search Field Expression extracts values only for the Message Types it is bound to; without them, a Log View searches only by time and correlation IDs.

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.

What is the Origin of Logged Events?

Platforms with built-in tracking, like BizTalk Server and IBM Integration Bus, have plug-and-play Log Agents. Other platforms and custom solutions use the Asynchronous Logging pattern, with no vendor lock-in.

Diagram: Integration platforms (purple, external) send events through Log Agents or directly to the Nodinite Log API (blue, Nodinite components).

Tags

Administrators assign Tags when creating or editing Log Views, and users filter the Log Views list by Tags, for example by environment or department.

What Data is Available to the End-User?

Administrators control what data Log Views show. Payloads can be transformed using XSLT or Liquid with the Nodinite Stylesheets.

A Log View shows a Search Field value only when the Search Field is part of it (a Restriction doesn't count). ^{New 5.4} Users don't see other fields; administrators see them as Hidden. Read Which Search Field Values a Log View Shows.

Animated walkthrough: a value the Log View doesn't include.

HideSearchFieldValuesInLogViews controls this; HideAdditionalFieldValuesInLogViews hides or masks built-in fields.

Tip

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

To keep sensitive context values logged but masked for users in Log Views, use the ProtectedContextValues System Parameter.

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. Administrators can filter Log Views by Repository Model entities using the Data to search tab configuration.

Example: Repository Model showing Log Event to Integration mapping.

The Repository Model tab shows which Service and System a single Log Event belongs to; a grouped Log View's runtime diagram shows how the related events move between them. See How Log Events Become Repository Model Stories.

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

Administrators add and edit Log Views from the Log Views - Overview and restore deleted ones. Each Role's access is set with the Permission Set for Log Views.

Next Steps

• How to Add or manage Log Views
• How to Add or manage Search Fields
• Add or manage Role – grant the Log View to your users
• Inspect grouped Log Views as runtime diagrams

Related Topics

• Message Types and Search Field Expressions - Prerequisites for Search Fields
• Log Views - Overview - List, add, clone, edit, and restore Log Views
• Permission Set for Log Views - What each Role may do in a Log View
• Display Field Configurations, Time Interval Configuration, and Tags
• Design grouped Log Views for runtime inspection
• Working with Log Views and Find an order by Order Id - End-user guides
• Copy API, Print, and Export to CSV
• Log Audits - Track all Log View operations for compliance
• Character Encoding - How the encoding of a message body is decided
• Non-Events Monitoring - Detect missing or delayed messages from Log View data
• Business Process Modeling (BPM) - Track end-to-end processes with grouped Log Views
• Reports - Build custom reports using Log View API URIs
• Logging Service - Processes and indexes Log Events for Search Fields
• Repository Model - Connect Log Events to Services, Systems, Integrations, and Endpoints