All Apps and Add-ons

Splunk Stream - Distributed Forwarder Management

Kendo213
Communicator

I am successfully collecting DNS logs from some domain controllers, but I noticed the Distributed Forwarder Management isn't working how I intended. All of my clients are falling under the 'defaultgroup'. I have a group called 'infra_dns' configured with a regex rule of 'infra_dns'

My inputs.conf on my domain controllers looks like this:

[streamfwd://streamfwd]
splunk_stream_app_location = https://splunkserver:8000/en-us/custom/splunk_app_stream/
stream_forwarder_id = infra_dns
disabled = 0

Any ideas?

0 Karma

markhill1
Path Finder

Have you tried removing the infra_dns from the stream_forwarder_id stanza in the inputs.conf?
Then restart the client instance. Go to the Distributed group you made in the Stream app and see if it appears in your available client regex area?

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!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...

Splunk Agent Observability: Measuring AI Value with Splunk Tokenomics on AWS

The AI landscape is moving faster than ever, and our latest 2026 State of Observability report provides the ...

Enterprise Security Watch Party: What’s New in 8.8 - Recap

Splunk Community HQ hosted a Splunk Enterprise Security Watch Party: What’s New In ES 8.8 last Thursday. I had ...