xMatters announced new feature advancements designed to facilitate a data-driven DevOps approach to incident resolution.
DevOps, SRE and operations teams can now easily create collaboration channels directly from the xMatters Incident Console, using Slack, Microsoft Teams and Zoom. New pre-built automation steps further streamline the incident resolution process so managers can quickly add notes and assign severity or priority levels to an incident. Because visibility into incident response processes is a key aspect of continuous improvement, xMatters also added the ability to monitor incident volume and severity over different time periods, and enhanced its Post-Incident Report with export capabilities to share insights with cross-functional stakeholders and guide blameless postmortems for continuous improvement.
“Competitive companies don’t want to simply reduce incidents and keep their services running, they want to do so while simultaneously releasing exciting products that customers will love. Traditionally, this has been a hard balance to strike—the faster and more innovative teams try to be, the more likely they are to break existing services or overlook factors that impact the customer experience in production,” said Doug Peete,CPO at xMatters. “Without the proper tools to support their desired velocity, development and operations teams are hamstrung dealing with technical issues that divert time and resources from core product initiatives...”
The latest updates to the xMatters platform facilitate seamless collaboration for ongoing incidents, drive continuous improvement and automate processes to power an adaptive approach to incident resolution:
- Facilitate seamless collaboration for ongoing incidents. Service teams can add collaboration channels like Slack, Microsoft Teams and Zoom conferences to an existing incident directly from the Incident Console. When a Slack or Teams channel is added, the specified name and description, plus a link to the channel will be visible to everyone working on the incident. These channels can be used to share up-to-date incident details for closer collaboration to resolve issues quickly and minimize the severity of the impact. This is also an easy way for incident resolvers to bring their favorite tools into the incident resolution process.
- Drive continuous improvement. To improve the incident response process, a new “Incidents by Severity” widget can be added to the xMatters dashboard to monitor trends in the volume and severity of incidents over different periods—such as over the past 24 hours, the past 90 days or at specific points in time. Managers can also drill through to the Incidents view to explore a graph’s underlying data in more detail. Additionally, new export options for post-incident reporting enable technical teams to share postmortem insights more broadly across the organization.
- React quickly to time-sensitive incidents. When accessing xMatters on the web and on mobile, new functionality in the messaging user interface displays a full-screen list view to guide users to easily access their workflows, forms and scenarios. Incident commanders can find specific messages with the new search bar and ‘star’ frequently accessed forms and scenarios for quick-access to a curated list. Mobile users can also search forms and scenarios, and sort them alphabetically (ascending or descending).
Technology teams can take advantage of these new features to foster dynamic collaboration and automate complex workflows across disparate systems in order to deliver service resilience and drive continuous improvement.
The Latest
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...
When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...
Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...
Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...
As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...
For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...
I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...
Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...
80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...