Add or Manage Log View

Nodinite Log Views empower your business with secure, self-service access to business transactions and end-to-end logging. This guide shows you how to add and manage Log Views, fine-tune columns, grouping, and permissions, and streamline integration monitoring for your organization.

Note

New to Log Views? Read What is a Log View first to understand the concepts, features, and user interactions before configuring them.

• ✅ Self-service intelligence - Business users search by Order IDs, Customer Numbers, and business data
• ✅ Message Types foundation - Search Fields extract business data based on configured Message Types
• ✅ Role-based security - Fine-tune permissions for viewing, downloading, resending, and repairing messages
• ✅ Advanced filtering - Combine Search Fields, Message Types, Endpoints, and Repository Model filters
• ✅ Flexible display - Customize columns, grouping, and post-group filters for complex queries
• ✅ Runtime inspection ready - Design grouped Log Views that open useful Participants mode and Systems mode views
• ✅ Business intelligence - Enable Non-Events Monitoring and BPM process tracking

Important

Prerequisites: Configure Message Types and Search Fields BEFORE creating Log Views

To enable self-service search by business data in Log Views, you must complete these steps first:

1. Message Types - Define business transaction types (e.g., "PurchaseOrder#1.0", "InvoiceMessage#2.0")
2. Search Field Expressions - Configure XPath, JSON Path, or RegEx expressions to extract business data based on Message Type
3. Search Fields - Associate expressions with Message Types to make them searchable
4. Log Views - Create views that include Search Fields for powerful business intelligence

Without Message Types and Search Fields configured first, Log Views can only search by:

• Timestamps (start/end dates)
• Correlation IDs
• Basic properties (Log Status Code, Log Text)

This severely limits business value. Message Types and Search Fields unlock the true power of self-service logging.

Understanding the Log View configuration

People are purple, the prerequisites teal, the Log View you configure blue, access through Roles orange, and the features a Log View enables green.

The tabs map to what the Log View does:

Features

The Nodinite Log View is a composite view where filters and settings determine what options are available to end-users in one or more Roles.

There are extensive filter options, allowing you to create virtually any type of Log View to streamline search operations for end-users.

Tip

Use Log Views to enable Non-Events monitoring and empower your business with actionable insights.

Below is the list of filter options:

• Search Fields - Facilitate custom search options for the end-user based on content in Payload/Body and Context
  • Restrictions - Provide complex filters based on Search Fields to limit the result set
• Repository Model - Filter on Log Events associations with selected parts of the Nodinite Repository Model.
  • Integrations
  • Systems
  • Services
  • Message Types
  • Endpoints
• Log Agents

Manage Log View

• Add a new Log View
• Manage existing Log View

Add a new Log View

As the Nodinite Administrator, click on the Add Log View button from the Log Views Overview.

Click the Add Log View button to create new Log View.

Manage existing Log View

As the Nodinite Administrator, from the Log Views Overview, you can manage existing Log Views by clicking on one of the entries in the Name column or using the Edit action button. Deleted Log Views can be restored, see View and Restore Deleted Records. Import/Export, used to copy Log Views to another environment, is disabled in Nodinite 7.0; use the Web API for now.

General tab

From the General tab, the Nodinite administrator sets essential and required information for the Log View.

• Name - Mandatory field - A unique name is required to create a new Log View.
• Description - Optional field - A short user-friendly description of the Log View.
• Website - Optional field - Use the link field feature to allow the end-user to click and navigate to the specified address.
• Roles - Required setting - Grant and access rights.

Here's an example of the essential and required information for a Log View.

Roles

To manage the set of Roles with access to the Log View, click on the Edit button in the Roles section.

Edit the set of Roles to manage the grants set on the Nodinite Log View.

Then, grant a selection of Roles to access the Log View. For a new Log View, the Roles listed in the DefaultRolesInViews System Parameter are pre-selected; you can remove them or add others before saving.

Next, click on the Selected tab and manage the permissions for the Roles.

Manage the permission set for Roles.

• Access this View - Allow or deny user access to this Log View.
• View Context - Allow or deny user access to Context Properties.
• View Body - Allow or deny the User the ability to view and download the payload.
• View Transformed - Allow or deny the User the ability to view the message using a Stylesheet
• Resend - Allow or deny the User the ability to resend messages.

  The Nodinite Log Events can include options to resend messages to a pre-defined target. Please review the Context Options user guide for details.
  The System Parameter AllowResubmit must be set to 'true' to allow the resend feature.

