Feature Request - Logging of extension generated traffic

[AkikoOrenji]

Is it possible to log all the requests the extension is generating ? Apart from forwarding system proxy to burp and capturea i can't think of another way to do so ? Its a bit of a black box at the moment with not much logged apart from the below in the extension UI.

Beginning subdomain scanning, gathering subdomain lists. Building a list from the file: fierce-hostlist.txt Beginning HTTP/HTTPS subdomain scanning for AWS S3/Heroku/Github. Beginning DNS subdomain scanning for Azure. Subdomain scanning has completed.

[codewatchorg]

I would think an extension like Logger or Logger++ would log the requests. This seems redundant to add logging to the extension itself. It also adds "Issues" in the Target Site map as cloud resources are enumerated.

[AkikoOrenji]

I checked logger++ and didn't see any traffic being generated from the extension. Is that just me ?

[codewatchorg]

Logger++ visibility is determined by where it sits in your extension list (from what I understand), so you want it at the bottom to have visibility to all the other extensions (at least that is how I understand it).

If it is still not seeing/logging the traffic, then I'm not sure why, but I'm not sure it makes sense to add logging for every request the extension makes - unless the extension observes a cloud-based resource, it is mostly passive anyway.

[AkikoOrenji]

Thanks for the tip on Logger++. I wasn't aware of that one. Didn't seem to make a difference but appreciate the feedback.