Kentik announced an expanded partnership with New Relic.
The initiative deepens New Relic’s full-stack observability into the network layer, giving IT operations, SREs and development teams shared context to resolve issues quickly.
“When software fails, it happens in unexpected ways and at the worst time. Development teams can be quick to suspect a network failure, but they usually don’t have the tools or context to diagnose if the network really is the problem,” said Buddy Brewer, Group VP of Strategic Partnerships for New Relic. “With Kentik, we’re closing the visibility gap by bringing network context directly into the New Relic One platform, giving teams a fast and easy way to determine whether the network is the root cause of an issue.”
In December, Kentik and New Relic formed an initial partnership to provide joint-customers with a way to combine DevOps and NetOps observability using the Kentik Firehose, a service to export enriched traffic data from the Kentik Network Observability Cloud. With this partnership expansion, New Relic users can add out-of-the-box network context via custom visualizations from Kentik to application and infrastructure data directly within New Relic One.
“The lack of integrated application and network observability continues to claim a high toll in latency and downtime. Even the companies with well-budgeted IT teams are exposed to user experience impact when they do not have a unified view of their environments,” said Avi Freedman, Co-founder and CEO of Kentik. “Through our expanded partnership with New Relic, we’re helping network and development teams quickly identify and troubleshoot application performance issues correlated with network traffic, performance and health data, and ultimately make services more reliable.”
With the new integrations, customers will have access to modern cloud telemetry like VPC Flow Logs from Amazon, Microsoft, Google and IBM; internet and WAN measurements via synthetic network transactions; and traditional network element telemetry like SNMP, NetFlow, sFlow and IPFIX.
The Latest
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 ...
40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...
Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...
Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...
Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...
Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...
Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...