Logs
The Logs page provides comprehensive system activity tracking and monitoring capabilities. It helps you track system events, debug issues, and maintain an audit trail of all operations performed in your Galago installation.
Table of Contents
Overview
Using Logs
Log Categories
Category | Description | Example |
---|---|---|
System Events | Core system operations and status changes | System startup, service status changes |
User Actions | Activities performed by users | Login, configuration changes, protocol creation |
Tool Operations | Events related to laboratory equipment | Tool connection, command execution, errors |
Protocol Executions | Protocol run events and status updates | Run start/stop, step completion, parameter values |
Error Messages | System and operational errors | Connection failures, execution errors, timeouts |
Best Practices
- Implement regular log rotation to prevent excessive file sizes
- Archive important logs for long-term storage and compliance
- Set appropriate retention policies based on your requirements
- Monitor log storage usage to prevent disk space issues
1
Use log filters to focus on relevant time periods and categories
2
Cross-reference timestamps with other system events
3
Check related events before and after an issue
4
Export logs when needed for detailed analysis or support
Tip: You can set up email notifications for critical log events by configuring alert rules in the system settings.
Note: Log files are stored in the /var/log/galago/
directory on the server. You can access these directly if needed for advanced troubleshooting.