• Repair - Allow or deny the User the ability to repair messages.

The System Parameter AllowResubmit must be set to 'true', to allow the repair feature.
Likewise, the System Parameter AllowRepair must also be set to 'true', to allow the repair feature.

For additional details, review the Permission Set for Log Views guide. Every action users take with these permissions is recorded in the Log Audits.

Search setup tab

The Nodinite Administrator manages the search options based on Search Fields and other pre-defined properties of a Nodinite Log Event in the Search Setup tab. For details on how end-users interact with these search options, see the Search Fields section in What is a Log View and, for the end-user steps, How to perform a Search. In the Web Client, the tab is labelled Search criteria.

Here's an example of options in the Search Setup tab.

Add every field users need to see: with the default settings, Search Field values that are not part of the Log View configuration show as Hidden (HideSearchFieldValuesInLogViews), and HideAdditionalFieldValuesInLogViews can hide or mask built-in event fields. A field you add to the Log View configuration is always shown.

There are five areas of interest on this tab:

1. Time Interval Configuration
2. Restrictions
3. Default search setup
4. Optional fields
5. Auto Start Search

Time Interval Configuration

You can assign a pre-defined Time Interval Configuration to the Log View to regulate the available time for the end-user to perform the search operations.

Select the Time Interval Configuration to use with the Nodinite Log View.

Once a configuration is selected, quick access links above the dropdown open the selected configuration or Add New to create one; see the example on What is a Time Interval Configuration.

Restrictions

The Nodinite Administrator can define restrictions to regulate the content to present to the end-user.

Note

These restrictions are not visible to the end-user, and there is no way for the end-user to circumvent these by altering the other available search options.

Default search setup

To facilitate search operations and narrow down the search options for end-users, the Nodinite Administrator can define what Search Fields are available. In addition, pre-set the proper relational operators and default values to make the search even easier and faster to use.

If you select to include two default search fields, when using the Log View, only these are on the display:

Here's an example of usage of the default search setup.

Optional fields

In addition to the default fields, the end-user may be allowed to further tune the search result using other fields of interest. The Nodinite Administrator may choose to include any of the search fields and the standard fields that comes with a Log Event.

The following fields are common:

• Log Status Code - A number that tells if the processing of the message went fine or not. For example, in BizTalk, the status code for OK is 0. See Log Status Codes.
• Search by Sequence Number - Sequence Number is a number labeled on the message or event. For example, a run may consist of multiple steps. You can allow search by Sequence Number, which is helpful when you know exactly what Log Event to get.
• Log text - A piece of information coming with the message or event. You can allow search by Log text, which is helpful to narrow down the result set.

Auto Start Search

When checked, the search operation runs immediately with the default values from the search setup.

Data to search tab

Use the options available in the Data to Search tab to further refine the filters in use for the Log View.

Here's an example of the additional filter options available within the 'Data to Search' tab.

• Repository Model
  • Integrations
  • Systems
  • Services
  • Message Types
  • Endpoints
• Log Agents

Note

All entities (Endpoints, Message Types and so on) join with an AND operation. For example, if you add one item such as a Message Type and one Endpoint, then the Log Event must match both items. If you add another Message Type (item), an OR operation apply between the two Message Types. If you check the 'Visible in search' option, the User may choose which items to include in the search.

We recommend that you first try the options available in the Search setup tab.

Assigning Entries

Assign specific entities to narrow the scope of searchable data in your Log View. Click the Add button for each entity type to select which items should be included in the search filter.

Systems

Filter Log Events by source or destination systems (e.g., "SAP", "Salesforce", "Dynamics 365").

Example showing the Systems assignment dialog where administrators select which systems to include in the Log View filter.

Endpoints

Filter by specific integration endpoints (e.g., receive ports, send ports, API endpoints).

Example showing the Endpoints assignment dialog where administrators select which endpoints to include in the Log View filter.

Integrations

Filter by business integration flows (e.g., "Order Processing", "Invoice Handling").

Example showing the Integrations assignment dialog where administrators select which integrations to include in the Log View filter.

Log Agents

Filter by data sources that generate log events (e.g., "BizTalk Log Agent", "Custom Application").

Example showing the Log Agents assignment dialog where administrators select which log agents to include in the Log View filter.

Message Types

Filter by message formats or business transaction types (e.g., "PurchaseOrder#1.0", "Invoice#2.0").

Example showing the Message Types assignment dialog where administrators select which message types to include in the Log View filter.

