Monitoring & Restoration Service
Server administration is a task with a very heavy workload. Not only do you have to grasp the status of the server operating 24 hours a day, 365 days a year, you must also respond promptly in the event of failures. Our Monitoring Option lightens such burdens on server administrators. Let GMO Cloud - with our extensive operational experience in monitoring and first-rate response capabilities - take care of these tasks for you!
- Scope & Pricing
- Technical Details
Service Scope
We provide monitoring, first-level recovery, and reporting services for your virtual machines.
| Connection Monitoring | Monitors network reachability to the target device using ping tests. |
|---|---|
| Port Monitoring | Applies to the Monitoring and First-level Recovery Service. |
| Monitoring and First-level Recovery Service | Response to alerts triggered from the Connection Monitor and Port Monitor processes. We notify you by email and restart the server. |
| Reporting | We report the operational status of your virtual machines by email once per month. |
(*) OS templates that may be used are limited to CentOS (excluding beta versions).
(*) In order to monitor from a local network, the local network must be added to the virtual machine.
(*) Establishing the surveillance recovery option requires about 2~3 business days.
Pricing
| Setup Fee | Free |
|---|---|
| Monthly Fee | $100.00 per virtual machine |
(*) It is necessary for the customer to obtain SSL certification themselves or order through the Cloud Portal. Acquisition expenses incur separate fees.
Service Restart Scripts
In the event of errors detected by monitoring, the following scripts will be used to stop, then start services for each port. Scripts under /etc/rc.d/init.d will be used, and first-level recovery is not possible for services that cannot be restarted by this process.
| Service / OS | CentOS 5.5 / 5.7 LAMP | CentOS 5.5 PLESK | CentOS 5.5 HDE |
|---|---|---|---|
| FTP (21) | vsftpd | xinetd | vsftpd |
| SSH (22) | sshd | sshd | sshd |
| SMTP (25) | postfix | xinetd | postfix |
| DNS (53) | named | named | named |
| HTTP (80) | httpd | httpd | httpd |
| POP (110) | dovecot | courier-imap | courier-imap |
| IMAP (143) | dovecot | courier-imap | courier-imap |
| HTTPS (443) | httpd | httpd | httpd |
| MySQL (3306) | mysqld | mysqld | mysqld |
| PostgreSQL (5432) | postgresql | postgresql | postgresql |
(*) The corresponding OS are: CentOS 5.5 LAMPP x64, CentOS 5.5 LAMPP x86, CentOS 5.5 Plesk x64, CentOS 5.5 Plesk x86, CentOS 5.5 HDE Controller 6 x64, CentOS 5.5 HDE Controller 6 x64, and CentOS 5.7 LAMP x86.
Services Monitoring
The following list of services are monitored in 5 minute intervals, and we notify you with an alert when a status other than "OK" results 4 consecutive times. Also, as a means of disaster recovery, actions starting from restarting of each individual service (daemon) up to restarting of the server will be conducted by us on your behalf.
| Monitored Item (*1) | Status | Monitoring Method |
|---|---|---|
| FTP (21) | OK | Able to connect to the port. |
| WARNING | Able to connect to the port, but the response took between 6-11 seconds. | |
| CRITICAL | The port is down, or the connection has been denied. | |
| SSH (22) | OK | Able to connect to port 22, and the header contains the string "SSH". |
| WARNING | N/A | |
| CRITICAL | The port is down, or the connection has been denied. | |
| SMTP (25) | OK | Able to connect to SMTP port (25), and a response was received. |
| WARNING | Able to connect to SMTP port (25), but the response time exceeded 5 seconds. | |
| CRITICAL | The port is down, or the connection has been denied. | |
| DNS (53) | OK | Forward lookup from the server resulted in proper name resolution. |
| WARNING | Forward lookup from the server resulted in a response time exceeding 5 seconds. | |
| CRITICAL | No response from the DNS server. | |
| HTTP (80) | OK | Able to connect to ports 80 and 443, and received a response to the "GET/HTTP/1.0" request. |
| WARNING | Able to connect to ports 80 and 443, but the response time to the "GET/HTTP/1.0" request exceeded 5 seconds. | |
| CRITICAL | The port is down, or the connection has been denied. | |
| POP (110) | OK | Able to connect to the port. |
| WARNING | Able to connect to the port, but the response took between 5 seconds. | |
| CRITICAL | Unable to receive a response from the port for more than 11 seconds, or the port is down. | |
| IMAP (143) |
OK | Able to connect to the port. |
| WARNING | Able to connect to the port, but the response time exceeded 5 seconds. | |
| CRITICAL | The port is down, or the connection has been denied. | |
| HTTPS (443) |
OK | Able to connect to ports 80 and 443, and received a response to the "GET/HTTP/1.0" request. |
| WARNING | Able to connect to ports 80 and 443, but the response time to the "GET/HTTP/1.0" request exceeded 5 seconds. | |
| CRITICAL | The port is down, or the connection has been denied. | |
| MySQL (3306) |
OK | Able to connect to the port. |
| WARNING | Able to connect to the port, but the response took between 6-11 seconds. | |
| CRITICAL | The port is down. | |
| PostgreSQL (5432) |
OK | Able to connect to the port. |
| WARNING | Able to connect to the port, but the response took between 6-11 seconds. | |
| CRITICAL | The port is down. |
(*1) To be carried out when abnormal conditions continue for more than 20 minutes. The services listed above are monitored for ping test results in 5 minute intervals, and we notify you with an alert when the same status results 4 consecutive times. Also, as a means of disaster recovery, actions up to restarting of the server will be conducted by us on your behalf.
(*) If you have configured features such as Basic Authentication for the Web server, monitoring port 80 at Layer 7 may return a 401 error. In such cases where the existing environment is not suited for monitoring, it is possible to switch to monitoring at Layer 4.
Ping Monitoring / First-level Recovery
| Connection Monitoring | Status | Monitoring Method |
|---|---|---|
| ICMP | OK | Average response time less than 100 (ms), and packet loss less than 20%. |
| WARNING | Upon sending 5 packets, average response time between 100 (ms) and 300 (ms), or packet loss between 20% to 60%. | |
| CRITICAL | Average response time exceeding 300 (ms), or packet loss over 60%. |
(*) Ping test results are monitored in 5 minute intervals, and we notify you with an alert if the same status results 4 consecutive times. Also, as a means of disaster recovery, actions up to restarting of the server will be conducted by us on your behalf.
