Do you need it because your page has redirects or any other reason?

Hi Pfeldman, thanks for the response. Yes actually our application has too many redirects during and also after login so everytime we open chrome dev tools for debugging or seeing response data, first thing our team has does is check network tab -> preserve log.

However is this a bug or this feature doesn't exists? But then if the feature doesn't exists, in the dev tools settings pane we do have an option to check it. But after checking and closing dev tools it gets unchecked by itself. Let me know. Thank you.

Hi Pfeldman, Also I asked this on stackoverflow and it has several upvotes so looks like there are other interested in it as well.

https://stackoverflow.com/questions/45133659/how-to-enable-preserve-log-in-network-tab-in-chrome-developer-tools-by-default

Thank you.

Able to reproduce on 60.0.3112.113 with the mentioned steps on Ubuntu 14.04, windows 7 and Mac 10.12.6.
This seems to be a Non-Regression issue seen from M-50[50.0.2624.0]. Hence, marking it as Untriaged.

Hi Keerthan, you mean to say this feature never actually worked after getting rolled out to production??

@allada what do you think about this feature request?

A common workflow of developers to reload their page extremely frequently. We could implement a "persist log after devtools closes" button, but if we did this with every setting, it would greatly bloat the settings panel. As for now I am going to close this issue because because a better solution might be to allow an extension or something for these alternative workflows to get what they need.

So, in short, we need to think hard on these kinds of changes for what it means to the millions of other developers and their workflows. A simple solution is possible, but not elegant.

Thanks for the report though!

@allada, why would you need a configuration option to simply persist an already existing option? Additionally, the console settings already have an option to remember persisting console messages. Why should the network tab be any different? If anything, it would make the DevTools more consistent with user expectations. 

Allada, your "common workflow" scenario has nothing to do with persistence.  Presumably the developers you speak of would have their (correctly persisting) setting unchecked.

Allada, Ok I have a question for you. I have highlighted two settings in the attachment. 'Console' one preserves the logs but the 'Network' one doesn't. So my question to you is, why did the Dev tools team intentionally made one of them work and another one didn't. and released it to Production? 

Deleted: Image.png 45.7 KB

	Image.png 45.7 KB View Download

@allada I came here to report what seems to be exhibiting as a bug as well.  I am hard pressed to find any interpretation of a checked "Preserve log" box > in network area > developer tools settings ... ...if not to always have preserve log checkbox on by default in the network tab while dev tools open.

I believe this is an exceedingly common developer use case.
Use case: I have some error in my login code.  My login causes a redirect after success or failure (almost all do).  So I see an error with login.  I then open dev tools to a blank network tab.  I login, the error flashes by, but before I can examine it, the page gets redirected, wiping the error.  I then click perserve log and log in again, to finally examine the error.

What is the point of the DevTools > Settings > Network > Preserve error if not to avoid me having to manually set preserve log whenever I open devtools?

It seems that both checkbox, "Preserve Log" in the Network tab and "Preserve Log" in the Preferences, behave the same way - they both only allow preserving logs for one time. I think they both just point to the same temporary variable that won't persist.

Please make this persist. At the very least, the "Preserve Log" checkbox in the Preferences should make it sticky since what is a preference setting if not for the user to make some setting persistent forever. You do not need yet another checkbox, just make this existing checkbox in Preferences panel work.

This is a bug.

Can you allow this feature to Preserve log if we check it in Setting alteast. we now have to Preserve log each time i open the network tab. 

Can you please answer Varun's question?

....So my question to you is, why did the Dev tools team intentionally made one of them work and another one didn't. and released it to Production? 

@Jgilli - Doubt they will reply to that. Anyway 'Firefox Developer' Edition has this feature (persist network logs even after closing browser). Please see here for more info - https://stackoverflow.com/questions/45133659/how-to-enable-preserve-log-in-network-tab-in-chrome-developer-tools-by-default. However, Chrome Dev tools has quite rich feature set as compare to Firefox in other areas.

It seems that tracking the first redirect of a popup isn't possible with Dev Tools. Even when the "Auto-open DevTools for popups" option is selected, it will be too late to click Preserve log manually after the page redirects.

The best solution for now is probably to install some spyware-like extension to log every network request in the entire browser.

This seems a clear case of the dev not understanding the bug complaint. There would be no bloat as @allada claims in #7. The option is *already* there in DevTools Settings>Preferences. It simply doesn't persist, as one would expect from anything in Settings>Preferences. What does "Preferences" mean if not persistent settings??? In fact, it's in it's *current* sate that it's acting as UI bloat. Despite appearing in Preferences, it simply duplicates the functionality of the toolbar checkbox. See attachment.

Deleted: devtools bug.png 149 KB

	devtools bug.png 149 KB View Download

Totally agree - either this preference should persist, or the option should be removed from preferences panel. If removed, that would be massively disappointing, as similar tools from other vendors have this option and it does persist.

@ jcapp...@simonsfoundation.org - Fully agree with you. They probably know it is a bug but not prioritizing it. And thanks for letting us know the other options that don't work either.

This is so frustrating, having to remember to check preserve log as soon as a new tab/window opens - especially when it's the first-page load of the new tab I'm trying to track in the first place.

Looks like fixing this is low priority?

When same URL is put into the address bar or clicked in MS Word, it is redirected to a different page. I would be grateful to have ability to analyze passed headers to inspect the difference - directly in Chrome. I am able to have DevTools opened by default via the --auto-open-devtools-for-tabs cmdline parameter. But the list of network traffic is incomplete when URL is opened from MS Word (I can see referenced scripts, but I am missing the main html page). I suppose it could be fixed with that Preserve logs option, but this settings doesn't persist. Please reconsider this behavior.

This bug is very annoying, please do fix it!

Start to think about using Firefox for this feature...

What I am working on has a lot of redirects, so it is always necessary to persist log. Every time, I forget to check it in a new tab, I need to reproduce the test again. It is very annoying.

I don't see any activity on this and it still has a status of WontFix. It would be great if you could re-evaluate/re-consider that decision!! There is already a setting in preferences for this so the comment#7 doesn't seem accurate (fixing the issue will NOT introduce a new setting). The chrome/chromium team appears to have already/previously made a decision that this was an important option - since there is a checkbox for it in settings! - I just isn't working (e.g. It's a bug) I am hard pressed to understand why this wouldn't actually be the default setting anyway. I work for company with a very large development staff, and every time I work with someone to troubleshoot an issue, the first thing they do when opening up chrome developer tools is to go in and check the "Preserve Log" checkbox so that they can actually use the tool to debug what is going on, without losing track of the requests that were made. For instances where an app is linking out to another site (e.g. New Tab) not having Preserve Log on by default (or having the option to have it on by default) means we can't use chrome to debug any issue related to redirects at the start of a link-out without have a 3rd party network tracing tool (which we shouldn't need since we have "Developer Tools"). Please re-consider fixing this issue or consider having "Preserve Log" turned on by default. Thanks

Deleted: chrome-developer tools-settings-preferences-network-preserve log.png 51.6 KB

	chrome-developer tools-settings-preferences-network-preserve log.png 51.6 KB View Download

>I don't see any activity on this and it still has a status of WontFix.

There are no developers in CC field.
The owner allada@ last visit was 175 days ago.

In other words, this thread is dead.
The funny thing is, just posting a new one will likely get duped into this one.