It’s a check of sites and servers by using an ICMP protocol. This check shows the response time of your server. MonitorBot sends 4 requests to your website and marks based on the answer, whether it works or not.
This check may not work if ICMP requests are blocked on the server

This is a verifying of websites over the HTTP/HTTPS protocol and determining their working capacity by the response code of the web server. MonitorBot sends the GET request to the specified URL; as if the user did that, taking into account all of the redirects. If the page loads successfully, the server returns a response code 200. If the status of your site suddenly changes (for example, it becomes 403 or 502) - the system immediately notifies you about it.

With the help of an individual URL, it is possible to send you messages with any text by Telegram (the maximum length of the message sent is 200 characters). You can use this function to inform you of some events.

К примеру, в вашей квартире установлена система умный дом. Вы можете интегрировать произвольные сообщения в систему умного дома и всегда будете в курсе происходящих событий. Кто-то пришел или ушел, система прислал вам сообщение, забыли выключить утюг или воду в ванной, система напомнит вам об этом

MonitorBot checks the time at which the content had been generated by server. Time of content generation is the time from the reception of the request by the server until the transfer of the first byte. This metric is important for determining cases, when the server on which the website is running, significantly reduces its performance. Web search engines use the rate of content returning speed as a ranking factor for search results. The time of content generation also affects the conversion greatly

Critical errors – errors that appears in websites software (known also as «Fatal error», «Warning» or «Notice»). More often, they appear in start of content and corrupt appearance of the site. Main causes of appearing of this type of errors are using of outdated features, missing file or missing variable. These errors need an attention of specialists anyway. MonitorBot checks the presence of this kind of errors and informs about them.

Cyclic redirection is a condition when the requested page redirects query to oneself or to another page that in its turn redirects to first page, closing each other so request is redirecting permanently.
MonitorBot does 7 transitions max, if redirection continues, you’ll receive notification about cyclic redirection.

Main reasons that cause cyclic redirections are incorrect configuration of semantic URL, config files .htaccess, ngx_http_rewrite_module or wrong cookie installation

Redirection to another website is a condition when requested page redirects users request to another site. E.g. for checking URL http://example.com was choosed but you are redirected to http://example1.com. As soon as MonitorBot detects such redirection, it’ll notice you about this.

Redirection to another website may indicate that your site was hacked and users were redirected to another URL. In addition, this can happen if unchecked plugins that redirect to another URL had been installed or if hosting-provider disables website and redirects all users to another site.

In a role of this kind of identifier unique number from Google Analytics code or from Yandex.Metrika or any other code with latin characters, numbers, dash or underscore can be used.

Content/identifier checking helps you to notice website defacement in case of hackers attack or disabling of website by hosting-provider in time.

Сhecks out whether website has been contributed to UNIFIED REGISTER of the domain names, website references and network addresses and whether this site has not been blocked in Russian Federation respectively. This checking is produced by secure way – bot makes request to URL through servers that are located in Russian Federation so in case of blocking original content of website will be unavailable.

MonitorBot monitors over the expiration date of domain name and sends you notices 30, 7 and 1 day before it ends.

Objects are the data repository + triggering. The possible use of objects greatly variates. Objects allow to configure transference and monitoring of arbitrary numerical values – it gives a chance to use MonitorBot for monitoring many different metrics, E.g. to control number of orders, users, balance of funds, number of not processed tickets and much more.

How does it work?
E.g. you want to configure notice on your website if the number of orders exceeded the certain limit. For that, you need to create object, preliminarily stated condition and value for notification. After object had been created you receive unique link, E.g. https://monitorbot.me/mon/HASH/CODE/NAME/[VALUE], on which you need periodically, but not often than once a minute, send value of controlled metric (current number of orders) to MonitorBot.

As soon as condition works out and a number of orders will exceed adjusted limit, MonitorBot notifies you about that.

