Splunk Search

2 Sourcetype, Parsing done on each sourcetype

mha_it_network
New Member

Hi,

The following is what we have.

  • 1 x Forwarder(Heavy Forwarder)
  • 1 x Indexer
  • 1 x Search Head

We are attempting to forward multiple sourcetypes to the indexer with Parsing done on the Heavy Forwarder for each sourcetype.

Problem: Forwarder is Parsing and Forwarding sourcetype mydataA but not mydataB.
Can anyone help?

The following was configured in etc/system/local

inputs.conf
sourcetype = mydataB
index = mydataB


outputs.conf
[tcpout:indexer]
disabled = false
server = 1.1.1.1:9997
hearbeatFrequency = 45
defaultGroup = indexer
indexAndForward = false


props.conf
[mydataA]
TRANSFORMS-dataA = setnulla,setparsinga
[mydataA]
TRANSFORMS-dataB = setnullb,setparsingb


transforms.conf
[setnulla]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue

[setparsinga]
REGEX = error
DEST_KEY = queue
FORMAT = indexQueue

[setnullb]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue

[setparsingb]
REGEX = SUCCESSFUL
DEST_KEY = queue
FORMAT = indexQueue

Tags (1)
0 Karma

dart
Splunk Employee
Splunk Employee

Duplicate up your config, so you have another monitor stanza in inputs.conf, with a different sourcetype, then another stanza in props.conf for the new sourcetype, with new transforms for the appropriate behaviour.

0 Karma

Ayn
Legend

Yes, what is the problem? What did you try that didn't work?

0 Karma
Get Updates on the Splunk Community!

What the End of Support for Splunk Add-on Builder Means for You

Hello Splunk Community! We want to share an important update regarding the future of the Splunk Add-on Builder ...

Solve, Learn, Repeat: New Puzzle Channel Now Live

Welcome to the Splunk Puzzle PlaygroundIf you are anything like me, you love to solve problems, and what ...

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...