HideAdditionalFieldValuesInLogViews - System Parameter
HideAdditionalFieldValuesInLogViews sets each built-in Log Event detail field on the Additional Field Values tab of a Log View, such as EndPointUri, LogText, or ProcessingUser, to show, hide, or mask. The Web Client reads it and applies it in every Log View, for every user.
At a Glance
| Property | Value |
|---|---|
| Key | HideAdditionalFieldValuesInLogViews |
| Data type | json |
| Default | {} (all fields shown) |
| Read by | Web Client |
| Takes effect | Up to 1 hour (the Web Client caches this value); no restart needed |
| Status | ✅ Active |
| Since | Nodinite 6.0.0.30 |
How It Works
- Global, not per Role. The setting applies to all Log Views and all users. It doesn't grant or remove anything per Role; to give different audiences different fields, give them different Log Views.
- The Log View configuration wins. A field that an administrator adds to the Log View configuration in Add or Manage Log View is always shown, whatever this parameter says.
- Administrators see the same result. The Administrator Role isn't checked: in a normal Log View, administrators see hidden and masked fields exactly like other users. The values are visible only in the built-in system Log View that shows all events.
- Display only. The values are still logged and stored; the parameter only changes what the Web Client shows.
Scope
This parameter covers the built-in fields on the Additional Field Values tab only. Values of Search Fields on the Search Field Values tab are controlled by the sibling parameter HideSearchFieldValuesInLogViews. To protect context properties, use ProtectedContextValues or keep them from being logged with ContextPropertiesFilters; to show only selected parts of the message body, use Stylesheets.
Value Format
A JSON object. Each property name is a built-in field name, and each value is one of three states:
| Value | Effect on the Additional Field Values tab |
|---|---|
show |
The field and its value are shown (the default for any field you leave out) |
mask |
The field row is shown, but its value is masked |
hide |
The field row isn't shown at all |
Write the states in lowercase, exactly as above. An empty object {} shows every field.
Example
The example lists the built-in field names; MessageGuid, ServiceInstanceSequenceNo, ServiceInstanceActivityId, and EndPointUri are masked, and ProcessingUser is hidden.
{
"SequenceNo": "show",
"EventId": "show",
"MessageGuid": "mask",
"EventNumber": "show",
"ServiceInstanceSequenceNo": "mask",
"ProcessingMachineName": "show",
"ProcessName": "show",
"ProcessingModuleName": "show",
"ProcessingModuleType": "show",
"ProcessingTime": "show",
"ProcessingUser": "hide",
"LocalInterchangeId": "show",
"ApplicationInterchangeId": "show",
"ServiceInstanceActivityId": "mask",
"LogText": "show",
"MessageTypeName": "show",
"OriginalMessageTypeName": "show",
"EndPointName": "show",
"EndPointUri": "mask"
}
Choosing a Value
- Use
maskwhen users should know the field exists but not see its value, for exampleEndPointUriwhen addresses contain credentials or internal host names. - Use
hidefor fields that only confuse your audience, such as internal sequence numbers. - Allow up to an hour before you verify a change in the Web Client.
Next Steps
- Add or Manage Log View - Add a field to a Log View to always show it
- Manage System Parameters - Change the value
Related Topics
- HideSearchFieldValuesInLogViews - Hide Search Field values that aren't in the Log View
- ProtectedContextValues - Protect context values
- ContextPropertiesFilters - Remove context properties before they're stored
- Stylesheets - Present only the selected data of interest
- Additional Fields tab - What end users see in a Log View
- What is a Log View?
- Web Client
- System Parameters