- 3 minutes to read

HideSearchFieldValuesInLogViews - System Parameter

HideSearchFieldValuesInLogViews controls whether the Web Client shows Search Field values that are not part of a Log View's configuration. With the default true, users only see the Search Field values the administrator added to the Log View; every other value shows as Hidden.

At a Glance

Property Value
Key HideSearchFieldValuesInLogViews
Data type boolean
Default true (hide values not in the Log View configuration)
Read by Web Client
Takes effect Within about 15 seconds; no restart needed
Status ✅ Active
Since Nodinite 5.4

How It Works

When a user opens a Log Event in a Log View, the Search Field Values tab lists the Search Field values extracted from the message. This parameter decides what happens to values for Search Fields the Log View doesn't include:

Value Search Field in the Log View configuration Search Field not in the Log View configuration
true (default) ✅ Shown ❌ Shown as Hidden
false ✅ Shown ⚠️ Shown

Search Field Values tab with values shown as Hidden
The Search Field Values tab: Search Fields that are not part of the Log View show Hidden instead of their value; Search Fields in the Log View, such as Order number and City, are shown.

To show a hidden value, add the Search Field to the Log View on the Search Setup tab in Add or Manage Log View. A Search Field in the Log View configuration is always shown, whatever this parameter is set to. Read What is a Search Field for how Search Fields extract their values.

Who Sees Hidden Values

  • Every user sees the same hiding, administrators included. The parameter doesn't check the Administrator Role: in a normal Log View an administrator sees Hidden exactly like any other user.
  • The only exception is the built-in system Log View that shows all events. Hidden values are visible there, and nowhere else in the Web Client.

Scope

This parameter covers Search Field values only. The built-in event detail fields on the Additional Field Values tab, such as EndPointUri, LogText, or ProcessingUser, are controlled by the sibling parameter HideAdditionalFieldValuesInLogViews, which can show, hide, or mask each field.

The parameter only changes what the Web Client displays. It doesn't change what is logged, what is extracted and indexed, or what is stored in the Log Databases, and it doesn't stop users from searching with the Search Fields their Log View includes. To keep sensitive data out of Nodinite altogether, use ContextPropertiesFilters; to show only parts of the message body, use Stylesheets.

Choosing a Value

  • Keep true (default) in production. A new Search Field stays hidden in every Log View until an administrator adds it, so nothing leaks before review.
  • Give each audience its own Log View. Create one Log View per Role and include only the Search Fields that Role needs.
  • Use false only temporarily, for example in a test environment while you verify a Search Field Expression. Every user with access to a Log View then sees every extracted value, including values from Search Fields you never meant to show, such as personal data or tokens. Set the value back to true when you are done.

Next Steps