Dynatrace announced Thursday it has agreed to acquire AI observability company Arize in a $915 million cash and stock transaction.
Rick McConnell, CEO of Dynatrace, said the company expects demand for AI observability will keep growing as more AI systems move into production. He said acquiring Arize would speed up Dynatrace’s roadmap, expand its developer reach and bring Arize’s AI team into the company.
Dynatrace said the deal would combine Arize’s AI evaluation and observability software with its own platform for correlating telemetry and tracing dependencies across applications, services and infrastructure. The transaction includes about $815 million in cash and replacement equity awards for Arize employees and is expected to close later this quarter or early in Dynatrace’s fiscal third quarter.
DevOps teams are already used to piecing together telemetry across distributed systems when something breaks. AI adds another source of context to correlate when information about model and agent behavior and output quality lives in separate systems from the application and infrastructure data used to investigate failures. That can leave AI engineering, SRE and platform teams trying to reconstruct the full story across the production environment.
That is where Arize fits. Its tools track what happens during an AI or agent run, including model calls, retrieval and tool use, and use those traces to evaluate both the final output and the path the agent took to reach it. Arize co-founder Jason Lopatecki said the company collects billions of agent trajectory events, while Dynatrace tracks what the surrounding software does. Combining those views could give teams an easier trail between an agent’s actions and the transaction, service or infrastructure involved when something goes wrong.
Mitch Ashley, vice president and practice lead for software lifecycle engineering at the Futurum Group, sees that connection as the deal’s key value.
“Dynatrace is paying $915 million for the observability-native link between AI observation and agent behavior,” Ashley told DevOps.com. “An AI engineer measures output quality in one tool. Without it, the current state-of-the-art is that the on-call SRE sees a failed transaction and has no path back to the prompt.”
The issue becomes more than a debugging problem once agents start taking actions in production. Teams also need a record of what the agent did, what systems it touched and what happened afterward. When that trail is incomplete, verifying agent behavior becomes another manual task for platform and operations teams.
“Enterprises ship agents only as fast as they can prove that those agents’ behavior is accountable,” Ashley said. “Verification debt lands on platform teams as a review backlog.” Because agents often run across more than one vendor’s stack, Ashley said enterprises should make that accountability trail a contract requirement that carries across those different systems. That trail has to remain intact as agents cross vendor boundaries.
That need for continuity helps explain the fit between Arize and Dynatrace. Lopatecki said Arize contributes a deep record of agent trajectories, while Dynatrace provides the traces and logs needed to connect those actions with the environment. He sees the acquisition as a way to join those two views as agents become more embedded in production software.
“These two areas just belong together if we are going to build the future systems that continuously improve,” he said.
from DevOps.com https://ift.tt/FG3BlUb
Comments
Post a Comment