Full Stack JavaScript Strategies

Chapter 12. Monitoring, Logging, and Incident Handling

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 12th chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the author at [e-mail].

Now that you have built your backend, it’s time to take a deeper look into your monitoring and logging tools. This is where you’ll get the info you need to figure out what’s happening in your app across different environments and decide how to handle it.

You’ve set up logging throughout your code, so you already understand what to log and have plenty to test and check for. The goal now is to get meaningful insights from what you’re already logging, such as figuring out when incidents are occurring and resolving them.

In this chapter, I’ll go over:

• Multiple uses for logs and monitoring data

• How different tools work

• Incident plans for production based on logs and monitoring

Monitoring and logging aren’t there just for when something goes wrong. They tell you the story about what is going on across your full stack app and even on the infrastructure level. If you know exactly what happens with the app and when it happens, then you ...