By adding your URL or object to monitoring you can specify an additional URL. When errors are happening MonitorBot notifies about them and additionally makes GET request to secondary URL, to which adds associative array with monitorbot[] name and information about the problem.
E.g., http://yoururl.com/sitetrouble?monitrobot[site_id]=1&monitrobot[site_url]=http://example.com&monitrobot[site_name]=sitename&monitrobot[timestamp]=1491267840&monitrobot[error_type]=server_code&monitrobot[http_code]=502
This function can be used for any other additional action besides notification about the problem.

Notification type "once" notifies about problem only once and waits for recovery of website’s working capacity. If working capacity was recovered, you will receive notification, that working capacity was restored

Notification type "wait for response" notifies about problems (if they are) once per minute for 30 minutes, after that once per 10 minutes for next 12 hours.
To deactivate notifications about this problem you may press "OK" button after any of notifications

Notification type "no signal" sends no any notifications about problems accordingly and after the working capacity was restored you can know about the problems only through statistics page at the web-panel of MonitorBot

MonitorBot supports group use function

To plug in bot to group you must do that:
- Add MonitorBot to contacts
- Create group
- Find MonitorBot in contacts list and go to profile info
- Click "ADD TO GROUP" button
- Select group that was created by you from the list
- Confirm you choice
- Start to work with the bot by entering /start command

You can monitor your websites and objects collectively when MonitorBot had been added to group. All of the group members will see statistics, notifications. Collective work will help to react on problems more operatively

It happens that MonitorBot sends notification about the problems with website, but when you go in that site, it works in normal state. That may happen in these cases:
- Hoster blocked one of our IP, from which monitoring was carried out;
- Website really was unavailable for a short period. For instance restart of server or updating of software by administrator was made, etc;
- It were malfunctions of internet connection in data-center where website Is located;

This situation may happens by these occasions
- Error may happens in period when MonitorBot wasn’t checking you website. Frequency of checks depends on selected subscribe;
- This error type isn’t included in selected subscribe. If you want MonitorBot to monitor that type of errors you need to switch for suitable subscribe;
- Website isn’t available from your IP only and it works from other addresses and our servers in normal state;

If any of cases isn’t suitable connect our support team then

You can add websites with Cyrillic domain names for monitoring in MonitorBot, they will be converted to punycode automatically

In order to give instructions to the bot, you need to enter a query. The available queries and their description follow below:

✳ Basic commands
/login - generates a PIN code for authorization on the website https://MonitorBot.Me
/lang - changing the language
/support - sending a message to the support team
/pay - activation of the subscribe payment code
/info - shows information about your current subscribe
/message_url - receives a link to send a free message (maximum 200 characters)
/del - deletes your account

✳ URL Monitoring
/add - adding an URL
/list - list of your URLs
/edit - URL editing
/ping - gets the response time and safety of packages
/curl - get connection time and number of redirects
/gen - gets the time of content generation
/exp - gets the expiration time of the domain
/remove - delete an URL

✳ Object Monitoring
/add_obj - adding an object
/list_obj - list of your objects
/edit_obj - editing an object
/obj - get the history of the object
/obj_clear - clears the history of the object
/remove_obj - delete an object

With help of /login command in MonitorBot you can receive disposable pin-code for an authorization in MonitorBot’s web-panel at https://monitorbot.me.
Pin-code is active for 5 minutes – by this time you can authorize in your account. Pin-code deactivates after 5 minutes expired or after successful authorization.

The keychain helps you to bind your social media account to the MonitorBot. So you can to log in using Facebook, VK, Google, Yandex in web-panel at https://monitorbot.me/ instead of log in requesting a pin-code in MonitorBot. To bind your social media account in first place it's necessary to log in with a help ofpin-code and then proceed to keychain page and bind account here.

Not all of registrars of domain names give information about the expiration date of the domain name (or we cannot execute this checking yet). Domain names that have no this info (or we can’t receive it) cannot be checked by expiration date of the domain name because MonitorBot can’t receive it.