log - Monitor LogsWatch real-time logs from your local PrestaShop Enterprise development environment containers for debugging and monitoring.
The log command provides real-time streaming of logs from selected Docker containers in your local development environment, helping you monitor application behavior, debug issues, and understand system activity during development.
Before running the log command:
ps-enterprise authps-enterprise start# Shows container selection menu
ps-enterprise log
# Monitor all running containers (default behavior)
ps-enterprise log
# Monitor specific containers by name
ps-enterprise log webserver database
# Monitor containers matching partial names
ps-enterprise log web data ngrok
# Show static logs without real-time streaming
ps-enterprise log --static
| Flag | Short | Description | Required |
|---|---|---|---|
--static |
Display static logs instead of live streaming | No | |
--help |
-h |
Show command help | No |
The log command follows this workflow:
# Run with interactive selection
cd my-prestashop-project
ps-enterprise log
# Interactive menu appears:
# ? Select container(s) to watch
# ✓ webserver
# ✓ database
# ○ ngrok
# [Use arrows and space to select, Enter to confirm]
# Selected containers start streaming:
# webserver 192.168.1.100 - - [03/Nov/2025:10:30:15 +0000] "GET /admin HTTP/1.1" 200 1234
# database 2025-11-03T10:30:15.123456Z Query: SELECT * FROM ps_configuration WHERE name='PS_SHOP_ENABLE'
# Monitor only web server and database
ps-enterprise log webserver database
# Output shows only selected containers:
# webserver [03/Nov/2025 10:30:15] GET /index.php HTTP/1.1 200
# database [03/Nov/2025 10:30:15] Query executed: SELECT * FROM ps_product (0.003s)
# Monitor containers with names containing 'web'
ps-enterprise log web
# Matches: webserver, web-php, etc.
# If multiple matches found:
# Multiple containers found matching 'web':
# 1. webserver
# 2. web-php
# ? Select containers: [1,2]
# Show recent logs without streaming
ps-enterprise log --static
# Displays recent log entries and exits:
# webserver [Recent logs from webserver container]
# database [Recent logs from database container]
# [Command exits after displaying recent logs]
# Terminal 1: Start environment
ps-enterprise start
# Terminal 2: Monitor logs
ps-enterprise log webserver database
# Terminal 3: Development work
# Navigate to http://localhost:8080 and watch logs in Terminal 2
# Edit files, test features, observe real-time logs
❌ Containers not found with names ["webserver"]
Solution: Start the environment first:
ps-enterprise start
ps-enterprise log
❌ Containers not found with names ["nonexistent"]
Solution: Check available containers:
docker ps --format "table {{.Names}}\t{{.Status}}"
❌ webserver Error: permission denied while trying to connect to Docker daemon
Solution:
❌ webserver Container disconnected or stopped
Solution:
docker psps-enterprise stop && ps-enterprise startIf containers aren’t detected:
Verify Environment Status:
ps-enterprise start
docker ps
Check Container Names:
docker ps --format "table {{.Names}}\t{{.Image}}\t{{.Status}}"
# Monitor containers with complex name patterns
ps-enterprise log $(docker ps --format "{{.Names}}" | grep -E "(web|db)")
# Pipe logs to external analysis tools
ps-enterprise log --static | grep ERROR
ps-enterprise log webserver | awk '/404/ {print $0}'
#!/bin/bash
# automated-testing.sh - Monitor logs during automated testing
ps-enterprise log webserver database > test-logs.txt &
LOG_PID=$!
# Run automated tests
npm test
# Stop log monitoring
kill $LOG_PID
# Morning routine
ps-enterprise start
ps-enterprise log webserver database & # Background monitoring
# Development work with logs visible
# Edit code, test changes, observe logs
# End of day
kill %1 # Stop background logs
ps-enterprise stop
# Reproduce issue while monitoring
ps-enterprise log webserver database
# In another terminal, reproduce the problem
# Navigate to problematic page or feature
# Observe real-time logs for error patterns
# Monitor performance during load testing
ps-enterprise log database redis
# In another terminal, run performance tests
# Watch for slow queries and cache behavior
auth - Required for container access authenticationclone - Required for container configurationstart - Must be run first to have containers generating logsstop - Stops containers and ends log generationexec - Access containers directly for detailed inspection