In this quest, you’ll learn how to set up the New Relic Instant Observability Dashboard for your backend application so you can explore your data, understand context, and resolve problems faster.

By now you’re probably comfortable with our production systems and have more visibility into what’s going on with them. Now we have some clarity when problems arise, but we also want to know what’s going on in our system and what went wrong (or just see what’s going on in the system). In this quest, you will add a log monitoring tool to improve visibility into what is happening in the application’s production environment.

If a system falls in the forest, does it make a sound? Yes, yes it does, and so do engineers when their systems fail—and these sounds are strikingly similar! The one thing that’s even worse than dealing with a failing system is not knowing that your system is failing. That’s why in this quest, you’ll add monitoring capabilities to your project by setting up observability tools and alerts.

Production systems are like a hike in a lush forest: beautiful, yet scary and full of encounters with nasty bugs. But unlike the woods, here they aren’t a part of an ecosystem, and can be squashed without feeling guilty. Which is exactly what we’ll be doing during this quest! We’ll go through the entire workflow of an urgent production bug mitigation: detection, reproduction, finding the root cause and uploading a fix.