[ MIGRATION ]

Migrate from Flare to NightOwl

Flare's exception tracking is great. NightOwl adds queries, queues, schedules, cache, and request latency — one tool, one bill.

QUICK ANSWER

How do I migrate from Flare to NightOwl?

Install NightOwl alongside Flare (both SDKs run in parallel). Point NightOwl at your PostgreSQL. Validate exception coverage matches Flare for a week. Recreate your alert channels in NightOwl. Remove Flare SDK when confident. Unlike Flare, NightOwl captures queries, queues, scheduled tasks, cache, mail, notifications, outgoing HTTP, and logs — so you can probably cancel your separate performance APM too.

Updated · 2026-04-13

What you get by switching

Watcher Flare NightOwl
ExceptionsYes (polished)Yes
Request tracesNoYes
Query patterns + p95NoYes
Queue jobsNoYes
Scheduled tasksNoYes
Cache hit/missNoYes
Outgoing HTTPNoYes
Data storageFlare cloudYour PostgreSQL

Migration steps

01

Install NightOwl

composer require nightowl/agent, then php artisan nightowl:install. Flare SDK remains untouched.

02

Point at PostgreSQL

Run the installer with your Postgres credentials. Schema is created automatically.

03

Parallel run (1 week)

Both SDKs active. Validate exception coverage matches Flare. Explore the new watchers — queries, queue jobs, schedules.

04

Reconfigure alert channels

Recreate Slack/Discord/Email webhooks in NightOwl. Disable Flare alerts to avoid duplicate pages.

05

Remove Flare SDK

composer remove spatie/laravel-flare, delete config/flare.php, remove FLARE_KEY env var.

06

Cancel Flare subscription

After a week running solo on NightOwl. Keep Flare read-only if you want historical access; otherwise cancel.

Code removal

bash
composer remove spatie/laravel-flare
rm config/flare.php

# .env — remove:
# FLARE_KEY=...

# If you registered Flare in the exception handler, remove:
# - App\Exceptions\Handler @ register() Flare-specific reporters

php artisan config:clear

The cost case

Flare is $9/mo Hobby (single user, single project, 10K errors), $29/mo Standard, $69/mo Growth, or $279/mo Premium. If exception tracking is your only monitoring need and you're a tiny app, Flare Hobby is cheaper — but you're missing performance monitoring. Teams running Flare Standard + a separate APM (Scout $99, Inspector $39, etc.) typically pay $60-130/mo total. NightOwl from $5/mo replaces both.

AFTER MIGRATION

One tool for errors + performance + queues

Exception grouping, query patterns, queue failure rates, scheduled task history — all in one dashboard. Data in your PostgreSQL. From $5/month flat.

INSTALL

Install in 60 seconds

Works on Laravel 10+ / PHP 8.2+. Keep the official Nightwatch package — NightOwl reads the same instrumentation.

$ composer require nightowl/agent
$ php artisan nightowl:install

Publishes the config, creates monitoring tables in your PostgreSQL, and starts the agent. First payload lands in the dashboard within 30 seconds.

Frequently asked questions

Why would I switch from Flare to NightOwl?

Flare is excellent at exception tracking but that's all it does — you still need a separate APM for queries, queues, scheduled tasks, cache, and request latency. Many teams find that running Flare + a second APM costs more per month than NightOwl, which covers all of it from $5/month flat with BYOD Postgres.

Can I keep Flare and add NightOwl alongside?

Yes, they don't conflict at runtime. Both SDKs can run in parallel. Some teams keep Flare permanently for its specific Spatie-ecosystem polish on exceptions and add NightOwl for the wider APM surface. Cost-wise, NightOwl alone usually wins, but if you love Flare's UX for exception triage, parallel operation is legitimate.

How long does the Flare → NightOwl migration take?

~30 minutes of install + 1 week of parallel validation + 10 minutes of cleanup. The install itself is straightforward (composer require + a config pointing at your PostgreSQL). Parallel period lets you make sure NightOwl surfaces the same exceptions Flare did.

What does NightOwl add that Flare doesn't have?

Request performance (per-route p95), SQL query monitoring (fingerprinted patterns with call counts, slow queries, per-request query lists), queue job monitoring (per-class failure rate, runtime), scheduled task history, cache hit/miss tracking, outgoing HTTP monitoring, logs aggregation. Flare does one thing (exceptions) very well; NightOwl does many things.

Can I migrate my Flare alert configuration?

Not directly — each product has its own alert channel concepts. Recreate your Slack/Discord webhooks in NightOwl's alert channels UI. The webhook URLs are still valid; just paste them into NightOwl. Takes 5 minutes per channel.

Will my existing Flare team members have to learn new tooling?

Yes, but the concept map is similar. Both tools offer issue status, priority, assignment, and comments. NightOwl's UI is different but the vocabulary is familiar. Expect a short onboarding curve, not weeks of training.

What happens to my Flare historical data?

Stays in your Flare account until you cancel. No migration path. Keep Flare read-only for a month after switching if you want access to closed-issue history; most teams find they don't actually reference it.

PRICING

Flat pricing. No event caps. No per-seat fees.

14-day free trial, no credit card. Your PostgreSQL, your data.

HOBBY

$5 /month

1 app · 14 days lookback · all Laravel events

TEAM

$15 /month

Up to 3 connected apps · unlimited environments · all Laravel events

AGENCY

$69 /month

Unlimited apps · unlimited agent instances · same flat rate at any traffic

Related