At StackPulse, we’re on a mission to help developers and site reliability engineers build and run more reliable software services. As part of this, we’re big believers in translating manual processes into executable code, and automating that execution where it makes sense. That’s why we’re excited to share our first GitHub action – StackPulse Apply Playbook.
Code-based incident response with the StackPulse Apply Playbook action
Instead of manually configuring playbooks, or updating them in production after each release, you can build, update and test your playbooks – then leverage the GitHub action to deploy them as you push application code changes to production. That means in addition to shipping new application code, you can also ship code detailing your operational process for responding to alerts and managing incidents.
Gone are the days of 3AM phone calls, war rooms, and escalations. By turning your incident response practices into code you can automatically enrich alerts and incidents with contextual data, use that data to understand root cause, and take actions to remediate – all without human intervention. Of course, we’re all about checks and balances too, so you can put in as many or as few control gates as you’d like!
It’s easy to get started – you just need an active StackPulse account and API keys. Applying a playbook or trigger is straightforward – you can check out a few example actions on the GitHub Marketplace.
What can you do with a StackPulse playbook?
StackPulse is designed to empower developers by automating incident response, reducing siloed knowledge, and analyzing data on why and how your services fail, and how you respond when they do. This automation and data frees teams from the toil of responding – helping you invest in delivering more reliable services.
“GitHub Actions puts powerful, flexible CI/CD and automation directly into developers’ workflows allowing them to deliver more secure software. With StackPulse’s first Apply Playbook action, teams can now automatically deploy playbooks and triggers along with their code, further tightening the loop between development and SRE.”Chris Patterson, Product Manager for GitHub Actions
StackPulse playbooks collect data on your running services and environment to enrich alerts, distribute this data to on-call teams automatically, and perform remediation steps to resolve common issues.
Below you can see an example StackPulse playbook. This triggers a redis error, performs investigation into root cause, and delivers results to a Microsoft teams channel.