[Feature Request] Introduce the unique trace id to debug easily

### Motivation
It's hard to analyze which process cost the most time of one remote request in current codebase, due to lacking corresponding trace id in client and server side.

### Plan
Maybe we could introduce the unique trace id which is generated on time/client-machine-id in one remote request, and then record it in client's log. And when requesting remote server, we should populate this to server and make it recorded in server's log.

The issue names no files or tests; begin by locating the client and server entry points for a remote request and their logging paths. Trace how request metadata crosses that boundary, then define the trace ID generation and propagation scope. Done means one request can be correlated through the client and server logs using the same unique ID.

Written by the indexing model from the issue text.