Skip to main content
​
October 14, 2025

​
SOC 2 Type 1 Compliance

SOC2 Type 1
We’ve achieved SOC 2 Type 1 certification for Nightwatch. Type 1 compliance ensures that Nightwatch’s security and data protection controls are properly designed, providing robust security practices to protect your data.Request our SOC 2 Type 1 compliance report.
​
October 1, 2025

​
Auto-resolve stale issues

Auto-resolve stale issues
Nightwatch can now automatically resolve issues with no new activity after 7, 14, or 30 days. This keeps your issue list focused on what’s actively impacting your apps. You can enable this from your application settings.

​
Identify the user behind each job

Nightwatch now links queued jobs and their events, such as exceptions, back to the user that dispatched them. This lets you see the direct user impact of failing jobs and other errors, giving you a clear picture of how asynchronous activity affects your users. Update the Nightwatch package to v1.14.0 or later to get started.
​
September 16, 2025

​
Sydney region now available

Nightwatch is now available in Sydney, our first Asia Pacific data centre.
Sydney Region
Teams across APAC can enjoy faster ingestion and queries, while Australian organisations gain compliance with local data sovereignty requirements.Learn more about our supported regions.
​
August 30, 2025

​
Attach custom metadata with Laravel Context

Add metadata with context
Nightwatch now integrates with Laravel Context to let you attach rich metadata to each event, making it easier than ever to reproduce and debug issues. You can augment requests or jobs with any extra details, such as user type, subscription plans, tenant information, and active feature flags.Learn more about attaching metadata with Context.

​
Enhanced stack traces

Enhanced stack traces
We’ve redesigned the exception viewer to surface the information you care about most. Your application frames are now easier to distinguish from vendor frames and include code snippets to provide you with the contextual information needed to pinpoint the issue.

​
Improved fatal error monitoring

We’ve enhanced fatal error capturing, including out-of-memory errors and max execution timeouts. By reserving a minimal amount of memory, we now ensure these fatal errors are successfully delivered to Nightwatch. To benefit from these improvements, upgrade the Nightwatch package to v1.13.2 or later.
​
July 30, 2025

​
Light mode

Light mode
Light mode has arrived, bundled with a series of accessibility and usability improvements for a cleaner, brighter workspace. Easily switch between light and dark mode in your profile settings.

​
Slack integration

Slack integration
Get key updates directly in Slack with our latest integration. You can now receive alerts for:
  • New exceptions
  • Performance threshold breaches
  • Regressions to previously resolved issues
  • Issue status changes
View our integration setup guide.

​
Issue management

Issue management
We’ve enhanced our issue management capabilities to streamline your workflow. Our latest updates now allow you to perform bulk actions and assign users, priorities, and statuses directly from the dashboard.

​
Agent Docker image

Agent Docker Image
We’ve released our official Nightwatch Agent Docker Image making it simpler than ever to monitor Laravel apps in containerized environments. You can run the agent as a sidecar, background process, or agent service.Get started with our Docker image.

​
Lower cost for additional events

Building on our recent 50% event increase across all plans, we’ve also reduced the price of additional events across the board. This makes it easier and more affordable to scale up or debug your applications without interruption.Learn more about additional events.
​
June 26, 2025

​
Laravel Octane support

Laravel Octane
Laravel Octane is now fully supported by Nightwatch. Upgrade the Nightwatch package to v1.9.0 or greater to get started.

​
Advanced sampling and filtering

Advanced sampling
Nightwatch now supports advanced sampling and filtering options, allowing you to customize which events are captured and which are excluded.

​
Route sampling

The Sample middleware lets you apply custom sampling rates to specific routes or route groups within your application.This is especially useful when you want to increase visibility on critical endpoints or reduce noise from high-traffic, low-value routes.
// web.php

use Illuminate\Support\Facades\Route;
use Laravel\Nightwatch\Http\Middleware\Sample;

// Applied to a single route
Route::get('/users', [UserController::class, 'index'])
    ->middleware(Sample::rate(0.8));

// Applied to a route group
Route::middleware(Sample::rate(0.2))->group(function () {
  // ...
});

​
Unmatched routes

The Sample middleware can also be applied to unmatched routes, useful for monitoring bot traffic.
// Applied to unmatched 404 routes
Route::fallback(fn () => abort(404))
    ->middleware(Sample::rate(0.1));
Learn more about route-based sampling.

​
Always capture exceptions

By default, Nightwatch will always capture exceptions, no matter what sampling rules are in place. This means that even if a request or job was sampled out, any exception that occurs forces the entire lifecycle to be recorded, ensuring you collect all the most important context leading up to that event.If you want to disable this behavior and only capture exceptions when they occur on sampled routes, you can set the NIGHTWATCH_EXCEPTION_SAMPLE_RATE environment variable to 0.
NIGHTWATCH_EXCEPTION_SAMPLE_RATE=0

​
Event filtering

In addition to sampling, you can filter out specific event types entirely. This allows you to focus your event allocation on the events that matter most to your application.When an event type is filtered, it is completely excluded from the collection; no data will be sent to Nightwatch, and the event will not appear in your stream, traces, or usage metrics.For example, if you want to ignore cache events, you can set the NIGHTWATCH_IGNORE_CACHE_EVENTS environment variable to true.
NIGHTWATCH_IGNORE_CACHE_EVENTS=true
View the full list of filterable event types.

​
Log-level filtering

By default, Nightwatch respects Laravel’s default logging behavior, but we have added a new environment variable to allow you to customise which logs are sent to Nightwatch.
NIGHTWATCH_LOG_LEVEL=warning
This setting ensures that only logs at the specified level or higher (e.g., warning, error, critical) are sent to Nightwatch. Lower-level logs (e.g., info, debug) will be ignored.Learn more about log-level configuration.
​
June 17, 2025

​
Introducing Nightwatch

First class monitoring designed for Laravel
Hyper-optimized and Laravel-native, it’s the official application monitoring platform for Laravel apps, giving you unparalleled insights into how your app performs in the real world.
  • Launched with U.S. and EU data residency, with more regions coming soon
  • Open-sourced our Nightwatch agent
Get started with Nightwatch.
⌘I