From the course: Node.js: Debugging and Performance Tuning
Unlock the full course today
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Challenge: Cross-application request IDs
From the course: Node.js: Debugging and Performance Tuning
Challenge: Cross-application request IDs
- [Instructor] Welcome to the chapter three challenge, where we'll apply the cross-application transaction tracing techniques we've been discussing the entire rock paper scissors application. This challenge is optional, but it's a great way to reinforce what we've done in this chapter. There are four overarching objectives for this challenge. We updated both web and players with express-request-id and the request logger, but the game service still needs to be updated. We're logging the HTTP port when listening on web, but not on players and games. We added support for request ID in the HTTP clients. Let's require it to ensure everything is logged correctly. Since it will be required, we'll need to update all of the usages of the games and players clients to send a request ID. Let's break each objective down a little bit more. There are two steps for express-request-id and requestLogger in games, and we've already done it elsewhere. We just need to add and use express-request-id in the…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
-
(Locked)
Why and what should I log?6m 26s
-
Problems with Node.js console6m 1s
-
(Locked)
Implementing Express error pages6m 48s
-
(Locked)
Choosing a logging library5m 40s
-
(Locked)
Adding Winston for Node logging4m 41s
-
(Locked)
Request logging with Morgan6m 39s
-
(Locked)
Correlating requests in logs6m 18s
-
(Locked)
Cross-application request correlation5m 32s
-
(Locked)
Challenge: Cross-application request IDs2m 14s
-
(Locked)
Solution: Cross-application request IDs9m 30s
-
(Locked)
-
-
-