Aye, passing the on-call baton to the next soul is not a challenge but a duty.

PagerDuty is used by the Cloud Operations team for data operations, infrastructure operations, devops, engineering, and executive crisis management. It addresses the ability to raise awareness from the simplest of issues that exist in production to critical incidents requiring marshaling everyone to virtual war rooms. When outages or service impacts occur the ability to reach out without having to find contact information, calling ten to fifty people is key. Time wasted is time lost in resolving issues.

I wish to say zero downtime has never occurred, but a delay in sent notifications has occurred in their growth. Being aware of these issues was a challenge but has gotten better in the past 24 months.

Our integrations into PagerDuty is the key to its success. Currently, we utilize SMTP, Splunk, Slack, LogicMonitor, Homegrown API, Bitbucket, Git, JIRA, Jenkins and, many more to keep aware of the success and failure states.

Customer data feeds are paramount in the timely flow of transactions in our platform. When a feed is no longer accepting messages the cascading impact could prevent a customer from getting their goods to port, or even worse, miss their container slot. We utilize the automated incident response to layer coverage on our platform to exceed our SLAs and keep our customers tasks flowing smoothly.

This is a new feature for us and we are excited at the prospects.