Uptime Monitoring (NodePing)
Posted by on 05 September 2019 05:21 PM
Applicable Plans - Virtual Cloud Servers, Virtual Machines, and Platform as a Service (PaaS) environments
Using the Uptime Monitoring (NodePing) Service
Uptime Monitoring allows you to set up monitoring checks for any port or URL of your eApps server, or any server anywhere, from multiple remote locations. Alerts can be configured to notify individuals or groups, that you define, whenever a remote check fails. This service works for all Virtual Cloud Servers, Virtual Machines, and Platform as a Service (PaaS) environments.
Creating Monitors for Your Server
Creating Monitoring Checks for Your Server
In order to create monitors for your server, you will need to do the following:
A Contact is an e-mail address that alerts from the monitoring service will be sent to. A Contact can also be added to a Contact Group (covered below). Contacts must be created before any Contact Groups.
Adding a Contact
Available Contact Methods
A Contact Group allows you to designate which contacts get notified in the event of a certain kind of alert from the monitoring service. For example, you could have a Contact Group called "Webmaster" that contains the contacts for your web development team who would get notified if there was a problem with the website, and a Contact Group called "System Admin" that contains the contacts for your system and network administrators team who would get notified if there was a problem with the Virtual Server or network. You can have any number of Contact Groups in your account, and Contact Groups can have any number of Contacts.
Creating Contact Groups
Adding a Contact Group
Creating Monitoring ChecksAfter adding Contacts and (optionally) Contact Groups, you can create a Monitoring Check.
Check Label - a label to identify the check. This is what will appear when viewing Monitoring Checks in your customer portal.
Enable Check - enable or disable the Monitoring Check
Region - where you want to check your service from. For example, if your server is in North America but you have several customers in Asia, it may be a good idea to configure the region as Asia. This way you will be alerted when that region is unable to reach your server.
Check Frequency - how often the service should be checked. If this is a critical application we recommend checking every minute. For less critical components, you may set up less frequent checks.
URL - The URL that you want to monitor
Timeout - how long to wait before the check is considered a failure
Sensitivity - how soon you want the Monitoring Check to try again after a failure.
Dependency - it is common to have a server hosting multiple services and applications. When you set up a Monitoring Check as a dependency of another, you will only get an alert for the parent Monitoring Check. This means if you have set up a ping check as a dependency of two other checks (MySQL, HTTP) and the server goes down, you will only get an alert for the ping check failing instead of all three failing
Notify - The Groups and/or Contacts you want to receive the Alerts
Delay - Polling interval for the monitor
Schedule - Time period for receiving alerts that you assign to a Contact or Group. The schedule defaults are as follows:
Custom Monitoring ChecksIf you need a Monitoring Check that is not supported, our technicians can create a custom one for a fee. Contact firstname.lastname@example.org for more information.
ReportsYou can view a history of alerts for a given check as well as uptime reports for each check you have configured.
UptimeThe uptime report will display graphs to track your server's uptime over time.
HistoryThe history will show you the results of every single check done on the server. You can use this together with the uptime graphs to track when your service goes down and for how long.