What is a Web Check?
A WebCheck consists of one HTTP request to a web application. If the web application is only accessible via a proxy, then the request is routed through the specified proxy.
ServicePilot Web Check supports both HTTP and HTTPS to periodically test a web application page and extract data as indicators.
Application Web Check monitoring
This package automatically provisions the ServicePilot Manager and configures the ServicePilot Agent to collect indicators from a Web Application Page using the ServicePilot Agent to collect the Response Time, Status, SSL Certificate information, and page data.
Requests to pages can be customized as required e.g. using GET or POST methods, and with additional HTTP Headers and POST parameters. Page data can also be extracted as indicators and graphed (for numeric data).
The indicators gathered for each Web Check include:
- Page Code
- Page display time
- HTTP status
- SSL Certificate information
- Certificate common name
- Number of days left before certificate expiry
- Custom indicator extraction...
URL Page code and HTTP status are a very good way to establish a web application availability SLA baseline. Additional web checks can be performed to cover different simple HTTP tests or accessibility scenarios.
A good indicator of your web server application performance is the initial connection time to the application server (connection time), also known as "time to first byte". This is the elapsed time between request and the first element returned being displayed. See your browser's "Inspect" Network waterfall diagram. In general, this should be less than 1 second (or as small as possible), ideally under 200 ms.
Long web application server response times delay page loading speeds and display time. Front-end optimizations are more than vital in order to optimize HTTP(S) Page Display Time. Page display time should ideally be under 3 seconds.