Deployment Architecture

Splunk test environment

erikwie
Path Finder

I need to set up an splunk test environment to test out apps before adding them to production environment, also to test out adding new data into new indexes before adding it to production.

We run an splunk enterprise 7.3.1, all in one single instance on a physical server.

My plan for the test environment is to set up a standalone splunk installation with the free 500MB/day license and test the new stuff.

Does any of you have any experience with something similar?
Can I get the universal forwarder on a few servers to send data to two splunk servers, In the docs on the universal forwarder I understand that there is a support for loadbalancing between several indexers, but it seems like it will send to either and not both.

Tags (1)
0 Karma
1 Solution

rmjharris
Path Finder

In outputs.conf on the forwarders:

[tcpout]
defaultGroup = prodserver, testserver

[tcpout:prodserver]
server =

[tcpout:testserver]
server =

From the outputs.conf documentation.

"# You can have as many target groups as you want.

If you specify more than one target group, the forwarder sends all data

to each target group. This is known as "cloning" the data."

View solution in original post

rmjharris
Path Finder

In outputs.conf on the forwarders:

[tcpout]
defaultGroup = prodserver, testserver

[tcpout:prodserver]
server =

[tcpout:testserver]
server =

From the outputs.conf documentation.

"# You can have as many target groups as you want.

If you specify more than one target group, the forwarder sends all data

to each target group. This is known as "cloning" the data."

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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...