Telegram Bot Commands for Server Monitoring

Use these commands in the Telegram chat where you manage the server.

• Refresh status: request a fresh server card.
• Restart service: restart a detected allowed systemd service.
• Clean logs: run controlled cleanup actions.
• Confirm reboot: queue reboot only after explicit confirmation.
• Cancel action: stop a risky action before it is queued.

Start with /status or /server_status to get the current picture. Check whether the server is online, then compare CPU, RAM, disk and load. If a service looks failed, use the service list before pressing a restart button. This keeps the workflow predictable under pressure.

Use thresholds as early warning limits, not as proof that the server is broken. CPU and load can spike briefly during deploys or backups, while disk usage usually needs earlier warning. Tune one value at a time so you can see which change reduces noise.

In a group chat, commands become part of the operational record. That is useful for transparency, but it also means pairing tokens and maintenance buttons are visible to the group. Keep the group small and trusted, and avoid forwarding install commands elsewhere.

• New server: /add_server, run install command, then /servers.
• Routine check: /status, review metrics, then refresh if values are stale.
• Noisy alerts: /thresholds, raise one threshold, watch the next few reports.
• Failed service: open server services, review state, then use restart only if you understand impact.

Maintenance commands should be short-lived. If a command sits too long before the agent polls it, the agent may reject it as expired. This is a safety feature: an old reboot or restart request should not execute unexpectedly after the operational context has changed.

Status commands should be safe and read-only. Service restart, log cleanup, threshold changes and reboot confirmation can change server behavior. Treat action buttons as production operations, especially in a shared Telegram group.

Use recognizable hostnames and labels so commands are clear in Telegram. A generic hostname makes it easy to restart or inspect the wrong machine. If you manage several VPS instances, rename them before pairing or document which hostname belongs to which service.

If a command produces no answer, check whether the bot is still in the chat, whether the server is online, and whether the agent heartbeat is recent. For action buttons, also check that the command result reached the backend. The troubleshooting page lists local checks.

Commands should not ask for passwords, private keys or arbitrary shell snippets. If a support conversation asks you to paste secrets into Telegram, stop and use the security contact instead. The bot should guide safe workflows, not replace normal server access controls.

• Do not share pairing tokens publicly.
• Use maintenance actions only on servers you control.
• Reboot can interrupt websites, mail and database services.
• If a button is missing, check the troubleshooting guide.

Read the setup guide before installing the agent, the security model before using maintenance actions, and the troubleshooting guide if commands do not appear.