We’re thrilled to now deliver PagerDuty support for incident-based webhooks to all users. With webhooks generally available, we’re helping to enable a more real-time Web in PagerDuty so that devops teams can improve collaboration and incidence response through customizations to suit their needs. Even better, we worked with Atlassian HipChat, the popular hosted group chat and IM service, to create a deep integration with webhooks to show what’s possible with third-party web services.
Back to Webhooks Basics
Webhooks enable developers to make web applications more programmable, integrated and automated. As demonstrated in Dave’s post on animating incidents with webhooks, adding webhooks to PagerDuty allows for HTTP callbacks surrounding an interesting event to a specified URL. Any changes to the state of the incident or users will trigger outgoing messages to be sent. With this integration now available to all users, webhooks allow PagerDuty and our customers to better integrate with third-party tools to do customized reporting, alerting and other connections between web services. That’s where your imagination comes in!
PagerDuty Incidents Get Social with HipChat
HipChat is persistent group chat for teams, with over 140 integrations and native clients for desktop and mobile devices. HipChat has integrated its chat and communication platform into PagerDuty’s alerting ecosystem. This means that thanks to webhooks, HipChat can rebroadcast PagerDuty incident status on all state changes, including triggers, acknowledgements, resolves, assigns and escalations.
We’re big HipChat fans at PagerDuty. Our teams use the tool every day to communicate with remote teammates, collaborate on tasks and inform each other of everything from when lunch is ready to web production changes. Bringing PagerDuty incident status changes into HipChat makes it even easier to respond to alerts quickly and keep your team in sync while you do it.
“We jumped at the opportunity to integrate PagerDuty with webhooks because of how immediately handy this collaboration would be for both us and our customers – and it was fast and easy to do,” said Garret Heaton, Co-Founder of HipChat. “Adding PagerDuty functionality via webhooks not only helps our customers to communicate more seamlessly, but also aids us internally to stay synced about every incident status change.”
Building Your Own Integrations
Webhooks can be widely used to integrate PagerDuty incidents with other web services. To get your creative wheels turning, here are a few more ideas:
- Build two-way integrations
Previously, you could only set up your monitoring system to push events to PagerDuty, which would then notify users. Now, with webhooks, you can set up your monitoring system to find out when incidents change state in PagerDuty. Someone acknowledged or resolved an incident in PagerDuty? The monitoring system can automatically update its own alert to match what’s in PagerDuty.
Manage a team? Want to receive an e-mail whenever a new incident is triggered? Before webhooks, that was pretty hard to do if you weren’t the person on-call. With webhooks, it’s easy!
- Automate reminders to send notes on incident resolutions
Learn from your resolutions and send reminders to your on-call person to write a note when an incident is resolved. With webhooks, you can find out when an incident is resolved, and then check to make sure there are notes attached to the incident.
Try Webhooks Yourself
Existing PagerDuty customer accounts already have webhooks enabled, so you can get started today!
Review PagerDuty’s Webhooks API documentation.
Find out about our most popular uses for PagerDuty webhooks here.
Read the HipChat PagerDuty integration guide, which uses webhooks.
For an example implementation of how to send out emails for incident state change notifications, read this Knowledge Base article
New to PagerDuty? Learn why thousands use PagerDuty to receive critical IT alerts.
If you have questions on how to get started, contact firstname.lastname@example.org.