PagerDuty is the enterprise incident resolution service that integrates with ITOps and DevOps monitoring stacks to improve operational reliability and agility. From enriching and aggregating events to correlating them into incidents, PagerDuty streamlines the incident management process by reducing alert noise and resolution times.
Here is an example of a PagerDuty dashboard with netdata notifications:
To have netdata send notifications to PagerDuty, you'll first need to set up a PagerDuty Generic API service and install the PagerDuty agent on the host running netdata. See the following guide for details:
https://www.pagerduty.com/docs/guides/agent-install-guide/
During the setup of the Generic API PagerDuty service, you'll obtain a pagerduty service key. Keep this service key handy.
Once the PagerDuty agent is installed on your host and can send notifications from your host to your Generic API service on PagerDuty, add the service key to DEFAULT_RECIPIENT_PD in health_alarm_notify.conf:
#------------------------------------------------------------------------------
# pagerduty.com notification options
#
# pagerduty.com notifications require the pagerduty agent to be installed and
# a "Generic API" pagerduty service.
# https://www.pagerduty.com/docs/guides/agent-install-guide/
# multiple recipients can be given like this:
# "<pd_service_key_1> <pd_service_key_2> ..."
# enable/disable sending pagerduty notifications
SEND_PD="YES"
# if a role's recipients are not configured, a notification will be sent to
# the "General API" pagerduty.com service that uses this service key.
# (empty = do not send a notification for unconfigured roles):
DEFAULT_RECIPIENT_PD="<service key>"