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 On Tuesday, October 18, 2016 at 9:05:31 AM UTC+2, ruben.ka...@monitis.com wrote: > > 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 >> <http://www.softwareishard.com/blog/har-12-spec/>. >> >> Note that Firebug is merged into the Firefox DevTools since Firefox 49.0 >> <https://blog.getfirebug.com/2016/06/07/unifying-firebug-firefox-devtools/> >> 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 >> <https://addons.mozilla.org/firefox/addon/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. >>> 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 >>> >>> <https://groups.google.com/d/msgid/firebug/24db890b-e61f-4625-b22c-fdeea90750a7%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- 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+unsubscr...@googlegroups.com. To post to this group, send email to firebug@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/5eb9d747-ea88-45e1-aac4-f0ff7e700b0e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
