Harness Introduces PagerDuty Support for Real-Time Deployment Notifications

PagerDuty Integration Banner

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.”

PagerDuty Support: Setting Up Notifications


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

PagerDuty Support: Setting Up Notifications


After opening our Dev Team User Group, we can edit its Notification Settings:

PagerDuty Support: 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.

Failed Deployment


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 free trial of Harness.
Cheers,
Steve.

Modernizing Continuous Integration Banner

Modernizing Continuous Integration: Best Practices and Challenges

Modernizing Continuous Integration is great, but there are some key challenges to avoid - and best practices to ensure success!

Feature Flags Best Practices Banner

Feature Flags Best Practices (Feature Toggles)

Testing in production, trunk-based development, using feature flags by default - these are all Feature Flags Best Practices. Learn more now, and make your feature flag experience as beneficial as it can be!

Jenkins Pipelines to Harness CD Banner

Migrating CD Jenkins Pipelines to Harness Using Helm

Making the switch from Jenkins pipelines to Harness CD was a breeze! Here was Corey's experience.

GitHub Actions Support in Harness CI Banner

GitHub Actions Support in Harness CI

GitHub Actions let you create custom actions that can perform predefined tasks. Learn how to use them in Harness CI for added extensibility.