Splunk Search

Still necessary to disable typeahead?

Jason
Motivator

I recently upgraded a Splunk environment from 3.4.x and the previous documentation included recommendations to disable typeahead for search performance and "data leakage" reasons.

Are these still valid concerns in 4.1.x?

Tags (1)

zscgeek
Path Finder

From what I have seen in my install performance of type-ahead is a LOT better in 4.1.x and there is no need to disable it for that.

However the data leakage issue still exists if you are using search filters to restrict access to events between roles or users. Suggestions will include data that would be blocked in search filters. If you don't use search filters per role or user I would not worry about it however.

--- RJ

Get Updates on the Splunk Community!

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...

Adoption of Infrastructure Monitoring at Splunk

  Splunk's Growth Engineering team showcases one of their first Splunk product adoption-Splunk Infrastructure ...

Modern way of developing distributed application using OTel

Recently, I had the opportunity to work on a complex microservice using Spring boot and Quarkus to develop a ...