Getting Data In

How to turn off logging from a particular host when a server is decomissioned?

Kaushikkatta03
Explorer

As one of our servers is decommissioned, we need to turn off the logging from that particular host. Please kindly help us in doing this.

Tags (2)
0 Karma
1 Solution

inventsekar
SplunkTrust
SplunkTrust

for temporary turn off the data logging from a particular host, we can turn off the splunk process -
$SPLUNK_HOME/splunk stop

as host is decommissioned, you can uninstall the universal forwarder

  1. If you configured the universal forwarder to start on boot, remove it from your boot scripts before you uninstall.
    cd $SPLUNK_HOME
    ./splunk disable boot-start

  2. Stop the forwarder.
    ./splunk stop

  3. Uninstall the universal forwarder with your package management utilities
    RedHat Linux
    rpm -e splunk_product_name

Debian Linux
dpkg -r splunkforwarder

https://docs.splunk.com/Documentation/Forwarder/6.4.3/Forwarder/Uninstalltheuniversalforwarder

View solution in original post

somesoni2
Revered Legend

One option would to be blacklist the host serverclass.conf on Deployment server so that it doesn't receive any data input configuration and doesn't monitor/logs any data. The decommissioning should take care of the un-install anyways.

0 Karma

inventsekar
SplunkTrust
SplunkTrust

for temporary turn off the data logging from a particular host, we can turn off the splunk process -
$SPLUNK_HOME/splunk stop

as host is decommissioned, you can uninstall the universal forwarder

  1. If you configured the universal forwarder to start on boot, remove it from your boot scripts before you uninstall.
    cd $SPLUNK_HOME
    ./splunk disable boot-start

  2. Stop the forwarder.
    ./splunk stop

  3. Uninstall the universal forwarder with your package management utilities
    RedHat Linux
    rpm -e splunk_product_name

Debian Linux
dpkg -r splunkforwarder

https://docs.splunk.com/Documentation/Forwarder/6.4.3/Forwarder/Uninstalltheuniversalforwarder

Kaushikkatta03
Explorer

Thanks I did it . logging stopped

0 Karma

esix_splunk
Splunk Employee
Splunk Employee

Stop Splunk running on the server.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...