Add or Manage Log View
Nodinite Log Views give your business secure, self-service access to business transactions and end-to-end logging. This guide shows how to add a Log View and gives an overview of its five tabs; each tab has its own page with the details.
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 in runtime diagrams
- ✅ Business intelligence - Enable Non-Events Monitoring and BPM process tracking

Animated walkthrough: from Add Log View to a Log View that is ready to search.
- In Administration > Log Views, click Add Log View and name the Log View on the General tab.
- Under Roles, click Edit, tick the Role that may use it, and click Confirm and close.
- On Data to search, click Edit on Message Types, filter, tick the types, and click Confirm and close.
- On Search criteria, click Edit on Default search setup and add a clause with the Search Field users search on (O2C - Order ID).
- Leave Display result on Default and click Save and show.
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:
- Message Types - Define business transaction types (e.g., "PurchaseOrder#1.0", "InvoiceMessage#2.0")
- Search Field Expressions - Configure XPath, JSON Path, or RegEx expressions to extract business data based on Message Type
- Search Fields - Associate expressions with Message Types to make them searchable
- 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, correlation IDs, and basic properties (Log Status Code, Log Text).
Understanding the Log View configuration
Search Fields"] roLV["fa:fa-hard-drive Log View
General, Search criteria, Data to search,
Display result, Grouping"] roRole["fa:fa-users-class Roles with
permissions"] roUser["fa:fa-users End-user"] roNE["fa:fa-alarm-clock Non-Events Monitoring
and BPM"] roAdmin -->|"configures first"| roMT roMT -->|"make business data searchable"| roLV roAdmin -->|"add or edit"| roLV roLV -->|"granted to"| roRole roRole -->|"members"| roUser roUser -->|"search for business transactions"| roLV roLV -.->|"enables"| roNE style roAdmin fill:#9E59BB,color:#fff style roMT fill:#3F827B,color:#fff style roLV fill:#2678BD,color:#fff style roRole fill:#E47528,color:#fff style roUser fill:#9E59BB,color:#fff style roNE fill:#93d16d,color:#000
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 five tabs map to what the Log View does:
| Tab | Decides | Typical settings | Details |
|---|---|---|---|
| General | Who may use it | Name, description, website, Tags, Roles and their rights | Log View General Tab |
| Search criteria | What users can search | Time Interval Configuration, Restrictions, default and optional Search Fields | Log View Search Criteria Tab |
| Data to search | Which events are in scope | Integrations, Systems, Services, Message Types, Endpoints, Log Agents | Log View Data to Search Tab |
| Display result | What users see | Columns, Display Field Configurations | Log View Display Result Tab |
| Grouping | How events are combined | Group by fields, post-group filter | Log View Grouping Tab |
Add or edit a Log View
- Add: in the Log Views Overview, click Add Log View.
- Edit: click a name in the list, or use Edit in the row's Action menu.
- Duplicate: in the editor toolbar, click Duplicate and give the copy a new name. The copy gets everything: the General tab with its Roles and their rights, Search criteria (Restrictions included), Data to search, Display result, and Grouping.
- Restore: deleted Log Views can be restored, see View and Restore Deleted Records.
- Copy to another environment: Log Views are not part of Import/Export, neither in the Web Client nor in the Web API. Read the Log View with
GET api/LogViewsfrom the Web API in one environment and create it withPOST api/LogViewsin the other.

Click the Add Log View button to create a new Log View.
The editor's footer has Save, Save and show (opens the Log View), Save and close, and Cancel.
General tab
Name the Log View, and decide who may use it. Only users in the assigned Roles see the Log View; the rights per Role decide whether they may read context and message bodies, view them through a Stylesheet, resend, or repair. New Log Views start with the Roles in DefaultRolesInViews.
Search criteria tab
Decide what users search on: the time ranges they may pick, the fields the search starts with (default search setup), the fields they may add (optional fields), and hidden Restrictions that always apply. The fields you include here also decide which Search Field values the Log View shows; see Which Search Field Values a Log View Shows and HideSearchFieldValuesInLogViews.
Read the Search criteria tab →
Data to search tab
Decide which events are in scope: only those of the Integrations, Systems, Services, Message Types, Endpoints, and Log Agents you pick. Items of one type combine with OR, the types with AND.
Display result tab
Decide which columns users see: the default columns, your own selection with Artifact Renaming, or a reusable Display Field Configuration.
Grouping tab
Turn the event list into one row per business transaction with Group by, and keep only the groups you want with the post-group filter. Grouped Log Views power BPM tracking, Non-Events monitoring, and runtime diagrams; see Design grouped Log Views for Runtime Inspection.
Next Steps
- Add or manage Role - Assign permissions for viewing, downloading, and resending
- Add or manage User - Grant users access to Log Views through roles
- Non Events Agent - Enable automated monitoring based on Log View data
- BPM - Set up end-to-end business process tracking
- Working with Log Views - Share the end-user guide with your business users
Related Topics
- Log View General Tab
- Log View Search Criteria Tab
- Log View Data to Search Tab
- Log View Display Result Tab
- Log View Grouping Tab
- Which Search Field Values a Log View Shows - Hidden values, Restrictions, and the Admin view
- 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 Views - What is a Log View overview
- Log Views - Overview - Manage all Log Views
- Tag - Organize Log Views with tags
- Find an order by Order Id - Order flow scenario
- Roles - Configure role-based permissions
- Users - Manage user access
- Permission Set for Log Views - Detailed permission options
- Access Management - Security overview
- Log Event - Understand logged events structure
- Asynchronous Logging - Logging pattern for custom solutions
- System Parameters - Configure AllowResubmit, AllowRepair, and other settings
- Runtime Inspection Design - Improve grouped runtime inspection
- Reports - Custom reporting with API URIs