Some photography, SRE, and a little DevOps!
Recent Posts
Goodbye X-Clacks-Overhead: GNU Terry Pratchett
Sorry to say, my blog is no longer carrying the x-clacks-overhead signal.
read moreVarious Python (& Other) Book Recommendations
Book recommendations for Python learning & other technology topics.
read moreUpdating X-Clacks-Overhead: GNU Terry Pratchett
Adding x-clacks-overhead HTTP header to a Cloudfront Hosted site, using a response headers policy.
read moreSetting the Priority of Pagerduty Incidents with Service Event Rules in Terraform
Using Terraform pagerduty_service_event_rule to set an incident’s Priority based on it’s severity.
read moreManaging PagerDuty Business Services With Terraform
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 😢.
PagerDuty Change Events & GitHub Actions
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. Being on building on the Terraform in the previous post, it’s just adding another data source and resource to your Terraform: