New Relic CodeStream connects observability directly to developer workflows in the IDE
Yesterday, New Relic brought observability directly into developer workflows with the acquisition of CodeStream, a collaboration tool that is found in popular integrated development environments (IDEs) and also integrates with a range of applications. ‘other tools, from GitHub to Jira and Slack. A new version of CodeStream that integrates with the New Relic One observability platform is able to bring up application telemetry data directly in the IDE to the relevant point in the code, so developers can instantly get up to speed. at work to solve problems. We spoke to Peter Pezaris, CEO and Founder of CodeStream, and Buddy Brewer, GVP and GM, New Relic, to learn more about the news.
The company believes the new product, along with a new pricing tier, will broaden New Relic’s appeal among developers whose primary role is coding, rather than traditional users of monitoring and observability tools. that focus on operational availability and reliability. Customers will also gain additional value from their investment in collecting and analyzing telemetry data, as Brewer explains:
Especially with the move to the cloud and the breaking down of monoliths into software containerization, there is so much telemetry that it’s a massive investment companies are making. The value of this investment can go far beyond just using this data when the software is on fire …
By bringing this telemetry data into the IDE – I think there are like 14 IDEs that are supported by CodeStream – you can embed this data into your IDE. This allows these developers to access this data when they plan and create software, not just when they run it. We believe this will help them derive much more value from the telemetry investment and also help them create better software.
From error alert to IDE in one click
The integration with New Relic Errors Inbox is one of the most compelling examples of how the newly integrated product blurs the line between building code and its execution in production. This newly introduced and already popular feature provides a single place to view and process errors from anywhere in the application stack, with the ability to see details in the stack trace. But as Pezaris points out, for all his convenience, what do you do then? There is a button to copy the stack trace to a clipboard, but it’s up to you then to determine where to go next. Whereas with the integration with CodeStream, all of these following steps are automatically performed for you. He explains:
You will now be able to click on this stack trace and open it directly in your IDE. We will check you at the right repo. We are going to open the SHA build that was used to build this production artifact. And now that stack trace becomes clickable. So you can click through all the stack frames, go straight to the parts of the code where the problem occurred.
Because CodeStream is good at collaboration, every time you do this we’ll tell you who wrote that code. You can easily engage them in the conversation, divide the problem between production and non-production engineers, and find the root cause of the problem faster. We will also keep track of who was affected which errors. So now every time you open your IDE, you see all the errors assigned to you, so that you can investigate and fix those issues.
Another feature uses integration with Pixie, the technology New Relic acquired last year, which automatically collects telemetry data from deep application code running in Kubernetes clusters. With dynamic logging, a developer who wants to instrument a particular function in their source code to see how it performs in production, can call Pixie directly from their code editor to insert a probe and immediately begin logging. Pézaris explains:
You can right click on it and say “Start instrumenting this thing”. And then you will have real-time feedback in your editor, without having to deploy. You don’t have to validate the code, you don’t have to change the code, you don’t have to push the code. Immediately, you will begin to reconnect for each call to this feature.
As part of the announcement, New Relic highlighted its partnership with Microsoft around CodeStream, which works with IDE VS Code and Visual Studio, and also integrates with GitHub and Teams. Commenting in a joint press release, Scott Guthrie, Executive Vice President, Cloud + AI, Microsoft, welcomed the news of the acquisition, saying:
Closer collaboration between development projects and improved connections between existing applications are just some of the benefits New Relic CodeStream will bring to the developer community.
To help encourage adoption, there will be a new Core user pricing option for New Relic One, starting at $ 49 per user per month, plus usage fees based on the volume of telemetry data. Developers can create a free account for a preview period ending in January, after which some features will require a paid license.
Joining forces with CodeStream – which is effectively an interruption to coders, but with a lot of the integration chops of a built-in Slack as well – is a huge step forward for New Relic in furthering its mission of software-based software. data, which was a big topic at his FutureStack conference earlier this year. This helps come full circle by ensuring that the people who create the software have as much access to the telemetry about how it works in production as the people responsible for running it. It can only improve the quality and performance.
It is also an excellent illustration of why the collaboration inside applications where people spend a large part of their working day is just as important and valuable as collaboration about in apps like Teams and Slack – and highlights the value of onboarding that automates futzing, wasting people time, moving information from one place to another and putting it in the right place. context and then get started. When I write about Frictionless Enterprise, this is exactly the sort of thing I am talking about.