- 10 minutes to read

Log Audit Search

Build trust and confidence in your Nodinite environment with Log Audit Search, your always-on audit trail for every sensitive operation. Auditing can't be switched off, so you always have a record of who did what, when, and how, for compliance, security, and operational transparency.

  • ✅ Find who permanently deleted, changed, or restored an item, and read the whole entry
  • ✅ See who read a message body or its context in a Log View, and who changed a Role
  • ✅ Follow one operation across all its steps with Show Related for full traceability, and reuse the search through the Web API

Find who permanently deleted the Service Contoso Temp Service: Audit Trail, read the whole entry, and open Show Related, animated walkthrough (7.12)
Animated walkthrough: the permanent delete of a Service is one entry that names what was removed and what was kept.

  1. In Administration, open Log Audit Search on the Tools card, or Tools > Log Audit Search in the sidebar.
  2. In Functions, pick cnfg_RepositoryEntities_HardDelete, the permanent deletes of Services, Systems, Integrations, Domains and Contracts.
  3. In Operation, type the Service's name, and click Search.
  4. Click more on the entry to read all of it: Permanently deleted 1 Service: Service 'Contoso Temp Service: Audit Trail' (Id …). Kept and detached from them: Contract '…: Stock Levels' (Id …). The entry also counts the Transport Contracts that lost the Service.
  5. Open Action > Show Related. For a permanent delete, the dialog holds just this entry: the purge is one operation, and its counts are in that entry.

Understanding Log Audits

