Logging & Monitoring
Logging system, log files, and performance monitoring
Log Files
Log File Locations
| Platform | Location |
|---|---|
| Windows | %APPDATA%\CryptArtist Studio\logs\ |
| macOS | ~/Library/Application Support/CryptArtist Studio/logs/ |
| Linux | ~/.config/cryptartist-studio/logs/ |
Log Files
- session.log - Current session log with all events
- recent.log - Last 1,000 lines of activity (rolling)
- history.log - Full history log (all events)
Log File Format
[2026-03-14 12:00:00] [INFO] Application started
[2026-03-14 12:00:01] [DEBUG] Loading configuration
[2026-03-14 12:00:02] [INFO] Workspace initialized
[2026-03-14 12:00:03] [WARN] API key not configured
[2026-03-14 12:00:04] [ERROR] Failed to load project: File not found
Log Levels
| Level | Description | Use Case |
|---|---|---|
| DEBUG | Detailed diagnostic information | Development and troubleshooting |
| INFO | General informational messages | Normal operation tracking |
| WARN | Warning messages for potential issues | Unusual but recoverable conditions |
| ERROR | Error messages for failures | Serious problems that need attention |
| FATAL | Critical errors that cause shutdown | Unrecoverable failures |
Enabling Debug Logging
Set Environment Variable
Before launching CryptArtist Studio, set the RUST_LOG environment variable:
Windows (PowerShell)
$env:RUST_LOG="debug"
.\CryptArtist Studio.exe
macOS/Linux
export RUST_LOG=debug
./cryptartist-studio
Log Level Options
# Show only errors
RUST_LOG=error
# Show warnings and errors
RUST_LOG=warn
# Show info, warnings, and errors
RUST_LOG=info
# Show all messages including debug
RUST_LOG=debug
# Show all messages including trace
RUST_LOG=trace
Module-Specific Logging
# Debug only media processing
RUST_LOG=cryptartist_studio::media=debug
# Debug multiple modules
RUST_LOG=cryptartist_studio::media=debug,cryptartist_studio::ai=debug
Frontend Logging
Browser Console
Open the browser developer console (F12) to see frontend logs:
- Component lifecycle events
- State changes
- API calls and responses
- User interactions
Console Methods
console.log("General message");
console.warn("Warning message");
console.error("Error message");
console.debug("Debug message");
console.info("Info message");
Filtering Console Output
In the browser console, use the filter dropdown to show only specific log levels.
Performance Monitoring
Performance Metrics
CryptArtist Studio tracks performance metrics:
- Startup Time - Time to launch the application
- Project Load Time - Time to open a project
- Render Time - Time to render frames (Media Mogul)
- API Response Time - Time for API calls
- Memory Usage - Current memory consumption
- CPU Usage - Current CPU utilization
Viewing Performance Data
Performance data is logged to the session log. View it with:
cryptartist-studio system logs | grep "performance"
Performance Profiling
Use browser DevTools Performance tab to profile frontend performance:
- Open DevTools (F12)
- Go to Performance tab
- Click Record
- Perform actions to profile
- Click Stop to view results
Monitoring Best Practices
Regular Log Review
- Check logs regularly for errors and warnings
- Monitor API response times
- Track memory usage trends
- Look for performance degradation
Log Retention
- Recent logs are kept for quick access
- History logs retain full records
- Old logs are automatically rotated
- Manually clear logs if needed:
cryptartist-studio system cache clear
Troubleshooting with Logs
- Enable debug logging when investigating issues
- Look for ERROR and FATAL level messages
- Check timestamps to correlate events
- Include relevant log excerpts when reporting bugs
