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!

Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA

Join us on Wed, Dec 10. at 10AM PST / 1PM EST for a live webinar and demo with Splunk experts! Discover how ...

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...