- 10 minutes to read

HideSearchFieldValuesInLogViews – System Parameter

Control the visibility of Search Field values in Nodinite Log Views with the HideSearchFieldValuesInLogViews system parameter. This setting determines whether search field values that are not explicitly included in the Log View configuration are displayed to end-users.

What you'll achieve with this parameter:

  • Hide search field values not configured in Log Views
  • Enhance data privacy and security
  • Simplify user interface by showing only relevant fields
  • Fine-tune data visibility on a per-Log View basis

The HideSearchFieldValuesInLogViews System Parameter controls whether Search Field values that are not explicitly included in a Log View's configuration are displayed when users view Log Events. This provides administrators with granular control over data visibility and helps maintain privacy and security policies.

System Parameter Name Data Type Values/Example Comment
HideSearchFieldValuesInLogViews boolean true Default = true (hidden). Set to false to show all search field values regardless of Log View configuration.

When set to true (default), only Search Fields explicitly configured in the Log View's Search Setup tab are displayed to end-users. When set to false, all available search field values are shown, even if they weren't included in the Log View configuration.

Note

Changes to this parameter are effective immediately in the Web Client. You do NOT need to restart any services for the new value to take effect.

How It Works

Behavior Matrix

The following matrix shows exactly how the parameter behaves in all scenarios:

Scenario Parameter Value User Type Search Field in Log View Config? Result
1 TRUE (default) Regular User No Hidden - No values shown, displays "Hidden"
2 TRUE Regular User Yes Visible - Values shown normally
3 TRUE Admin User No Hidden - Even admins see "Hidden" (values not shown)
4 TRUE Admin User Yes Visible - Values shown normally
5 false (override) Regular User No HiddenForcedVisible - Values shown with security warning
6 false Regular User Yes Visible - Values shown normally
7 false Admin User No HiddenForcedVisible - Values shown with security warning
8 false Admin User Yes Visible - Values shown normally
9 Any Any System Property View Always Visible - isAdminView=true bypasses check

Important

Critical Security Note: When set to TRUE, even administrators cannot see Search Field values that are not explicitly configured in the Log View. This enforces the principle of least privilege consistently across all user types.

With HideSearchFieldValuesInLogViews = true (Default)

When this parameter is set to true, the Web Client displays a clean, focused interface showing only the Search Fields that administrators have configured for each Log View:

Configured Search Fields - Only fields selected in the Log View configuration appear
Other Fields Hidden - Search field values not in the configuration display "Hidden"
Enhanced Privacy - Sensitive data not intended for the audience remains hidden
Simplified UI - Users see only relevant fields for their specific use case
Consistent Enforcement - Applies to all users including administrators

Hidden Search Field values
Example: Search Field values not defined in the Log View are hidden when the parameter is set to true.

With HideSearchFieldValuesInLogViews = false

When set to false, all available Search Field values are displayed, even if they weren't explicitly configured in the Log View:

All Fields Visible - All search field values appear regardless of Log View configuration
Security Warning Shown - Web Client displays warning banner but values remain visible
Forced Visibility - Search Fields show as "HiddenForcedVisible" state in the UI
Maximum Transparency - Users can see all extracted data from Log Events
Data Exposure Risk - Sensitive data (passwords, tokens, PII) may be exposed
Temporary Debugging - Useful for troubleshooting search field extraction

Warning

Security Risk: Setting this to false exposes ALL Search Field values to ALL users with access to the Log View. This includes potentially sensitive data like passwords, API tokens, credit card numbers, or personally identifiable information (PII). Use only in development/test environments or temporarily for debugging.

Use Cases

Scenario 1: Production Security (value = TRUE)

Environment: Production
Requirement: Strict data governance and compliance
Configuration:

  1. Set HideSearchFieldValuesInLogViews = TRUE (default)
  2. Carefully configure each Log View to include only necessary Search Fields
  3. Assign Log Views to appropriate Roles based on business function
  4. Document which fields are visible in each Log View for audit purposes

