How to Configure HSLAB HTTP Monitor Ping HSLAB HTTP Monitor is a reliable software solution designed to track the uptime, availability, and response performance of websites, network services, and server infrastructure. One of its most fundamental deployment tasks is setting up an ICMP-based check—commonly referred to as a Ping Monitor—alongside its web-based tracking tools. This configuration allows you to separate network-layer accessibility issues (Layer 3) from application-layer software failures (Layer ⁄7).
The following step-by-step guide walks you through the configuration process to ensure accurate, real-time alerts. 1. System Requirements & Prerequisites
Before starting the configuration, verify that you have met the necessary infrastructure baselines:
Administrative Privileges: Ensure you are logged into the host operating system or the HSLAB control panel with full administrative rights.
Network Permissions: Confirm that outbound Internet Control Message Protocol (ICMP) echo requests are permitted.
Firewall Exceptions: Update local and perimeter firewalls to let the HSLAB service send ping packets without being throttled or blocked as a false positive security threat. 2. Step-by-Step Ping Monitor Configuration
To deploy a new ping active check within the application environment, complete the following parameters sequentially: Step 1: Initialize the Monitor Entry Open the HSLAB HTTP Monitor main dashboard interface.
Navigate to the Monitors or Settings Library tab on the navigation tree.
Click Add New (or the + icon) and select Ping Monitor from the active target type selector. Step 2: Define Core Properties
Name: Provide a distinct, human-readable identifier for your target (e.g., Core_Web_Server_Ping).
Description: Add internal notes specifying the machine’s role or hosting provider for faster incident sorting.
Host Address: Enter either the precise IPv4/IPv6 address or the Fully Qualified Domain Name (FQDN) of the remote resource. Step 3: Optimize Network and Performance Thresholds
Adjust the lower operational bounds to prevent false alarms while maintaining visibility over network performance degradation: Recommended Value Functional Purpose Timeout 2000 ms to 5000 ms
The maximum duration HSLAB waits for an echo reply before logging a connection drop. Retries 2 or 3 consecutive drops
The number of failed attempts allowed before escalating the node’s status to an “Offline” alert state. Payload Size 32 bytes to 64 bytes
Standard ICMP packet data size. Do not exceed 1472 bytes to avoid packet fragmentation. Check Interval 60 seconds
The frequency at which the monitor repeats the ping operation. Step 4: Finalize and Apply How to configure a ping active monitor – Progress Community
Leave a Reply