slow-path-hotspot-correlation

Instruction

Some requests have been noticeably slow, and I need something tighter than "latency was up." Using roughly the last six hours of telemetry, tell me which HTTP path owns the most request logs over 1 second, about how many such slow requests it generated, and roughly what share of all >1s request logs that path represents. Then use traces for that same path to tell me whether the same latency hotspot keeps recurring across several slow examples or if the slowness is spread around. Name the service and operation that are actually eating the time, and include one trace id you really saw.