I noticed that both the timeline and requests tab display middleware with names that might not always be immediately identifiable or distinguishable. For example, Morgan shows up as "logger", which is technically accurate, but maybe not as specific as it could be (why not call it "Morgan" or "Morgan logger"?). Furthermore, it may be interesting to display some of the config of the Morgan middleware (e.g. format?), since that might explain/impact the cost of the logical event.
Additionally, if an app is configured to parse JSON via multiple MIME types, the timeline/requests will simply show them all as "jsonParser". There are probably other scenarios beyond these two, so I'm just using them to illustrate the general desire to have additional event metadata be displayed where relevant, so that the semantics of the requests/timeline tab is as high as possible.
I noticed that both the timeline and requests tab display middleware with names that might not always be immediately identifiable or distinguishable. For example, Morgan shows up as "logger", which is technically accurate, but maybe not as specific as it could be (why not call it "Morgan" or "Morgan logger"?). Furthermore, it may be interesting to display some of the config of the Morgan middleware (e.g. format?), since that might explain/impact the cost of the logical event.
Additionally, if an app is configured to parse JSON via multiple MIME types, the timeline/requests will simply show them all as "jsonParser". There are probably other scenarios beyond these two, so I'm just using them to illustrate the general desire to have additional event metadata be displayed where relevant, so that the semantics of the requests/timeline tab is as high as possible.