What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

HTTP Transaction vs HTTP Full Web Page



This might be a bit of a foolish question, however after reading the documentation of the "http transaction" sensor, I was led to believe that setting the sensor to "get" requests the webpage directly, just as you and I would browse to it. What I find puzziling is that this sensor has completley different data to the "full web page" sensor set to the same website

Http transaction on "get" will give around 4 seconds Http "full web page" will give around 10 seconds

What is different about the sensors?

http-full-web-page http-sensor http-transaction-sensor

Created on Jan 8, 2013 7:23:53 PM

2 Replies

Accepted Answer



Only the Full Page sensor actually loads all the embedded objects (images, scripts, JAVA applets, etc.) - all other HTTP sensors only load the HTML source code directly from the document under the specified URL. Beyond that, all other HTTP sensors do not execute active elements (e.g. Javascript) in the HTML code. This can also make a difference if, for example, code is loaded after the initial connection.

Created on Jan 9, 2013 1:58:27 PM by  Patrick Hutter [Paessler Support] (7,225) 3 3



Thanks, that is exactly what I was after :)

Created on Jan 10, 2013 8:42:24 PM

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.