CodeStream is now part of New Relic. Joining together to bring observability into your IDE.
Learn More
Michael GershFast error resolution is an important point of collaboration between development and operations teams. CodeStream 12.0 makes observability actionable for developers by bringing New Relic One into the IDE. Operations and dev teams can identify application owners quickly, easily work together to resolve critical production errors, and improve software performance with unprecedented ease and efficiency.
To use the New Relic One integration you’ll need to be a New Relic One user and configure your user API key in CodeStream. If you don’t already have a user API key you can easily create one, and if you don’t already have a New Relic account, you can sign up and get your user API key at the same time.
After you connect to your New Relic account, if CodeStream detects that you’ve got a .NET Core, Java or Node.js project you’ll be given the option to instrument the project by going through a setup wizard right in your IDE.
Instead of manually opening your IDE and searching for files and relevant lines of code, click on “Open in IDE” from an error and streamline your debugging workflow. The error will be opened automatically pointing to the code associated with the first step in the stack trace.
Debug production errors faster with the ability to step through stack-traces in a source-code context.
CodeStream has been the easiest way to discuss code and now that applies to code associated with production errors. Just highlight a block of code to begin a debugging discussion with teammates. The full discussion can be attached to the lines of co
Debugging an error in CodeStream? Browsing it from New Relic One? Add comments and participate in the same discussion from either place. The discussion is kept in sync so your dev and ops teams are kept in sync.
See an error being discussed by your teammates but would like a little more information? Click on the error from CodeStream to view it in New Relic One.
See an error in CodeStream that you’d like to tackle? Or you know who should tackle it? Assign it directly from CodeStream to let everyone viewing it in New Relic One know that someone’s on it.
After fixing a problem in record time thanks to being able to navigate through stack traces and easily discussing it with your teammates, shave a few more minutes of time by updating the error’s status from your IDE.
From the Observability panel you can view all open production errors assigned to you and those related to the code in the repo you are working on.
Users with Go projects that have set up Pixie will be able to do live logging from within their IDE. Just select “Dynamic Logging Using Pixie” on the context menu of method name to configure and indicate the duration of the logging period. Once clicked, a table appears below the form where results will be displayed.
Please post any questions or general feedback to @teamcodestream on Twitter or reply to the tweet below. If encountering a bug please review our GitHub Issues and please create a new issue if we’re not aware of it. Thanks!
Please share your thoughts and feedback @teamcodestream.
New Relic CodeStream integrates all of your essential dev tools, such as GitHub, GitLab, Bitbucket, Slack, Teams, Jira, Trello and more, into VS Code, Visual Studio, and any JetBrains IDE.
During our daily stand-ups we demo features in development to allow everyone, which now includes you too, to stay in the loop and provide early feedback.