graph LR U["fa:fa-user Users
Web Client and Web API"] -->|"sensitive operations"| LA["fa:fa-clipboard-list Log Audit records"] S["fa:fa-gears Core Services
Monitoring and Logging Service"] -->|"system operations"| LA LA --> Search["fa:fa-magnifying-glass Log Audit Search
filter and Show Related"] LA -->|"older than DaysToKeepLogAudits"| Clean["fa:fa-broom Deleted by the
Logging Service cleanup"] style U fill:#2678BD,color:#fff style S fill:#9E59BB,color:#fff style LA fill:#3F827B,color:#fff style Search fill:#93d16d,color:#000 style Clean fill:#c33d34,color:#fff

Blue and purple: the two sources of audited operations, Users and the Core Services. Teal: the records. Green: where administrators search them. Red: records older than DaysToKeepLogAudits are deleted for good by the Logging Service.

Who can open it, and for how long

The Tools card on the Administration overview with Nodinite Overview, Log Audit Search, and User Notifications (7.12)
The Tools card on the Administration overview page. The sidebar has the same entry under Tools.

What is audited in 7.12

The Function column names the code that wrote the entry. Search on it to list one kind of operation.

Area What is audited Functions (examples)
Repository and configuration Create, save, delete, and restore of every entity: Integrations, Systems, Services, Contracts, Message Types, Endpoints, BPMs, Domains, Articles, C4 Diagram Sets, Component Types, Images and Files, Monitor Views, Log Views, Log Agents, Resources, Custom Metadata, Roles, Users, and Tags cnfg_Services_Insert, _Update, _Delete, _Restore; Endpoints as cnfg_EndPoints_*, Images and Files as cnfg_SharedAssets_*
Permanent delete One entry per operation, with the counts of what was removed and what was kept cnfg_RepositoryEntities_HardDelete (Services, Systems, Integrations, Domains, Contracts), and per entity cnfg_EndPoints_HardDelete, cnfg_MessageTypes_HardDelete, cnfg_LogAgents_HardDelete, cnfg_Resources_HardDelete, cnfg_Articles_HardDelete, cnfg_C4DiagramSets_HardDelete, cnfg_C4ComponentTypes_HardDelete, cnfg_Tags_HardDelete, cnfg_SharedAssets_HardDelete. Transport Contracts left empty get their own cnfg_TransportContracts_HardDeleteEmptied entry
Roles and Users Roles, their rights, their members, and the Log Views, Monitor Views, and C4 Diagram Sets they may use cnfg_Roles_*, cnfg_Permissions_*, cnfg_UsersInRoles_*, cnfg_RolesInMessageViews_*, cnfg_RolesInC4DiagramSets_*, cnfg_Users_*
Log View actions Reading a message body or its context values (New 7.12); export, remove, Resend and Repair, and reindex of events and Message Types. Failures to read a message or its context are written too LogEventsController Body, BodySafe; SearchController FlowEvent; MessageController GetMessageContext, ExportEvent, Remove, Resend, Repair, Reindex
System Parameters Every change, with the key and the new value cnfg_SystemParameters_*
Alarm Queue Changes and purges of Alarm Queue entries cnfg_AlarmQueue_*
Monitoring Service Synchronizing Resources with a Monitoring Agent, configuration backups, and Remote Actions Source Synchronizer Worker, Execute Action, Execute Remote Action (generator)
Logging Service Database creation, copying, and cleanup; messages too large to process (MessageProcessingMaxBodySize) Create Database Worker, Database Cleanup Worker, Log_LogAudits_DeleteByDays

Sign-ins are not audited: there is no entry for a login.

How do I find out who did what and when?

Combine these filters, then click Search. All of them must match:

  • Date range - From and To. Log Audit Search opens on today, 00:00:00 to 23:59:59.
  • Level - Info, Warning, Error, Critical, or Debug.
  • Users - Every name that appears as Created By: people, service accounts, and SQL logins. A member of a Windows AD Group shows up under their own Windows name once they have done something that is audited. The list is refreshed every 5 minutes.
  • Functions - The internal name of the code, see the table above.
  • Operation - Entries whose operation contains this text, such as an item's name or Log View with ID: '4270'. It matches plain text; it is not a like expression.
  • Source - The service that wrote the entry, such as Nodinite Web API.

The box to the right counts the system error entries in the audit log this week.

Log Audit Search with the date range, Search, and the Level, Users, Functions, Operation, and Source filters, and the weekly count of system errors (7.12)
The filters above the result.

Narrow today's audit trail to one user's Contoso changes with the Users, Level, and Operation filters, animated walkthrough (7.12)
Animated walkthrough: from everything audited today to one user's Contoso changes.

  1. Click Search to list everything audited today.
  2. In Users, pick a name, and search again. The count drops.
  3. In Level, pick Info, and search.
  4. In Operation, type Contoso, and search. The result shows one user's Contoso changes today.

The result lists Level, Created, Operation, Created By, Function, Source, and Duration, with page sizes from 10 to 500. A long entry is shortened; click more to read all of it.

Log Audit Search result with one permanent delete entry and the columns Level, Created, Operation, Created By, Function, Source, and Duration (7.12)
Each row says what happened, who did it, and which function wrote it.

Example: who deleted a Log Agent?

New 7.12 Search for the Function cnfg_LogAgents_HardDelete to list every permanent delete of a Log Agent. The entry names the Log Agent Ids and counts the Endpoints, Transport Contracts, Log View filters, Log Status Codes, Categories, and BizTalk configurations it removed, and lists the Log Views that lost a filter. Soft deletes and restores show up as cnfg_LogAgents_Delete and cnfg_LogAgents_Restore.

Log Audit Search result with Permanently deleted Log Agents entries and Soft deleted and Restored Log Agent entries (7.12)
A Log Agent's whole story: soft deleted, restored, deleted again, and finally permanently deleted with its Endpoints.

Who read a message body?

Nodinite audits every read of a message body in a Log View, as the Functions LogEventsController Body and LogEventsController BodySafe. Created By is the user's account.

Read an order's message body in the Log View Contoso: Orders, then find the read in Log Audit Search, animated walkthrough (7.12)
Animated walkthrough: a body read in a Log View, and the two audit entries it leaves.

  1. In the Log View Contoso: Orders, search for the order ORD-10001, and open Action > View message body on an event.
  2. In Log Audit Search, type the Log View's id in Operation, here Log View with ID: '4270', and click Search.
  3. Click more: User is trying to access a body … referring to Log View with ID: '4270', with the EventId, the MessageId, and the database. Reads through View message formatted as are audited the same way.
  4. Open Action > Show Related: the second entry says the body was read, with its size.

Who may read bodies at all is set per Role, see Permission Set for Log Views.

Who read a message's context?

New 7.12 Nodinite also audits every read of a message's context values, with the same wording as a body read, so one Operation search on Log View with ID: '…' finds both. Each read writes one Info entry with the Status Succeeded, the Source Nodinite Web API, and the user's account in Created By:

The message context with MessageId: '…' (N context values) was read from database: '…' on server: '…' referring to Log View with ID: '…'.

Action in the Log View Function When it writes the entry
Show Details on an event, also from a BPM SearchController FlowEvent The user's Role may see the context (View Context in the Permission Set for Log Views) and the event has context values. An event without context values writes nothing.
The Resend and Repair dialogs, and the Search Field Wizard (Show Details > Action > Search Field Wizard) MessageController GetMessageContext Every time the dialog loads the context, also when the message has 0 context values.

Log Audit Search entry for a message context read through the Log View Contoso: Orders (7.12)
Show Details on the Order Received event of ORD-10001 in the Log View Contoso: Orders leaves an Info entry with the Function SearchController FlowEvent, the number of context values, and the Log View's id.

To find the reads, search on Operation message context, on the Log View's id, or on one of the two Functions. A failed context read is a Warning entry with the Status Failed, as before. The values on the Search Field Values tab of Show Details are not audited: the audit covers the logged message data, the body and its context, not the values extracted from it.

Who changed a Role?

Saving a Role writes one entry for the Role and one per permission row that changed; unchanged rows are not audited.

Change a right of the Role Contoso: Operations, then find the change and its permission entry in Log Audit Search, animated walkthrough (7.12)
Animated walkthrough: a changed right, and the entries the save wrote.

  1. In the Role Contoso: Operations, set Resend on the Log View Contoso: Orders on the Log Permissions tab, and click Save.
  2. In Log Audit Search, type Name: Contoso: Operations in Operation, and click Search: Update a Role. Name: Contoso: Operations, RoleId: 2369 …
  3. Open Action > Show Related, and click more on the permission entry: Updated Permission (PermissionId …) for Role 'Contoso: Operations' (RoleId 2369): … on Log View 'Contoso: Orders' (Id 4270) … Permitted: Allow -> Deny. The walkthrough was recorded before 7.12 and shows the older text with ids only.

The permission entry names the Role, the right, and the view, with their ids. A new row reads Added Permission … : Allow, and a removed one Removed Permission … from Role ….

Log Audit Search result with Removed Permission entries that name the Role Contoso: Verify E Role and its RoleId, written by cnfg_Permissions_DeleteHard (7.12)
Permission entries name the Role and the view, not only their ids.

Many operations take several steps, sometimes in more than one service. Open Action > Show Related on an entry to list every entry with the same correlation id from around that time, and see the whole operation.

Action menu of a Log Audit entry with its only item, Show Related (7.12)
Show Related is the only item in an entry's Action menu.

Related Log Audits dialog with Copy API URL, Reload, one permanent delete entry, and Statistics (7.12)
The Related Log Audits dialog has Copy API URL and Reload.

Copy the API URL of the related entries and of the whole search, animated walkthrough (7.12)
Animated walkthrough: the same searches as Web API URLs, for a report or a monitoring tool.

  1. Search for the permanent delete, as in the walkthrough at the top, and open Action > Show Related.
  2. Click Copy API URL in the dialog: the URL of the related entries.
  3. Close the dialog, and click Copy API URL above the result: the URL of the whole search, Use the URI link in your preferred reporting tool to import the JSON data.

Copy API URL also works when the search finds nothing, so you can save a search that has no hits yet.

Copy API URL dialog over an empty Log Audit Search result that says There is no result to present with the specified search criteria (7.12)
The URL of a search with no result yet.

Use the Web API

There is no CSV export: use Copy API URL, or call the Web API directly. Every route needs the Administrators Role.

Route Returns
GET api/LogAudits/Search?searchJson=… The same search as the page; the URL that Copy API URL gives
GET api/LogAudits Entries page by page, with level, fromDate, toDate, and orderBy
GET api/LogAudits/GetLast The latest entry
GET api/LogAudits/NumberOfLogAudits The number of entries
GET api/LogAudits/GetUsers The names the Users filter offers

The URL shows the Web API address of your installation. Use it in custom Reports or scripts.

Get alerted on Log Audit content

Use the Web Services Monitoring Agent to raise alerts based on Log Audit content; see How to Monitor Log Audit.

Why Log Audit Search Matters

Log Audit Search is your foundation for trust and accountability. With Nodinite, you know what happened, who did it, and when. It helps you:

  • Prove compliance to auditors and stakeholders
  • Investigate incidents and resolve issues faster
  • Detect unauthorized changes and support security policies

Next Steps