Browser monitoring
Server Monitor for Chrome and Firefox
Use Chrome or Firefox as an additional monitoring interface for the same Linux agent and backend used by the Telegram bot.
Product
A browser extension alongside the Telegram bot
Server Monitor from Chrome or Firefox is a second client for the existing monitoring service. Telegram remains available for alerts and operational chat. The extension gives a compact browser dashboard for servers already paired through the backend.
Architecture
Same backend, same Linux agent, separate interface
The extension does not connect to servers directly, does not use SSH, and does not execute shell commands. It calls server.howprog.one over HTTPS, reads the same server records, metrics, alert state and thresholds, and shows them in the browser popup.
Setup flow
Install the agent first, then connect the extension
The Linux agent is still the first step. Get a PAIRING_TOKEN, run the install command on the server, wait for the agent to register, then install the Chrome or Firefox extension and enter the same PAIRING_TOKEN.
curl -fsSL https://server.howprog.one/agent/install.sh -o install.sh
sudo bash install.sh --api https://server.howprog.one --pair PAIRING_TOKENChecks
What the browser extension can show
- Online/offline state and last heartbeat.
- Hostname, OS and kernel info when available.
- CPU, RAM, disk, inode usage and load average.
- Uptime and recent metrics timestamp.
- SSL certificate days left when the agent discovers web domains.
- Detected systemd service state when reported by the agent.
- Active alerts and alert severity.
Notifications
Browser notifications for active alerts
The background worker polls the extension alerts API and shows browser notifications for new active alerts. It stores notified alert IDs locally to avoid duplicate notification spam. Browser notifications require Chrome or Firefox to be running; Telegram is still better for urgent 24/7 alerts.
Downloads
Download developer builds
- Download Chrome developer build.
- Download Firefox developer build.
- View extension version.json.
- Chrome Web Store and Firefox Add-ons links are not published yet. Use local developer installation for now.
Security
Security model for browser monitoring
- No SSH password is required.
- No direct SSH session is opened by the extension.
- No arbitrary shell command can be typed in the extension.
- No Bearer token, access token or email/password login is used for the MVP.
- Requests are authorized with
X-Pairing-Tokenand scoped to servers linked to that pairing token. - Agent secrets are never exposed to the extension.
Related pages
Read the setup and platform-specific guides
- Install the server agent with the Linux setup guide.
- Read Chrome Server Monitor Extension.
- Read Firefox Server Monitor Extension.
- Use Online Server Monitor Bot for Telegram alerts.
FAQ
Browser extension FAQ
- Does the extension replace the Telegram bot? No. It is an additional browser dashboard that uses the same backend and Linux agent.
- Do I need to install the Linux agent first? Yes. Install the agent with the PAIRING_TOKEN, then connect the extension using the same PAIRING_TOKEN.
- Does the extension use SSH? No. It only talks to the server.howprog.one API over HTTPS.
- What can I monitor from the browser? CPU, RAM, disk, inodes, load average, uptime, SSL expiry, online/offline state, systemd services and active alerts when available.
- Will browser notifications work when the browser is closed? No. The browser must be running.
- Can one PAIRING_TOKEN see another user’s servers? No. The backend returns only servers linked to that PAIRING_TOKEN.
Start monitoring
Connect a Linux server from Telegram.
Open the bot, request a one-time pairing command, run it on the server and receive the first status report in Telegram.