Extend observability and code discussion to your IDE with New Relic CodeStream

Until now, observability was coupled tightly to the operations function and constrained in stand-alone UIs designed for operations engineers. This makes it difficult for developers focused on writing code and delivering innovation to apply critical observations gained from production code early in their software’s development. But with our acquisition and integration of CodeStream, we took an important step to materialize our vision for observability: a world where data drives all stages of software development. Let me show you how.

With CodeStream, you can instrument your applications, collaborate with teams, and debug production issues faster and more simply—without ever having to leave your IDE.

Plan, prioritize, and begin tasks from your IDE

Whether tackling a simple bug fix or starting work on a major new feature, there are many steps and services involved that can disrupt your development flow. With New Relic CodeStream, you can do it all in one step, right from your IDE.

Through integrations with Jira, Trello, Asana, GitHub, GitLab, YouTrack, Clubhouse, and Azure DevOps, you can:

  • Browse your outstanding tasks.
  • Update your task status or create a branch.
  • Keep ticket context with pull and feedback requests.

Start and manage your pull request workflow

For most development teams, the final step before deployment is a pull request. New Relic CodeStream provides a rich pull request interface that enables developers to keep the entire pull request workflow right in the IDE:

  • Create, review, and edit pull requests inside the IDE.
  • Compare diffs side-by-side.
  • Create a pull request across forks.
  • Display pull request comments as code annotations.
  • Work with GitHub, GitLab, and Bitbucket.

Instrument from your IDE

With New Relic CodeStream, it’s never been easier to instrument your applications. All it takes is a few clicks directly from your development environment. With support for Visual Studio, Visual Studio Code, and JetBrains, the New Relic CodeStream integration is available to preview today for free in all regions outside of EMEA.

Debug production errors fast

Responding to issues and resolving errors fast is an important point of collaboration between development and operations teams. With New Relic CodeStream, operations teams can identify application owners quickly and work together to resolve critical errors. In a single click, developers can jump from New Relic Errors Inbox to their IDE and step through the stack trace for code-level debugging of high-impact errors. Additionally, developers can discover, view, and update the status of open issues all from the comfort of their favorite IDE.

See what’s next

As we continue to strengthen the connection between New Relic One and your IDE, we’ll keep delivering deep, rich experiences that make it easier for you to take action. One such experience will be Pixie Dynamic Logging. Logs are essential for debugging in production, especially given the unpredictability of production errors. But parsing through that volume of data can be inefficient.

Using New Relic CodeStream, developers with Go projects who have set up Pixie in New Relic One will be able to add production logging on the fly and surface results directly in the IDE. Accessing dynamic logs in the IDE closes the loop in the all-too-critical troubleshooting workflow and makes the logs that developers use when debugging their Go application more useful.

Next steps

If you want to evaluate New Relic CodeStream, sign up for a New Relic account today.

DISCLAIMER: Webiscope LTD hereby declare that it do not own the rights to this content. All rights belong to the owner. No Copyright Infringement Intended.

Contact Us

Webiscope is now part of Aman Group

We are happy to announce that Webiscope is now part of Aman Group. We look forward giving our customers and partners greater value with more complete solutions and outstanding service.