xMatters announced platform advancements that are powering a new method for incident response and management––adaptive incident management.
New adaptive incident management features available today in the xMatters platform include:
- an Incident Console to better triage, visualize and guide the entire incident lifecycle
- automation for incident response and improved collaboration
- the ability to quickly and easily scale the response to the incident as it evolves
- comprehensive incident analytics to drive continuous improvement.
Whether it’s a small technical issue affecting one software service or an enterprise-wide outage cascading across business services, these new capabilities empower technology teams to work within their preferred tools and deliver digital service resilience––the ability to recover quickly, adapt and learn from incidents such as performance issues and outages.
“Technology professionals today are expected to not only create and innovate digital services, but are also under extreme pressure to maintain service levels and uptime with well-tuned incident response and management. During a time when there is a critical reliance on digital services, traditional incident management processes and applications are not sufficient,” said Troy McAlpin, CEO at xMatters. “By adding adaptive incident management capabilities to our platform, we are automating repetitive, mundane work, and transforming how services are kept available for customers to enjoy.”
Technology organizations can minimize––and even avoid––the business impact from incidents by automating incident response and management with xMatters. New xMatters adaptive incident management features, which are accessed through the new Incident Console, and powered by xMatters’ visual workflow builder Flow Designer, solve the challenges of responding to service interruptions across different teams, cultures and systems.
New capabilities available from within the xMatters platform empower technology teams to:
■ Bridge incident management processes, data insights and disparate tools for cohesive and collaborative enterprise response automation:
- Incidents Views help teams find, evaluate and collaborate on incidents as they evolve, keeping track of incident statuses and allowing for efficient use of resources.
- The Incident Console shows a live view of an incident as it evolves through its lifecycle, including incident status and severity, notified and engaged responders, associated collaboration channels and roles.
- Incident Status Reports include timelines, key metrics and associated collaboration channels to support stakeholder communications and postmortem activity.
■ Combine the power of human problem-solving and process automation for faster, more targeted resolution:
- Critical incident metrics are automatically collected from integrated systems then delivered with the initial notification, reducing manual look-ups and improving resolution time.
- Flow Designer automations keep related systems up-to-date, including issue tracking systems, service desks, status pages and other supporting systems.
■ Accelerate continuous improvement and service resilience through comprehensive incident data and advanced analytics:
- The Incident Timeline provides a detailed record of what happened and when.
- Resolved incident metrics give teams a way to compare information from one incident to the next so teams can build metrics based on consistent data and improve digital service resilience over time.
- Performance Analytics helps evaluate the cost and impact of incidents in an organization’s environment and identify areas of improvement.
These xMatters platform advances are powered by the technical underpinnings of the xMatters platform. This includes Flow Designer for orchestration and automation, integrations that can be used to build powerful toolchains, sophisticated on-call management, event flood control, and configurable dashboards for visual incident and group performance tracking. With xMatters Flow Designer, teams with roles ranging from software developers to IT generalists can create incident management workflows without a single line of code. This drag and drop experience has revolutionized the way IT, DevOps, Operations and SRE teams integrate, synchronize and automate incident management toolchains.
“Investing in avoiding known types of incidents is an important part of digital service delivery. However, innovative companies know that eliminating incidents completely is impossible in practice. Our mission, then, is to help customers resolve incidents as quickly as possible and minimize their impact,” said Tobias Dunn-Krahn, CTO at xMatters. “We’ve developed the technology needed to make this happen. Now, customers can access powerful yet flexible applications that build upon our renowned approach to workflow automation, range of integration capabilities and sophisticated enterprise grade features to deliver digital service resilience and continuous improvement. By applying an adaptive incident management methodology, teams can automate incident resolution tasks and maximize the time spent making customers happy.”
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 ...