Services

Filter by integration services (e.g., orchestrations, workflows, microservices).

Example showing the Services assignment dialog where administrators select which services to include in the Log View filter.

Display result tab

From the Display result tab, the Nodinite Administrator can adjust the columns in the result from a search operation.

Example with the display result options.

Column Configuration

The Nodinite Administrator can fine-tune which columns are included in the search results. These columns appear when end-users search for Log Events; each user can reorder them with a Display Field Configuration. To rename columns, use the powerful Artifact Renaming feature!

Custom Column Configuration with Artifact Renaming.

You can select columns using three flexible methods:

1. Default (automatic selection)
2. Manual Configuration (custom selection)
3. Use an existing configuration—see the Display Field Configurations user guide for details.

Grouping Tab

From the Grouping tab, the Nodinite Administrator can add one or more Group by fields and set a Post-group filter to gain deeper insights into your data. Advanced grouping enables powerful use cases like tracking BPM processes and Non-Events monitoring.

• Group by options
• Post-group filter

Group by Options

• Grouping - Group the results by the selected field(s).

  Info

  You can select up to four group by fields for advanced analysis.

• Lock group by - When checked, prevents users from changing the group by field(s).
• Use paging for events in a group - When checked, improves performance for large numbers of groups or events.
• Display a group summary - When checked, displays a summary row for each group.
• Collapse the group - When checked, collapses the list of events for each group for a cleaner view.

Here's an example of the Grouping tab.

Design for runtime inspection

Grouped Log Views work best for runtime inspection when the group represents one business transaction and the related events can be explained by clear Repository context.

Good design choices include:

• grouping by a stable business identifier or interchange identifier
• exposing Search Fields that help users find the right transaction quickly
• keeping Services, Contracts, and Systems current in the Repository
• validating that the sample group tells a clean story before publishing the Log View

Read the full design guidance for runtime inspection, and see how users open the result in Inspect grouped Log Views as runtime diagrams.

Post-group Filter

^{New 6.0}

With this feature, you can perform advanced queries such as:

• List all parcels that have been in Oslo (Any)
• List all parcels that never left Oslo (All)
• List all parcels that originated in Oslo (First)
• List all parcels where the last position is Oslo (Latest)
• List all parcels that have never been to Oslo (None)

The Operator After Grouping decides how the filter applies to the events in each group.

Important

Post-group operations may involve significant disk IO on the SQL Server instance. For best performance, optimize your queries and use the shortest possible time frame to narrow down the result set.

Next Steps

Complete Log View configuration with these steps:

1. Add or manage Role - Assign permissions for viewing, downloading, and resending
2. Add or manage User - Grant users access to Log Views through roles
3. Non Events Agent - Enable automated monitoring based on Log View data
4. BPM - Set up end-to-end business process tracking
5. Working with Log Views - Share the end-user guide with your business users

Related Topics

Critical Prerequisites (Configure First)

• Message Types (Mandatory) - Define business transaction types before creating Search Fields
• Search Field Expressions - Configure extraction expressions based on Message Types
• Search Fields - Understand how Search Fields work with Message Types

Log View Configuration

• Log Views - What is a Log View overview
• Log Views - Overview - Manage all Log Views
• Display Field Configurations - Reusable column configurations
• Time Interval Configurations - Control time ranges
• Tag - Organize Log Views with tags

For End Users

• Working with Log Views - Search, view details, and timeline
• Find an order by Order Id - Order flow scenario

Access and Security

• Roles - Configure role-based permissions
• Users - Manage user access
• Permission Set for Log Views - Detailed permission options
• Access Management - Security overview

Data Sources

• Log Event - Understand logged events structure
• Log Agents - How data enters Nodinite
• Asynchronous Logging - Logging pattern for custom solutions

Transformation and Display

• Stylesheets - Transform data into user-friendly formats based on Message Types
• Context Options - Filtering and resend options
• System Parameters - Configure AllowResubmit, AllowRepair, and other settings

Advanced Features Powered by Log Views

• Non Events Agent - Automated monitoring and alerting
• BPM - End-to-end business process tracking
• Runtime Inspection Design - Improve grouped runtime inspection for Participants mode and Systems mode
• Reports - Custom reporting with API URIs

Repository Integration

• Repository Model - Connect events to Integrations, Systems, Services
• Integrations - Business integrations
• Systems - Source/destination systems
• Services - Integration services
• Endpoints - Specific endpoints