Requests

The Requests resource displays a chronological list of all incoming HTTP requests captured by Laritor. Each entry provides key metrics—such as URL, timestamp, duration, memory usage, and status code—allowing you to quickly identify performance patterns or anomalies.

Note: Access the Requests page from the sidebar navigation under “Requests.”

---

1. Requests Index Table

• Ordering: Entries are sorted by request date in descending order (most recent first).
• Pagination: By default, 50 results are shown. Click Load More at the bottom of the table to append the next 50 records.

1.1 Columns

1. URL
   • The full request path.
2. Request Date
   • Timestamp of when Laritor recorded the request.
3. Duration
   • Total time taken to process the request (in milliseconds).
4. Memory
   • Peak memory usage for the request (in megabytes).
5. Status
   • HTTP status code returned (e.g., 200, 404, 500).
6. View Icon (👁️)
   • Click to open the Request Details page for that specific entry.

---

2. Filters

At the top of the Requests index, you can refine the displayed results using multiple filter controls. All filters can be combined to narrow down to exactly the data you need.

1. Search

   • Searches across:
     • Request URL
     • Client IP address
     • User-Agent string
   • Partial matches and substrings are supported.

2. Date Range

   • Select a Start Date & Time and End Date & Time to limit results to a specific window.

3. Route

   • A dropdown menu showing all detected routes.
   • Selecting a route filters to requests matching that route.

4. Duration

   • A numeric input (milliseconds) to filter requests by minimum or maximum duration.

5. Memory

   • A numeric input (megabytes) to filter requests by memory usage thresholds.

6. Suspicious

   • A badge/button that, when clicked, filters to requests flagged as potentially malicious.
   • Common patterns include requests for /.env, /.htaccess, wp-config.php, SQL‐injection–style paths, etc.

7. Bot

   • Click this badge/button to filter to requests identified as originating from bots (based on IP/User-Agent heuristics).

8. Request Method

   • A badge/button for each HTTP method (GET, POST, PUT, PATCH, DELETE).
   • Click to filter to requests using that method.

9. Status

   • Badges/buttons for each status code class:
     • 2xx (Success)
     • 3xx (Redirect)
     • 4xx (Client Error)
     • 5xx (Server Error)
   • Click any badge to filter to that status category.

---

3. Grouping

Above or adjacent to the filters, you will find a Group By control. Use this to aggregate and organize the results by:

• User (authenticated user who made the request)
• URL (group all identical request paths)
• Route (group by named application route)

Grouping helps you quickly spot trends—such as which endpoints or users generate the most load or exhibit higher latencies.

---

4. Best Practices

• Combine Filters: Use multiple filters (e.g., Date Range + Status) to pinpoint specific issues, such as “all 5xx errors in the past hour.”
• Watch for Suspicious Activity: The Suspicious filter quickly highlights attempted probes or attacks. Investigate any unexpected hits to sensitive paths.
• Monitor Bot Traffic: Use the Bot filter to understand how much of your traffic is automated (crawlers, scrapers) to inform rate-limiting or caching strategies.
• Leverage Grouping: Group by route or URL to identify slowest endpoints and optimize accordingly.
• Use Pagination Wisely: If you have a large dataset, refine your date‐range filter first to limit the number of rows you need to traverse with Load More.

By taking advantage of these filters, grouping options, and the detailed Request Details view, you can efficiently diagnose performance issues, identify anomalies, and gain actionable insight into your application’s traffic patterns.