PingAlert Standalone Lightweight Monitoring

Email + Microsoft Teams + Telegram Notification for SMB IT Operation.
Workers / Parallel Checking multiple hosts in parallel using worker threads. This is useful to monitor many devices, routers, servers, or branch endpoints.
Standalone lightweight ping monitoring software for Windows/Linux, designed as an economical and practical monitoring tool for small and middle business IT teams. PingAlert checks whether important hosts are alive, sends Email, Microsoft Teams, and Telegram alerts when a host becomes unreachable, and sends a recovery message when the host is restored. Microsoft Teams notification makes it suitable for team-based. No installation required. Edit configuration files and run it in 1 minute.

License and Purchase

Standalone Lightweight monitoring for small and middle business.
No setup. No server. No complexity.
One-time license purchase. No subscription charges.

PingAlert Standalone uses an offline local license file named license.dat.

Recommended customer flow:
Download ZIP → Test PingAlert → Generate probe.txt → Purchase License → Send probe.txt → Receive license.dat → Run production monitoring

Step 1 - Generate probe.txt

pingalert -probe > probe.txt

This command generates the machine information required for license creation.

Step 2 - Purchase License

To purchase or renew your license, please visit:
https://www.smartbooth.com/purchase_lic.htm

Step 3 - Send probe.txt

Email your generated probe.txt to:

service@smartbooth.com

A matching license.dat will then be prepared for your machine.

Step 4 - Verify License

pingalert -licenseinfo

This command displays current license mode, customer, expire date, and machine matching result.

Download PingAlert

Download the correct package for your operating system:

Overview

Designed for Small and Middle Business Multi-threading Support Offline License Email Alert Microsoft Teams Alert Telegram Alert Recovery Notice IamAlive

PingAlert Standalone Lightweight is designed for simple, affordable, and reliable monitoring of websites, remote servers, routers, internal devices, firewalls, VPN endpoints, and office network hosts for small and middle business environments.

Recommended use cases: website availability monitoring, office gateway monitoring, branch network device monitoring, server host alive check, small business IT monitoring, and simple NOC-style alerting.

Files Included

FileDescription
pingalert.exe / pingalertMain monitoring program for Windows/Linux.
license.datLicense file. You will receive this after purchasing a license.
pingalert_host.txtHost monitoring settings.
pingalert_email.txtSMTP, Microsoft Teams webhook, and Telegram settings.
pingalert_log.txtRuntime log file created by the program.
This package does not include curl.
PingAlert uses the built-in curl available on modern Windows/Linux systems.

Quick Start

  1. Unzip and copy all files into one folder.
  2. Make sure curl is available on this Windows/Linux system.
  3. Edit pingalert_host.txt to define the hosts and worker count you want to monitor.
  4. Edit pingalert_email.txt to define your SMTP, Microsoft Teams webhook, and Telegram settings.
  5. Run pingalert -check first to validate config format, then run pingalert -test to confirm Email, Microsoft Teams, and Telegram delivery before enabling background mode.
  6. Place your valid license.dat in the same folder.
  7. Open Command Prompt in this folder and run pingalert.
curl --version
pingalert
pingalert -check
pingalert -test
pingalert -start
pingalert -status
pingalert -stop
pingalert -licenseinfo
pingalert -probe
Configuration format: key : "value"
Use : as separator. = is not supported by the recommended config standard.

Host Configuration

Edit pingalert_host.txt.

interval : "15"
fast_retry_interval : "5"
pingcount : "2"
workers : "2"

host : "192.168.3.3"
description : "Internal Server"
timeoutsec : "5"
alertcount : "3"
pinglossmsg : "default"
pingbackmsg : "default"
tcpfallback : "yes"

* Marked to skip monitoring. Remove * to enable.
*host : "8.8.8.8"
*description : "google dns"
*timeoutsec : "5"
*alertcount : "3"
*pinglossmsg : "google dns down"
*pingbackmsg : "google dns back"
*tcpfallback : "no"

Parameter Description

ParameterDescription
intervalNormal check interval in seconds.
fast_retry_intervalShorter retry interval used when one or more monitored hosts are in failure state.
pingcountNumber of ping attempts to make for each host.
workersNumber of hosts checked at the same time. Default is 2. Maximum safe limit is 50.
hostHost name or IP address to monitor.
descriptionYour note for this target.
timeoutsecPing timeout for each check.
alertcountNumber of consecutive failures before sending a DOWN alert.
pinglossmsgCustom DOWN alert text. Use default for built-in wording.
pingbackmsgCustom RECOVERY alert text. Use default for built-in wording.
tcpfallbackyes to try TCP fallback when ping is blocked. no to disable fallback.

Workers / Parallel Checking

PingAlert still runs as one background process, but it can check multiple hosts in parallel using worker threads. This is useful when a small or middle business needs to monitor many devices, routers, servers, or branch endpoints.

workers : "2"
SettingRecommended Use
workers : "2"Default setting. Good for trial mode and small monitoring lists.
workers : "5" to "10"Good for small and middle business networks with more devices.
workers : "50"Maximum safe limit. Use only when the monitoring machine and network can handle many checks at once.
If workers is not set, PingAlert uses the default value 2. The -check command will show: Info: workers not set, default workers:2 will be used.

Email, Microsoft Teams, and Telegram Configuration

Edit pingalert_email.txt.

Microsoft Teams notification is recommended for small and middle business IT operation monitoring.
PingAlert can send DOWN and RECOVERY alerts directly into a Teams channel through a Power Automate webhook. This allows all IT staff to see network outage alerts immediately.
* This is the configuration file for Email, Microsoft Teams, and Telegram alerts.

*** Email alert setting
server : "smtp://smtp.gmail.com:587"
email : "your@gmail.com"
password : "your_app_password"
from : "your@gmail.com"
to : "admin1@hotmail.com,admin2@yahoo.com"
iamalive : "admin1@hotmail.com"

*** Microsoft Teams notification. Remove * to enable.
*teams_webhook : "https://your-power-automate-webhook-url"

*** Telegram notification. Remove * to enable.
*token : "your telegram bot token"
*chat_id : "-123456789"

Microsoft Teams Setup

  1. Create a Teams channel for network monitoring alerts.
  2. Create a Power Automate flow using a Teams webhook or HTTP request trigger.
  3. Copy the generated webhook URL.
  4. Paste the URL into teams_webhook in pingalert_email.txt.
  5. Run pingalert -check to validate configuration format.
  6. Run pingalert -test to verify Email, Microsoft Teams, and Telegram delivery.
Teams webhook URLs are usually very long and may include query values such as api-version=1, sv=1.0, and sig=.... Keep the full URL on one line inside double quotes.

Parameter Description

ParameterDescription
serverSMTP server and port. Example: smtp://smtp.gmail.com:587
emailSMTP login account.
passwordSMTP password or app password. The program can auto-convert it to encrypted format.
fromSender email address.
toMain alert recipients.
iamaliveDaily keep-alive recipient. IamAlive is sent by Email at midnight.
teams_webhookMicrosoft Teams / Power Automate webhook URL. Leave blank or mark with * if not used.
tokenTelegram bot token. The program can auto-convert it to encrypted format.
chat_idTelegram chat ID or group ID.
Gmail with App Password is recommended because it is easy to set up, fast, and reliable for sending alert emails. Microsoft Teams is recommended for IT operation team visibility.

Alert Behavior

  • When a monitored host fails continuously and reaches alertcount, a DOWN alert is sent.
  • After a DOWN alert is sent, the internal failure counter is reset.
  • Before the host recovers, repeated DOWN alerts are not sent again and again.
  • When the host becomes reachable again, a RECOVERY alert is sent.
  • Daily IamAlive can be sent to confirm the program is still running.
  • If tcpfallback : "yes", PingAlert may treat a host as alive when ICMP ping is blocked but TCP still responds.
[192.168.3.3] Ping Timeout... 192.168.3.3 received=0/4 count 3/3

Sending email alert ...
Email command rc=0

Sending Microsoft Teams alert ...
Teams command rc=0

Sending Telegram alert ...
Telegram command rc=0

Trial Mode Limits

ItemTrial Limit
Email alerts2 per day
Microsoft Teams alerts2 per day
Telegram alerts2 per day
IamAlive1 per day
Monitoring targetsMaximum 2 hosts
Default workers2 workers
Licensed mode removes the above Trial limits. Worker count can be increased up to the maximum safe limit of 50.

Command Reference

CommandDescription
pingalertRun in foreground mode.
pingalert -startStart in background mode.
pingalert -stopStop background process.
pingalert -statusCheck whether the monitor is running.
pingalert -checkValidate config file format. Use this first to catch = and missing keys.
pingalert -testSend a test Email, Microsoft Teams, and Telegram alert to verify configuration.
pingalert -probePrint machine probe information.
pingalert -licenseinfoShow current license status.
pingalert -sSilent mode.
pingalert -h / pingalert --helpShow command help and usage summary.

Recommended command flow: edit config → run pingalert -check → run pingalert -test → use pingalert -start for background monitoring.

Recommended Deployment

  • Install in a fixed folder such as C:\PingAlert.
  • Keep pingalert, license.dat, and config files in the same folder.
  • PingAlert Standalone Lightweight uses the built-in Windows/Linux curl command for Email, Microsoft Teams, and Telegram delivery.
  • Use a stable SMTP account.
  • Test one invalid host first to verify Email, Microsoft Teams, and Telegram alerts are working correctly.

Troubleshooting

No Email Alert

  • Check SMTP server, account, password, and firewall rules.
  • Confirm Windows/Linux built-in curl is available by running curl --version.
  • Review pingalert_log.txt.

No Telegram Alert

  • Check token and chat_id.
  • Ensure the bot has permission to message the target chat or group.
  • Confirm Windows/Linux built-in curl is available by running curl --version.

No Microsoft Teams Alert

  • Check teams_webhook in pingalert_email.txt.
  • Make sure the webhook URL is complete, on one line, and enclosed in double quotes.
  • Confirm the Power Automate flow run history shows success.
  • Confirm Windows/Linux built-in curl is available by running curl --version.
  • Run pingalert -test and check console output for Teams command rc=0.

Host Still Looks Alive

  • Check whether tcpfallback is enabled.
  • If you want pure ping-only behavior, set tcpfallback : "no".

Still in Trial Mode

  • Confirm license.dat is in the same folder as pingalert.
  • Run pingalert -licenseinfo to check the reason.

curl Not Found

  • This package does not include curl.
  • Run curl --version in Command Prompt.
  • If curl is not available, use a Windows/Linux version that includes built-in curl.