Server Management
Monitor server health, run AI-powered diagnostics, manage configuration files, and control systemd services from a unified dashboard.
Adding Servers
Servers in PulseGuard are linked to SSH connections, allowing the platform to connect to your servers and collect health metrics, manage configurations, and control services.
Linking to an SSH Connection
Navigate to Servers > Add Server and select an existing SSH connection from the dropdown. Each server must be linked to an SSH connection so PulseGuard can access it remotely. If you have not created an SSH connection yet, see the SSH Portal documentation to set one up first.
Naming Servers
Give your server a descriptive name that helps you identify it at a glance (e.g., "prod-web-01", "staging-db", "monitoring-server"). Server names are displayed across the dashboard, health alerts, and diagnostics reports.
Tags
Add tags to organize and filter your servers (e.g., "production", "staging", "database", "web"). Tags help you quickly find servers when you have a large fleet. You can filter the server list by tag and group servers by tag in the dashboard overview.
Health Monitoring
PulseGuard continuously monitors your server's vital metrics over SSH. Get real-time visibility into CPU, memory, disk, and network utilization with configurable alert thresholds.
Metrics Collected
| Metric | Details |
|---|---|
| CPU | Total CPU usage percentage, per-core breakdown, load averages (1m, 5m, 15m) |
| Memory | Total/used/available RAM, swap usage, buffer/cache breakdown |
| Disk | Usage per mount point, total/used/available space, inode usage |
| Network | Bytes sent/received per interface, packet counts, error rates |
Alert Thresholds
Configure thresholds for each metric to receive alerts when values exceed safe limits. For example, set a CPU alert at 90% usage, a memory alert at 85%, or a disk alert at 95%. When a threshold is breached, PulseGuard sends notifications through your configured alert channels (email, Slack, Discord, etc.). Thresholds can be set per-server in the server settings.
Historical Metric Charts
All metrics are stored historically and displayed in interactive charts on the server dashboard. You can view metric trends over the last hour, 24 hours, 7 days, or 30 days. Charts support zooming and hovering for precise values at any point in time. Use historical data to identify patterns such as peak usage times, memory leaks, or gradual disk filling.
AI Diagnostics
PulseGuard uses Gemini 2.5 Pro to analyze your server health data and provide intelligent diagnostics with actionable fix suggestions.
Automated Diagnostics
Click Run Diagnostics on any server to initiate an AI-powered analysis. PulseGuard collects current system metrics, recent logs, running processes, and service states, then sends this data to Gemini 2.5 Pro for analysis. The AI identifies potential issues such as:
- High CPU usage caused by specific processes
- Memory leaks or excessive swap usage
- Disk space issues and which directories are consuming the most space
- Failed or degraded services
- Security concerns in system configuration
Fix Suggestions (Approve/Reject Workflow)
For each issue identified, the AI generates a specific fix suggestion that includes the exact command or configuration change needed. Fixes are presented in a review workflow:
1. Review the suggestion
Each fix includes a description of the problem, the proposed solution, the exact command(s) that will be executed, and the expected outcome. Review these carefully before taking action.
2. Approve or reject
Click Approve to execute the fix on your server via SSH, or Reject to dismiss the suggestion. Approved fixes are executed immediately and the result is logged. No fix is ever applied automatically without your explicit approval.
3. Verify the result
After a fix is applied, PulseGuard re-checks the affected metric to verify the issue was resolved. The diagnostics history shows all past analyses, applied fixes, and their outcomes.
Config Management
View and edit server configuration files directly from the PulseGuard dashboard. Configuration changes are tracked with version history so you can review and revert changes.
Viewing & Editing Config Files
Navigate to your server's Config tab to browse configuration files. PulseGuard reads files from common configuration directories (e.g., /etc/nginx/, /etc/apache2/, /etc/systemd/). Files are displayed with syntax highlighting. Click Edit to modify a file. Changes are saved back to the server via SSH. A backup of the original file is created before any changes are applied.
Version Tracking
Every configuration change is tracked with a timestamp, the user who made the change, and a diff showing exactly what was modified. You can view the full version history for any config file and compare any two versions side by side. If a change causes issues, you can revert to a previous version with a single click.
Service Management
Manage systemd services on your servers remotely from the PulseGuard dashboard. Start, stop, restart, enable, and disable services without opening a terminal.
Available Actions
| Action | Command | Description |
|---|---|---|
| Start | systemctl start | Start a stopped service immediately |
| Stop | systemctl stop | Gracefully stop a running service |
| Restart | systemctl restart | Stop and start a service (applies config changes) |
| Enable | systemctl enable | Configure a service to start automatically on boot |
| Disable | systemctl disable | Prevent a service from starting automatically on boot |
Navigate to your server's Services tab to see a list of all systemd services with their current status (active, inactive, failed). Each service shows its load state, active state, and sub-state. Click the action buttons next to any service to execute the corresponding systemctl command via SSH. All service actions are logged in the server activity history.
Important: Service management actions require the SSH user to have sudo privileges. If the connected user does not have permission to run systemctl commands, the actions will fail with a permission error.