Result:
✅ Users only see approved Search Fields per their role
✅ Sensitive fields (SSN, credit cards, passwords, API tokens) remain hidden
✅ Different teams have different visibility (sales, support, finance, IT)
✅ Principle of least privilege enforced automatically
✅ Safe for multi-tenant and shared environments

Example:
Your organization has a "Customer Support" Log View configured to show only OrderID, CustomerName, and OrderStatus. With this parameter set to true, support staff won't see sensitive fields like CreditCardNumber, SSN, or APIToken that might exist in other Search Fields.

Scenario 2: Development/Debugging (value = false)

Environment: Development or Test
Requirement: Full visibility for troubleshooting Search Field extraction
Configuration:

  1. Temporarily set HideSearchFieldValuesInLogViews = false
  2. All Search Field values become visible with security warnings in UI
  3. Debug and verify Search Field extraction logic
  4. Reset to TRUE after debugging!

Result:
Developers can see all extracted values for debugging
Security warning banner displayed in Web Client
Verify XPath, JSON Path, or RegEx expressions are working
Test Message Type and Search Field configuration

Caution

Temporary Override Only! This setting should only be used temporarily during development or troubleshooting. Always reset to TRUE when finished to restore security controls.

Scenario 3: Incremental Search Field Rollout

Scenario: Adding new Search Fields to existing [Message Types][]
With TRUE (Recommended):

New Search Fields are automatically hidden until explicitly added to Log Views
Safe default - No accidental data exposure
Administrators review and approve new fields before making them visible
Controlled rollout to different Roles based on need

With false (Risk):

New Search Fields immediately appear to all users
Potential exposure of sensitive data before review
No opportunity to limit visibility by Role

Scenario 4: Administrator-Only Environments

Setting this parameter to false may be appropriate for:

Internal IT Team Only - Where all users are trusted administrators
Non-Production Environments - Test instances without sensitive data
Full Visibility Requirements - Organizations with no data privacy restrictions
Research & Development - Analyzing log patterns and testing configurations

Warning

Security Risk: Even in administrator-only environments, consider whether all administrators should see all data. Apply the principle of least privilege whenever possible.

Integration with Log View Configuration

This parameter works in conjunction with the Add or Manage Log View configuration, specifically the Search Setup tab:

Search Setup Tab Configuration

When administrators create or edit a Log View, they select which Search Fields to include in the Search Setup tab:

  1. Default Search Fields - Pre-configured fields that appear automatically
  2. Optional Fields - Additional fields users can add to their search
  3. Restrictions - Mandatory filters that apply to all searches

How the Parameter Affects Display

  • When HideSearchFieldValuesInLogViews = true:
    Only the Search Fields configured in steps 1-3 above are displayed when viewing Log Event details

  • When HideSearchFieldValuesInLogViews = false:
    All available Search Fields are displayed, regardless of the Log View configuration

Additional Field Values Tab

The Additional Fields Tab in the Log Event details view is also affected by this parameter:

  • Hidden (true): Only configured fields appear in the Additional Fields tab
  • Visible (false): All extracted search field values appear

Best Practices

Security & Privacy

Secure - Only Search Fields explicitly configured in the Log View are visible
Principle of Least Privilege - Users only see what administrators have approved
Safe for Multi-Tenant - Different teams can have different visibility without data leakage
Compliance Ready - Supports GDPR, HIPAA, PCI-DSS, and SOX requirements
Safe Field Rollout - New Search Fields are hidden by default until approved
Note: Even administrators cannot see hidden Search Field values in the UI

When false (Security Risk)

Exposes All Search Fields - All Search Field values become visible to all users with Log View access
Potential Data Leak - Sensitive data (passwords, API tokens, PII, credit cards) may be exposed
Compliance Violation Risk - May violate GDPR, HIPAA, PCI-DSS, or internal security policies
Multi-Tenant Unsafe - Data from one team may be visible to another
Security Warning Shown - UI displays warning but values are still visible
Use Case: Troubleshooting/debugging scenarios only (temporary override)

