Deployment Architecture

search head props.conf

rv6abob
Engager

Before we used distributed search, we used to have a stanza like this in props.conf:

[lan]
pulldown_type = true
maxDist = 3
TIME_FORMAT = %b %d %H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 32
TRANSFORMS = syslog-host
REPORT-syslog = syslog-extractions
SHOULD_LINEMERGE = False

That doesn't seem to work if we put that on the search head. Do we have to put it on each of the indexers? Is the SHOULD_LINEMERGE statement only active at index time?

Tags (2)

Genti
Splunk Employee
Splunk Employee

The search head does not do any indexing. Hence a props.conf such as this on the search head does nothing.
This needs to be put in all your indexers, (or at least the indexers where you receive events for the "lan" sourcetype)
Should_linemerge is active at index time.

gkanapathy
Splunk Employee
Splunk Employee

Not exactly. The REPORT-syslog clause will take effect (as will the pulldown_type setting). The others will not. Please see, as usual: http://www.splunk.com/wiki/Where_do_I_configure_my_Splunk_settings%3F

Get Updates on the Splunk Community!

Index This | When is October more than just the tenth month?

October 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

What’s New & Next in Splunk SOAR

 Security teams today are dealing with more alerts, more tools, and more pressure than ever.  Join us for an ...