Stop Sending Data to Loggly
To stop sending data to Loggly from your system(s)/application(s) please follow the instructions below. The specific uninstall instructions you should use depend on the method used to send logs to Loggly. If you used a script to configure logging, it’s easy to use the same script to stop sending your logs to Loggly.
Method 1: Uninstall Using the Loggly Script
Linux, Apache, Tomcat, Nginx, or Mac OS:
Uninstall is very straightforward using the same the script used during installation. Just run the script with the -r flag to remove the configuration.
For example: The Linux Configuration Script (Configure-linux.sh) could be used to uninstall Loggly as follows.
Step 1. Download the script again if you can’t find your copy.
curl -O https://www.loggly.com/install/configure-linux.sh
Step 2. Run:
sudo bash ./configure-linux.sh -a SUBDOMAIN -r
Replace subdomain with your own Loggly subdomain.
File Monitoring Script
sudo bash configure-file-monitoring.sh -a SUBDOMAIN -l FILE_ALIAS -r
Note: FILE_ALIAS is the same alias you chose when you set it up.
AWS S3 File Monitoring Script
sudo bash configure-s3-file-monitoring.sh -a SUBDOMAIN -s3l S3-BUCKET-ALIAS -r
Note: S3-BUCKET-ALIAS is the same alias you chose when you set it up.
Legacy Syslog-ng Configuration Script
To remove the changes made by the syslog configuration script, run
Method 2: Manual Uninstall
If you have used any manual instructions to log from our supported logging platforms, please remove any configuration that you added and restart the related service(s).
For example: If you followed the manual configuration such as Manually Configure Rsyslog or Syslog-ng you could uninstall by following the steps below.
- Check and remove the 22-loggly.conf file (or the ones you created for Loggly) under either /etc/rsyslog.d/ or /etc/syslog-ng/
- Restart the syslog process
- Check whether rsyslog or syslog-ng are running
Method 3: Uninstall Using Documentation
For other log sources you can follow the steps described in the documentation for your log source. Run the installation steps in reverse to undo any changes you made earlier. Additionally, if you are sending logs to Loggly from one of the sources listed in our catalog here, please refer to the instructions/readme for the library in use. They are maintained by the community and it’s best to check the latest instructions.
If you have any issue stopping the sending of logs to Loggly, please contact support or post/search in our community forum.
When the APM Integrated Experience is enabled, Loggly shares a common navigation and settings with the other integrated experiences' products. How you navigate Loggly and access its features may vary from these instructions. For more information, go to the APM Integrated Experience documentation.
The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.