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!

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 ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had 3 releases of new security content via the Enterprise Security ...

Archived Metrics Now Available for APAC and EMEA realms

We’re excited to announce the launch of Archived Metrics in Splunk Infrastructure Monitoring for our customers ...