We are transitioning from getting the HEC data through HFs to getting it directly to the indexers and we are wondering if upon introducing a new data source are we forced to do an indexer rolling restart.
Since you're talking about rolling restart, I suppose you're using indexer cluster.
In this case adding an input (as opposed to removing one) might not require you to do a restart (but there are some cases when CM says it will do the restart anyway; that's one of pros for having a layer of HFs before your indexers)
As per your other question - you can manipulate several config items, including inputs, using REST API. But you shouldn't do that on a cluster since your config should be consistent across all nodes.
Hi @danielbb
If you are using config files to create your HEC tokens, which I suspect you will be! then Yes you will need to restart Splunk for it to allow the new HEC tokens to work.
For more info check out https://docs.splunk.com/Documentation/SplunkCloud/latest/Data/UseHECusingconffiles#:~:text=Restart%2....
Please let me know how you get on and consider adding karma to this or any other answer if it has helped.
Regards
Will
Great @livehybrid, "If you are using config files to create your HEC tokens", what are my options on-prem to configure the HEC token?
Hi @danielbb
As @PickleRick has pointed out in his reply just now, as you have an indexer cluster you should be making changes by pushing your indexer config via a configuration bundles pushed from your Cluster Manager.
This means making changes in the manager-apps/yourOrg_inputs/local/inputs.conf file (or similar) and then pushing a bundle. Splunk will determine if a restart is needed however I think improvements have been made in more recent versions to reduce the number of restarts needed, but there is no guarantee if wont need a restart. When you click "Validate and Check Restart" it should tell you if a restart is required.
Please let me know how you get on and consider adding karma to this or any other answer if it has helped.
Regards
Will