Quickstart – DevLens Components
DevLens is split into three independently deployable services that work together to give you real‑time error monitoring, AI‑powered fixes, and health checks.
| Component | What it does | Typical deployment |
|---|---|---|
| App | • Web UI for exploring errors & health • Sends alerts to Slack, Teams, PagerDuty, etc. • Manages data retention and archival |
1‑node Docker image or a self‑hosted binary |
| Agent | • Runs on each host (k8s pod, VM, container) • Collects host telemetry (CPU, memory, network) • Acts as a thin wrapper around Sentry SDKs so your app can emit errors without a native Sentry agent |
Deploy as a DaemonSet, side‑car, or standalone binary |
| AI Service | • Forwards error events + surrounding source code & docs to an LLM provider (OpenAI, Anthropic, etc.) • Returns actionable fix suggestions to the UI |
Separate Docker image or binary; can be disabled if you don't need AI |
The agent and AI service are optional components.
Installation Options
| Method | Steps |
|---|---|
| Docker Compose | docker-compose up -d – pulls all three images, sets environment variables, and connects them. |
| Single‑binary | Download the platform‑specific binaries for each component from the releases page and run them as system service. |
Tip: If you only need the server (e.g., for a quick demo or local deployment), you can skip the agent and AI service; the server will still receive events via the DevLens API.
Once the services are running, navigate to http://localhost:8000 (default) to start exploring your application’s errors, health checks, and AI‑generated fix suggestions.