How to aggregate logs for full-stack visibility?

Full stack visibility ~ defined as the possibility to have a timely(time-series) birds eye view of logs from Clients(Web/Mobile/SDKS) to Middleware to Databases. Logs~: pre-defined trackable events that can be tied to metrics measuring overall software health.

In this article we will talk about:

Even though this blogpost was designed to offer complementary materials to those who bought my Testing nodejs Applications book, the content can help any software developer to tuneup working environment. You use this link to buy the book. Testing nodejs Applications Book Cover

Logging tools

Distributed logs

Analyzing logs can be a daunting task in nodejs environment. Some strategies to detect and correct issues found via logs can be found in the following articles.

This article is unfinished business and will be adding more content as I experience logging problems, or find some interesting use cases in the SRE community.

Conclusion

In this article, we revisited how to aggregate nodejs logs for full-stack visibility, with aim at detecting hidden anomalies. We used the term full-stack to refer to adjacent applications such as middleware, databases alongside client applications such as SDKs, widgets, mobile and webapps. There are additional complimentary materials in the “Testing nodejs applications” book.

References