mirror of
https://github.com/librenms/librenms.git
synced 2024-09-29 14:26:25 +00:00
PagerDuty transport docs
This commit is contained in:
parent
477a857a77
commit
2c04e001a5
@ -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
|
||||
> `>`).
|
||||
|
||||
## <a name="transports-pagerduty">PagerDuty</a>
|
||||
|
||||
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!
|
||||
|
||||
# <a name="entities">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 <tablename>`.
|
||||
|
Loading…
Reference in New Issue
Block a user