search

Glimpse / Home

Project Glimpse: Node Edition - Spend less time debugging and more time developing.
http://node.getglimpse.com
Other
252 stars 9 forks source link

[Feature Request] Allow users to better understand the duration of console.time/console.timeEnd calls #39

Closed lostintangent closed 8 years ago

lostintangent commented 8 years ago

It's awesome that Glimpse displays console.time/console.timeEnd intervals (I was so happy to see this!). However, there are a few things which I found somewhat strange about the way they're currently displayed:

  1. Neither the From Start or Duration columns are populated, which would actually be very useful, particularly for custom time interval entries. The duration is displayed in the log message, so this isn't a blocker, but it's generally easier to read structured data in a tabular format (for me at least), instead of needing to parse the message content for relevant data.
  2. Because a time entry represents an interval, and not a discrete event/message, its ordinal position in relation to other logs can make it confusing to know which logs happened between the start and end of the timer. Since it's valuable being able to correlate logs in relation to others, I could imagine it would be meaningful for users to be able to understand the relationship between a timer and its child/sibling logs. I'm not sure what the right solution would be here (E.g. Adding a "virtual" entry to the list of logs that helps you see where the call to console.timeEnd was), but in general, the mismatch between individual messages and intervals isn't completely ideal.

In practice, neither of these suggestions may actually matter to users, but I just thought I would throw it out there.

nikmd23 commented 8 years ago

Thanks @lostintangent.

This issue highlights a larger problem we need to address with timings in general. I'm not assigning this to a milestone just yet, but we'll track this and I suspect we'll need to solve all of our timing issues sooner rather than later.

nikmd23 commented 8 years ago

This issue depends on Glimpse/Glimpse.Node#122.

philliphoff commented 8 years ago

This issue is related to Client work Glimpse/Glimpse.Client#132

nikmd23 commented 8 years ago

👌

nikmd23 commented 8 years ago

This is now available in version 0.14.1. For more information, please see our announcement. If you continue to experience this issue, please let us know. - :heart: the Glimpse team.