Laravel monitoring questions, answered

Laritor FAQs.
Simple answers to your questions.

Laritor helps you track exceptions, investigate issues, and monitor performance in your Laravel app. Learn what it records, how pricing works, and how to use it with your team’s tools.

Getting started

What Laritor does, how to install it, and where it runs.

What is Laritor?

Laritor is a performance monitoring and issue tracking tool for Laravel. Track exceptions, find slow or failing requests and jobs, and inspect the queries, API calls, logs, and other events behind them. Choose Exception tracker issue tracker, or full observability recording to keep the activity your team needs.

What makes Laritor specific to Laravel?

Laritor understands Laravel requests, Artisan commands, queues, scheduled tasks, exceptions, database queries, cache operations, mail, notifications, and other supported events. It connects recorded events to the execution that produced them, so you can investigate a Laravel workflow in context. Custom events and optional integrations let you add details from your own app.

How do I add Laritor to my Laravel app?

Create an account and install binarybuilds/laritor-client with Composer. Add the ingest endpoint and backend key supplied by your Laritor dashboard, enable recording, and run php artisan laritor:sync. Choose a recording mode and add the sync command to your deployment process to keep application metadata up to date.

Which Laravel and PHP versions does Laritor support?

The current requirements list Laravel 9 through 13 and PHP 8.0 through 8.5. Your app must also meet the requirements of its Laravel version and the client package version you install. Check the requirements guide before upgrading or adopting Laritor.

Can I use Laritor with Octane, Vapor, or shared hosting?

Yes. Supported deployment setups include VPS and shared hosting, Laravel Octane, Laravel Vapor, serverless infrastructure, and autoscaling environments. Generic long-running PHP applications outside supported Laravel Octane setups are not listed as supported. Review the requirements and configure the client for your deployment.

Can I monitor multiple apps and environments in one account?

Yes. Laritor supports multiple Laravel apps and environments under one account, with unlimited apps, environments, servers, and users in the plans shown on the homepage. Keep production and staging activity separate and configure alert routing for each environment. Your event usage includes the activity you send.

Do I need to run a separate monitoring agent?

No separate, continuously running monitoring agent is required for application event ingestion. The Laravel client collects and sends supported activity. Server resource metrics are optional and require scheduling php artisan laritor:send-metrics, while application metadata is refreshed with php artisan laritor:sync.

How much performance overhead does Laritor add?

Laritor’s client is designed to keep collection and ingestion overhead small, but the impact depends on your workload, recorded events, payload sizes, and configuration. Use filters to exclude unnecessary activity and compare performance under a representative workload. The performance guide explains Laritor’s ingestion approach.

Can I use Laritor to monitor a non-Laravel application?

Laritor’s client and monitoring features are designed for Laravel applications. There is no general-purpose client SDK for non-Laravel applications. Check the supported Laravel and PHP versions before installing the package.

Can I use Laritor alongside another monitoring tool?

You can install Laritor in an app that also uses other monitoring tools. Check the combined collection overhead, event listeners, and recording settings in your environment before a production rollout. Laritor is designed for Laravel applications; it is not a general SDK for every programming language.

Recording modes

Keep exceptions, detected issues, or a broader view of your app.

Do I need full observability to use Laritor?

No. Use exceptions-only mode for exception tracking, or issue tracker mode to include problems such as slow requests and failed jobs. Laritor keeps related recorded events with each retained occurrence, so you still have context for debugging. Full observability adds successful activity for broader performance monitoring.

What does exceptions-only mode record?

Exceptions-only mode keeps a request, job, command, or scheduled-task occurrence when it contains an exception. It retains the related recorded events from that execution, including useful queries, logs, API calls, and other context. You can see what happened before the failure without recording every successful execution.

What does issue tracker mode record?

Issues-only mode keeps occurrences with detected issues, such as exceptions, slow or failed requests, slow queries, and failed jobs or commands. Related recorded events are retained with those executions. The client’s filter preset is customizable, so review which problems and thresholds your app uses.

