Logs

The Logs resource provides a centralized list of all log entries generated by your application. Use this page to quickly search error messages, audit informational logs, and navigate directly to the context (request, job, command, etc.) where each log was written.

Navigation: Access Logs via the sidebar under the “Logs” section.

---

1. Logs Index Table

The main content of the Logs page is a table displaying individual log entries. By default, 25 entries are shown per page, ordered by Date in descending order (most recent first). Click Load More at the bottom to fetch additional records.

1.1 Columns

1. Date

   • Timestamp when the log entry was created (e.g., 2025-05-30 15:12:09).

2. Log Level

   • Severity level of the log (e.g., DEBUG, INFO, WARNING, ERROR, CRITICAL).

3. Message

   • The log message text, as defined by your application’s logging calls (for example, Order #1234 processed successfully or Database connection timeout).

4. Occurrence

   • The context in which this log entry was recorded:
     • Request (e.g., Request #1023)
     • Command (e.g., Command cache:clear)
     • Scheduled Task (e.g., Task backup:run)
     • Queued Job (e.g., Job SendEmailJob)
   • Clicking the occurrence link navigates to the corresponding details page (for example, Request Details), allowing you to see the full event timeline around this log.

Note: If a log entry was written in a global context (e.g., application bootstrapping), the Occurrence field may show a generic “Boot” or “System” label.

---

2. Filters

Above the Logs table, a set of filter controls enables you to refine which log entries are displayed:

1. Search (Message)

   • A free-text search field that matches against the Message column.
   • Partial matches and substrings are supported (e.g., searching “timeout” will match “Database connection timeout”).

2. Date Range

   • Select Start Date & Time and End Date & Time to show only log entries created within that window.

3. Log Level Filter

   • Clickable badges or a dropdown menu listing log levels (e.g., DEBUG, INFO, WARNING, ERROR, CRITICAL).
   • Selecting one or more levels filters to entries at those severities.

Tip: Combine Search and Log Level filters to locate all recent ERROR messages containing a specific keyword (for example, “payment”).

---

3. Load More

• By default, the Logs table shows the 25 most recent entries.
• Click the Load More button at the bottom to retrieve the next batch of 25 entries, ordered by Date descending.
• This incremental loading ensures fast initial page loads while still providing access to your application’s complete log history.

---

4. Best Practices

• Search Common Error Keywords

  • Use the Search filter to locate log messages containing frequently occurring keywords (e.g., “timeout,” “exception,” “deprecated”).

• Isolate Critical Levels

  • Filter by ERROR or CRITICAL to focus on high-severity issues. Reviewing these first helps you address the most urgent problems.

• Narrow by Date Range

  • When troubleshooting a deployment or incident, set a tight Date Range around the deployment time to surface relevant log entries quickly.

• Understand Context via Occurrence

  • Click the Occurrence link to navigate to the parent request, command, scheduled task, or queued job where the log was emitted. This context can reveal upstream triggers or downstream effects.

• Monitor INFO & WARNING

  • Don’t ignore INFO and WARNING logs—frequent warnings (e.g., “Deprecated method called”) may signal upcoming issues or required code updates.

• Use Pagination Strategically

  • If you have high log volume, combine filters first (for example, ERROR level + specific date range) to reduce the number of pages you need to load via Load More.

---

By leveraging the Logs index, its filters, and occurrence links, Laritor helps you efficiently search, audit, and diagnose all log activity—providing the context you need to maintain application health and troubleshoot issues.