Debugging
The context you wish you had at 3 in the morning.
A stack trace tells you where it broke. nopanic also records what the request looked like and which queries ran, so you can see why.
Request and query context
For every exception nopanic captures the request payload and the SQL that ran, so you can reproduce the bug instead of guessing.
Debug sessions on live sites
Start a debug session for a client site to capture extra context for a short period, without deploying debug code to production.
Sensitive data stays out
Passwords, tokens and other sensitive fields are filtered before anything leaves your server.
Linked to the incident
Debug context sits in the same timeline as the outage and the exception, so the whole story of an incident is in one place.
Frequently asked questions
Does debugging slow down my app?
Context is only collected when an exception happens or while a debug session is active.
Is this a replacement for Laravel Telescope?
Telescope is great locally. nopanic is built for production, across all your client sites, with data stored in the EU.
Which data is filtered?
Common sensitive fields such as passwords and tokens are filtered by default, and you can add your own.
Part of one platform
- Uptime monitoring Website uptime monitoring every 60 seconds
- Error tracking Laravel error tracking, hosted in the EU
- Security Laravel security scanner for every client app
- Cron monitoring Cron job and Laravel scheduler monitoring
- SSL monitoring SSL certificate monitoring and expiry alerts
- Status pages Status pages on your own domain
All of this for every client site, in one place.
Monitoring, errors, debugging and security for every Laravel app you run. Hosted and processed in the EU.
