FAQ: Monitoring history

I just configured my first check. Why can't I see any data yet?

The monitored website must be working properly. :)
In the first tab of the monitoring history you will find a graph and a list of failures—but it will be empty until the first such event occurs.
In the second tab you will see your website's average daily response times—but they will start appearing there only after the first 24 hours of monitoring.

How to read the availability report?

There are two lines in the chart:

  • the red one is the total unavailability time on a given day, its scale is on the right Y axis,
  • the yellow one is the number of failures on a given day, its scale is on the left Y axis.

In order to check the precise value of a point on the chart, place the mouse pointer on it.

How do you read the response times graph?

For availability and content checks, the server response time chart is available in the second tab.
Each bar shows the average response time for a given day. The coloured elements of the bar are the individual components of the total response time (DNS, Connect, Pretransfer, Starttransfer and Redirect). Hover your mouse cursor over the selected element to see the time of this component and the total average time for that day.

How do you read the graph of average loading times?

In the case of the load time check, the second tab contains a graph of average loading times. It is a line chart, showing only one value for each day—average time it takes to fully load the page on a given day.
Hover the mouse cursor over a point to display the value for the selected day.

How do I read Core Web Vitals charts?

The colors green, orange and red correspond to the ranges of values according to the limits recommended by Google. If the value of a given indicator is in the green area, it indicates good quality. The orange area means that the indicator "needs improvement". Meanwhile, red is "poor", which means a really bad score.

Why is the duration of each failure given in minutes without seconds?

Our system tests the monitored websites and servers every 60 seconds. This naturally makes data be displayed with an accuracy of one minute.

What is there in the "response" column in the list of events?

It is information about the type of each failure. Here you can find:

  • HTTP 1.1/xxx - server responses other than "HTTP 1.1/200 OK" (availability check)
  • CONNECTION TIMEOUT - no server response within a defined time (availability check)
  • PING TIMEOUT - response timeout ("ping" type availability check)
  • LOADING TIMEOUT - the page cannot be loaded in the defined time (availability check)
  • PAGE LOADING TIMEOUT - page loading time exceeded (page speed check)
  • NOPHRASE - no defined phrase (content check)
  • NOPHRASE FORM - lack of defined content on the result page (form check)
  • PROCESS(x) - problem at step x of the scenario (process check)
  • CHECKSUM - discrepancy between the checksum of the file and the reference (file integrity check)
  • DOMAIN EXPIRED - website domain has expired (condition of the day check)
  • INVALID SSL CERT - invalid or expired SSL certificate (condition of the day check)
  • BLACKLISTED (GOOGLE) - the site has appeared on Google blacklist (daily health check)
  • BLACKLISTED (RBL) - the site has appeared on the RBL blacklist (condition of the day check)
  • ROBOTS BLOCKED - search engine robots are blocked on the website (condition of the day check)
  • CHANGE DETECTED - a change has been detected in the content of the monitored page or the specified HTML element (change monitoring)
  • CHANGE - ELEMENT NOT FOUND - the indicated element was not found on the monitored page (change monitoring)
  • CONTINUATION - means continuation of a failure from the previous day or change in the type of failure.

How can I export the failure history of a selected time period?

Select the date range for the chart and table using the calendars on the left—after refreshing the view, click the "" icon, which you will find below the list of events.

I need to send a report to my boss in the form of a document. How can I get it?

Specify the time range for the report (as above) and then click the "" icon, located under the list of events.

I have set to receive weekly and monthly reports. When will I receive them?

The weekly reports are sent on Monday morning and contain data for the past week. Meanwhile, the monthly reports are sent on the first day of the month and cover the entire month.

Why on the Core Web Vitals charts do I see "No data" in the "Field data" tab?

Google provides Field data only for those sites and URLs for which it has collected enough data from users' browsers. Perhaps your site (or URL) is not popular enough yet and Google has too little data to present.

Why are Lab data and Field data different in Core Web Vitals?

When measuring Core Web Vitals, the parameters and performance of the devices on which the pages are loaded are of great importance. Network latency, related to the location, is also significant.
We measure the Lab data from our servers, with a specific (averaged) browser configuration. And these are the data measured at a given moment. The Field data, on the other hand, is a moving average over the last 28 days of thousands of measurements taken by the Chrome browser during visits by real users.
There is no point in comparing Lab data with Field data. It's best to consider them separately, comparing current values with historical values.

Field data gives an overall picture of the interface quality in the medium term and presents the values of indicators that are considered by Google when evaluating websites.
Lab data, on the other hand, shows the situation at a given moment and allows you to immediately detect any sudden deterioration in interface quality.

Core Web Vitals: Why is there FID in the Field data and TBT in the Lab data?

FID (First Input Delay) is a Field type indicator and cannot be simulated in a lab measurement.
TBT (Total Blocking Time) measures another thing, but is so strongly related to FID that it is recommended as a replacement for FID in Lab data.
TBT values should not be compared directly to FID values.