When should I choose full observability?

Choose full observability when you want to compare routine performance and successful activity as well as failures. It provides a broader view of request traffic, route performance, queues, queries, and user journeys. You can still filter unwanted activity and control individual payload fields.

What are the related events in a recorded request or job?

A recorded execution can include the queries, logs, cache operations, outbound requests, exceptions, mail, notifications, feature-flag checks, and custom events that happened within it. The timeline shows their order and available details so you can investigate the cause of a problem. Filters and payload settings determine which events and values are available.

Can I exclude specific requests, jobs, queries, or events?

Yes. Generate and register a Laritor filter class, then customize the recording methods for the activity you want to keep. You can exclude routine endpoints or particular event types, change your recording preset, and separately control payload and context fields. This helps reduce noise and event usage.

How do recording modes affect charts and user journeys?

Charts, counts, averages, error rates, and session histories reflect the activity Laritor records. Exceptions-only and issue tracker modes can overrepresent problems and leave gaps in successful activity. Use full observability when you need a broader performance comparison, and account for filters, limits, and retention when interpreting the data.

Pricing and event usage

Understand the trial, included events, retention, and spending controls.

Is there a free trial of Laritor?

Yes. The free trial includes 300K events and lets you try all three recording modes. The homepage lists unlimited apps, environments, servers, users, alerts, dashboards, and reports, with recorded data kept for 14 days during the trial. Paid plans are available for ongoing use.

What happens if I send more than 20 million events in a month?

On the pay-as-you-go plan, 20 million events are included in the monthly base price. Additional usage is charged at $0.20 per extra 100K events. The included allowance is not a hard ingestion limit; a configured spending threshold can pause ingestion, so review your usage and billing settings.

Does each recording mode have a different price?

No. All three modes use the same $20 monthly base price with 20 million events included. Recording only exceptions or detected issues can reduce additional usage because you send fewer events. Choose the mode for the activity you need to investigate, rather than paying to record every successful occurrence.

What counts as an event in Laritor?

Requests, jobs, commands, scheduled tasks, queries, logs, exceptions, and other recorded entries count as individual events. A request with three queries, one log entry, and one exception uses six events if each entry is 2KB or less. Requests and their related events are counted separately.

How does event size affect billing?

Each event is billed in 2KB increments. An event up to 2KB counts as one event, a 3KB event counts as two, and a 5KB event counts as three. Large payloads, detailed logs, and attached output can increase event usage even when the number of requests stays the same.

Can I set a spending limit?

Yes. A spending threshold can pause event ingestion when your usage cost reaches the configured amount. Threshold calculations run daily, so final charges can slightly exceed the setting. Ingestion remains paused for the rest of the billing period unless the threshold is updated; it is not an exact, instant hard cap.

Can I receive billing alerts before usage becomes expensive?

Yes. Configure a billing alert threshold and recipient email addresses to be notified about usage costs. Billing alerts notify you; they do not pause ingestion. Use a spending threshold as well if you want ingestion to pause, and monitor event usage and payload sizes.

How long does Laritor keep recorded data?

The current plans on the homepage keep recorded data for 14 days during the free trial and 30 days on the pay-as-you-go plan. Retention affects which occurrences and execution details are available for investigation. Contact support if you need a different retention arrangement.

What you can monitor

Exceptions, performance, background work, and user activity in Laravel.

What information does Laritor capture for an exception?

Laritor records the exception class, message, file, line, full stack trace, and the occurrence where it happened. Open its recorded execution to inspect the events leading up to the failure. Grouped occurrences and alert integrations help you investigate recurring problems and prioritize a fix.

Can Laritor help me find slow or failing Laravel requests?

Yes. Review request duration, memory, status, and route context, then filter to slow or failing activity. Route monitoring helps you compare endpoints and follow performance changes. Open an affected request to inspect its queries, API calls, logs, exceptions, and other events.

Can Laritor help me investigate bot or suspicious traffic?

