Logs and Monitoring
Checking Logs
Unified Log Viewer
View the logs of all services together in real time:
cd /home/kopens/plantpulse-ai/bin
./log-viewer.sh
Per-Service Logs
Each module also provides its own log viewer:
# AI Chat Web
/home/kopens/plantpulse-ai/web/bin/log-viewer.sh
# TimeSeries
/home/kopens/plantpulse-ai/timeseries/bin/log-viewer.sh
# LightRAG (RAG)
docker logs -f lightrag
Log File Locations
| Service | Log File |
|---|---|
| System (all) | logs/application.log |
| System (all) | logs/system.log |
| Installation log | logs/setup.log |
| AI Chat Web | web/logs/system.log |
| TimeSeries | timeseries/logs/system.log |
| LightRAG (RAG) | docker logs lightrag |
AI Agent Observability — Task View
As of the 2026-07 revision, Arize Phoenix has been removed from the stack. Agent execution flows are viewed in the AI Chat Web Task View (AgentTraceStore).
The built-in agent keeps the tool call sequence of the most recent turn (input → tool call → output) in memory, so you can trace which tool was called with which arguments and what result was returned from "Task View" on the chat screen.
Service Status Monitoring
status.sh
cd /home/kopens/plantpulse-ai/bin
./status.sh
Checks the running status of all services based on their ports. [OK] indicates normal, [DOWN] indicates abnormal.
Health Check Endpoints
| Service | Health Check URL |
|---|---|
| AI Chat Web | http://127.0.0.1/actuator/health |
| LightRAG (RAG) | http://127.0.0.1:7114/health |
| TimeSeries | http://127.0.0.1:8970/health |
| LiteLLM | http://127.0.0.1:4000/health |
| Qdrant | http://127.0.0.1:6333/healthz |
The unified MCP is provided by the PlantPulse Platform server-web, so its health check is performed on the Platform side as well.
Log Cleanup
When disk space runs low:
cd /home/kopens/plantpulse-ai/bin
./clean.sh
Cleanup targets:
- Log files in all
logs/directories - Temporary caches of each service
- Build artifacts
Be sure to back up any logs you need before running clean.sh.