Exceptions

The Exceptions resource provides a consolidated view of all exceptions captured across your application. Each exception is displayed as a card showing key metadata, and you can click into any exception to see full details—including a highlighted stack trace, occurrence history, and AI-based recommendations for resolution.

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

---

1. Exceptions Index

The index lists the most recent exceptions in paginated card format, allowing you to quickly triage and investigate errors as they occur.

1.1 Exception Cards

• Pagination & Ordering:

  • Displays 25 exceptions per page, ordered by Last Seen (descending).
  • Click Load More at the bottom to retrieve additional exception cards.

• Card Contents: Each exception card includes:

  1. Exception Class
     • The fully qualified class name (for example, App\Exceptions\DatabaseException).
  2. Exception Message
     • The error message thrown by the exception (e.g., SQLSTATE[42S22]: Column not found).
  3. File & Line Number
     • The file path and line where the exception was raised (for example, /app/Http/Controllers/UserController.php:45).
  4. First Seen
     • Timestamp of the earliest captured occurrence for this exception.
  5. Last Seen
     • Timestamp of the most recent captured occurrence.
  6. Total Occurrences
     • The cumulative count of times this exception has occurred.

• Clickable Cards:

  • Click anywhere on a card to open the Exception Details page for that exception.

Tip: Scanning the exception cards helps you identify recurring errors (high total occurrences) or newly introduced issues (recent “First Seen” date).

1.2 Filters

Above the exception cards, use the following filters to narrow down the results:

1. Date Range

   • Select Start Date & Time and End Date & Time to show only exceptions whose Last Seen (or First Seen, depending on implementation) falls within that window.

2. Total Occurrences

   • A numeric input to filter exceptions by how many times they have occurred. For example, set a minimum threshold to surface only exceptions that have happened at least N times.

3. Search (Exception Class / Message)

   • A free-text search field that matches against both the exception class name and exception message. Partial matches and substrings are supported.

Tip: Combine the Search and Total Occurrences filters to quickly locate frequently occurring exceptions that match a specific error keyword (e.g., “SQLSTATE”).

---

2. Exception Details

Clicking an exception card opens the Exception Details page, which provides the same card-level metadata plus two informative tabs: Stack Trace and Occurrences.

---

2.1 Exception Summary Card & AI Fix Button

At the top of the Exception Details page, a summary card displays all key fields exactly as on the index:

• Exception Class

• Exception Message

• File & Line Number

• First Seen

• Last Seen

• Total Occurrences

• In the top-right corner of this section, a Fix Using AI button. Clicking this opens a dialog where Laritor’s AI engine analyzes the exception context and the series of events leading up to it, providing:

  • Insights on why the exception occurred
  • Recommendations on how to resolve or prevent it
  • Example code changes or configuration tweaks (where applicable)

Tip: Use the AI suggestions as a starting point for remediation. The recommendations are generated based on the recorded stack trace, logs, and related events.

---

2.2 Tabbed Layout: Stack Trace & Occurrence History

Below the summary card, two tabs organize the detailed information:

1. Stack Trace (default active)
2. Occurrences

2.2.1 Stack Trace Tab

• Purpose: Displays a preview of the source file containing the exception, with the exact line highlighted.
• Content:
  • A code snippet view of the file where the exception was thrown.
  • Automatic highlighting of the line number at which the exception occurred.
  • Surrounding lines for context (for example, 10 lines before and after the highlighted line).
• Usage:
  • Quickly identify the code path and inspect variables or function calls leading up to the exception.
  • Use your own editor or IDE to navigate to the full file if deeper debugging is required.

Tip: If the file preview does not match your local repository (e.g., due to deployment differences), confirm that you’re viewing the correct release or commit on your source control system.

2.2.2 Occurrences Tab

• Purpose: Lists every individual occurrence of this exception, showing where and when it happened across the application.

• Occurrences Table:

  • Columns:

    1. Occurrence Source
       • Indicates the context that triggered the exception:
         • Request (if raised during an HTTP request)
         • Command (if raised during an Artisan command)
         • Scheduled Task (if raised in a scheduled task run)
         • Queued Job (if raised in a background job)
    2. Occurred On
       • Timestamp when the exception was recorded for that specific occurrence.
    3. View Link
       • A clickable link (for example, “View Request” or “View Job”) that navigates to the respective Request Details, Command Details, Scheduled Task Run Details, or Job Details page for further analysis.

  • Ordering:

    • Rows are sorted by Occurred On in descending order (most recent first).

• Filters:

  • Date Range
    • At the top of the occurrences table, a Start Date & Time and End Date & Time filter allow you to limit occurrences to a specific window. This is helpful for correlating spikes in exceptions with recent deployments or configuration changes.

Tip: Use the View Link to jump directly into the context where the exception was thrown (e.g., the specific HTTP request or job run). This makes it easier to examine surrounding events like queries, logs, or external calls that may have contributed to the error.

---

3. Best Practices & Troubleshooting

• Identify Trends

  • Sort by Total Occurrences to find the most frequent exceptions. Investigate those first to reduce noise and improve overall application stability.

• Track New Errors

  • Use the First Seen timestamp to flag newly introduced exceptions—especially after deployments or configuration changes.

• Leverage AI Recommendations

  • Click Fix Using AI to get context-aware suggestions on why the exception occurred and how to fix it. These recommendations combine stack trace analysis with best-practice guidance.

• Correlate with Recent Deployments

  • Filter the Occurrences table by a date range corresponding to a recent release. This helps isolate issues caused by new code.

• Dive into Context Quickly

  • Clicking “View” under Occurrences takes you directly to the detailed event timeline for that specific request, command, scheduled task, or job, where you can inspect queries, logs, and more.

• Examine Stack Traces for Root Cause

  • The Stack Trace tab highlights exactly where the exception was raised. Check the surrounding code to understand input values or state that led to the failure.

• Monitor Exception Aging

  • If an exception’s Last Seen date is far in the past, it may have been resolved. Conversely, a recent Last Seen indicates it’s still active and requires attention.

• Filter by Error Message

  • Use the Search filter on the index to find variations of the same exception class with different messages (e.g., database constraint violations vs. connection errors).

---

By leveraging the Exceptions index, Exception Details view, and the AI-powered Fix Using AI feature, Laritor enables you to prioritize, troubleshoot, and resolve errors efficiently—gaining visibility into new or recurring issues and understanding exactly where and why they occur.