Getting Data In

Filter events on indexer from multiple universal forwarders

takemusu
Explorer

We've about 20 universal forwarders monitoring different log files. Our system doesn't allow to use heavy forwarders because of their performance impact on data indexing.
These universal forwarders send their data to a couple of indexers.

I've read Route and filter data docu (Discard specific events and keep the rest section). My question is that as we have different source log files located on different boxes, how would I refer them in props.conf file:

[source::?????]
TRANSFORMS-null= setnull

For example, on one box I monitor /log/log.1 and on another /log/log.2.
Should I point the hostname after the source:: as well? Could somebody show an example?

Thanks in advance,
Alexey

0 Karma
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

Editing sourcetypes.conf rarely ever is required, your own sourcetype settings reside in props.conf.

Put your transforms list under your common sourcetype log4j in props.conf:

[log4j]
TRANSFORMS-null = ...

Remember, this will affect every event with sourcetype=log4j regardless of host and sourcetype.

View solution in original post

martin_mueller
SplunkTrust
SplunkTrust

Editing sourcetypes.conf rarely ever is required, your own sourcetype settings reside in props.conf.

Put your transforms list under your common sourcetype log4j in props.conf:

[log4j]
TRANSFORMS-null = ...

Remember, this will affect every event with sourcetype=log4j regardless of host and sourcetype.

takemusu
Explorer

Yes, for now these files are using the same sourcetype (log4j). When you say put the TRANSFORMS-foo value under that sourcetype - do you mean editing sourcetype.conf?

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Do those files use the same sourcetype? If so, put the TRANSFORMS-foo value under that sourcetype.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...