Xitoring Document
Home
FAQ
Support
Register
Home
FAQ
Support
Register
  • Xitoring

    • Introduction
    • Release Notes
    • Xitoring Release Notes
    • Linux Xitogent Release Notes
    • Windows Xitogent Release Notes
    • Xitoring Mobile App Release Notes
    • Account Management
    • API Access & Automation
    • Team Management & Collaboration
    • Billing & Subscription Management
  • Getting Started

    • Getting Started with Xitoring
    • Workflows & Guides
    • Monitor Your First Server
    • Import / Migration
    • Migrate from UptimeRobot to Xitoring
    • Migrate from Pingdom to Xitoring
    • Migrate from Uptime.com to Xitoring
    • Migrate from BetterStack to Xitoring
  • Help & Support

    • FAQ & Troubleshooting
    • Glossary
  • Server Monitoring

    • Server Monitoring
    • Graphs
    • Live Statistics
    • Monitor Services
    • Auto-Triggers
  • Xitogent on Linux

    • Install Xitogent on Linux
    • Update Xitogent on Linux
    • Uninstall Xitogent on Linux
  • Xitogent on Windows

    • Install Xitogent on Windows
    • Uninstall Xitogent on Windows
    • Xitogent Service
    • Update Xitogent on Windows
    • Disk Performance (I/O)
  • Xitogent on Azure

    • Xitogent on Azure
    • Monitor Azure Linux VM
    • Monitor Azure Windows VM
  • Xitogent CLI

    • Xitogent CLI
    • Xitogent Pause/Unpause
    • Xitogent Status
    • Xitogent debug
    • Xitogent Diagnosis
    • Which data we collect
  • Xitoring CLI

    • Xitoring CLI
  • Uptime Monitoring

    • What is Uptime Monitoring
    • Monitoring Nodes (Geographic Locations)
    • What is Check
    • Auto-Discovery
    • Auto Fault Tolerance
    • Heartbeat Check
    • Ping Check
    • HTTP(S) Check
    • DNS Check
    • FTP Check
    • SMTP Check
    • IMAP Check
    • POP3 Check
    • TCP Check
    • UDP Check
  • SSL Monitoring

    • SSL Monitoring
  • Incidents

    • Incidents
    • Incident's Root Cause
    • Incidents Notification
    • Incident Notes
    • Resolving Incidents Manually
    • Incident Policy
  • Maintenance Schedule

    • Maintenance Schedule
  • Email Reports

    • Email Reports
  • Integrations

    • Integrations
    • Apache Integration
    • CoreDNS Integration
    • CouchDB Integration
    • Disk Health Integration
    • Docker Integration
    • Dovecot Integration
    • Exim Integration
    • HAProxy Integration
    • IIS Integration
    • InfluxDB Integration
    • Kafka Integration
    • KeyDB Integration
    • LiteSpeed Integration
    • MongoDB Integration
    • MySQL Integration
    • Netstat Integration
    • Nginx Integration
    • OpenLiteSpeed Integration
    • OpenVPN Integration
    • PHP-FPM Integration
    • Postfix Integration
    • PostgreSQL Integration
    • RabbitMQ integration
    • Redis Integration
    • MS SQL Server Integration
    • Supervisor Integration
    • Varnish Integration
    • Wireguard Integration
  • Notifications

    • Notifications
    • Creating Notification Roles
    • Email Integration
    • Mobile Push Notifications
    • SMS Integration
    • Phone call Integration
    • Webhook Integration
    • Integration for Slack
    • Telegram Integration
    • WhatsApp Integration
    • Mattermost Integration
    • Discord Integration
    • Google Chat Integration
    • Microsoft Teams Integration
    • Atlassian Opsgenie Integration
    • Splunk On-Call Integration
    • Pushover Integration
    • Pushbullet Integration
    • Gotify Integration
    • Ntfy Integration
    • Spike.sh Integration
    • PagerDuty Integration
    • Zapier Integration
    • AlertOps Integration
  • Status Page

    • Status page
  • 3rd Party Status Pages

    • Using 3rd party Status Pages
    • Atlassian Status Page Integration with Xitoring
    • Status.io Integration with Xitoring
    • Statuspal Integration with Xitoring
    • Instatus Integration with Xitoring
  • Dashboards

    • Main Dashboard
    • Custom Dashboards
  • Metrics

    • Metrics
  • MCP Server

    • Setup & Tool Reference

