Yes, all environments. For example, we have one server acting as the license master, and all of our boxes in test/prod environments point to it as their license master.
It is good practise to avoid sharing the same license between prod and test, and allocate different pools instead. Mainly to avoid test using too much license out of your production one while you are testing things. For instance, you could allocate 1GB to test and the remaining to prod or something similar.
If you have several teams using Splunk this is a good practise too as you could buy a bigger license and save a lot of money but then allocate the right amounts to each team.
See this: http://docs.splunk.com/Documentation/Splunk/latest/Admin/Createalicensepool
Yes, all environments. For example, we have one server acting as the license master, and all of our boxes in test/prod environments point to it as their license master.
Very interesting - thank you.
Right. How Splunk licensing works
says -
Any host in your Splunk Enterprise infrastructure that performs indexing must be licensed to do so.