Over the past decade, PagerDuty has become the defacto standard for waking up notifying developers and DevOps teams of incidents relating to their applications or services.
Just over a month ago the company went public and cited 11,000 customers as part of their filing.
At Harness, we’re empowering developers with self-service deployment capabilities so Continuous Delivery and change is the new norm.
In addition to email, HipChat, and Slack notifications, PagerDuty was one of the most requested integrations by our customers. Today, all these notification channels are now supported.

Real-Time Deployment Notifications

A Harness deployment workflow is constructed of many steps and strategies. One of which is a notification strategy that allows users to notify based on specific execution conditions and scope.
For example, a Harness user can notify if a deployment workflow or canary phase succeeds, fails, or is paused.
Let’s create a new notification strategy and use our new PagerDuty integration as the channel.

Creating a Notification Strategy

To get started, let’s edit an existing deployment workflow in Harness.
In the top right of the below screenshot, we have a section called “Notification Strategy.”

Let’s click “+ Add Notification Strategy” to define our strategy.

The above strategy will now notify our User Group Dev Team when our workflow fails.
The last thing we need to do is integrate PagerDuty to our Dev Team User Group.

Integrating PagerDuty With Harness

Good news – it takes 30 seconds to integrate PagerDuty with Harness.
Let’s go and edit our Dev Team User Group by going to:
Harness > Continuous Security > Access Management > User Groups
After opening our Dev Team User Group, we can edit its “Notification Settings”:

Then, all we need to do is paste in the PagerDuty Integration Key from the Account/Service that you wish to map.

You can copy your Service Integration Key from PagerDuty:
Configuration > Services > Service Details > Integrations
That’s it! Our PagerDuty notification is now ready to go.  We just need a failed deployment now….so let me go kill a canary or something.

Example: A Failed Deployment

Below is a screenshot showing an instance of our deployment workflow (Prod GCP Docker Workflow) that happened to fail.

A few seconds later, all hell breaks loose on my phone:

Logging into PagerDuty also confirms our failed deployment incident:

Feel free to test our new PagerDuty support with a 15-day trial of Harness.

Keep Reading

  • The Women of DevOps: Patricia Anong

    The Women of DevOps: Patricia Anong

    Meet Patricia Anong, DevOps Consultant. We're thrilled for you to meet her!
  • Introduction to Helm: Charts, Deployments, & More

    Introduction to Helm: Charts, Deployments, & More

    Probably one of the first packages installed after your Kubernetes cluster is up and running is Helm. A stalwart in the Kubernetes ecosystem, Helm is a package manager for Kubernetes. If you are unfamiliar with Helm, Helm helps users to have a more consistent deployment by packaging up all of the needed resources needed for a Kubernetes deployment.
  • GitOps Got Me Up

    GitOps Got Me Up

    Two years ago, I joined the technology space - and as such, I am now a strong proponent for DevOps methodologies.