[Listing] Filter toggling the visibility of static assets

[lostintangent]

After using Glimpse a little bit over the last couple of days, I keep finding it somewhat disorienting that it doesn't display static assets anywhere. I really like the "focused" view that Glimpse is providing, but if a Node server is setup to actually receive and serve static assets (as opposed to delegating that to a reverse proxy such as nginx), then it seems a little odd (for me at least) for that traffic to be entirely omitted from the UI. I think I agree with not showing these requests by default, but I can't help but feel like it would be valuable to allow the end-user to choose to see them somewhere, if for nothing else than to be able to "cross check" what the tool is showing them, and feel comfortable with the data.

When we re-built the network tool in F12, we had a lot of users compare us against Fiddler or Chrome's network tool, and I suspect that Glimpse might receive similar comparisons. The lack of static assets is definitely an obvious divergence.

Personally, I think it would be pretty awesome if static assets were displayed either as child rows within the request list (if that list was turned into a tree), or if there was a new tab added to the request details page that displayed the child requests that were made as a result of it. I may be alone in wanting to see this, based on having used traditional web tools for a long time, but I just wanted to log this perspective as a first-time user.

[avanderhoorn]

Great feedback, currently we profile the requests but don't show them. Just incase you are interested, if you look in the console of the main glimpse client, it dumps out the requests its filtering out. I totally agree this needs to be looked at, its just a matter of what we can do in the time we have, given the current priorities.

This will go through triage and be prioritized accordingly. If others would like to see this feature sooner rather than later, feel free to comment or vote.

[nikmd23]

I'd like to see this folded into our overall request filtering story.

We currently didn't have thoughts around filtering by Content-Type, but we probably should, with perhaps a quick toggle for "Static Files" (which still needs to be defined).

Feedback on the filtering mock would be great too.