Managing Agents
Deploy, monitor, and manage AI-powered agents
An Agent in FixPanic is an autonomous software unit that runs on your infrastructure. Agents can investigate issues, execute commands, and respond to incidents using AI-powered intelligence.
Agent Lifecycle
Agents go through several states during their lifecycle:
| State | Description |
|---|---|
| Created | Agent record exists but not yet deployed |
| Deploying | System is provisioning and starting the agent |
| Running | Agent is active, healthy, and performing tasks |
| Paused | Agent is suspended (no compute, config preserved) |
| Stopped | Agent has terminated (manually or due to error) |
| Failed | Agent encountered an error and stopped |
Viewing Agents
Navigate to the Agents page to see all your agents in a tabular view.
Agent List Columns
| Column | Description |
|---|---|
| Name | Agent identifier |
| Status | Current lifecycle state |
| Cluster | Which cluster the agent belongs to |
| Last Active | Time of last activity |
| Uptime | How long the agent has been running |
Filtering Agents
Use the filter options to narrow down your view:
- Search: Filter by agent name or ID
- Status Filter: Show only Running, Paused, or Failed agents
- Cluster Filter: View agents from a specific cluster
Agent Actions
Individual Actions
Click the actions menu (three dots) on any agent row:
| Action | Description |
|---|---|
| View Details | Go to the full agent details page |
| Pause | Temporarily stop the agent |
| Resume | Restart a paused agent |
| Restart | Force a reboot of the agent |
| Configure | Update environment variables or settings |
| View Logs | See real-time agent activity |
| Delete | Permanently remove the agent |
Warning: Delete is irreversible! This action removes the agent and all its data permanently.
Bulk Actions
Select multiple agents using the checkboxes on the left:
- Bulk Pause - Pause all selected agents
- Bulk Resume - Resume all selected agents
- Bulk Delete - Remove all selected agents
Agent Details Page
Click on an agent name to access its detail page:
Overview Tab
- Status: Current state with health indicator
- Cluster: Parent cluster with link
- Version: Agent software version
- Uptime: Time since last start
- Connection: Real-time connection status
Logs Tab
View the agent's activity log:
[2024-01-15 10:23:45] INFO Connected to FixPanic platform
[2024-01-15 10:23:46] INFO Received task: check_cpu_usage
[2024-01-15 10:23:47] INFO Executing command: top -bn1
[2024-01-15 10:23:48] INFO Task completed successfullyLog Controls:
- Follow: Auto-scroll as new logs arrive
- Filter: Search within logs
- Download: Export logs as a file
Metrics Tab
Real-time metrics from the agent:
- CPU usage
- Memory consumption
- Network activity
- Disk I/O
Configuration Tab
View and edit agent configuration:
- Environment variables
- Resource limits
- Restart policy
Deploying an Agent
There are two ways to deploy an agent:
Method 1: Dashboard + CLI (Recommended)
- Create a cluster in the dashboard (if you haven't already)
- Copy the Agent ID and API Key from the cluster
- On your server, install and deploy:
curl -fsSL https://install.fixpanic.com/install.sh | bash fixpanic agent install --agent-id="your-id" --api-key="your-key" - The agent will appear in your dashboard automatically
Method 2: Dashboard Only
- Navigate to Agents page
- Click "Deploy Agent"
- Select the target cluster
- Follow the on-screen instructions to install on your server
Agent Configuration
Environment Variables
Inject configuration at runtime:
environment:
LOG_LEVEL: debug
CUSTOM_VAR: valueSet these via the Configuration tab or during deployment.
Resource Limits
Control resource consumption:
| Setting | Description | Default |
|---|---|---|
| CPU Limit | Maximum CPU cores | No limit |
| Memory Limit | Maximum RAM | No limit |
| Timeout | Command execution timeout | 30 seconds |
Restart Policy
Define behavior when the agent crashes:
| Policy | Behavior |
|---|---|
| Always | Restart automatically on any exit |
| OnFailure | Only restart on non-zero exit code |
| Never | Do not auto-restart |
Troubleshooting Agents
Agent Status: Failed
- Click on the agent to view details
- Check the Logs tab for error messages
- Common causes:
- Network connectivity issues
- Invalid credentials
- Resource exhaustion
- Configuration errors
- Fix the underlying issue, then click Restart
Agent Status: Deploying (Stuck)
If an agent stays in "Deploying" state:
- Check cluster health - Is the cluster healthy?
- Check resources - Does the cluster have available capacity?
- Check configuration - Are environment variables valid?
- Check logs - Any error messages during deployment?
Agent Not Responding
If an agent shows as Running but doesn't respond to commands:
- SSH into the server
- Check agent status locally:
fixpanic agent status fixpanic agent logs - Restart if needed:
fixpanic agent restart
Best Practices
Naming Conventions
Use descriptive names that include:
- Server role (web, db, worker)
- Environment (prod, staging, dev)
- Region or location
Examples:
prod-web-us-east-1staging-worker-01dev-db-local
Monitoring
- Set up alerts for agent status changes
- Review logs regularly for unusual activity
- Monitor resource usage to prevent exhaustion
Security
- Keep agents updated to the latest version
- Use unique API keys per cluster
- Review agent activity logs for security audit
Next Steps
- Chat Interface - Interact with your agents using natural language.
- Billing - Understand agent runtime costs.