This spring I had the pleasure of setting up Opsgenie for internal use here at Isos. For the unfamiliar, Opsgenie is an alert management system that provides the means for an organization to address notifications generated by tools they already have in place from a centralized platform. For example, if your monitoring system detects a service outage, it can notify Opsgenie and then Opsgenie can notify the team responsible for addressing the matter. Now you may think, “that’s all well and good, but what if the tools I use aren’t supported?” That is an appropriate concern, but Opsgenie boasts integration support for over 200 different tools. And if you still can’t find what you’re looking for, API-based and email-based integrations are also possible.

Going back to the example, my first objective was to tie in our system monitoring tool. I was impressed with how easy it was to configure the integration to open and close alerts. The ability to establish multiple rules for alert creation allowed me to specify which system was impacted and forward the information to Statuspage using another integration. Taking things one step further, pushing notifications to Slack was just as convenient.

To be fair, the praise I offer here is in hindsight. While getting the essentials in place is fairly simple process, going through it the first time can be a bit daunting. The amount of flexibility offered by Opsgenie can be a bit overwhelming initially. I couldn’t help but feel like I needed to address every aspect of the tool in order to get the functionality I needed. After spending some time digging through the documentation though, I was able to identify the features that could be safely ignored while still meeting our basic requirements. To say the least, it made things considerably easier. When it came time to configure integrations for Jira Service Desk, I felt quite comfortable with the overall process. The initial hesitation I experienced had faded quickly.