Firebug net load event issue

[ruben.ka...@monitis.com]

Hello,

I hope you are doing well.

We represent a monitoring company that uses Firebug for showing a web page net view in our monitoring.

Recently we have encountered an issue that we are not able to understand and also explain to a customer. 

On our Full page load monitor we can see very long loading time for mentioned URL, but in the Net data

we can't see the resource that takes such long loading time. http://screencast.com/t/J6xmJKEjV

Please see the attached files with exported net data in json format and also in a CSV file. 

Please help us understand why we are getting such a huge time for window load event: example  http://screencast.com/t/tuEdPAtyZfy 

Thanks in advance.

[Sebastian Zartner]

I wonder how you retrieve the data from Firebug, but normally this is done using the HTTP Archive (HAR) format.

Note that Firebug is merged into the Firefox DevTools since Firefox 49.0 and Firebug 2 stops working once multi-process Firefox is enabled.

Unfortunately the Firefox DevTools don't output the 'load' and 'DOMContentLoaded' events to HAR yet (see https://bugzil.la/1174091), which you need for your measurements, but this issue is actively worked on already.

You may also be interested in the HAR Export Trigger extension, which allows automatic export of the network request data (similar to NetExport for Firebug).

Sebastian

--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebug+unsubscribe@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/24db890b-e61f-4625-b22c-fdeea90750a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ruben.ka...@monitis.com]

Hello Sebastian,

Thank you for your response. 

We are retrieving the net data with json format by calling Firebug.NetMonitor.getContent(context). We are using this method already for years and never had

any issue with that. Here is the net data that is seen in our Full page monitor when this issue occured: http://screencast.com/t/wWbDJgDioOmG 

We just encountered this time such issue when the net data does not include the element that takes so long to load the hole page. For example

there is another peak on the monitor that is showing that the page was loaded within 35 sec and in the net data we can clearly see which resource took so 

long to load: http://screencast.com/t/cLYFlmQr   http://screencast.com/t/OCAiOSljr

We need to understand if there may be any known case when this kind of issues may occur and you are aware of it and if there is any solution for this.

Thank you.

On Friday, October 14, 2016 at 11:41:38 AM UTC+4, Sebastian Zartner wrote:

I wonder how you retrieve the data from Firebug, but normally this is done using the HTTP Archive (HAR) format.

Note that Firebug is merged into the Firefox DevTools since Firefox 49.0 and Firebug 2 stops working once multi-process Firefox is enabled.

Unfortunately the Firefox DevTools don't output the 'load' and 'DOMContentLoaded' events to HAR yet (see https://bugzil.la/1174091), which you need for your measurements, but this issue is actively worked on already.

You may also be interested in the HAR Export Trigger extension, which allows automatic export of the network request data (similar to NetExport for Firebug).

Sebastian

On 12 October 2016 at 16:04, <ruben.ka...@monitis.com> wrote:

Hello,

I hope you are doing well.

We represent a monitoring company that uses Firebug for showing a web page net view in our monitoring.

Recently we have encountered an issue that we are not able to understand and also explain to a customer. 

On our Full page load monitor we can see very long loading time for mentioned URL, but in the Net data

we can't see the resource that takes such long loading time. http://screencast.com/t/J6xmJKEjV

Please see the attached files with exported net data in json format and also in a CSV file. 

Please help us understand why we are getting such a huge time for window load event: example  http://screencast.com/t/tuEdPAtyZfy 

Thanks in advance.

--
You received this message because you are subscribed to the Google Groups "Firebug" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebug+u...@googlegroups.com.

[Sebastian Zartner]

Hi Ruben,

from the screenshot you can see that the browser spent about 32 seconds waiting for the response from the server. So I assume it was either a peak in server load or a temporary connection issue.
Though I am not an expert in network request info. Honza may be able to give more detailed feedback on this.

Sebastian

[ruben.ka...@monitis.com]

Hello Sebastian,

If you mean the last two screenshots that I have sent ( http://screencast.com/t/cLYFlmQr ,   http://screencast.com/t/OCAiOSljr) than in this case everything is correct and there is no issue here,

it is showing 35.32 sec on the graph and in the netview also seen a resource that took so long to load, it is the main GET URL appstore.vivo.com.br. The issue was in my previous provided screenshot

http://screencast.com/t/3Ikp0k5OM0ln here if we scroll to the end we can see no resource that loaded long, but on the graph you can see that overall load time was 61.27 sec: http://screencast.com/t/s8bV4nHVl

So in the netView you can't see any resource that took around 60 sec to load. In my original message I have attached the netview of this exact check with both json format and also in csv file.

In the CSV file you will see all the resources that loaded and their timings. I will paste this file with xlsx format in this post so it will be more clear. So no resource shows this much high value of load

time, but the overall load time was shown 61 sec.

Thank you. 

[Sebastian Zartner]

Hi Ruben,

thanks for the clarification!
So, it looks like this might be a bug in Firebug or the Firefox APIs it uses. I can imagine two possible scenarios:

1. There was a long-running request, which held up the load event from getting fired, but it was not added to the data you retrieved via Firebug.NetMonitor.getContent(context) for some reason.
   You might be able to check this through the server logs.
   
2. The load event time was calculated incorrectly for some reason.
   

Though, as I said, I'm not an expert in that area, so I can't give further information. And without a reproducible test case it will be very hard to find out what happened.

Sebastian

PS: Note again that Firebug 2 will not work anymore once multi-process Firefox is enabled, so you will need to switch over to the Firefox DevTools soon.

[ruben.ka...@monitis.com]

Hello Sebastian,

OK , thank you anyway for your time!

Have a nice day!

Best regards.