Endpoint Operations Management allows the user to monitor a particular application resource or a service from various geographies.

You can configure remote monitoring using the following methods:

• HTTP
• ICMP
• TCP

When you configure a remote HTTP, ICMP or TCP check, it is created as a child object of the tested object that you are monitoring and of the monitoring agent.

A remote check can be configured on the Operating System and the Endpoint Operations Management Agent object type.

Here are a few examples where the remote checker can be used:

• Let's say there is an application server that runs in Buffalo. The same Tomcat server also provides services to Cork and Munich. This is a perfect use case for remote check. You can configure a remote check of the application service that resides in Buffalo from Cork and Munich.
• Let's say you configured the ICMP test. Now, if the communication between the sites is broken, the remote check should fail and the same would be visible in vRealize Operations in the form of alerts and symptoms.
• Remote check is an option to monitor an object without having an agent installed on it.

Let's configure an example check.

Perform the following steps to configure an ICMP check:

1. In vRealize Operations, navigate to the object (server) you want to monitor.
2. Click Actions and select Monitor this Object Remotely.
3. Fill in the following information for the ICMP check:
   • Display Name: Enter a display name for the check
   • Monitored From: Select the system from which the check will be displayed
   • Check Method: Select ICMP check
   • Hostname: Type the FQDN or IP of the object which the check will be performed against

In this example, the server I selected in Monitored From and the server I entered in Hostname are in two different geographical locations:

If you take a look at the All Metrics tab of the object again, you will notice that now, the object relationship shows the remote checker as well.