![]() With the HTTP content sensor, you can check up to 50 results that are returned by an HTTP request, with each result in square brackets. o Other configuration options include special HTTP settings, or simulating specific user agents. So you can simulate a login into the website, and check that specific content is or is not appearing on the resulting page. o Show settings for "Time to first Byte" o If we look at the Settings for this sensor, we see that it also supports authentication and you can use it to check for specific content on the page. O For each channel in the sensor, you can set individual thresholds and alarms. The HTTP advanced sensor shows not only the response time, but also the bytes received, download bandwidth speed, and time to first byte. ![]() If the sensor doesn't receive an answer, or if it receives a 404 status code, then the sensor goes into Down state. The simplest sensor, the HTTP Sensor, loads a web page and monitors the response time. PRTG offers the following sensors for monitoring content and user experience: Let's look at each of these inside PRTG. I'm now going to show you how you can monitor each of these areas using PRTG, starting with how to monitor content and user experience. The basic network services include having enough bandwidth, that DNS is working, that certain ports are reachable, and that devices such as proxies or load balancers are functioning correctly. The server health includes not only the hardware, but also the operating system and application-level services that are running on that server. I've divided these into two sections: the health of the server, and the basic network-level services. Underneath this services level come the hardware devices such as web, application and database servers, and network devices such as switches and firewalls. This set of functions is partially at the user experience level, because the user sees the results, and partially at the system level, because they're part of fundamental business processes. In addition to serving up the content of the web site, web servers also need to perform additional supporting functions such as performing user authentication, providing security features such as certificates and encryption, forwarding to other URLs, reporting HTTP status codes, and logging web server activity. Since content can be static or dynamic, we should be able monitor both. In the user experience level, we should monitor the quality of user experience, which includes both the content the user receives, and the response times for loading the content. We can differentiate between two main categories of web server monitoring: the user experience level, and the system or IT level. Let's look at the different areas of web server monitoring that need to be considered. The most important question to start with, is: What, exactly, should I monitor? What components and services are most important? Your webservers depend not only on the underlying hardware - they're also dependent on applications and network services such as DNS or AD. As such, it is essential to ensure that your webservers are performing correctly, to avoid failures and to avoid business losses. Web servers are a critical part of every business: as online shops, for customer communication, partner portals, or as part of your corporate marketing strategy. In this video, I'm going to discuss the different aspects of web server monitoring, and how you can perform these using PRTG. My name is Kimberley Trommler and I'm a systems engineer at Paessler. ![]() ![]() ![]() Hello, und welcome to this video about monitoring Web Servers with PRTG ![]()
0 Comments
Leave a Reply. |