In a distributed environment, which is quite frequent in Meteor apps, it is difficult to track the full path of a request.
- Having correlation IDs (aka "tags") allows tracking the flow of a single request across multiple loggers
- Having session IDs (not necessarily identical to login sessions) allows relating multiple requests to a user context
In a distributed environment, which is quite frequent in Meteor apps, it is difficult to track the full path of a request.