Web site checks

Using Web site checks you can monitor Web servers running on your host. For each check you could specify protocol, port, page, and other site properties.


  • The system where the monitored Web server runs is defined as host in CloudRadar. For details, see Creating a new host.

  • The Web server you want to monitor is running. For example, you could run a command like curl to check server's status.

  • There are no checks defined yet for the Web resource you want to monitor. For example, after defining a check for the /books/flowers page on at port 80, you cannot define another check for the same page and port.


  1. Choose Hosts on the left, and then choose the icon (Settings) for the host where you want to add a check.

    You could also access host's settings from the dashboard.

  2. In the Add check screen area, choose Website Check.

  3. Choose the protocol, and optionally specify the port.

  4. In the Path field, enter the path to section of the Web site you need to monitor.

    For example, if you need to monitor the https://en.wikipedia.org/wiki/FQDN page, you should create a Web site check for the wiki/FQDN path for the en.wikipedia.org host.

  5. Choose the request method, and optionally enter the expected HTTP status.

  6. Select additional options as needed:

    • You can choose to ignore redirects.

    • You can check if a particular text string is present in the raw HTML at the specified path. To achieve this, enter the string in the Expected string field, and set the Search HTML source option.

    • When you have specified the check to be performed using the HTTPS protocol, you can choose to ignore SSL errors.

  7. Specify the interval at which the check should be performed, and also the timeout.

  8. Save your changes.


On saving a new Web site check (or updating existing), CloudRadar performs an initial test referred to as preflight:

  • If the test is successful, the check is displayed in the list of checks.

    This list is on the Settings page of the host, just below the Add check screen area. If needed, later you can update check's parameters, disable it, or delete it.

  • If the test is unsuccessful, CloudRadar displays a corresponding message.

    The preflight test could fail when the Web resource specified in the check is not available, or when some of the check parameters are incorrect (for example, the search string or the status code). You should check what happened, and decide whether to modify the check, or save it as is.

After the Web site check is defined and saved, CloudRadar would start performing it regularly at the specified interval. Next, you should check if there rules that cover the check you created. If not, you should create a corresponding rule as described in -Creating rules-.