how to export console logs in expanded format using consoleexport?

[ketan kale]

Hi,

I am using consoleexport to export console logs to remote server. The logs exported are in collapsed format. So now I have two queries around exporting console logs:

1. Can we export the logs in expanded format so they are more useful during debugging process? - (I read about console logs on internet and it is mentioned that, its the known and default behaviour of console logs)

2. Is there any way we can pass the page title/URL or any other parameter during exporting logs using "consoleexport.serverURL" so the the final report contains page name/URL and error log which in turn will help debugger to easily identify the error and the page in test?

--

Thanks,

Ketan

[Jan Honza Odvarko]

On Monday, March 16, 2015 at 7:42:26 AM UTC+1, ketan kale wrote:

Hi,

I am using consoleexport to export console logs to remote server. The logs exported are in collapsed format. So now I have two queries around exporting console logs:

1. Can we export the logs in expanded format so they are more useful during debugging process? - (I read about console logs on internet and it is mentioned that, its the known and default behaviour of console logs)

What specific logs do you have in mind? console.group, XHR...?
I think that every log needs to be solved separately and things can get
more complicated when this feature is supporting remote devices (planned)
and getting the detailed (expanded) info requires another request
to the backed (over RDP - Remote debugging protocol).
 

2. Is there any way we can pass the page title/URL or any other parameter during exporting logs using "consoleexport.serverURL" so the the final report contains page name/URL and error log which in turn will help debugger to easily identify the error and the page in test?

This could be relatively simple. We can add the URL (+ title) into every packet sent to the server.
Would that work for you?
Please create a new report here:
https://github.com/firebug/consoleexport/issues
(please cross post the issue link here)

And I'll fix it.

Honza
 

--

Thanks,

Ketan

[ketan kale]

Hi,

Thank you for your reply :)

Please see my reply below:

1. I think I did not asked the question in correct way. 

Details on my question: when the logs are generated in console, they are displayed along with + sign and we can click the + sign to view details in expanded mode. So my question is, is it possible to get those logs in expanded format by default so when details are exported using consoleexport, the file contains all the details and not only the error line.

2. Passing an URL with each packet will really help.

I have created an issue as suggested by you. Here's the link: https://github.com/firebug/consoleexport/issues/14 

As of now, I am trying to pass the URL of page by adding "console.error(document.URL)" to my code. This is of course a work around.

[Jan Honza Odvarko]

On Monday, March 16, 2015 at 8:53:17 AM UTC+1, ketan kale wrote:

Hi,

Thank you for your reply :)

Please see my reply below:

1. I think I did not asked the question in correct way. 

Details on my question: when the logs are generated in console, they are displayed along with + sign and we can click the + sign to view details in expanded mode.

What specific logs do you have in mind? E.g. XHR logs are exported, but they can't be expanded...

 

So my question is, is it possible to get those logs in expanded format by default so when details are exported using consoleexport, the file contains all the details and not only the error line.

2. Passing an URL with each packet will really help.

I have created an issue as suggested by you. Here's the link: https://github.com/firebug/consoleexport/issues/14 

Excellent, patch and test build attached to the report.
Please let me know how it works for you.

Honza