Skip to content

Transatel/pd-centreon-connector

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 

Repository files navigation

pd-centreon-connector

Propagate ACKs from PagerDuty to Centreon.

This is a reimplementation of pd-nag-connector in PHP, targeting Centreon, with additional features.

Features

Support for multi-poller architecure

By using Transatel/api-centreon-notification-helper, we can send acks / unacks to any service even in a multi-poller architecure.

Multi-API version support

The code is compatible with both PagerDuty Webhooks API v1 and v2.

User and channel in ACK message

The username as well as the channel (website or mobile) will be extracted from the webhook request and used to compose the ack message in Centreon:

Acknowledged by <USER> (via PagerDuty - <CHANNEL>)

Loop prevention

Before ack'ing / deack'ing, we test the state the service / host to ensure that we don't trigger a loop in case of a bi-directional integration between Centreon and PagerDuty.

Configuration

The configuration is at the top of the pagerduty.php file.

Here is the bare minimum you need to configure:

Key Description
NOTIF_HELPER_API_URL URL to access Transatel/api-centreon-notification-helper

Additionally, you can play with the following:

Key Description
UNACK_ON_RESOLVE If true unacks when receiving an incident.resolve
IS_STICKY Does ack stay on status change. Either NAGIOS_STICKY_YES or NAGIOS_STICKY_NO
DO_NOTIFY Do we notify on ack. Either NAGIOS_NOTIFY_YES or NAGIOS_NOTIFY_NO
IS_PERSISTENT Is ack persistent bewteen poller reboots. Either NAGIOS_PERISTENT_YES or NAGIOS_PERISTENT_NO
DEFAULT_ACK_USERNAME Fallback username to put in ACK message

About

🔕 Propagate ACKs from PagerDuty to Centreon

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages