-
Notifications
You must be signed in to change notification settings - Fork 9
[Overview] UX/UI for when Network/Server/Client data isn't available #28
Comments
Apologies not needed! This is a perfectly valid question, and something we need to consider and make more clear. Unfortunately, I'm going to give you a semi-crumby response right now, and that is that the entire overview section is in need of a design update and re-implementation. So we'll use this question as feedback into that process. |
@lostintangent Any data we show appears because it was collected by an agent first. We have different agents that run in different environments and as a consequence have different perspectives. Its these perspectives that sometimes mean that we have different data available for different requests. In this case, for origin requests that occur in the browser, we have access to network and client timing data; where as for ajax and http client requests, don't have the same data set currently available. Its possible that we might be able to get it in some cases, but there is alway going to be cases where we don't have some of the timing data. @chetsangnil what do you think we can/should/need to do given these cases. |
@chetsangnil what specifically should the text say (its trimmed in the image)? |
I've filed an issue to track the client work necessary for this: Glimpse.Client#311 |
This should all be added to the design wiki if it hasn't been already. |
I haven't been able to determine when and why the
Network
,Server
andClient
metrics appear in the summary for a request when selecting it. Are these expected to always show up? Is there a specific attribute of a request that causes it to have this data? Apologies if this is cluttering up the issues, but I figured I would log this question in case its a bug that this data doesn't seem to consistently or reliably display.The text was updated successfully, but these errors were encountered: