Blameless Integrates Opsgenie
February 02, 2023
Share this

Blameless announces the integration of Opsgenie, Atlassian’s alerting solution for incident responders.

Integrating with Opsgenie allows Blameless users to quickly and intelligently assemble the right team members at the outset of an incident by accessing data from Opsgenie’s service catalog.

Blameless users can select and notify responders based on both specific service ownership and team responsibility on-call.

Making the integration between Opsgenie and Blameless both service-aware and team-aware helps users adapt to situations where the scope of responsibilities per team is unclear or changes. It also allows users to more quickly identify the origin of a potential incident by assembling based on the service affected. This has the benefit of bringing engineers with service-specific expertise directly to the incident rather than relying on first determining which broader team owns that part of the infrastructure.

Opsgenie is connected to Blameless via the service catalog and alerting functions, both of which are embedded within the Blameless Slackbot interface. Blameless users responding to or managing an incident, can escalate to any teams defined in Opsgenie. Users can do this directly by team name if known or by selecting the related services and, next the teams responsible for that service. When a service is selected via the bot command via Slack, those team members are automatically notified. Like every other action taken within Blameless, the service catalog and alerting data generated throughout the lifecycle of an incident is automatically captured and stored on the Blameless Incident Timeline.


- Simplicity and speed. Users of both Opsgenie and Blameless now quickly and intuitively assemble the right, relevant people, which is a critical first step during an incident. With this powerful integration, Blameless has made it simple to identify appropriate service owners as well as follow the defined escalation protocol. Blameless can also display the actual user name of each responder notified per the escalation policy to help with team member identification and downstream reporting.

- Alert Automation. When using Blameless via Slack or Microsoft Teams, Opsgenie alerts are automated when the incident channel is created, and the pre-selection of relevant services takes place. Alerts can also be manually triggered using commands from the Blameless chatbot for those who prefer to trigger alerts from within Slack or Teams.

- Track Every Event for Learning. All triggered alerts can now be tracked as an event in the Blameless Incident Timeline, with the name of the user who started the alert, the name and link to the service, and the team which has been notified. This is ultimately included in the retrospective report and also downstream analytics, so users know exactly what happened and when.

"Our customers and the market have been asking for this level of integration with Opsgenie, which is a popular and growing solution for responders...This depth of integration makes it much easier for teams to codify their incident playbook and streamline the entire end-to-end workflow,” said Jim Gochee, CEO of Blameless. “Blameless integrations are a key engineering tenet for our product,”

Share this

The Latest

March 23, 2023

APMdigest and leading IT research firm Enterprise Management Associates (EMA) are partnering to bring you the EMA-APMdigest Podcast, a new podcast focused on the latest technologies impacting IT Operations. In Episode 2 - Part 1 Pete Goldin, Editor and Publisher of APMdigest, discusses Network Observability with Shamus McGillicuddy, Vice President of Research, Network Infrastructure and Operations, at EMA ...

March 22, 2023

CIOs have stepped into the role of digital leader and strategic advisor, according to the 2023 Global CIO Survey from Logicalis ...

March 21, 2023

Synthetic monitoring is crucial to deploy code with confidence as catching bugs with E2E tests on staging is becoming increasingly difficult. It isn't trivial to provide realistic staging systems, especially because today's apps are intertwined with many third-party APIs ...

March 20, 2023

Recent EMA field research found that ServiceOps is either an active effort or a formal initiative in 78% of the organizations represented by a global panel of 400+ IT leaders. It is relatively early but gaining momentum across industries and organizations of all sizes globally ...

March 16, 2023

Managing availability and performance within SAP environments has long been a challenge for IT teams. But as IT environments grow more complex and dynamic, and the speed of innovation in almost every industry continues to accelerate, this situation is becoming a whole lot worse ...

March 15, 2023

Harnessing the power of network-derived intelligence and insights is critical in detecting today's increasingly sophisticated security threats across hybrid and multi-cloud infrastructure, according to a new research study from IDC ...

March 14, 2023

Recent research suggests that many organizations are paying for more software than they need. If organizations are looking to reduce IT spend, leaders should take a closer look at the tools being offered to employees, as not all software is essential ...

March 13, 2023

Organizations are challenged by tool sprawl and data source overload, according to the Grafana Labs Observability Survey 2023, with 52% of respondents reporting that their companies use 6 or more observability tools, including 11% that use 16 or more.

March 09, 2023

An array of tools purport to maintain availability — the trick is sorting through the noise to find the right one. Let us discuss why availability is so important and then unpack the ROI of deploying Artificial Intelligence for IT Operations (AIOps) during an economic downturn ...

March 08, 2023

Development teams so often find themselves rushing to get a release out on time. When it comes time for testing, the software works fine in the lab. But, when it's released, customers report a bunch of bugs. How does this happen? Why weren't the flaws found in QA? ...