nodejs/nodebestpractices
1
0
Fork 0
mirror of https://github.com/goldbergyoni/nodebestpractices.git synced 2025-10-31 17:47:26 +08:00
Code Issues Packages Projects Releases Wiki Activity

correlation id added

Browse Source
This commit is contained in:
Yedidya Schwartz
2021-01-27 20:29:54 +02:00
committed by GitHub
parent 4ca0c3a8c0
commit f44e477c15
1 changed files with 11 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -49,7 +49,7 @@ Read in a different language: [![CN](/assets/flags/CN.png)**CN**](/README.chines
## Table of Contents
1. [Project Structure Practices (5)](#1-project-structure-practices)
2. [Error Handling Practices (11) ](#2-error-handling-practices)
2. [Error Handling Practices (13) ](#2-error-handling-practices)
3. [Code Style Practices (12) ](#3-code-style-practices)
4. [Testing And Overall Quality Practices (13) ](#4-testing-and-overall-quality-practices)
5. [Going To Production Practices (19) ](#5-going-to-production-practices)
@ -237,6 +237,16 @@ especially if the cause of the abnormal behavior is inside of the missing functi
🔗 [**Read More: returning promises**](/sections/errorhandling/returningpromises.md)
<br/><br/>
## ![✔] 2.13 Give you error's log a context by adding a correlation ID
**TL;DR:** Correlation ID lets you linking log records, even if they belong to different services. It can save your day when a process that including 20 different microservices throws an exception in one of them, and you have no idea where did the problem started across the flow.
**Otherwise:** Once an error will occure, you might read the logs without any context of understanding what caused the unexpected input and which logs of other services are related to your investigated transaction.
🔗 [**Read More: Correlation ID: help your logs tell you a story and give you error a context**](/sections/errorhandling/correlationid.md)
<br/><br/><br/>
<p align="right"><a href="#table-of-contents">⬆ Return to top</a></p>