Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Concourse Pagerduty Notification Resource

Sends alerts to Pagerduty. This resource can now send log output of failing Concourse task(s) to Pagerduty, as well as the standard description and incident_key fields.

Resource Type Configuration

- name: pagerduty-notification-resource
  type: docker-image
    repository: fidelityinternational/pagerduty-notification-resource
    tag: latest

Source Configuration

  • service_key: Required. The GUID of one of your "Generic API" services. This is the "Integration Key" listed on a Generic API's service detail page.

The following fields are required if you want to see erroring Concourse task output in the Pagerduty notification:

  • atc_external_url: Optional The ATC external URL (if username and password is supplied but not the ATC URL, it will attempt to use the standard in-built ATC_EXTERNAL_URL instead)
  • atc_username: Optional ATC username is required if atc_external_url is supplied.
  • atc_password: Optional ATC password is required if atc_external_url is supplied.

Example resource config:

- name: pagerduty-notify
  type: pagerduty-notification-resource
    atc_external_url: ...
    atc_username: ...
    atc_password: ...
    service_key: ...


out: Sends alert to pagerduty.

Send alert to pagerduty with the configured parameters.



  • description: Static text of alert to send


  • incident_key: Provides an incident key that can be used to dedupe alerts. Defaults to `/<job-name
  • action: Specifies whether to trigger, resolve, or acknowledge an insident. Defaults to trigger


See our sample pipeline.yml for a working example.


To test this resource, install a test Concourse with Docker following the guide here.

Push the sample pipeline to it (remember to update the Pagerduty resource configuration options first, as appropriate):

fly login -t local -c http://localhost:8080 -u concourse -p changeme
fly -t local set-pipeline -p test -c pipeline.yml

Browse http://localhost:8080 and run the monitoring-test job. One of the tasks in that job is supposed to succeed, and one is supposed to fail. Note the Pagerduty put: on the failing job. This should now trigger, so check your Pagerduty account for an incoming alert.

Inside the alert message you should find pipeline, job_name, concourse_build_url and output fields which contain useful error messages.

You can’t perform that action at this time.