As a new director joining Bitly , Kyle needed to find the best solution, fast and present the business case to the CTO. With a lengthy background in ITOps, DevOps, Networking and Security he had the chance to try various solutions in previous jobs. “I had familiarity with PagerDuty, I knew the pain of that really. Opsgenie stood out right away. It was modern, the mobile app seemed easy to use, the API calls were good, and the Slack integration was built in.” During the Proof of Concept, Kyle and his team quickly determined that Opsgenie was the way to go, he even put a Junior Engineer who had only been working for 6 months in charge of rolling over to Opsgenie because he felt it would be that easy.
“When you wanted to take on-call, you had to take your laptop to make an API call to AWS and let it know so that it would text the right number, people would always forget and then you’re paging someone in the movie theatre who isn’t even on-call.” said Kyle of the system in place prior to Opsgenie.
“For the team, it was a no-brainer, giving them Opsgenie was like giving saltines to starving people in the desert, and then the saltines turned into filet mignon.”
As time went on, the on-call tem was growing to include more members of the backend and front end teams, as well as other service owners. The on-call experience improved greatly, and the team no longer had to make manual API calls to AWS and various tools so it knew who to page.
“Someone who spent a lot of years on-call definitely built this product, it’s clear to us each day we use it. We haven’t had any outages in the 2 years we’ve been using Opsgenie.”