Hi deepthi5,
technically this is not a problem to achieve, personally I would find the reason why one host is sending more events than usually and fix that problem.
Okay, here is what you can do:
Read the docs about Access and use the CLI on a remote server and enable remote login on your universal forwarders. Create a search that returns only the host you want to stop and save it as alert which will trigger a script.
Now, here is the tricky part: Splunk will not pass the search result to this script, but you can pass either an URL or a file name where the event result is available to the alert script. So your alert script must ab able to
read the host name which you want to stop
be able to remote login to this host and stop Splunk via CLI command
As I said, I wouldn't do it this way ..... because, if your script or your search go crazy .. bad things could happen, like stopping the wrong host.
cheers, MuS
... View more