> but I think it's an API limitation Author here - I believe that's the case. There isn't a way to specific start & end time: https://w3c.github.io/server-timi

> but I think it's an API limitation Author here - I believe that's the case. There isn't a way to specific start & end time: https://w3c.github.io/server-timing/#dom-performanceservertiming https://w3c.github.io/server-timing/#dom-performanceserverti... That said, the spec also mentions: > To minimize the HTTP overhead the provided names and descriptions should be kept as short as possible - e.g. use abbreviations and omit optional values where possible. I could see significant issues if we tried to send data in timeline fashion (such as creating a metric for each database record call in an N+1 scenario). One idea: pass down an URI (ie - https://scoutapp.com/r/ID https://scoutapp.com/r/ID) that when clicked, provides full trace information.