Using Terraform pagerduty_service_event_rule to set an incident’s Priority based on it’s severity.

This is my third blog post about PagerDuty, and the second about using the Terraform provider for PagerDuty. This time I’ll be focusing on business services. So far I’ve not a chance to make use of business services, but I have spent quite sometime investigating and creating custom tooling using the APIs following the release in early 2020 (which was before I started on my Terraform journey). I can see how business services would be very useful when widely adopted and combined with status pages, which don’t have APIs yet 😢.

Following on from Managing PagerDuty Services With Terraform, another rather nice PagerDuty feature is Change Events. This was release at last years PagerDuty Summit. Which I started making use of these a few months ago, as they add some additional context around possible changes that were deployed that could be relevant for incidents on the service. Using them is in GitHub is really simple, first you just need to add the integration to the service.

For the last couple of years, I had been the primary maintainer for some tooling which makes heavy use of the PagerDuty REST API. Given my increasing use of Terraform plus now PagerDuty has a free account level. I thought I could get myself a PD account for receiving alerts from any monitoring for my blog that I may do and more importantly also complete a little brain bump of some PagerDuty + Terraform thoughts that are currently rattling around before start focusing on different things for my new job next week.