Log Storage
Store and access deployment logs with Lighthouse integration. View real-time streams and maintain persistent log history.
Prerequisites
Before enabling log storage, you need a Lighthouse API key.
Step 1: Get a Lighthouse API Key
- Visit Lighthouse Storage
- Create an account or sign in
- Open your dashboard and generate an API key
- Copy the key for use during deployment
Note
Lighthouse provides decentralized storage for logs. Credits are required in your Lighthouse account to store logs.
Enable Log Storage on Deployment
Enable log storage when creating a new deployment.
Step 2: Configure Log Storage
- Go to New Deployment
- Select your template and configure your deployment
- In the configuration panel:
- Toggle Store Logs to ON
- Enter your Lighthouse API Key in the field provided
- Complete your setup and click Deploy
Your deployment will now automatically store logs in Lighthouse.
View Real-Time Logs
Once your deployment is running, you can view live logs in the console.
Step 3: Access Logs
- Open your deployment details page
- Go to the Logs tab
- The interface provides:
- Connection status (Connected/Disconnected)
- Real-time log stream with timestamps
- Search to filter log content
- Log level filters (All, Stdout, Stderr)
Log Interface Features
- Search logs – Search message content or raw log data
- Filter by type –
- All: All logs with counts
- Stdout: Standard application output
- Stderr: Errors and warnings
- Log controls –
- Refresh: Reconnect and reload recent logs
- Clear: Clear the current display (stored logs remain intact)
Log Format and Colors
Logs are color-coded for quick identification:
- Gray – Standard output (
stdout) - Red – Error output (
stderr) - Blue – Meta/system messages
Each entry includes:
- Timestamp (HH:mm:ss.sss)
- Message (log content)
Persistent Log Storage
With Lighthouse integration enabled:
- Automatic storage – Logs are sent to Lighthouse and persist even after a deployment ends
- Access stored logs – Logs are accessible via your Lighthouse dashboard, organized by deployment and timestamp, with search and download options
Best Practices
-
API key security
- Keep your Lighthouse API key private
- Avoid committing it to code or public repos
- Rotate keys periodically
-
Log management
- Monitor Lighthouse storage usage
- Costs are based on stored log volume
- Apply retention policies to control costs
-
Debugging workflow
- Enable log storage for important deployments
- Use real-time logs for immediate debugging
- Access stored logs for historical analysis
- Use search and filters to pinpoint issues
Troubleshooting
-
Connection issues
- Ensure your deployment is running
- Check network connectivity
- Refresh the connection
-
Missing logs
- Confirm log storage was enabled
- Verify the Lighthouse API key is valid
- Ensure sufficient Lighthouse credits are available
-
Search not working
- Searches are case-insensitive
- Broaden search terms if no results appear
- Clear filters to reset the view
Pricing
- Aquanode logging – Free (no additional cost for the interface)
- Lighthouse storage – Pay-per-use, based on:
- Storage size (typically $0.0005–0.001 per MB per month)
- Network fees for decentralized storage
Check your Lighthouse dashboard for current usage and costs.
Lighthouse integration ensures your deployment logs remain available for real-time debugging and long-term analysis.
Backups
Automated backup and restore system for VM deployments. Schedule regular backups and restore data across deployments.
Running a VM
Virtual machines on Aquanode give you complete control over your GPU computing environment. Unlike managed services, VMs provide root access, custom configurations, and the flexibility to install any software you need.