Getting Data In

How to route a monitor input to specific indexer?

cybermonday
Explorer

I have a Syslog collector receiving logs from multiple Syslog devices and writing them in a directory-structured log file. The same host runs as my HF.
One of those .log files, I want to read using [monitor] and send to a specific indexer (10.20.30.40:9998)
where others continued to be read by their respective monitors and sent to one of the indexers as chosen by indexerDiscovery (some configs in my below outputs are missing but that works as that's not the issue).

the issue is - I am facing difficulty in onboarding logs from this .log file, however, I am getting the internal logs of the HF which means there is no networking issue.

below are my configs, any correction in them would be highly appreciated.


inputs.conf
----------------------------------------------------------
[monitor:///var/log/splunk/Checkpoint/*/*.log]
disabled = 0
Sourcetype = cp_log
index = index1
host_segment = 5
# _TCP_ROUTING = isolationGroup

[monitor:///var/log/splunk/Checkpoint_sys/*/*.log]
disabled = 0
Sourcetype = cp_log
index = index1
host_segment = 5


props.conf
----------------------------------------------------------
[cp_log]
TRANSFORMS-routing = isolationRouting


transforms.conf
----------------------------------------------------------
[isolationRouting]
REGEX = .*
DEST_KEY = _TCP_ROUTING
FORMAT = isolationGroup


outputs.conf
----------------------------------------------------------
[tcpout:my_indexers]
clientCert = /opt/splunk/etc/auth/my_certs/my_serverCert.pem
indexerDiscovery = MyIndexersDiscovery
useACK = true

[tcpout:isolationGroup]
server = 10.20.30.40:9998

 

Labels (3)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @cybermonday,

as described at https://docs.splunk.com/Documentation/SplunkCloud/latest/Forwarding/Routeandfilterdatad#Route_inputs... you have to apply this configuration to the system that you're using to ingest data:

outputs.conf

[monitor:///var/log/splunk/Checkpoint/*/*.log]
disabled = 0
Sourcetype = cp_log
index = index1
host_segment = 5
_TCP_ROUTING = isolationGroup

[monitor:///var/log/splunk/Checkpoint_sys/*/*.log]
disabled = 0
Sourcetype = cp_log
index = index1
host_segment = 5

inputs.conf

[tcpout:my_indexers]
clientCert = /opt/splunk/etc/auth/my_certs/my_serverCert.pem
indexerDiscovery = MyIndexersDiscovery
useACK = true

[tcpout:isolationGroup]
server = 10.20.30.40:9998

you don't need of props and transforms, they are used to modify some values after inputs, on Heavy Forwarders or Indexers.

Ciao.

Giuseppe

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Introduction to Splunk AI

How are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. Lucky for ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Maximizing the Value of Splunk ES 8.x

Splunk Enterprise Security (ES) continues to be a leader in the Gartner Magic Quadrant, reflecting its pivotal ...