A Graylog plugin that triggers PagerDuty events
Java
Permalink
Failed to load latest commit information.
src
.gitignore Update .gitignore Jan 29, 2015
.mailmap
.travis.yml
LICENSE Rename COPYING to LICENSE Jul 27, 2015
README.md
pom.xml Prepare next development iteration Jul 20, 2016

README.md

PagerDuty Plugin for Graylog

Build Status

An alarm callback plugin for integrating PagerDuty into Graylog.

Screenshot: Overview

Required Graylog version: 2.0 and later

Plugin versions starting with 1.3.0 require Graylog 2.0 and higher. For older Graylog versions please use previous releases.

Installation

Download the plugin and place the .jar file in your Graylog plugin directory. The plugin directory is the plugins/ folder relative from your graylog-server directory by default and can be configured in your graylog.conf file.

Restart graylog-server and you are done.

Usage

The only thing you need to do in your PagerDuty interface is to add a new service called Graylog. Click Services in the main menu and then hit the Add new service button.

Screenshot: Adding a new service in PagerDuty

Give the new service any name you’d like, for example graylog and select an escalation policy. Select Graylog from the Integration type dropdown box and click Add Service.

On the next page you will see the Service API Key that Graylog needs to notify PagerDuty about alerts. Copy it.

Screenshot: Copying the Service Key from PagerDuty

The last thing to do is to copy that token into the alarm callback configuration in Graylog.

Screenshot: Configuring the PagerDuty alarm callback in Graylog

Click Add alert destination and you are done. Your PagerDuty account will now receive alerts of this stream.

Build

This project is using Maven and requires Java 8 or higher.

You can build a plugin (JAR) with mvn package.

DEB and RPM packages can be build with mvn jdeb:jdeb and mvn rpm:rpm respectively.

Plugin Release

We are using the maven release plugin:

$ mvn release:prepare
[...]
$ mvn release:perform

This sets the version numbers, creates a tag and pushes to GitHub. TravisCI will build the release artifacts and upload to GitHub automatically.