Track chain of requests
Just like users go from one page to another on a website, the users' clients send request after request to perform different tasks. So, it is a good idea to know which requests the user sent before this one because in some cases, previous requests can have an impact othes. So, to track this, you can simply pass an identifier for the first time and should expect the same among all other requests.
Another advantage is that it will not only show you flow, but it will also be easier for you if you are asked to explain why some specific problem occurred. If that identifier is at the client side, the concerned person can give you that identifier for reference with their error report so that you can can understand which request ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access