Ping Monitor / Ping Monitor (EUM)
Creating a new Ping monitor
Using the REST API to add a new Ping monitor / Ping monitor (EUM):Click here
To create a Ping monitor, follow the steps given below:
- Click on New Monitor link. Choose Ping Monitor / Ping Monitor (EUM) under 'Services' category.
- Specify the display name of the monitor.
- Provide Host Name / IP Address.
- Enter the Timeout value for the monitor in seconds.
- Specify the Polling Interval for the monitor in minutes.
- If you are adding a new monitor from an Central Server, select a Probe Server.
- Select the Monitor Group with which you want to associate the monitor to, from the combo box (optional). You can choose multiple groups to associate your monitor.
- Associate the monitor instance to the agent. *
- Enable Run on Server option to run the ping monitor in the local instance of Applications Manager.
- Enable Run on Agent option to run the ping monitor from multiple locations. Select the necessary agents from where you want this monitor to be executed. This option will be available only if you enable the EUM add-on.
- Click Add Monitor(s). This adds the Ping monitor and the monitoring will be started as per the polling interval configured.
Note: - Security/Firewall Requirements - The Host/IP address should be accessible from the machine where Applications Manager is installed.
Note:
* This is only for Ping Monitor (EUM) servers.
In some cases, Applications Manager may not provide the expected metrics output due to incorrect responses for non-English OS. To get the expected output, regex support is available for Ping Monitor. The user needs to customize the output in a property file based on the language. The user can define ping response for metrics like Packet Stats and Round Trip Time for different languages. To do so, create a properties file named ping.properties and place it under <Applications Manager Home>/conf directory (or under the <EUMAgent>/conf in case of agent-based Ping monitor). The user can understand the response pattern of the ping request and can customize it by using the same patterns as in the properties file. Following is the sample contents used in the Italian version of the ping.properties file:
################################ Windows properties #####################################
#Windows Status poll matcher String.
ReplyFrom=Risposta da
bytes=byte
#Windows ResponseTime String. Ex: Minimum or Maximum or Average.
Windows_ResponseTime=Medio
#Windows Packet Sent matcher String.
Windows_PacketSent=Trasmessi
#Windows Packet Received matcher String.
Windows_PacketReceived=Ricevuti
#Windows Packet Loss matcher String(case sensitive).
Windows_PacketLoss=persi
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Ping Monitor or Ping Monitor (EUM) available in the Services section. Displayed is the Ping monitor's bulk configuration view distributed into three tabs:
- Availability tab gives the availability history for the past 24 hours or 30 days.
- Performance tab gives the health status and events for the past 24 hours or 30 days.
- List view tab enables you to perform bulk admin configurations.
Applications Manager uses Ping Monitor to track if the particular host / IP address is accessible or not. It checks for availability of a device, server or network device. Following are the parameters monitored in the Ping monitor:
| Parameter | Description |
|---|
| PACKET STATISTICS |
| Packet Loss | Amount of packets that failed to reach the destination (in percentage). |
| Packets Sent | Number of packets sent. |
| Packets Received | Number of packets received. |
| ROUND TRIP TIME |
| Round Trip Time | Time taken for each packet exchange (in milliseconds). Ping places a timestamp in each packet, which is echoed back and is used to compute how long each packet exchange took. |