Ping Check

Ping check is a basic and simple monitoring method that checks the availability of a network device, such as a server or a router. Xitoring uses Ping check to monitor the availability of network devices by periodically sending a small packet of data (known as a Ping) to the device and waiting for a response.

During a Ping check, Xitoring measures the response time, or latency, of the Ping to determine if there is any delay in the device's response. If the device responds within a specified time frame, Xitoring considers the device to be available. If the device fails to respond or responds after a certain threshold, Xitoring considers the device to be unavailable or experiencing connectivity issues.

Ping check is a critical monitoring method used to detect network issues, such as network connectivity problems. By monitoring Ping responses, Xitoring can detect and alert the IT team in real time if there is an issue with a device's availability or connectivity.

Create a Ping Check

Creating a Ping check is very easy as the required fields are few and easy to configure. you have two main parts to create a Ping check, Check Options and Trigger Options in this section both parts and their files will be broken down into details for better understanding.

Check Options

Type

From the list of available check types Ping will be selected.

Related Server

As in Xitoring, there are Server checks and independent checks, you can Create a check and assign it to a Server so it will count as one of the checks of a specific server. this option also can be changed or edited later.

So the list will contain a list of registered servers that the user can assign the check to them.

Hostname

The hostname is the address of the Ping check, it can be an IPv4 or IPv6 address or a domain name, you can see examples of each of them in the following box:

IPv4
107.45.66.2

IPv6
fe80::a510:68bd:7405:1869

Domain
xitoring.com

If domains are used it has to be plain domain without http or https

Check Label

Users can choose a name for the check that is being created using this field, Check label can contain characters, space, and numbers. Special characters are not allowed in the check label section.

Group

The next option is Group. Xitoring has an advanced Group/Sub-Group management system so users can sort and organize Checks and Server, For example, some users organize their assets based on location and create Groups for countries and Sub-Groups for Cities. it can help see the records for a specific part of your assets easily.

Using the gear icon next to the title, you can access the Group management mini tool, the user can create, delete and edit groups and sub-groups.

Interval

Interval sets how often probing nodes will make their requests to your URL, 1 minute will provide the most detailed, accurate, reports and notifications. Also For some services, the Higher interval makes more sense. So you can configure Xitoring to Check your Ping Check status every minute or you can make it check every 10 minutes.

Trigger Options

The most important part of creating a check is Trigger options Triggers will define the incident status of a Check.

Notification Roles

In this section user can assign one or more notification roles to this check trigger, it will define who gets notified and how every time this check has an incident. For Example, the user has two notification roles one for the IT team that contains the Email and phone numbers of the team members, and one notification role for the CTO. Users can configure the trigger to notify the IT team and the CTO in time of an incident using Email and SMS notifications.

Fault Tolerance

Fault tolerance is a time value (Minutes) that determines how much stress can a system take before it's entering a critical state. If you set FT to 5 we send an incident report when the incident is existing for 5 minutes. A more accurate example is provided in the Packet loss section.

Packet loss

Ping packet loss refers to the percentage of Ping packets that are sent from a device to a network destination but fail to reach their destination. Packet loss can occur due to network congestion, hardware failure, or connectivity issues. in the Packet loss.

For example, User wants to get notified of an incident if the Ping check returned a 50% packet loss record for 5 minutes. then the Fault tolerance needs to be set to 5 and the packet loss section set to 50.

Tips

The Run Test button can be used to either determine the current status of the check or make sure that the entered information is correct.

Last Updated: 5/22/23, 2:47 PM
Prev
Heartbeat Check
Next
HTTP(S) Check