UID in Logs for each request made to the server

Suppose there are concurrent users using the server at the same time.
One of the API calls fails. In the current logging system made with logrus identifying the exact issue will be tiresome.

Proposed solution:

• Setup a middleware in the router file. Each API call will be assigned a Unique ID. This id will be passed around throughout the code with the help of context.
• We can also set up a middleware that tells the exact file and line at which the code failed in the logs.
• Maybe convert/ store the logs in JSON to make it easier to plug in ELK or some monitoring tool in the future.

I have a clue to work on the proposed solution in Echo framework. I will have to learn and implement it in Mux.
If this looks like a genuine feature do let me know, I am available for the task.
cc: @gmajan @HarrisLawYF

Start by locating the router file and the existing logrus setup, then review how request context is passed through the server. Clarify whether the required scope is request IDs, failure locations, structured JSON logs, or some combination. Done should be defined by maintainers with tests or a concrete logging example, since the issue currently proposes several optional directions.