Documentation forLoggly

AppOptics Integration

SolarWinds Snap Agent allows for integration between AppOptics and Loggly. With this integration, logs and metrics from infrastructure and systems can be sent from an AppOptics account to Loggly.

This section provides a high level procedure of log forwarding setup from an AppOptics account to Loggly. For the detailed parameters and configurations for logs.yaml used by Snap Agent, please refer to the AppOptics documentation here.

Server Setup

Windows Setup

  1. Open AppOptics and go to AppOptics Home page and click on the "Add Host" button. It will show you the steps below to install the agent via msi package.
  2. Download agent msi installer from here.
  3. Run the installer as Administrator and provide your API key when requested. The installer also supports command line installation. Advanced installation for Windows is documented here.
  4. After the installation, go to C:\ProgramData\SolarWinds\Snap\plugins.d and rename the file logs.yaml.example to logs.yaml
  5. Edit the file logs.yaml and enter the full paths to the logs you want to monitor under logs: > all: > files. If you will send logs to Loggly, make sure that the Loggly Ports and Loggly API Token sections of the file are configured properly.
  6. Save the changes in logs.yaml.
  7. Open Services and look for SolarWinds Snap Agent. Right click the service and click Restart.

Linux Setup

  1. For Loggly clients with different Loggly and AppOptics tokens, you have to invoke installation script with additional options to enable log monitoring. Detailed installation procedure is referenced here.

    sudo bash solarwinds-snap-agent-installer.sh --token <your api token> --detect-logs --loggly-token <your loggly token> [--yes] [--debug]
  2. When you install the SolarWinds Snap Agent, a user called solarwinds which is part of adm group will be created. The solarwinds user runs the SolarWinds Snap Agent service swisnapd.
  3. The folder and files that will be monitored must be owned by adm or your custom group. If your folder and files are owned by a custom group, you need to add solarwinds user to the custom group so it can access the folder and files in it. Run the command below:

    sudo usermod -a -G custom-group-name solarwinds
  4. If the folder and files are not yet owned by adm, run the command below to change the group ownership.

    sudo chgrp adm -R <directory name> #The -R flag will allow you to change the group ownership of folder and files to adm

    If you will monitor log files that are NOT in a subfolder of any default folders in ROOT (/) File System, you don't need to use the -R flag to change the group owner of the files.

  5. If you're using custom group name for folder and files, run the command below to change the group ownership:

    sudo chgrp customgroupname -R <directory name> #The -R flag will allow you to change the group ownership of folder and files to your custom group
  6. Make sure that the group has execute (x) permission to the parent directory and read permission to the files. If the group has no execute permission to the directory yet, run the command below:

    sudo chmod g+x <directory name>/
  7. After the installation, go to /opt/SolarWinds/Snap/etc/plugins.d and rename the file logs.yaml.example to logs.yaml
  8. Edit the file logs.yaml and enter the full paths to the logs you want to monitor under logs: > all: > files. If you will send logs to Loggly, make sure that the Loggly Ports and Loggly API Token sections of the file are configured properly.
  9. Save the changes in logs.yaml file.
  10. Restart the SolarWinds Snap Agent service by running the following command on the same host:

    sudo service swisnapd restart

AppOptics Setup

To enable Logs plugin in the AppOptics UI:

  1. Go to the Integrations Page of your AppOptics Dashboard
  2. Select the Logs plugin to open the configuration menu in the UI.

  3. Enable the plugin.

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.