Yes. Inspect requests classified as bot or suspicious activity, including their URLs, IP addresses, user agents, status, and duration. Use the details to improve rate limits or filtering in your app or firewall. Laritor provides monitoring context; blocking rules are applied in your application or infrastructure.

Can I monitor queues, failed jobs, and job wait times?

Yes. Laritor records supported job executions, queue and connection details, duration, failures, and dispatch context. Queue insights help you investigate waiting work and compare processing behavior. Open a recorded job to inspect the queries, API calls, logs, and exceptions within its execution.

Can I monitor Artisan commands and scheduled tasks?

Yes. Inspect command and task executions, completion status, duration, and related events. Scheduled-task views help you investigate slow, failed, or delayed runs. Command output can be captured by adding the client’s output trait to the command you want to inspect.

Can Laritor identify slow queries, N+1 queries, and duplicate queries?

Yes. Review recorded SQL queries and their execution times, then investigate N+1 and duplicate query patterns in the related request or job. Open query details to inspect available source and binding context. Configure query binding recording and redaction to control sensitive values.

Can I monitor API calls made by my Laravel app?

Yes. Laritor records supported outbound HTTP requests with their target URL, response status, duration, and originating execution. Use this context to investigate slow dependencies or failed API calls. Request and response payload fields are configurable, so collect the details your team needs.

Can I inspect cache activity and Laravel logs together?

Yes. Laritor records supported cache operations and log messages with their execution context. Inspect them alongside queries and API calls to understand repeated work, cache misses, or warnings around a problem. Filters let you choose the log levels, context fields, and cache activity you retain.

Can I track mail and notifications sent by Laravel?

Yes. Inspect recorded mail and notification activity, the available recipient details, and the execution that triggered it. This helps you investigate when and why your app attempted to send a message. Application-side records do not by themselves confirm inbox delivery or provider acceptance.

Does Laritor support Laravel Pennant and other feature flags?

Yes. Laravel Pennant checks are recorded automatically, and other providers can be recorded manually using the client’s feature-flag recorder. Inspect active and inactive outcomes alongside performance and recorded errors. An error during a flag’s surrounding execution does not by itself prove the flag caused it.

Can I follow a user’s journey through a Laravel session?

Yes. Find an identified user or a guest session, review its recorded requests, and inspect entry and exit activity. Open slow or failing requests to understand what happened during that journey. Laritor follows server-side requests and events rather than replaying the browser screen; custom events can add meaningful workflow steps.

Can I include user attributes such as role or team?

Yes. Customize redactAuthenticatedUser to send useful attributes alongside the required user ID, name, and email fields. Laritor displays the recorded profile details so you can investigate differences between roles, teams, or other groups. Preserve your privacy rules when choosing which values to send.

Can I track custom application events?

Yes. Call Laritor::addCustomEvent() where your code reaches a useful action, such as a payment retry, checkout stage, or completed job phase. Attach a stable event name and small pieces of metadata. The event appears in its recorded execution timeline and the Custom Events view, following the recording mode for that occurrence.

Can I monitor built-in and custom health checks?

Yes. Laritor supports checks for application dependencies such as databases, cache, queue workers, the scheduler, file storage, and sessions. Add custom checks for services or conditions specific to your app, then review recorded runs, results, output, and context. Configure alerts to be notified when a check reports a problem.

Can I monitor server CPU, memory, and disk usage?

Yes. Configure optional server metric collection and schedule php artisan laritor:send-metrics on each server you want to monitor. Review resource trends, reporting status, runtime information, and application configuration alongside performance problems. Server metrics need this setup in addition to ordinary application event recording.

Alerts, AI, and reports

Get notified, debug with AI, and keep your team informed.

Where can Laritor send problem alerts?

Laritor supports email lists, Slack, Discord, Microsoft Teams, Telegram, GitHub issues, Linear issues, and custom webhooks. Configure the integrations you want, then select the issue types and destinations in Alerts. Alerts can include application context and links to the relevant recorded activity.

