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
The 2024 State of the Data Center Report from CoreSite shows that although C-suite confidence in the economy remains high, a VUCA (volatile, uncertain, complex, ambiguous) environment has many business leaders proceeding with caution when it comes to their IT and data ecosystems, with an emphasis on cost control and predictability, flexibility and risk management ...
In June, New Relic published the State of Observability for Energy and Utilities Report to share insights, analysis, and data on the impact of full-stack observability software in energy and utilities organizations' service capabilities. Here are eight key takeaways from the report ...
The rapid rise of generative AI (GenAI) has caught everyone's attention, leaving many to wonder if the technology's impact will live up to the immense hype. A recent survey by Alteryx provides valuable insights into the current state of GenAI adoption, revealing a shift from inflated expectations to tangible value realization across enterprises ... Here are five key takeaways that underscore GenAI's progression from hype to real-world impact ...
As software development grows more intricate, the challenge for observability engineers tasked with ensuring optimal system performance becomes more daunting. Current methodologies are struggling to keep pace, with the annual Observability Pulse surveys indicating a rise in Mean Time to Remediation (MTTR). According to this survey, only a small fraction of organizations, around 10%, achieve full observability today. Generative AI, however, promises to significantly move the needle ...
While nearly all data leaders surveyed are building generative AI applications, most don't believe their data estate is actually prepared to support them, according to the State of Reliable AI report from Monte Carlo Data ...
Enterprises are putting a lot of effort into improving the digital employee experience (DEX), which has become essential to both improving organizational performance and attracting and retaining talented workers. But to date, most efforts to deliver outstanding DEX have focused on people working with laptops, PCs, or thin clients. Employees on the frontlines, using mobile devices to handle logistics ... have been largely overlooked ...
The average customer-facing incident takes nearly three hours to resolve (175 minutes) while the estimated cost of downtime is $4,537 per minute, meaning each incident can cost nearly $794,000, according to new research from PagerDuty ...
In MEAN TIME TO INSIGHT Episode 8, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses AutoCon with the conference founders Scott Robohn and Chris Grundemann ...
Numerous vendors and service providers have recently embraced the NaaS concept, yet there is still no industry consensus on its definition or the types of networks it involves. Furthermore, providers have varied in how they define the NaaS service delivery model. I conducted research for a new report, Network as a Service: Understanding the Cloud Consumption Model in Networking, to refine the concept of NaaS and reduce buyer confusion over what it is and how it can offer value ...