Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Logs from both Logger/Logger++ get erased when closing Burp

Adam | Last updated: Jan 26, 2022 04:16PM UTC

Every time I close Burp after saving, all my logs from Logger / Logger++ get erased. The only method that seems to work for me is if I manually export the logs to a CSV file. Is there a way to persist the logs after closing them so they still persist after reopening Burp?

Ben, PortSwigger Agent | Last updated: Jan 27, 2022 10:32AM UTC

Hi, Currently, the logged data within both Logger++ and the native Logger tool will not persist when Burp is closed. The only option is to do as you have described and export the logs from both tools in order to keep a record of that log data. We do, however, have an existing feature request to create an option to allow users to specify whether they wish logged data to persist in project files (that way disk-based project files could be reloaded with this logged day still in place) - I will add your interest this this particular feature. We can then both accurately monitor the demand for the feature and also update this thread if we have any further news to share about it in future. In terms of Logger++, this is written by a third party (so requests for additional features would have to be raised with the authors themselves) but I can see that the functionality to be able to import an exported csv file has already been raised with them (as detailed below): https://github.com/nccgroup/LoggerPlusPlus/issues/10 https://github.com/nccgroup/LoggerPlusPlus/issues/133 Perhaps you could also add to one of these entries so that the authors are aware of your interest?

Liam, PortSwigger Agent | Last updated: Feb 17, 2022 02:25PM UTC

We were curious about your request regarding the Logger. To help us flesh out the development ticket, could you provide some detail on your workflow? What are you using the Logger data for?

Login | Last updated: Feb 01, 2023 12:23PM UTC

+1 for this feature request! Having everything directly in Burp makes it easier to handle requests made by extensions/scanners/etc.. For example, if a customer wants to know if a specific request was sent at a specific time, it's a hassle to filter this with the current Logger log file. If all the requests could be persisted into the Logger or imported from the Logger log file, this would be a huge help!

Liam, PortSwigger Agent | Last updated: Feb 02, 2023 10:29AM UTC

Thanks for your message, Login. We still have a decision about implementing this feature in the UI. It is possible to use an extension - https://portswigger.github.io/burp-extensions-montoya-api/javadoc/burp/api/montoya/MontoyaApi.html - the new persistence functionality allows you to save to a project file. Please let us know if you need any further assistance.

Raynes, | Last updated: Oct 10, 2023 10:20AM UTC

Adding my +1 to interest. Any updates on this? It'd be such a massive help to have logging across the Burp tools that can actually persist across sessions. Some clients force you to restart your machine for compliance, which means losing the really useful Logger output. And I don't think any progress has been made with Logger++ on this front.

Liam, PortSwigger Agent | Last updated: Oct 10, 2023 11:25AM UTC

Thanks for your message, Christopher.

Following recent roadmap planning, we have no current plans to implement this feature. I have added a note of your interest to the triage ticket. Thanks for your feedback.

Chris | Last updated: Dec 20, 2023 03:24AM UTC

I genuinely don't understand how this is not a feature yet, or what the original design decision behind not saving these logs was. Knowing and being able to audit all requests we have sent to a client's system is pretty central to being responsible testers. Short version, please add my vote for this feature.

Liam, PortSwigger Agent | Last updated: Dec 20, 2023 02:05PM UTC

Krzysztof | Last updated: Mar 11, 2024 11:13AM UTC

I don't understand. :( Why has saving on project file size become so important? With today's disk storage, this should be the least important thing. After all, this functionality is critically important! How can I go back to the history of a given test if I cannot (after reloading the project) have a complete history of all requests and responses from/to the server? It's already 2024... is there anything known about it?

Michelle, PortSwigger Agent | Last updated: Mar 11, 2024 02:30PM UTC

Hi Even though disk storage is not the issue it once was, project files can get very large. Is there a particular type of request you want to save? Any requests from the Proxy HTTP history will be saved with the project file, and items such as Intruder attacks can be saved as tasks in the Dashboard now. If you want to save requests from other tools, there is also an option to save them to a separate file by going to Settings > Project > Logging. Would this help for auditing purposes?

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.