DockLog is a lightweight, secure, and modern developer Observability dashboard built for teams. Stop deploying heavy logging stacks just to inspect container outputs.
Core product signals that matter most when you are monitoring live containers in a fast-moving environment.
Tiny memory use for always-on monitoring.
Handles fast log streams without lag.
Modern backend performance and low overhead.
Fast enough to ship in a single deploy.
DockLog delivers essential container logs and CPU/memory statistics without needing database servers, external agents, or configurations.
WebSocket-driven logs load instantly in your browser with smart autoscrolling, back-caching, and millisecond timestamp precision.
Restrict staff views to specific container stacks using wildcards or regular expressions, preventing unauthorized database viewings.
Keep an eye on host CPU utilization, active cores, and physical memory parameters alongside container telemetry logs.
DockLog keeps the experience focused on the work that matters: reading logs, understanding host health, and taking action quickly when something is wrong.
Tail container stdout and stderr without polling delays, then jump between workloads without losing context.
Use RBAC rules to decide exactly which team members can reach each container or stack.
Run a single self-hosted service with no indexing cluster, no agents, and no heavy platform sprawl.
The product is built to stay out of your way. Pick a mode, mount the socket, and start using the dashboard immediately.
Mount `/var/run/docker.sock` and point DockLog at the containers you already run.
Start with auth mode for team access or no-auth mode when you want a fast local dashboard.
Read logs, watch CPU and memory, then start, stop, or restart containers from one screen.
Stay on a single container footprint instead of shipping a logging stack that needs a second stack.
DockLog is not a big observability platform. It is the focused interface you open when you need answers now.
Move faster during debugging with a UI that keeps live logs and host signals side by side.
Control who can see what with rules that are simple enough to maintain and strict enough to trust.
Keep logs on your own infrastructure and avoid sending operational data to third-party services.
Switch between auth and no-auth modes, pick your port, and generate a ready-to-paste Docker Compose snippet.
Configure your deployment settings interactively
version: "3.8"
services:
docklog:
image: aimldev/docklog:latest
container_name: docklog
ports:
- "8888:8000"
environment:
- SECRET_KEY=generate-secret-here
- DB_PATH=/app/data/docklog.db
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./data:/app/data
restart: unless-stopped💡 Save this text into a file named docker-compose.yaml on your server, then run docker compose up -d to spin up DockLog.
DockLog is built from the ground up for minimal resource usage, security compliance, and zero-latency performance.
Engineered using Go 1.24 and the lightweight Echo web framework. By integrating directly with the native Docker Engine SDK, DockLog reads raw streams from the container socket with negligible CPU overhead. This allows the backend binary to run comfortably with a memory footprint under 30MB.
The user interface is powered by Vue 3 and Vite, presenting logs in a sleek glassmorphic dashboard. WebSockets feed logs directly to the browser, and a built-in auto-reconnection mechanism ensures that streams are instantly restored if network drops or VPS restarts occur.
A lighter setup, faster onboarding, and fewer moving parts than the heavy stacks teams often reach for first.
| Feature | DockLog | Elastic Stack |
|---|---|---|
| Setup Complexity | ⚡ under 1 min | 🔧 Very complex |
| Dynamic per-user RBAC | ✅ Yes (SQLite backed) | ✅ Enterprise Only |
| Container Actions | ✅ Start/Stop/Remove | ❌ View Only |
| Database Required | ❌ Optional (No-Auth) | ✅ Heavy SQL/NoSQL |
Use the docs for setup, auth mode, password recovery, and RBAC rules, or jump in with the config builder above and generate a compose file in seconds.