Integrate with Loggly

 

Contents

Introduction

Configure xMatters

Configure the integration

Download resources

The information in this article is the intellectual property of xMatters and is intended only for use with xMatters products by xMatters customers and their employees. Further, this intellectual property is proprietary and must not be reused or resold.

Introduction

This article provides installation, configuration, and implementation details for the xMatters On-Demand for Loggly integration via Zapier.

Loggly is a SaaS solution for log data management. The purpose of the integration is to inject events based on trends that Loggly observes in log files:

  • The integration can be triggered off of any filter that you configure within Loggly
  • You will need to provide authentication information for xMatters. It is recommended that you create a dedicated user account for submitting Loggly events.
  • This integration is outbound from Loggly only (Loggly was not able to accept the web hook callbacks from xMatters.) 
  • Zapier (or a similar technology) is needed, since Loggly cannot send the event information directly to xMatters (Loggly couldn't provide the authentication information needed by xMatters). 
  • At the time of this development, there was no Loggly specific Trigger in Zapier, so we utilized the more generic Webhook connector to receive events from Loggly into Zapier.

Integration created and supplied by Sally Kim and Phil Petrella

Before you start...

You will need some things before you start:

  • An account and login information for Zapier
  • An account and login information for Loggly
  • Access to your xMatters deployment, and the ability to create communication plans

Configure xMatters

Before configuring anything in Loggly, you'll need to configure xMatters.

Create an integration user

This integration requires a user who can authenticate REST web service calls when injecting events.

This user needs to be able to work with events, but does not need to update administrative settings. While you can use the default Company Supervisor role to authenticate REST web service calls, the best method is to create a user specifically for this integration with the "REST Web Service User" role that includes the required permissions and capabilities.

Note: If you are installing this integration into an xMatters trial instance, you don't need to create a new user. Instead, locate the "Integration User" sample user that was automatically configured with the REST Web Service User role when your instance was created and assign them a new password. You can then skip ahead to the next section.

To create an integration user:

  1. Log in to the target xMatters system.
  2. On the Users tab, click the Add New User icon.
  3. Enter the appropriate information for your new user (e.g. Username = loggly).
  4. Assign the user to the REST Web Service User role.
  5. Click Save.
  6. On the next page, set the web login ID and password. It is recommended that you use "loggly" for the User ID, so it is easily identified within your xMatters environment.
Make a note of these details; you will need them when configuring the Loggly side of the integration.

Create users and groups that will receive notifications

Loggly cannot send directly to a specific user or group within xMatters, but you can accomplish targeted notification by either creating subscriptions on the form, or by assigning a default recipient. You will need to create the target users and groups within xMatters that will receive notifications from events initiated by Loggly.

You can create multiple groups and users at once using the EPIC feature. 

Import the communication plan

The next step is to import the loggly communication plan.

To import the Loggly communication plan:

  1. Download the attached Loggly.zip file to your system.
  2. In the target xMatters system, on the Developer tab, click Import Plan.
  3. Click Browse, and then locate the file you downloaded.
  4. Click Import Plan.
  5. Once the communication planhas been imported, click Plan Disabled to enable the plan.

  1. In the Edit drop-down list, select Forms.
  2. For the "Loggly Alert" form, in the Not Deployed drop-down list, click Create Event Web Service.
    • After you create the web service, the drop-down list label will change to Web Service Only.
  3. In the Web Service Only drop-down list, click Permissions.
  4. Enter the integration user you configured above, and then click Save Changes.
To retrieve the web service URL for a form:
  1. On the Forms tab, In the Web Service Only drop-down list, click Access Web Service URL. Copy the highlighted URL at the top of the dialog box.
    • The Access Web Service URL option appears twice in the drop-down menu. Ensure that you click the option just below Create Event Web Service.
You'll need these URLs to configure Zapier.

Configure the integration

Configuring Loggly to initiate events on the xMatters communication plan requires that you create a new Zap in Zapier, and then configure Loggly. 

Configure a Web Hook with Zapier 

Now that you've configured xMatters, it's time to configure Zapier. Loggly is not an activated trigger in Zapier, but you can use the Web Hook set up.

In Zapier, first you need to create a Zap: Webhook in and xMatters out.

Second, you will generate the webhook URL that you will need in Loggly to send in events:

 

Third, you need to select and test your xMatters login:

Fourth, you can optionally specify filter criteria for when you want to trigger the "catch hook". We didn't specify any filter criteria and just let all events trigger the notification.

Fifth, you need to match up the inbound data from the webhook to the xMatters event layout:

Finally, you need to test and name the new Zap:

For more details about configuring Zapier, see the following article:

Setting up Zapier

Create a Loggly Alert

Now you need to configure Loggly to send the alert information to Zapier.
  1. Log in to Loggly and create a user account for xMatters.

  1. Create a Loggly alert, and select the Send to an endpoint check box.

  1. Click Add New, and then configure the endpoint as follows:
    • Endpoint: select HTTP Endpoint
    • Name: type the name to use for this endpoint.
    • URL: paste the web hook URL from Zapier that we generated before.
    • Method: Select POST

  1. Click Save to create the endpoint, and then save the alert.

Test the integration

To test the integration, send an alert from within Loggly.

To test the integration:

  1. Go to Zapier, and run the Zap you created.
  2. In Loggly, either force or wait for a new alert.
If you correctly set up your Loggly alert endpoint with the correct URL, you should see the notifications on the Reports tab in xMatters.

 

 

 

 

 

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk