CPUAlert Personal

CPUAlert Personal watches system CPU and RAM usage, sends Email, Microsoft Teams, and Telegram alerts after consecutive High / Low usage checks, alert includeing TOP1-TOP5 process detection, and sends recovery messages when usage returns to normal. Microsoft Teams notification is supported for modern IT operations. No installation required. Edit configuration files and run it in 1 minute.

License and Purchase

Simple, Standalone and No cloud dependency.
No setup. No server. No complexity.
One-time license purchase. No subscription charges.

CPUAlert Personal uses an offline local license file named license.dat.

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

Step 1 - Generate probe.txt

./cpualert -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

./cpualert -licenseinfo

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

Download CPUAlert

Download the correct package for your operating system:

Windows Version Linux Version

Overview

Offline License CPU Monitor Memory Monitor Email Alert Microsoft Teams Alert Telegram Alert IamAlive

CPUAlert Personal is designed for simple server and workstation monitoring where sustained high/low CPU or memory usage needs fast notification.

Recommended for Windows/Linux servers, SQL servers, web servers, remote desktops, branch office PCs, and always-on systems that need simple resource monitoring.

Files Included

File	Description
`cpualert`	Main monitoring program.
`license.dat`	License file. You will receive this after purchasing a license.
`cpualert_setup.txt`	CPU and memory monitoring settings.
`cpualert_email.txt`	SMTP, Microsoft Teams webhook, and Telegram settings.
`cpualert_readme.html`	This readme file.
`cpualert_log.txt`	Runtime log file created by the program.

This package does not include curl.
CPUAlert Personal uses the built-in curl available on modern systems.

Quick Start

Unzip and copy all files into one folder.
Make sure curl is available on this system.
Edit cpualert_setup.txt to define thresholds and intervals.
Edit cpualert_email.txt to define your SMTP, Microsoft Teams webhook, and Telegram settings.
Run ./cpualert -check first to validate config format, then run ./cpualert -test to confirm Email, Microsoft Teams, and Telegram delivery before enabling background mode.
Place your valid license.dat in the same folder.
Open Command Prompt in this folder and run cpualert.

curl --version
./cpualert
./cpualert -check
./cpualert -test
./cpualert -start
./cpualert -status
./cpualert -stop
./cpualert -licenseinfo
./cpualert -probe

Configuration format: key : "value"
Use : as separator. = is not supported by the recommended config standard.

Setup Configuration

Edit cpualert_setup.txt.

hostid : "192.168.1.2 MYSQL DB"
interval : "5"
cpuhighthreshold : "85"
cpuhighnum : "3"
memhighthreshold : "85"
memhighnum : "3"
cpulowthreshold : "15"
cpulownum : "30"
memlowthreshold : "20"
memlownum : "50"

Parameter Description

Parameter	Description
`hostid`	Your label shown in alerts and logs.
`interval`	Check interval in seconds.
`cpuhighthreshold`	CPU high usage threshold percentage.
`cpuhighnum`	Number of consecutive high CPU checks before sending a CPU alert.
`memhighthreshold`	Memory high usage threshold percentage.
`memhighnum`	Number of consecutive high memory checks before sending a memory alert.
`cpulowthreshold`	CPU low usage threshold percentage.
`cpulownum`	Number of consecutive low CPU checks before sending a CPU alert.
`memlowthreshold`	Memory low usage threshold percentage.
`memlownum`	Number of consecutive low memory checks before sending a memory alert.

Email, Microsoft Teams, and Telegram Configuration

Edit cpualert_email.txt.

Microsoft Teams notification is recommended for IT operation teams.
CPUAlert can send alert and recovery messages to a Teams channel through a Power Automate webhook. This is useful when multiple IT staff need to see the same CPU / MEMORY alert 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(telegram group chat id)"

Microsoft Teams Setup

Create a Teams channel for monitoring alerts.
Create a Power Automate flow with a Teams webhook or HTTP request trigger.
Copy the generated webhook URL.
Paste it into teams_webhook in cpualert_email.txt.
Run ./cpualert -check to validate the file format.
Run ./cpualert -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

Parameter	Description
`server`	SMTP server and port. Example: `smtp://smtp.gmail.com:587`
`email`	SMTP login account.
`password`	SMTP password or app password. The program can auto-convert it to encrypted format.
`from`	Sender email address.
`to`	Main alert recipients.
`iamalive`	Daily keep-alive recipient. IamAlive is sent by Email at midnight.
`teams_webhook`	Microsoft Teams / Power Automate webhook URL. Leave blank or mark with `*` if not used.
`token`	Telegram bot token. The program can auto-convert it to encrypted format.
`chat_id`	Telegram 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 team visibility. Telegram is optional.

Alert Behavior

CPU and MEMORY alerts are based on consecutive high/low checks, not a single spike.
Example: if cpuhighthreshold : "85" and cpuhighnum : "3", CPU usage must stay at or above 85% for 3 consecutive checks before an alert is sent.
Example: if memlowthreshold : "50" and memlownum : "30", MEMORY usage must stay at or below 50% for 30 consecutive checks before an alert is sent.
After a HIGH/LOW alert is sent, repeated HIGH/LOW alerts are not sent again and again while the condition stays high/low.
When the value goes back below threshold, a RECOVERY alert is sent.
Midnight IamAlive can be sent to confirm the program is still running.

CPU Usage >= 85% count [1] of [3]
CPU Usage >= 85% count [2] of [3]
CPU Usage >= 85% count [3] of [3]
  TOP1 CPU usage : PID: 3148 %CPU: 5.1 COMMAND: msedgewebview2.exe
  TOP2- PID: 37700 %CPU: 5.0 COMMAND: CrossDeviceService.exe
  TOP3- PID: 27340 %CPU: 3.1 COMMAND: explorer.exe
  TOP4- PID: 3384 %CPU: 2.9 COMMAND:  chrome.exe
  TOP5- PID: 31372 %CPU: 2.8 COMMAND: devenv.exe
Sending email alert ...
Email command rc=0
Sending Microsoft Teams alert ...
Teams command rc=0
Sending Telegram alert ...
Telegram command rc=0

MEMORY Usage >= 85% count [1] of [3]
MEMORY Usage >= 85% count [2] of [3]
MEMORY Usage >= 85% count [3] of [3]
  TOP1 MEM usage : PID: 3148 %MEM: 5.1 COMMAND: msedgewebview2.exe
  TOP2- PID: 27340 %MEM: 3.1 COMMAND: explorer.exe
  TOP3- PID: 134516 %MEM: 3.0 COMMAND: Photos.exe
  TOP4- PID: 141976 %MEM: 1.9 COMMAND: Photos.exe
  TOP5- PID: 37700 %MEM: 1.8 COMMAND: CrossDeviceService.exe
Sending email alert ...
Email command rc=0
Sending Microsoft Teams alert ...
Teams command rc=0
Sending Telegram alert ...
Telegram command rc=0
Wait 30 seconds for next time check .....
CPU Usage >= 85% Still HIGH (alert already sent)
MEMORY Usage >= 85% Still HIGH (alert already sent)

Trial Mode Limits

Item	Trial Limit
Email alerts	2 per day
Microsoft Teams alerts	2 per day
Telegram alerts	2 per day
IamAlive	1 per day

Licensed mode removes the above Trial limits.

Command Reference

Command	Description
`./cpualert`	Run in foreground mode.
`./cpualert -start`	Start in background mode.
`./cpualert -stop`	Stop background process.
`./cpualert -status`	Check whether the monitor is running.
`./cpualert -check`	Validate config file format. Use this first to catch `=` and missing keys.
`./cpualert -test`	Send test Email, Microsoft Teams, and Telegram alerts to verify configuration.
`./cpualert -probe`	Print machine probe information.
`./cpualert -licenseinfo`	Show current license status.
`./cpualert -s`	Silent mode.
`./cpualert -h` / `./cpualert --help`	Show command help and usage summary.

Recommended command flow: edit config, run ./cpualert -check and ./cpualert -test, then use ./cpualert -start for background monitoring.

Recommended Deployment

Install in a fixed folder such as CPUAlert.
Keep cpualert, license.dat, and config files in the same folder.
CPUAlert Personal uses the built-in Windows/Linux curl command for Email, Microsoft Teams, and Telegram delivery.
Use a stable SMTP account.
Test with lower thresholds 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 built-in curl is available by running curl --version.
Review cpualert_log.txt.
Check console output for Email command rc=0 or non-zero return code.

No Telegram Alert

Check token and chat_id.
Ensure the bot has permission to message the target chat or group.
Confirm built-in curl is available by running curl --version.
Check console output for Telegram command rc=0 or non-zero return code.

No Microsoft Teams Alert

Check teams_webhook in cpualert_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 built-in curl is available by running curl --version.
Run ./cpualert -test and check console output for Teams command rc=0.

Alert Sent Too Early

Check cpuhighnum, memhighnum, cpulownum, and memlownum.
These values mean consecutive checks, not total checks since startup.

Still in Trial Mode

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

curl Not Found

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