Getting Started with DevLens
DevLens consists of three services that work together to provide real-time error monitoring, AI-powered fixes, and system health checks.
| Component | Description | Deployment Options | Required? |
|---|---|---|---|
| App | • Web interface for viewing errors and health status. • Sends alerts to Slack, Teams, PagerDuty, and other tools. • Manages data storage and archiving. |
container, standalone binary | ✅ Yes |
| Agent | • Collects system metrics like CPU, memory, and network usage. • Connects to Sentry SDKs so your application can send errors without a native Sentry agent. • Must be deployed alongside the appication you are monitoring (machine or container). |
Kubernetes DaemonSet, container, standalone binary | ❌ Optional |
| AI Service | • Connector between App and AI services, enabling suggestions on how to fix errors. | container, standalone binary | ❌ Optional |
The App is always required, and provides an API for simple error reporting. The Agent and AI Service are optional, depending on your specific feature needs.
Installation Options
| Method | Description |
|---|---|
| Docker Compose | Run docker-compose up -d. This command downloads all three images, configures environment variables, and starts the services. |
| Single Binary | Download the binaries for your operating system from the releases page and run them as system services. |
!!! tip If you only need the main dashboard (for a demo or local testing), you can skip the Agent and AI Service. The App will still receive events through the DevLens API.
Once the services are running, open http://localhost:8000 in your browser to view your application's errors, health status, and AI fix suggestions.