topic Re: Trying to filter and route logs/events using a Splunk Heavy Forwarder in Getting Data In

Trying to filter and route logs/events using a Splunk Heavy Forwarder

shashank9 — Wed, 19 Feb 2025 04:47:56 GMT

Hi Everyone,

I've installed and configured a Splunk Heavy Forwarder on an EC2 instance in AWS and configured two Splunk Indexers on EC2 instances in AWS. I created a test.log file on my HF with sample log events to forward them to my Splunk indexers. I'm trying to forward the logs/events with keyword "success" to indexer_1 and forward logs/events with keyword "error" to indexer_2.

But, for some reason the logs/events from the HF are not visible in both Indexers. Just for the context, I have installed and configured a UF on another EC2 Instance in AWS and sending data to Indexer_1 and I can see the data successfully forwarded with no issues.

Below are the .conf files and setup on my HF and two indexers.

HF:

inputs.conf:

[monitor:///opt/splunk/var/log/splunk/test.log]
disabled = false
sourcetype = test

outputs.conf:

[tcpout:errorGroup]
server = indexr_1_ip_addr:9997

[tcpout:successGroup]
server = indexer_2_ip_addr:9997

props.conf:

[test]
TRANSFORMS-routing=errorRouting,successRouting

transforms.conf:

[errorRouting]
REGEX=error
DEST_KEY=_TCP_ROUTING
FORMAT=errorGroup

[successRouting]
REGEX=success
DEST_KEY=_TCP_ROUTING
FORMAT=successGroup

Indexer_1 & Indexer_2:

Configured the port 9997 on both indexers.

Note: I tried below steps to troubleshoot or identify the issue, but no luck so far:

1. Checked if the forwarder has any inactive forwards or receivers through CLI:

Active forwards:
indexr_1_ip_addr:9997
indexr_2_ip_addr:9997
Configured but inactive forwards:
None

2. Check the splunkd.log on the forwarder to see if there are any errors related to data forwarding: No errors

3. Checked the Security Group rules (Inbound and Outbound) in AWS console: Port 9997 is enabled for both Inbound and Outbound traffic.

4. All EC2 Instances running Splunk are on the same Security Group in AWS.

5. Tried to Ping both Indexers from HF. But, no response.

Can someone please help me with this issue as I'm stuck and unable to figure out what is the root cause of the issue. Also, I'm using the same security group for both HF and UF with same Inbound and Outbound rules, but I can only see the logs sent from UF and not seeing the logs/events from my HF. I'm not sure what I am missing here to resolve or fix the issue to see the logs/events from HF in my Indexers.

Thank you!

Re: Trying to filter and route logs/events using a Splunk Heavy Forwarder

kiran_panchavat — Wed, 19 Feb 2025 05:18:51 GMT

@shashank9

Can you check this on the heavy forwarder?

netstat -tulnp | grep 9997 OR ss -tulnp | grep 9997

Check the metrics.log if any queues are getting blocked.

tail -f /opt/splunk/var/log/splunk/metrics.log | grep -i "blocked=true"

Verify that outputs.conf the HF is correctly configured. Ensure there are no typos in the IP addresses or port numbers.
File permission issues could be a possible reason why Splunk HF is not reading test.log. If the Heavy Forwarder (HF) process does not have the required permissions to read the file, it won't be able to forward logs to the indexers.

Re: Trying to filter and route logs/events using a Splunk Heavy Forwarder

shashank9 — Wed, 19 Feb 2025 07:24:30 GMT

@kiran_panchavat Thank you for those steps and suggestions:

I tried those steps and below are the details:

Can you check this on the heavy forwarder?

netstat -tulnp | grep 9997 OR ss -tulnp | grep 9997

Ran the above command in on my HF:

1. First it said:

grep: invalid option -- 't'
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.

2. Then when I tried to only grep for 9997 (netstat -tulnp | grep 9997) I did not see any output.

Check the metrics.log if any queues are getting blocked.

tail -f /opt/splunk/var/log/splunk/metrics.log | grep -i "blocked=true"

Verify that outputs.conf the HF is correctly configured. Ensure there are no typos in the IP addresses or port numbers.
- I verified that both my indexers IPs mentioned in the HF's outputs.conf file are correct.
  - Can you please confirm if the below stanza name tcpout is correct or if there is any typo with it?
- [tcpout:errorGroup]
  server = indexr_1_ip_addr:9997
  [tcpout:successGroup]
  server = indexer_2_ip_addr:9997
File permission issues could be a possible reason why Splunk HF is not reading test.log. If the Heavy Forwarder (HF) process does not have the required permissions to read the file, it won't be able to forward logs to the indexers.
- On the HF the file /opt/splunk/var/log/splunk/test.log I changed the user and group ec2-user:
  - -rw-r--r-- 1 ec2-user ec2-user 1133 Feb 19 00:53 test.log
    - I restarted the HF and checked my indexers for logs/events from the HF under main index. But, no luck ☹️

Re: Trying to filter and route logs/events using a Splunk Heavy Forwarder

kiran_panchavat — Wed, 19 Feb 2025 08:40:39 GMT

@shashank9

1. Then, when I tried to only grep for 9997 (netstat -tulnp | grep 9997) I did not see any output.

--> it means the indexers are NOT listening for incoming data. This could mean, The HF not configured to listen on port 9997. Network issues preventing the HF from binding to port 9997.

Verify that outputs.conf the HF is correctly configured. Ensure there are no typos in the IP addresses or port numbers.

--> Your outputs.conf look correct:

[tcpout:errorGroup]
server=indexr_1_ip_addr:9997

[tcpout:successGroup]
server=indexer_2_ip_addr:9997

On the HF, in the file /opt/splunk/var/log/splunk/test.log I changed the user and group ec2-user:

--> The file permissions for /opt/splunk/var/log/splunk/test.log seem correct. However, ensure that the Splunk process has the necessary permissions to read the file. You can check the Splunk user running the HF and adjust permissions accordingly.

Check the splunkd.log in heavy forwarder:-

tail -n 100 /opt/splunk/var/log/splunk/splunkd.log | grep -i "ERROR"

tail -n 100 /opt/splunk/var/log/splunk/splunkd.log | grep -i "WARN"

Verify that the Splunk process is running on the HF: ps -ef | grep splunkd
Finally, I would recommend you add this to the heavy forwarder:

Go to cd /opt/splunk/etc/system/local

vi inputs.conf

[splunktcp://9997]
disabled = 0

Restart Splunk.

Re: Trying to filter and route logs/events using a Splunk Heavy Forwarder

shashank9 — Sat, 22 Feb 2025 00:37:38 GMT

Hi @kiran_panchavat actually I accidentally terminated my ec2 instances in AWS and had to re launch them and re-install Splunk from scratch on all those instances and once I set them up and configured the event routing to different Splunk receivers from my Heavy Forwarder I was able to see a specifc group of logs/events are sent to one of my Splunk receivers which is expected. I still could not see the data in my other Splunk receiver but I guess I just need to double check my configuration since it is working fine with one of the servers.

Also, thank you for your time in guiding me through those steps to troubleshoot the issue.

Re: Trying to filter and route logs/events using a Splunk Heavy Forwarder

kiran_panchavat — Sat, 22 Feb 2025 04:44:16 GMT

@shashank9

Thanks for the update. It’s great that one of your Splunk receivers is now getting the logs as expected. Since the other receiver still isn’t showing data, I’d recommend a quick review of its configuration to see if there’s a missing or misconfigured detail. If the steps were helpful and you resolve the issue, feel free to accept the solution. Thanks again for your update!