Suricat lets you monitor your website from remote computers. These remote computers host small programs called suricats, which monitor the websites of members of the suricat.eu network. Any malfunction of your site generates an alert that is sent to you (by email or SMS).

1. After registering on suricat.eu, you can request monitoring of your site or web server.
2. Suricats, small software programs installed on our technical platform and on certain network members, regularly connect to your web server and check its operation.
3. In the event of a malfunction, the suricats detect it and send a message to the central platform, which records it.
4. An email or SMS message can be sent to alert you.
5. You can then intervene to restore your service to working order.

• purchasing monitoring tokens
• One monitoring token corresponds to one connection attempt. Therefore, if you want to monitor your website for 60 minutes, making a request every 5 minutes, you will need 60/5 = 12 monitoring tokens.
  
• subscription to the service
Your subscription regularly provides you with a number set of monitoring tokens.
• participation in the Suricat network
• Your participation in the Suricat network allows you to earn monitoring tokens when one of your suricats monitors the network. These tokens are used to monitor your web server.

Note: Monitoring tokens are neither exchangeable nor redeemable for cash. They are linked to your account and cannot be transferred to third parties.

To participate in the Suricat network, you need to download software (the suricat) that you install on a personal computer or server. Downloading a suricat from your user account allows you to link the software to it.

Do not install a suricat from a site other than suricat.eu: the suricat installed on your computer will be working on behalf of a third party.

The suricat.eu network will inform the suricat software of the servers to be monitored. At regular intervals, the software will connect to the indicated sites and check their availability. In the event of a malfunction, it can notify suricat.eu so that the alert is recorded.

A suricat activity report is regularly sent to the suricat.eu site, which calculates their involvement in the network and the number of monitoring tokens earned by the suricats. These are credited to the owner of each suricat (the one who downloaded it from their suricat.eu account).

Your website is monitored by some of the suricats that are currently running. Also, when your computer is off or your suricat is not working, the other suricats on the network monitor your website.

Of course, this only applies if you have monitoring tokens.

When your suricat is not working, you spend your monitoring tokens. You can replenish your account by purchasing tokens, subscribing, or actively participating (with one or more suricats working) in the Meerkat network.

Note: A suricat "farm" on our technical platform also monitors the web servers.

Several ways to Monitoring your website is available on suricat.eu. You can choose the one that best suits your operation or combine them:

• Status monitoring
  This monitoring raises an alert as soon as the HTTP status of your server's response is greater than 400 or equal to 0 (no connection). This type of monitoring is particularly suitable for you if you want to verify that your website is providing a response. This helps rule out server errors, lack of web response, and connection issues.
• Response time monitoring
  This monitoring raises an alert as soon as your website's response time exceeds the limit you set. This type of monitoring ensures that your response is delivered quickly enough to users. The response times recorded here are measured at the suricats software level (and therefore for a panel of end users). Monitoring response times is useful for identifying periods when your website's response speed declines, often indicating congestion on your web platform.
• String search monitoring
  This type of monitoring is preferred when the content of the response is known and is identical for all users. This type of monitoring allows you to verify that your server has returned the expected response. If the expected string is missing, an alert is issued. This monitoring allows us to detect functional malfunctions of the platform.
• monitoring the status of all objects on a page
  This monitoring differs from web page status monitoring in that it identifies the components of a web page and checks the status of all its components (images, CSS, JavaScript, etc.). This advanced monitoring verifies the result as obtained by one of your visitors. This type of monitoring can produce more false positives than simple monitoring, since it is enough for a minor element on the page to have a status higher than 400, or to be unable to be retrieved by the suricat, for an alert to be issued.
• Monitoring based on the response time of a page and all its objects
  This monitoring differs from web page response time monitoring in that it identifies the components of a web page and measures the loading time of all its components (images, CSS, JavaScript, etc.). This advanced monitoring measures the response time as experienced by one of your visitors.