Monitoring

courtesy : Monitoring

Monitoring is an all-encompassing term for any activity that involves testing a website or web service for availability, performance, or function. A Website Monitoring service checks and verifies that the site is up and working and site visitors can use the site as expected. The term “Website Monitoring” refers to any activity that checks the availability, performance, and function of a website or web service. Typically, the term refers to automated testing or Real User Monitoring (RUM), but some sites still do not test at all or rely on periodic checks performed by employees. Manual testing is sporadic and undependable when considering the number of variables that influence a site’s availability, performance, and function. This article discusses primarily Synthetic Monitoring.

How does Website Monitoring work?

Automated Website Monitoring uses a network of computers located near the site’s end users. This network of computer checkpoints interacts with a website or service to verify that the service works as expected. The monitoring system designates a checkpoint to test the site, and the checkpoint may go through several steps to conduct the test. The checkpoint:

1. Initiates a connection with the website or service
2. Checks the return for a response code. For basic availability, the checkpoint reports the result and considers the test complete, but for more advanced monitoring the checkpoint continues.
3. Checks the return for specified content
4. Loads the content into a real browser (Real Browser Monitoring)
5. Records load times for each page element as it loads in the browser (performance monitoring)
6. Attempts to log in, conduct a search, use a shopping cart, even complete a purchase (web-application monitoring)
7. Reports its findings back to the monitoring service

If the result includes errors or slow response times, the service may initiate the check again from a different checkpoint to verify a persistent error before alerting the website’s support team. Monitoring may also use data coming from the actual users of the website or service. Known as Real User Monitoring (RUM), script files, agents, cookies, or server-side code track the website’s performance as each site visitor accesses the site. RUM provides real user insights, but RUM relies on user interaction with the website to get data making it an unviable method for tracking uptime.

What types of Website Monitoring are there?

Website Monitoring involves testing websites for availability, performance, and function and alerting support staff when the page doesn’t work as expected. Typically, a monitor type will fall into one of the previously mentioned categories, although the more advanced monitors may cover all three.

Availability monitoring

Availability is about uptime, or in other words, making sure a website or service is always accessible and to some degree functional. Availability can involve web services, domains, and pages.

Basic website and API monitoring – These basic monitors check for a successful response or a specific response from websites and APIs that support HTTP protocol, and they may perform basic authentication. Basic availability monitors can also measure the timing and size of the response and issue alerts for slow response times. HTTP(S) monitors do not load the content into a browser, but the monitoring service may check the response for the presence or absence of specified words, phrases, or a regular expression.

Server availability – As long as a server or device recognizes TCP/IP protocol, a monitoring service can verify availability for the device and selected ports. A monitoring service can check the availability as frequently as once per minute preventing costly downtime and lost productivity over the web or behind the firewall.

Advanced Availability – These specialized automated monitors verify DNS records, check for proper configuration of SSL certificates, query databases, log into email servers, and download files from FTP servers.

# Real User Monitoring (RUM)

#Basic website and API monitoring

# HTTP

#ISBC