Events are the core unit of observability in Nightwatch. They represent activity that has occurred inside your Laravel application — each one tied to a specific point in time and environment.
Database queries executed through Laravel’s query builder or Eloquent ORM are recorded, including their SQL statement, parameter placeholders, connection, execution time, and context within the request or job lifecycle.
Any outgoing HTTP requests made via Laravel’s Http facade or the underlying Guzzle client are tracked — including URL, method, response time, and any errors.
Tasks registered in Laravel’s scheduler (routes/console.php) are tracked when executed. You can see run times, success/failure, and view logs or exceptions generated during execution.
Artisan commands are logged whenever they run, capturing the command name, parameters, runtime, and exit code — useful for debugging CI/CD scripts or automated tasks.
Nightwatch captures interactions with Laravel’s cache layer — including hit, miss, delete, write and fail events. You’ll see which cache keys are being used and how frequently.
Structured logs written to Laravel’s logging system are ingested in real-time, allowing you to search and correlate them alongside requests, jobs, and other event types.
Outbound emails sent via Laravel’s mail system are logged, including subject, recipient, and delivery status. This makes it easier to trace email issues without needing to check your mail provider dashboard.
All exceptions are captured automatically. Nightwatch shows the exception type, message, stack trace, request context, and related events to help you debug without switching tools.
