The Business Challenge:
While initially satisfied with PagerDuty as their incident management tool, the company wanted a solution that provided timely notifications and kept incident responders and stakeholders informed during these incidents. PagerDuty’s cost model charged for both responders and stakeholders, along with additional fees for bolt-on capabilities, led the company to consider a change. Moreover, limitations in integration with the Atlassian ecosystem, such as the number of Jira issues per incident and field limitations, were having an impact on incident remediation speed.
Past Solution
The company had initially chosen PagerDuty, which served around 800 cross-functional engineers. They utilized various capabilities of PagerDuty, including monitoring, war rooms, notifications, incident post-mortems, and on-call processes. Their PagerDuty instance had multiple integrations, such as AWS CloudWatch, Data Dog, database CPU spike alarms, Linux patching, ServiceNow, Splunk, and bespoke monitoring tools. However, escalating costs and limitations within the Atlassian ecosystem prompted the exploration of alternatives.
During a Jira test-case management initiative with Trundl, the company learned about Opsgenie as a potential solution to address their limitations in incident remediation. Opsgenie offers improved integration into their existing operational model, allowing for seamless collaboration with Jira and Confluence. This solution opened doors for a potential shift in incident management tools and paved the way for finding a more cost-effective and integrated solution that aligns with the company’s needs.