Hi folks,
I have an httpfullsensor that's giving a 0 msec response time for a particular site. This doesn't seem believable because the site doesn't load in 0 seconds (!). The response time isn't always 0 msec, but mostly is.
Any ideas?
Thanks
Article Comments
The site is mypeexam.org. Opening with Chome's Develeoper Tools seems to show the site loading lots of graphics and other items, and it takes several seconds to open.
Feb, 2017 - Permalink
Hi there,
How long does it take to load the page if you open it directly on the PRTG Core Server or the according PRTG Probe's server?
Feb, 2017 - Permalink
Opening in Chrome on the PRTG core server (probes are on the same server) currently takes 5.75s.
Feb, 2017 - Permalink
Hi there,
Are you using any group-policy based proxy settings? Perhaps for the system user? Please enable the "Use Windows credentials of parent device" option within the sensor settings, does this work?
Feb, 2017 - Permalink
To confirm that the sensor inherits its proxy settings from the device. All our sensors do this.
We now have another website sensor that's behaving the same way, for www.showmyhomework.co.uk.
Not all sensor readings are 0 msec, but the bulk are.
Feb, 2017 - Permalink
Hi,
Please try to use the "PhantomJS" or "Internet Explorer" browser engine instead, does that work?
Feb, 2017 - Permalink
I've tried both, and oddly I seem to get even less response with those.
Chrome does seem to show the odd spike, but mostly the graph data is at 0msec.
Mar, 2017 - Permalink
Hi there,
Is the website by any chance publicly available so we can test and analyze this further on our side?
Mar, 2017 - Permalink
Yes, it's mypeexam.org. The sensor is pointing specifically at http://www.mypeexam.org
We were having an issue with kerboodle.com, but that is now working with Chromium.
We're using PRTG v16.1.22.2657.
Mar, 2017 - Permalink
Hi there,
On my side I get a valid request time, about 3 seconds load time. Please set the engine to "PhantomJS" and enable the "Render and store a screenshot of most recent sensor result as PNG" option in the sensor settings. Afterwards check the picture of the website, which is located under "C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Sensors)\", how does the webpage look like?
Best regards.
Mar, 2017 - Permalink
I've done that, and get a very long image! The image does appear to reflect the site. Yet still the loading time for the site is 0msec.
Mar, 2017 - Permalink
Hi there,
Then the website can be resolved. I think that issue is may caused by a bug in the sensor which is already fixed in one of the newer versions. Please update to the most recent version and check if the loading time is still 0 msec.
Best regards.
Mar, 2017 - Permalink
Hi there,
Okay, just come back with your result after the upgrade. If you have any further trouble do not hesitate and contact us via "support@paessler.com".
Best regards.
Mar, 2017 - Permalink
Having updated, the sensor now appears to be working correctly with Chromium. So it looks like all is OK, thanks for your help!
Mar, 2017 - Permalink
Hi there,
Great that it is working now, took a long time. But, enjoy your working sensor. :)
Mar, 2017 - Permalink
Hi there,
What exactly is displayed on the website? If it is just a Java site or site which is build with JavaScript, then the 0ms are possible. Please note that the sensors just loads the complete site with its assets excluding any executable scripts.
Feb, 2017 - Permalink