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.
Benefits:
- 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,”
The Latest
Broad proliferation of cloud infrastructure combined with continued support for remote workers is driving increased complexity and visibility challenges for network operations teams, according to new research conducted by Dimensional Research and sponsored by Broadcom ...
New research from ServiceNow and ThoughtLab reveals that less than 30% of banks feel their transformation efforts are meeting evolving customer digital needs. Additionally, 52% say they must revamp their strategy to counter competition from outside the sector. Adapting to these challenges isn't just about staying competitive — it's about staying in business ...
Leaders in the financial services sector are bullish on AI, with 95% of business and IT decision makers saying that AI is a top C-Suite priority, and 96% of respondents believing it provides their business a competitive advantage, according to Riverbed's Global AI and Digital Experience Survey ...
SLOs have long been a staple for DevOps teams to monitor the health of their applications and infrastructure ... Now, as digital trends have shifted, more and more teams are looking to adapt this model for the mobile environment. This, however, is not without its challenges ...
Modernizing IT infrastructure has become essential for organizations striving to remain competitive. This modernization extends beyond merely upgrading hardware or software; it involves strategically leveraging new technologies like AI and cloud computing to enhance operational efficiency, increase data accessibility, and improve the end-user experience ...
AI sure grew fast in popularity, but are AI apps any good? ... If companies are going to keep integrating AI applications into their tech stack at the rate they are, then they need to be aware of AI's limitations. More importantly, they need to evolve their testing regiment ...
If you were lucky, you found out about the massive CrowdStrike/Microsoft outage last July by reading about it over coffee. Those less fortunate were awoken hours earlier by frantic calls from work ... Whether you were directly affected or not, there's an important lesson: all organizations should be conducting in-depth reviews of testing and change management ...
In MEAN TIME TO INSIGHT Episode 11, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses Secure Access Service Edge (SASE) ...
On average, only 48% of digital initiatives enterprise-wide meet or exceed their business outcome targets according to Gartner's annual global survey of CIOs and technology executives ...
Artificial intelligence (AI) is rapidly reshaping industries around the world. From optimizing business processes to unlocking new levels of innovation, AI is a critical driver of success for modern enterprises. As a result, business leaders — from DevOps engineers to CTOs — are under pressure to incorporate AI into their workflows to stay competitive. But the question isn't whether AI should be adopted — it's how ...