Keep Default Setting - Leave at TRUE unless you have specific temporary debugging needs
Review Sensitive Data - Audit which Search Fields are configured before exposing them
Role-Based Views - Create different Log Views for different Roles with appropriate field visibility
Use ContextPropertiesFilters - Combine with ContextPropertiesFilters to prevent sensitive data from being logged
Regular Audits - Review Log Audits to track who accessed which data
Reset After Debugging - If you temporarily set to false, reset to TRUE immediately after troubleshooting

Configuration Strategy

Purpose-Built Views - Design Log Views with specific audiences in mind
Document Decisions - Record why certain fields are included or excluded
Test Visibility - Verify field visibility with test users before deploying to production
Monitor Access - Use Log Audits to track which users access which data

Frequently Asked Questions

Find more solutions and answers in the Nodinite System Parameters FAQ, as well as the Troubleshooting user guide.

How do I change the value?

Changing a value for the pre-defined System Parameters is described in the generic 'How do I change the System Parameters' article.

Do I need to restart anything?

No! Changes to this parameter are effective immediately in the Web Client. Users will see the updated field visibility the next time they access a Log View. No service restart is required.

Does this affect which data is logged?

No. This parameter only controls the display of search field values in the Web Client. It does not affect:

To control what data is actually logged, use the ContextPropertiesFilters system parameter.

Can I show different fields to different roles?

Yes! The recommended approach is:

  1. Keep HideSearchFieldValuesInLogViews set to true
  2. Create separate Log Views for each Role
  3. Configure different Search Fields in each Log View via the Search Setup tab
  4. Assign each Log View to the appropriate Roles

This gives you granular control over which fields each role can see.

What about the HideAdditionalFieldValuesInLogViews parameter?

The HideAdditionalFieldValuesInLogViews parameter is different:

  • HideSearchFieldValuesInLogViews - Controls visibility of Search Field values
  • HideAdditionalFieldValuesInLogViews - Controls visibility of additional technical fields (EventId, SequenceNo, etc.) with options to mask sensitive values

Both parameters work together to provide comprehensive control over field visibility.

Does this setting affect Log View search functionality?

No. Users can still search using any Search Fields configured in the Log View, regardless of this parameter's value. This parameter only affects the display of field values in the search results and event details, not the ability to search by those fields.

Can administrators override this setting?

Administrators with appropriate permissions can always view all data by:

  • Using the "View details" action which opens the full Log Event details page
  • Querying Log Databases directly via SQL
  • Accessing data through the Web API

This parameter primarily affects the standard Log View interface for end-users.

How do I modify this parameter?

Via Admin UI:

  1. Navigate to Administration → Settings → System Parameters
  2. Find HideSearchFieldValuesInLogViews in the list
  3. Set value to TRUE (recommended) or false (temporary debugging only)
  4. Click Save
  5. Changes take effect immediately for new API calls and page loads

Via SQL (Advanced):

-- View current value
SELECT [Name], [Value], [Description]
FROM [Nodinite].[dbo].[SystemParameters]
WHERE [Name] = 'HideSearchFieldValuesInLogViews';

-- Set to TRUE (recommended - secure)
UPDATE [Nodinite].[dbo].[SystemParameters]
SET [Value] = 'true'
WHERE [Name] = 'HideSearchFieldValuesInLogViews';

-- Set to false (temporary debugging only)
UPDATE [Nodinite].[dbo].[SystemParameters]
SET [Value] = 'false'
WHERE [Name] = 'HideSearchFieldValuesInLogViews';

Tip

Changes take effect immediately - no service restart required! The Web Client uses the updated value on the next API call.

Next Step

Log Views - Understand Log View capabilities
Add or Manage Log View - Configure field visibility
Search Fields - Learn about searchable fields
Roles - Configure role-based access