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!

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...

Built-in Service Level Objectives Management to Bridge the Gap Between Service & ...

Wednesday, May 29, 2024  |  11AM PST / 2PM ESTRegister now and join us to learn more about how you can ...

Get Your Exclusive Splunk Certified Cybersecurity Defense Engineer Certification at ...

We’re excited to announce a new Splunk certification exam being released at .conf24! If you’re headed to Vegas ...