New Relic announced CodeStream code-level metrics and service-level telemetry to deliver insights into software performance all the way down to the code level, allowing developers to quickly identify issues before they hit production and accelerate engineering velocity.
By bringing telemetry data to where developers build and flow, they can access meaningful data without leaving the Integrated Development Environment (IDE), relying on operations teams, or waiting for customers to report issues. New Relic is the only observability platform to connect telemetry data directly to the relevant code inside the IDE, so developers can monitor, debug and improve their applications with ease. New Relic CodeStream supports all core languages, including: .Net, Java, PHP, Python, Ruby, Go, and Node.js.
New Relic CodeStream helps engineers by integrating observability into the full software lifecycle so that developers can optimize the performance of their applications during development.
“Observability as an engineering practice presents a future where essential workflows are fueled by data,” said Peter Pezaris, New Relic SVP of Strategy and Experience. “By bringing production telemetry data into the IDE with New Relic CodeStream, our customers are able to tighten feedback loops and produce better performing software without impacting existing workflows or requiring expensive context switches. New Relic is focusing on shifting left, and CodeStream empowers engineers to get ahead of issues before they hit production and accelerate their development cycles, saving valuable time and money.”
New Relic CodeStream powers the future state of observability for developers by bringing telemetry and tools together in the IDE, allowing for always-on visibility into all metrics, deeper analysis, faster mean time to detection (MTTD), mean time to resolution (MTTR), and shorter development cycles. Capabilities include:
- Deploy in all core languages: New Relic CodeStream now supports all core languages, including: .Net, Java, PHP, Python, Ruby, Go, and Node.js.
- Monitor code-level performance: Telemetry metrics are displayed as a line of text above each instrumented method for speedy troubleshooting.
- Access service-level performance: Golden metrics for related services are easily surfaced to identify issues faster.
- Track performance against service-level objectives: View service performance against predefined targets to ensure overall service health.
- Data-driven code-reviews: Crucial telemetry data is displayed within pull requests and feedback requests to improve code in production.
CodeStream code-level metrics and service-level telemetry are included at no additional cost to all New Relic full platform and core users.
The Latest
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.