Monitoring overview
Know what’s happening in your infrastructure. Alpacon keeps detailed records of every action, so you can track team activities, troubleshoot issues, and meet compliance requirements.
Why monitoring matters
For security: See who’s accessing your servers and what they’re doing. Spot suspicious activity before it becomes a problem.
For compliance: Need to prove who did what and when? Full audit trails help you meet SOC 2, ISO 27001, and other regulatory requirements.
For troubleshooting: When something breaks, review what commands were run and what changed. Debug faster with complete activity history.
What you can track
Who’s using your servers
Every time someone opens a terminal to a server, it’s logged. See:
- Who connected to which server
- When they connected and for how long
- What commands they ran in the terminal
- Their browser and IP address
Perfect for security audits and understanding team workflows.
File transfers
Track all file uploads and downloads:
- What files were transferred
- Who transferred them
- File sizes and paths
- When it happened
Essential for data security and compliance.
Command execution
See every command sent to your servers:
- User-submitted commands
- Automated commands from integrations
- Command results and status
- When commands ran and who triggered them
Great for debugging and security monitoring.
User actions
Track workspace-level activities:
- Login attempts (successful and failed)
- Permission changes
- Setting modifications
- Resource access
Monitor administrative actions and unusual behavior.
System events
Centralized logs from all your servers:
- Application errors
- System events
- Security warnings
- Service status
Debug issues across your entire infrastructure from one place.
Common use cases
Security team:
- Monitor privileged access to production servers
- Track failed login attempts
- Audit administrative actions
- Investigate security incidents
DevOps team:
- Debug deployment issues with command history
- Track configuration changes
- Monitor system health across servers
- Review automated job executions
Compliance officer:
- Generate audit reports for certifications
- Prove who accessed sensitive systems
- Track data access and transfers
- Maintain detailed activity logs
Support team:
- Understand what users were doing when issues occurred
- Review commands run during incidents
- Check server logs for errors
- Track support team actions
Getting started
New to monitoring? Here’s where to start:
- Check Websh history - See recent terminal sessions
- Review commands - Understand what’s running on your servers
- Monitor user activity - Track team actions
- Set up system logs - Centralize your server logs
Who can access monitoring
Your own activity: Everyone can see their own actions and command history.
Full audit access: Staff and superuser roles can view all team activities and complete audit logs.
Need to give someone audit access? Learn about IAM permissions
Tips for effective monitoring
Review regularly: Don’t wait for incidents. Check logs weekly to spot patterns and potential issues early.
Set up alerts: Configure notifications for important events like failed logins or critical errors.
Use filters: Got lots of data? Filter by user, server, or time range to find what you need quickly.
Archive for compliance: If you have regulatory requirements, export and archive logs according to your retention policy.