Glossary
Definitions for the core concepts in Log Lens. Each term links to the feature or reference article that covers it in depth.
Core objects
| Term | Meaning |
|---|---|
| Application | An isolated workspace with its own database, logs, and sources. Identified by a URL-safe id (1-64 characters) and a display name (1-100 characters). The id default is reserved. See Applications. |
| Issue | A group of related events sharing one fingerprint (stored as an error_groups row). Carries a title, severity, exception class, source frame, occurrence count, first/last-seen timestamps, status, origin, and kind. See Issues and fingerprints. |
| Occurrence | A single logged event belonging to an issue. Records its source file, timestamp, severity, byte range, and a context preview. See Occurrences. |
| Source | A tracked log file (source_files) with a path, size, log type, and channel. See Supported formats. |
| Module | A label (name, slug, color) that groups sources and issues into a functional area such as Billing. See Modules. |
| Connector | An ingestion path that copies remote or local files into a workspace, tracked as source streams with a fetched_offset. See The local-directory connector. |
| Workspace | An application's processed and sources directories on disk. If the workspace moves, paths are repaired automatically. See Workspace path repair. |
Grouping keys
| Term | Meaning |
|---|---|
| Fingerprint | A SHA-256 hash of module / log type / severity / exception class / normalized title / normalized source frame. Two events with the same fingerprint become the same issue. |
| Exact fingerprint | The fingerprint plus the normalized stack trace. Identical exact fingerprints are treated as duplicate occurrences and skipped. |
| Normalization | Rewriting variable tokens to placeholders before hashing: {uuid}, {time}, {ip}, {email}, {release}, {line}, {n}. See Normalization. |
Attributes
| Term | Meaning |
|---|---|
| Severity | The log level: EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, NOTICE, INFO. See Severities. |
| Origin | How an issue was created - manual issues are authored by you; others come from ingestion. See Manual issues. |
| Status | The workflow state of an issue. A fixed issue that receives a new occurrence flips to reoccurred. See Reoccurrence detection. |
| Byte range | The byte_start/byte_end offsets that let an occurrence be read back from the original file. See Byte-range storage. |