After installing either the Log Analysis Quick Start plugin, it queries Sumo Logic to get aggregate information and statistics from your events. This information is then transformed and sent to your New Relic account, which is identified by your New Relic license key. The plugin requests data from Sumo Logic every minute and sends it to your New Relic account.


Install the New Relic Windows Plugin

These instructions are for installing the plugin on Windows servers. The plugin installer (windowsEvents-1.0.0.tar.gz) is attached to this article. In order to use this plugin, you must have an Enterprise account.

The plugin requests data from Sumo Logic every 15 minutes and sends it to your New Relic account. The plugin relies on pre-built searches and analytics, which means that the plugin expects the data coming into Sumo Logic to be standard Windows events (including system, application, security, or any other standard event categories).

 

To install the Windows plugin:

1. Download the compressed file (windowsEvents-1.0.0.tar.gz).

2. Unpack the plugin into a directory on the host server.

3. Open the newly unpacked /windowsEvents-1.0.0/config directory.

4. Open the newrelic.properties file for edit. Under the value for  LicenseKey, enter your New Relic license key.

 licenseKey = f263da765876851fd8c78d419b91b298ee859ac7

5. Open the sumologic.properties file for edit.

a. Under SumoLogicUser, add your Sumo Logic access ID. See Access Keys for more information.

SumoLogicUser = myaccessid

b. Under SumoLogicPassword, add your Sumo Logic access key. See Access Keys for more information.

SumoLogicPassword = myaccesskey

 c. Under SumoLogicDeployment, enter the deployment (pod or endpoint) that matches the location of your Sumo Logic account. Use one of these values:

SumoLogicDeployment = prod, eu, au, or us2

7. Execute the jar file, allowing for background execution of the plugin:

java -jar windowsEvents-1.0.0.jar &

 

The plugin will request data from Sumo Logic every 15 minutes to send to your New Relic account. If the plugin stops running, simply start it again by repeating step 3 (above). It’s recommended that the plugin be a monitored process to ensure that the data stream is continuous.