Overview
Data flow
1
Capture
The client package hooks into Laravel’s service container and captures requests, exceptions, queries, jobs, commands, and more from the monitored application.
2
Send
Captured data is sent via authenticated HTTP
POST to the server’s /api/ingest endpoint, using the project’s API token.3
Queue
The server immediately queues the payload and responds with
200 OK — zero processing delay, so your application’s request lifecycle is never blocked.4
Process
A queue worker picks up the
ProcessIngestedRecords job. The IngestService stores the records, calculates fingerprints to group related issues, runs security analysis, and evaluates alert thresholds.5
Broadcast
A WebSocket event (
ProjectDataIngested) is broadcast over Reverb so the React dashboard updates in real time — no refresh required.Why asynchronous ingestion matters
Because the server queues each payload and returns instantly, the cost of monitoring on your application is a single lightweight HTTP call. All the heavy work — storage, issue grouping, threat detection, and broadcasting — happens on the LaraOwl server’s background workers, not in your users’ requests.This is why a running queue worker is required on the server. Without it, ingested payloads are accepted but never processed, and nothing appears in the dashboard. See Troubleshooting.