RMON performs an HTTP(s) check by sending an HTTP or HTTP(s) request to a specified URL address. This process is crucial for ensuring the availability and proper functioning of web services.

RMON also allows users to select the HTTP method for the request in the "HTTP method" field. This enables users to specify whether they want to perform a GET, POST, PUT, DELETE, or other types of requests, depending on the nature of the service being monitored. For instance, a GET request might be used to retrieve data from a web page, while a POST request might be used to submit data to a server. Upon sending the request, RMON waits for a response from the server and evaluates the HTTP status code returned. A status code of 200 indicates that the request was successful and the server is functioning correctly. A warning message may be sent if the response code is anything other than 200.

Please note that the maximum upload size for data during the check is 10 MB.

In addition to monitoring the HTTP status code, RMON also checks the SSL certificate associated with HTTP(s) requests. If the SSL certificate is nearing its expiration date, RMON will send a warning message.

Another valuable feature of the HTTP(s) check is the ability to configure a body response check. This involves sending an HTTP(s) request to the specified address and examining the response body for specific keywords or phrases listed in the "Body response" field. This functionality is particularly useful for ensuring that the content returned by the server meets certain criteria. If the response body does not contain the specified words, RMON will send a warning message.

Additionally, you can specify the maximum number of redirects the system will follow when trying to reach the service in the "Maximum redirects" field.

The check can be created for several countries, regions, or agents at once. To do this, select the desired category in the "Place" field and click + next to the countries/regions/agents for which you want to add the check.

Fill in all the necessary fields, including the "Retries" field, which specifies the maximum number of attempts the system will make to reach the service before it is marked as down and a notification is sent. Additionally, you can specify the runbook in the "Runbook" field to provide a reference guide or set of instructions for troubleshooting the service in case it goes down.

RMON also allows users to configure notifications for alerts about any issues related to HTTP(s) checks by selecting from various channels, including Telegram, Slack, PagerDuty, and/or Mattermost, when adding a new check.

hello@rmon.oi Telegram chat Telegram channel Legal Notes GitHub Help SD