Skip to main content


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:

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:

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:

# notification options
# notifications require the pagerduty agent to be installed and
# a "Generic API" pagerduty service.
# multiple recipients can be given like this:
# "<pd_service_key_1> <pd_service_key_2> ..."
# enable/disable sending pagerduty notifications
# if a role's recipients are not configured, a notification will be sent to
# the "General API" service that uses this service key.
# (empty = do not send a notification for unconfigured roles):
DEFAULT_RECIPIENT_PD="<service key>"
# Which PD API are we going to use? For version 2 or newer, it is necessary to do a request for Pagerduty
# before to set the version(

Reach out

If you need help after reading this doc, search our community forum for an answer. There's a good chance someone else has already found a solution to the same issue.



Last updated on