UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.20 Safari/537.36

Steps to reproduce the problem:
When you load a resource-heavy website and want to inspect subresources of it, it's sometimes not easy to find a proper subresource quickly. 

All the requests in the network panel "look the same": black text on white background. The best you can get is either sorting the requests by some column, or filtering using the filter textinput and the buttons that filter by type. This is helpful, but it can be improved.

Especially the resources that have long request URLs are not easy to quickly distinguish.

What is the expected behavior?

What went wrong?
It would be great to add possibility to have the requests highlighted with a background color, depending on some persistently-defined rules.

Did this work before? N/A 

Chrome version: 71.0.3578.20  Channel: beta
OS Version: 10.0
Flash Version: 

The rules could be a function of URL, domain, response headers etc. They could be a defined in a panel similar to the "Request blocking" panel. 

Those rules could modify the bgcolor, and/or add text to a "comment" column.

(If you're a Windows user, I basically ask for something similar to what is possible with Fiddler through fiddlerscript.)

The rules could adhere to the already existing powerful syntax that the filter textinput uses:
https://developers.google.com/web/tools/chrome-devtools/network-performance/reference#filter-by-property

IMO this would greatly improve debugging and performance analysis experience.