Can production and staging use different alert destinations?

Yes. Set default alert channels for an application, then configure environment-specific overrides. For example, route production exceptions to Slack and Linear while sending staging alerts to Discord. Integrations must be configured before they can be selected as alert destinations.

How does Laritor’s in-app AI help with debugging?

Laritor’s AI recommendations can help explain recorded exceptions and investigate performance problems in requests and queries. The current AI provider guide includes 50 AI prompts per month by default, with an option to connect your own provider for additional usage. Review suggestions against your code and test changes before deploying them.

What can my AI coding agent do with Laritor MCP?

Laritor’s MCP server lets a compatible coding agent retrieve exception details and the recorded execution timeline, including the events around the failure. The agent can use that context alongside your repository to investigate the cause and work on a fix. The connection uses OAuth and has read-only access to your Laritor account.

Can I connect my own AI provider or API key?

Yes. The current integration guide lists Anthropic, DeepSeek, Ollama, OpenAI, xAI, zAI, and Gemini. Choose a supported provider and model in Settings, add the required connection details, and save the configuration. Usage through your own integration follows the provider’s quota and billing.

Can I customize dashboards and display them on a wall monitor?

Yes. Build dashboards from more than 85 widgets and choose the views your team needs. Live dashboards support a default time window and automatic refresh using URL parameters. This is useful for keeping an application overview visible on an office or operations screen.

Can I receive daily or weekly performance reports?

Yes. Create a report, choose its metrics and schedule, and select the email recipients. Laritor generates PDF snapshots covering the selected request, queue, query, exception, and other application data. Receive them without logging in and share the PDF with teammates.

Privacy, hosting, and support

Control sensitive information and understand how Laritor is hosted.

How can I protect sensitive data and personal information?

Laritor applies redaction in your app before recorded data is sent. Customize profile, email, IP-address, user-agent, string, and structured-value redactors to remove or anonymize information your team should not collect. Review payload controls and outgoing data for your app’s own sensitive fields, including custom event metadata.

Does Laritor record request bodies, headers, and session values by default?

The current DefaultOverride records request and response headers and session values by default. Request and response bodies are disabled by default, and redaction applies to recorded data. Customize payload and context methods to omit fields your team does not need; body settings alone do not control every other field.

Can I follow sessions without sending all session values?

Yes. Use recordSessionData to omit the values attached to a request while retaining the session ID used to connect supported requests. Session monitoring depends on a Laravel session being available; stateless requests may not belong to a recorded session. You can also customize profile and client information.

Where is Laritor data stored?

Choose your account’s storage region when signing up. The current requirements guide lists New York City in the United States and Amsterdam in the Netherlands. Use the ingest and MCP endpoints for your selected account region.

Can I self-host Laritor?

Laritor is currently offered as a cloud-hosted service, and a self-hosted version is not available. Install the Laravel client in your own application and send recorded activity to your Laritor account’s ingest endpoint.

Does Laritor use my application data to train AI models?

Laritor does not use customer application data to train AI models. AI insights use relevant recorded context to produce recommendations. If you connect your own AI provider, review that provider’s data handling and settings as well as the information your app records.

Can I export and share application performance snapshots?

Scheduled reports produce PDF snapshots that can be emailed to your team and shared with teammates. Choose the request, queue, query, exception, and other supported sections you want to include. Contact support if you need a different data export or migration format.

How do I request deletion of my data?

Email [email protected] with your account and the data you want deleted. The support team can help with the request and any account verification needed. The privacy policy explains how deletion requests and applicable retention obligations are handled.

Where can I get help with installation or an application issue?

Start with Laritor’s documentation for installation, recording controls, integrations, and resource guides. For an account question or help with your setup, email [email protected]. Include your Laravel and client versions, the relevant environment, and a description of the problem, while leaving out keys and private payloads.

Still have a question?

Get help with
your Laravel app and setup.

Tell us what you want to monitor or where you’re stuck. We can help you choose a recording mode, understand event usage, or configure an integration.