{"id":411,"date":"2025-08-27T21:04:56","date_gmt":"2025-08-27T21:04:56","guid":{"rendered":"https:\/\/1v0.net\/blog\/?p=411"},"modified":"2025-08-27T21:04:58","modified_gmt":"2025-08-27T21:04:58","slug":"using-laravel-telescope-to-debug-performance-issues","status":"publish","type":"post","link":"https:\/\/1v0.net\/blog\/using-laravel-telescope-to-debug-performance-issues\/","title":{"rendered":"Using Laravel Telescope to Debug Performance Issues"},"content":{"rendered":"\n

Using Laravel Telescope to Debug Performance Issues<\/strong><\/h2>\n\n\n\n

When your Laravel app slows down under traffic, it can be difficult to know whether the issue is database queries, cache misses, slow jobs, or external APIs. Laravel Telescope<\/strong> is a powerful debugging assistant that gives you full visibility into what your app is doing in real time. In this guide, we\u2019ll install Telescope, explore its dashboard, and learn how to use it to identify and fix performance bottlenecks.<\/p>\n\n\n\n

<\/div>\n\n\n\n\n

1 – Install Telescope<\/strong><\/h2>\n\n\n\n

Telescope is a Laravel package maintained by the core team. It\u2019s usually installed as a development dependency, but can also be deployed in production with proper authentication.<\/p>\n\n\n

composer require laravel\/telescope --dev\nphp artisan telescope:install\nphp artisan migrate<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
This installs Telescope, publishes its assets, and sets up the necessary database tables to store logs and metrics.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
2 – Protecting the Telescope Dashboard<\/strong><\/h2>\n\n\n\n
The dashboard is available at \/telescope<\/code>. You should restrict access to only admins or local environments for security.<\/p>\n\n\n
\/\/ app\/Providers\/TelescopeServiceProvider.php<\/span>\nprotected<\/span> function<\/span> gate<\/span>()<\/span>\n<\/span>{\n    Gate::define('viewTelescope'<\/span>, function<\/span> ($user)<\/span> <\/span>{\n        return<\/span> in_array($user->email, [\n            'admin@example.com'<\/span>,\n        ]);\n    });\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This gate ensures only whitelisted users can access Telescope in production. In local environments, it\u2019s usually open by default.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
3 – Monitoring Queries<\/strong><\/h2>\n\n\n\n
Telescope shows every query executed in your app, with bindings and execution times. This helps spot N+1 problems<\/strong> and missing indexes quickly.<\/p>\n\n\n
\/\/ Example of an N+1 problem<\/span>\n$users = User::all();\n\nforeach<\/span> ($users as<\/span> $user) {\n    echo<\/span> $user->posts->count(); \/\/ triggers extra query for each user<\/span>\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Telescope will display hundreds of queries in this case, showing the N+1 issue. The fix is eager loading:<\/p>\n\n\n
\/\/ Optimized with eager loading<\/span>\n$users = User::with('posts'<\/span>)->get();\n\nforeach<\/span> ($users as<\/span> $user) {\n    echo<\/span> $user->posts->count(); \/\/ no extra queries<\/span>\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Now Telescope will show just two queries: one for users, one for posts. For more on this technique, see Eager Loading vs Lazy Loading in Laravel: Best Practices<\/a>.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
4 – Tracking Requests & Exceptions<\/strong><\/h2>\n\n\n\n
Telescope records every incoming request and any exceptions thrown. This is extremely useful for debugging performance-related errors.<\/p>\n\n\n
\/\/ Example: log request info in Telescope<\/span>\nRoute::get('\/profile'<\/span>, function<\/span> ()<\/span> <\/span>{\n    return<\/span> view('profile'<\/span>);\n});<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
When visiting \/profile<\/code>, Telescope shows request duration, middleware stack, and queries executed. Exceptions appear in a separate tab, making it easy to trace issues.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
5 – Monitoring Queues & Jobs<\/strong><\/h2>\n\n\n\n
Telescope integrates with Laravel\u2019s queue system. It shows processed jobs, pending jobs, and failures in real time. This complements queues<\/a> and Horizon<\/a>, giving you both deep debugging and production monitoring tools.<\/p>\n\n\n
\/\/ Dispatch a queued job<\/span>\nSendWelcomeEmail::dispatch($user);<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
After dispatching a job, check Telescope\u2019s Jobs<\/strong> tab. You\u2019ll see job payload, execution time, and retry history\u2014perfect for debugging job performance.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
6 – Insights into Cache & Redis<\/strong><\/h2>\n\n\n\n
Telescope logs cache hits and misses. This is critical when evaluating caching strategies<\/a> for high-traffic apps.<\/p>\n\n\n
\/\/ Example: cached query<\/span>\nCache::remember('users.active'<\/span>, 60<\/span>, function<\/span> ()<\/span> <\/span>{\n    return<\/span> User::active()->get();\n});<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Telescope shows whether the result came from cache or DB. This makes it easier to validate that caching is working and saving resources.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
7 – Profiling Performance<\/strong><\/h2>\n\n\n\n
Telescope records timeline data for every request: middleware duration, query time, job dispatch delays, etc. This is invaluable for pinpointing slow points in your app\u2019s lifecycle.<\/p>\n\n\n\n
Combine Telescope insights with Octane<\/a> to spot memory leaks and performance issues in persistent worker setups.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
Wrapping Up<\/h2>\n\n\n\n
Laravel Telescope<\/strong> provides real-time visibility into queries, requests, jobs, cache, and exceptions. It\u2019s a must-have tool for debugging performance issues in development and can be secured for production use. With Telescope, you can spot bottlenecks like N+1 queries, missing indexes, or slow jobs before they impact your users.<\/p>\n\n\n\n
<\/div>\n\n\n\n\n
What\u2019s Next<\/h2>\n\n\n\n