The Ruby agent is 12 years old! What's Next?

For twelve years, the Ruby agent has been serving the Ruby community as the leading Application Performance Monitoring (APM) tool of choice. While the agent’s source code has always been publicly available, it recently joined the open source community with its new Apache 2.0 licensing terms.

The Ruby agent is not the"shiny-new-thing," but it has never stopped evolving. More than 90% of the deployments are configured with the core APM agent capabilities. But did you know the agent is sporting powerful distributed tracing, error reporting, and logging in context capabilities that can make your time to resolution stats shrink dramatically? We’ve come a long way.

So, what’s changed?

There’s lots to talk about. There are many new technologies we can instrument or improve… But what are they? Who’s using what and how?

I am opening this conversation because we are at a new juncture in the Ruby agent’s long legacy and you can be instrumental in shaping what comes next. In the full spirit of Ruby on Rails’ recent May of WTF’s, we want to hear from you about your experience, pet peeves, WTF? moments, and pain points using the Ruby agent.

Here’s your chance to add your voice without the high formality of submitting support tickets or writing up a well-researched and described problem in a Github issue. Tell us what’s on your mind.

  • What can the Ruby agent do better?
  • What blindspots does the agent have that we haven’t addressed after all the years.
  • What have you given up hope on us ever building into the agent?

The Ruby agent is now open source, which means it is now also a community effort to shape and build the future of our agent. This isn’t just a code dump. We’re consciously choosing to be full members of the open source community through contributing back to the libraries we instrument, supporting maintainers of Ruby gems that extend the Ruby agent’s capabilities, and even helping to diagnose and solve issues that stem from outside the agent proper. In short, we’re returning to our developer-first roots and we hope you’re as excited as we are about this new chapter in New Relic’s history.

Join in on the conversation

There are two ways to participate in this conversation! Start here and share your thoughts. We (the engineers/maintainers of the Ruby agent) are listening and will engage. Your fellow community members are sure to engage as well. Together, we can set a course for serving the Ruby community with the best in class observability tools and experience for the years to come.

Join us for our upcoming Nerd Hour Live Q&A: Ruby Agent.

We will review the Roadmap for the Ruby agent, our plans for OpenTelemetry support, our experience open sourcing the agent, and some of the advanced features of the agent that many are not taking advantage of today.