Modules
Modules group your logs into meaningful areas of an application - for example Billing, Auth, or Queue - so issues carry a label you can filter and scan by. Every issue can belong to one module (or none), and each module shows a live count of the issues assigned to it.
Why they matter
Modules turn a flat wall of errors into something you can triage by team or subsystem. Because a module travels with the issue, you can slice the dashboard down to just the errors that belong to the part of the app you own.
Creating a module
A module has three fields:
| Field | Rules |
|---|---|
| Name | 1-100 characters, must be unique |
| Slug | Derived from the name if you don't supply one: lowercased, non-alphanumeric runs collapsed to -, 1-64 URL-safe characters |
| Color | A six-digit hex value like #6366f1 (the default). Stored lowercase |
Creating a module whose name or slug already exists is rejected as a duplicate.
Folder inference
When logs arrive through a connected directory, Log Lens assigns a module automatically from the top-level folder the file sits in. A file at:
<incoming>/billing/laravel.log
is assigned to a module derived from billing. The folder name becomes the slug, and a human-friendly name is generated by replacing -/_ with spaces and title-casing it - so billing becomes Billing and payment-gateway becomes Payment Gateway. If a matching module already exists (by slug or name), it is reused; otherwise it is created for you.
Inference only fires when the file is nested at least one folder deep inside the connected root. Files sitting directly in the root get no module. Processed logs are archived into a per-module subfolder named after the module's slug.
Coloring
The color is purely presentational - it drives the dot and badge shown next to a module across the dashboard. Pick distinct colors so subsystems are easy to tell apart at a glance.
Managing modules
Modules are listed alphabetically (case-insensitive) alongside their issue counts. You can create them ahead of time and assign them by hand, or let folder inference build them as logs flow in.