Internal Ping Check using LM Uptime

Internal Ping Checks are performed by LM Collectors within your network to verify that a hostname or IP address is accessible to users on your network.

Requirements for Creating Internal Ping Checks using LM Uptime

To create internal ping checks, you need the following:

• LM Uptime license edition
• A user with “Manage” permission for Resources.
  For more information, see Resource Role Permissions.

Creating Internal Ping Checks using LM Uptime

1. In LogicMonitor, navigate to Resource Tree >  > select Internal Ping Check.
2. Select the Basic tab and do the following:
   1. In the Name field, enter a name for the Ping Check.
   2. In the Description field, enter a description for the Ping Check. For example, you could describe the scope and purpose of the Ping Check.
   3. Select from the existing group list where the Ping Check should belong from the Where should it be placed? dropdown menu. By default, the root (top-level) website group is selected.
   4. In the Properties table, add the relevant properties. For example, add http.port with the value 80.
      
3. Select the Settings tab and do the following:
   1. In the Host Name or IP field, enter the host name or IP address to which the ping test is sent.
   2. Select the number of packets to send for the Ping Check from the Number of Packets to Send dropdown menu. LogicMonitor defaults to five packets, but you can choose to send up to 50. Packets are sent one by one, with a delay of 250 milliseconds between each packet.
      
4. Select the Checkpoints tab and then specify the Collectors that send the checks. The Use Default Website Settings switch is selected by default.
   Note: Your user account must have Collector view permissions to view and select Collectors from this area of the dialog. For more information, see Roles.
   
5. Select the Alert Triggering tab and do the following:
   1. Toggle the Use Default Alert Settings switch to use the recommended default settings. 
       Important: If you want to customize and not use the default settings, you need ‘Resources: Group Threshold’ permission. For more information, see Access Group Permissions.
   2. Select how often the designated checkpoints will ping the host name or IP address from the Number of Packets to Send dropdown menu. You can choose from frequencies that range from once a minute to once every 10 minutes.
   3. In the Check whether (X)% of those packets are returned in (X) ms field, select the percentage of packets that must be returned and the designated time period (milliseconds) for the check to be deemed successful.
      Packets are sent one by one, with a delay of 250 milliseconds between each packet. For example, if you leave the default of five packets in the Number of Packets to Send field, it will take 1000 milliseconds (1 second) to deliver all five packets.
      Note: These two fields technically operate independently of each other. If either criterion is not met, the check is considered a failed check. For example, any returned packet takes longer than the minimum allowed return time or the number of packets returned is less than the minimum percentage threshold.
   4. Select the number of consecutive checks that must fail in order for an alert to be triggered from the After X failed checks dropdown menu.
   5. From the At X test location and trigger X dropdown menus, select the location and severity of the alerts respectively. You can select the location and severity of multiple or one selected alert. 
      
      For more information on the different scenarios on alert generation, see Website Data Alerting for LM Uptime.
6. Select Save.

The internal ping check is added to the resources.