From 2c04e001a577ffde35be35bdb38480b418116ee9 Mon Sep 17 00:00:00 2001 From: f0o Date: Thu, 14 May 2015 13:56:09 +0000 Subject: [PATCH] PagerDuty transport docs --- doc/Extensions/Alerting.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/doc/Extensions/Alerting.md b/doc/Extensions/Alerting.md index 99ac395564..a181565876 100644 --- a/doc/Extensions/Alerting.md +++ b/doc/Extensions/Alerting.md @@ -14,6 +14,7 @@ Table of Content: - [IRC](#transports-irc) - [Slack](#transports-slack) - [HipChat](#transports-hipchat) + - [PagerDuty](#transports-pagerduty) - [Entities](#entities) - [Devices](#entity-devices) - [BGP Peers](#entity-bgppeers) @@ -242,6 +243,20 @@ $config['alert']['transports']['hipchat'][] = array("url" => "https://api.hipcha > results, such as HipChat attempting to interpret angled brackets (`<` and > `>`). +## PagerDuty + +Enabling PagerDuty transports is almost as easy as enabling email-transports. + +All you need is to create a Service with type Generic API on your PagerDuty dashboard. + +Now copy your API-Key from the newly created Service and setup the transport like: + +```php +$config['alert']['transports']['pagerduty'] = 'MYAPIKEYGOESHERE'; +``` + +That's it! + # Entities Entities as described earlier are based on the table and column names within the database, if you are ensure of what the entity is you want then have a browse around inside MySQL using `show tables` and `desc `.