New Relic : Monitor Rails 7 applications with New Relic One

Make sure to commit both the new YAML and script files to GitHub.

After committing both files to your main branch on GitHub, it's time to create the blueprint on Render.

Navigate in your browser to https://dashboard.render.com/blueprints and select the New Blueprint Instance button. This opens a page asking you to connect your GitHub account to Render and choose the repository of your Rails app. Render will find the file in the root directory and run the instructions in it.

The process for deployment will typically take 2-3 minutes. As soon as it is done, you can visit the URL provided by Render and see your site live on the web!

At this point, you are ready to start analyzing your observability data on New Relic One. The more you and others interact with the site, the more data will be generated in your New Relic One dashboard.

To demonstrate the potential for New Relic observability in your Rails app, let's intentionally cause an error and see how you can use New Relic One to quickly diagnose it. You'll see how to find the error's cause so you can remedy it.

1. Open up the codebase for your application again in your code editor and you'll add the following link in your right under the Get Started link:

2. Then, open up the controller file in and add one more method for the path:

3. Add the route to the file:

4. Save the changes you just made and push them up to your main branch on GitHub. Render will automatically deploy them to your live app in production from that branch.

5. Now, when you navigate to your website, you'll see a bright red Make an Error button. Select it and you'll be greeted with the familiar Rails error page in production!