Work with multiple applications
Log Lens keeps each application in its own isolated workspace: a separate database, log directory, processed archive, and source list. Issues, occurrences, connectors, and settings never leak between applications. Use this to track staging separately from production, or to keep unrelated projects apart on one dashboard.
The default application
Every install starts with one workspace, default ("Primary application"). Its data lives at the top level of your install, not under applications/. The default id is reserved and cannot be reused.
Create an application
Give a new application a name of 1-100 characters. Log Lens derives a URL-safe id from the name (lowercased, with each run of non-alphanumeric characters collapsed to a single hyphen), or you can supply your own id. Ids must be unique and 1-64 characters.
| Field | Rule |
|---|---|
| Name | 1-100 characters |
| Id | 1-64 URL-safe characters; must be unique; default is reserved |
Each new application gets its own isolated tree:
applications/<id>/
log-lens.sqlite # its own database
logs/ # ingested log files
processed/ # processed archive
sources/ # tracked source streams
These directories are created automatically. The registry of all applications is stored in storage/applications.json.
Switch between applications
Select the application you want from the dashboard's application switcher. Everything you see - issues, sources, modules, connectors - is scoped to the active workspace. When no application is specified, Log Lens resolves to the first one in the registry.
Move a workspace
You can relocate an application's folder (for example onto a larger disk). When the processed or sources directory changes location, Log Lens automatically repairs the stored file paths on next run: it matches each moved file by its relative path and exact byte size, then rewrites the database. Files whose size no longer matches are left untouched, so nothing is mis-linked. See Automatic workspace path repair.
Next steps
- Applications and isolation - how the boundary between workspaces works.
- Ingest logs from a local directory - point a new application at its logs.
- Group logs into modules - organize issues within an application.
- Query Log Lens from the JSON API - list and target applications programmatically.