Laravel Debugbar

https://laraveldebugbar.com
Admin
Laravel Debugbar is a package that integrates PHP Debug Bar with Laravel to debug database queries,...
Tokens:18,094
Snippets:123
Trust Score:6.4
Update:10 months ago
Show doc for...
Tokens:
Raw
### Install Laravel Debugbar using Composer

Source: https://laraveldebugbar.com/installation

This command installs the Laravel Debugbar package using Composer. It is recommended to install it only for development environments using the --dev flag.

```bash
composer require barryvdh/laravel-debugbar --dev
```

--------------------------------

### Laravel Debugbar: Backtrace Example (PHP)

Source: https://laraveldebugbar.com/features

This snippet provides a backtrace example as logged by Laravel Debugbar. It lists the sequence of file and line number calls leading to a specific query execution. This is invaluable for debugging and tracing the origin of database operations.

```php
Users/barry/Sites/laravel-debugbar/src/DataCollector/QueryCollector.php:181
    * Users/barry/Sites/laravel-debugbar/src/LaravelDebugbar.php:384
    * vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php:129
    * vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php:104
    * vendor/laravel/framework/src/Illuminate/Cache/Repository.php:116
```

```php
Users/barry/Sites/laravel-debugbar/src/DataCollector/QueryCollector.php:181
    * Users/barry/Sites/laravel-debugbar/src/LaravelDebugbar.php:384
    * vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php:409
    * vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php:144
    * vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php:104
```

```php
Users/barry/Sites/laravel-debugbar/src/DataCollector/QueryCollector.php:181
    * Users/barry/Sites/laravel-debugbar/src/LaravelDebugbar.php:384
    * vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php:189
    * vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php:166
    * vendor/laravel/framework/src/Illuminate/Cache/Repository.php:236
```

```php
Users/barry/Sites/laravel-debugbar/src/DataCollector/QueryCollector.php:181
    * Users/barry/Sites/laravel-debugbar/src/LaravelDebugbar.php:384
    * vendor/laravel/pennant/src/Drivers/DatabaseDriver.php:153
    * vendor/laravel/pennant/src/Drivers/Decorator.php:357
    * vendor/laravel/pennant/src/Drivers/Decorator.php:385
```

--------------------------------

### Laravel Debugbar: SELECT Query Example

Source: https://laraveldebugbar.com/features

This snippet shows an example of a SELECT query logged by Laravel Debugbar. It includes the SQL statement and the bindings used. This information is crucial for understanding data retrieval patterns and potential optimizations.

```sql
select * from `cache` where `key` in ('remember')
```

```sql
select * from `features` where (`name` = 'debugbar' and `scope` = '__laravel_null')
```

```sql
select * from `features` where (`name` = 'new-api' and `scope` = '__laravel_null')
```

--------------------------------

### Debugbar Demo Connection Established Log (PHP)

Source: https://laraveldebugbar.com/installation

This snippet represents the logging of a database connection establishment within the debugbar demo. It includes a backtrace to pinpoint the exact location in the codebase where this connection event was initiated.

```php
namespace DebugBar\DataCollector;

class QueryCollector
{
    // ... existing code ...

    public function addConnection($name, $time)
    {
        // Assuming a method to log connection events exists
        $this->logConnection($name, $time, debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS));
    }

    protected function logConnection($name, $time, $trace)
    {
        // Logic to store connection information
        // For example purposes, we'll just show the structure:
        // echo "Connection Established: {$name} ({$time}ms)\n";
        // print_r($trace);
    }

    // ... existing code ...

    // Within a method that establishes a connection, e.g., in a demo controller or service provider:
    public function handleConnectionEstablishment($connectionName)
    {
        $startTime = microtime(true);
        // ... code to establish database connection ...
        $endTime = microtime(true);
        $this->addConnection($connectionName, ($endTime - $startTime) * 1000);
    }
}

```

--------------------------------

### Configure Laravel Debugbar Settings

Source: https://laraveldebugbar.com/installation

This snippet shows the configuration options for Laravel Debugbar within the `config/debugbar.php` file. It demonstrates how to enable/disable the debugbar using environment variables and configure ignored URIs.

```php
/*
 |--------------------------------------------------------------------------
 | Debugbar Settings
 |--------------------------------------------------------------------------
 |
 | Debugbar is enabled by default, when debug is set to true in app.php.
 | You can override the value by setting enable to true or false instead of null.
 |
 | You can provide an array of URI's that must be ignored (eg. 'api/*')
 |
 */

'enabled' => env('DEBUGBAR_ENABLED', null),
'hide_empty_tabs' => false, // Hide tabs until they have content
'except' => [
    'telescope*',
    'horizon*', 
],
```

--------------------------------

### Select from Cache Table Again (PHP)

Source: https://laraveldebugbar.com/features

This PHP code example, similar to a previous one, shows another query to select data from the `cache` table using a specific key. This repetitive logging can help in performance analysis.

```php
<?php
// Another example SQL query for selecting from cache
$sql = "select * from `cache` where `key` in (?)";
$bindings = ['from-cache'];
// Laravel Debugbar's QueryCollector tracks these cache operations.
```

--------------------------------

### Configure Laravel Debugbar in Lumen

Source: https://laraveldebugbar.com/installation

This snippet demonstrates how to configure the Laravel Debugbar in your Lumen application by calling the configure method with 'debugbar' as the argument. This allows you to publish and modify the debugbar's configuration file.

```php
$app->configure('debugbar');
```

--------------------------------

### Log SQL Query Execution with Bindings and Backtrace (PHP)

Source: https://laraveldebugbar.com/installation

This snippet demonstrates how a query is logged, including the SQL statement, its execution time, any bound parameters, and a backtrace indicating where the query originated within the application. This is fundamental for identifying and optimizing slow database queries.

```php
namespace DebugBar\DataCollector;

class QueryCollector
{
    // ... existing code ...

    protected function logQuery($sql, $bindings, $time, $trace = null)
    {
        // Logic to format and store the query details
        $this->queries[] = [
            'sql' => $sql,
            'bindings' => $bindings,
            'time' => $time,
            'trace' => $trace ?: debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS),
            'connection' => $this->connectionName,
            'is_duplicate' => false // Placeholder, actual logic to determine duplicates would be here
        ];
    }

    // ... existing code ...

    public function addQuery($sql, $bindings = [], $time = null, $trace = null)
    {
        // Example of how a query might be added, potentially with timing and trace information
        if ($time === null) {
            $time = $this->getRealSqlExecutionTime(); // Assuming this method exists and returns execution time
        }
        $this->logQuery($sql, $bindings, $time, $trace);
    }

    // ... existing code ...
}

```

--------------------------------

### Logging and Timing with Debugbar Helper Functions

Source: https://laraveldebugbar.com/usage

Provides examples of using global helper functions for dumping variables, measuring code execution time, and logging messages. These functions offer a more concise way to interact with the Debugbar.

```php
// All arguments will be dumped as a debug message
debug($var1, $someString, $intValue, $object);

// `$collection->debug()` will return the collection and dump it as a debug message. Like `$collection->dump()`
collect([$var1, $someString])->debug();

start_measure('render','Time for rendering');
stop_measure('render');
add_measure('now', LARAVEL_START, microtime(true));
measure('My long operation', function() {
    // Do something…
});
```

--------------------------------

### Select from Cache Table (PHP)

Source: https://laraveldebugbar.com/features

This PHP code example demonstrates a query to select data from the `cache` table based on a given key. It's a common operation for retrieving cached data and is logged by Laravel Debugbar.

```php
<?php
// Example SQL query for selecting from cache
$sql = "select * from `cache` where `key` in (?)";
$bindings = ['not-from-cache'];
// Laravel Debugbar's QueryCollector tracks such cache lookups.
```

--------------------------------

### Publish Laravel Debugbar Configuration

Source: https://laraveldebugbar.com/installation

This Artisan command publishes the configuration file for Laravel Debugbar. This allows you to customize its settings, such as enabling/disabling the debugbar or specifying ignored URIs.

```php
php artisan vendor:publish --provider="Barryvdh\Debugbar\ServiceProvider"
```

--------------------------------

### Add Laravel Debugbar to Octane Flush List

Source: https://laraveldebugbar.com/installation

This configuration snippet from `config/octane.php` shows how to add `BarryvdhDebugbarLaravelDebugbar` to the `flush` list. This is necessary when using Octane to ensure the debugbar functions correctly across requests.

```php
'flush' => [
    \Barryvdh\Debugbar\LaravelDebugbar::class,
    ],
```

--------------------------------

### Laravel Event Dispatching and Handling

Source: https://laraveldebugbar.com/installation

This section lists various events dispatched and handled within a Laravel application. It covers events related to routing, database operations, Eloquent model events, logging, queueing, and caching. These events allow for hooking into different stages of the application's lifecycle.

```text
Illuminate\Routing\Events\Routing
Illuminate\Routing\Events\RouteMatched
Illuminate\Database\Events\ConnectionEstablished
Illuminate\Database\Events\StatementPrepared
Illuminate\Database\Events\QueryExecuted
eloquent.booting: App\Models\User
eloquent.booted: App\Models\User
Illuminate\Database\Events\StatementPrepared
Illuminate\Database\Events\QueryExecuted
eloquent.retrieved: App\Models\User
Illuminate\Database\Events\StatementPrepared
Illuminate\Database\Events\QueryExecuted
eloquent.retrieved: App\Models\User
Illuminate\Log\Context\Events\ContextDehydrating
Illuminate\Queue\Events\JobQueueing
Illuminate\Database\Events\QueryExecuted
Illuminate\Queue\Events\JobQueued
Illuminate\Log\Context\Events\ContextDehydrating
Illuminate\Queue\Events\JobQueueing
Illuminate\Database\Events\QueryExecuted
Illuminate\Queue\Events\JobQueued
Illuminate\Log\Context\Events\ContextDehydrating
Illuminate\Queue\Events\JobQueueing
Illuminate\Database\Events\QueryExecuted
Illuminate\Queue\Events\JobQueued
Illuminate\Cache\Events\RetrievingKey
Illuminate\Database\Events\StatementPrepared
Illuminate\Database\Events\QueryExecuted
Illuminate\Cache\Events\CacheMissed
Illuminate\Cache\Events\WritingKey
Illuminate\Database\Events\QueryExecuted
Illuminate\Cache\Events\KeyWritten
```

--------------------------------

### Register Lumen Service Provider for Laravel Debugbar

Source: https://laraveldebugbar.com/installation

This code snippet shows how to register the BarryvdhDebugbarLumenServiceProvider in your Lumen application's bootstrap/app.php file. It ensures the debugbar is only registered when APP_DEBUG is enabled in your environment variables.

```php
if (env('APP_DEBUG')) {
 $app->register(Barryvdh\Debugbar\LumenServiceProvider::class);
}
```

--------------------------------

### Log Debug Message with Laravel Debugbar

Source: https://laraveldebugbar.com/installation

This PHP code shows how to log a debug message using Laravel's Log facade, which will be captured and displayed in the 'Logs' panel of the Laravel Debugbar. It also demonstrates adding a custom exception to the debugbar.

```php
\Log::debug('This is a log message.');
debugbar()->addThrowable(new \RuntimeException('Something went wrong'));
```

--------------------------------

### Laravel Debugbar: DELETE Query Example

Source: https://laraveldebugbar.com/features

This snippet illustrates a DELETE query logged by Laravel Debugbar. It displays the SQL statement, the keys targeted for deletion, and their corresponding bindings. This helps in analyzing data removal operations and their impact.

```sql
delete from `cache` where `key` in ('remember', 'illuminate:cache:flexible:created:remember') and `expiration` <= 1738425477
```

--------------------------------

### Laravel HTTP Request Handling Pipeline

Source: https://laraveldebugbar.com/installation

This snippet illustrates the middleware pipeline for handling HTTP requests in a Laravel application. It shows the sequence of middleware classes that process a request before it reaches the application's core logic. Dependencies include the Illuminate\Pipeline\Pipeline class and various middleware classes.

```php
vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php
```

--------------------------------

### Laravel Debugbar: INSERT Query Example

Source: https://laraveldebugbar.com/features

This snippet presents an INSERT query logged by Laravel Debugbar, specifically handling duplicate key updates. It shows the SQL statement, the expiration time, key, and value being inserted or updated. This is useful for understanding data persistence and caching mechanisms.

```sql
insert into `cache` (`expiration`, `key`, `value`) values (1738425478, 'remember', 's:6:"sdfdsf";') on duplicate key update `expiration` = values(`expiration`), `key` = values(`key`), `value` = values(`value`)
```

--------------------------------

### Register Debugbar Facade without Auto-Discovery

Source: https://laraveldebugbar.com/installation

This PHP code snippet demonstrates how to register the Debugbar facade manually within the `register` method of `AppProvidersAppServiceProvider.php` when auto-discovery is disabled. This allows you to use the `Debugbar` facade for logging messages.

```php
public function register(): void
{
    $loader = \Illuminate\Foundation\AliasLoader::getInstance();
    $loader->alias('Debugbar', \Barryvdh\Debugbar\Facades\Debugbar::class);
}
```

--------------------------------

### Insert Job into Jobs Table (PHP)

Source: https://laraveldebugbar.com/features

This snippet shows a PHP example of inserting a job into the `jobs` table, typically used for background task processing in Laravel. It includes the SQL query and associated data bindings.

```php
<?php
// Example SQL query for inserting a job
$sql = "insert into `jobs` (`queue`, `attempts`, `reserved_at`, `available_at`, `created_at`, `payload`) values (?, ?, null, ?, ?, ?)";
$bindings = [
    'default',
    0,
    1738425477,
    1738425477,
    '{"uuid":"b02f18e3-bce4-44ee-87e9-66880aef0626","displayName":"App\\Jobs\\DemoJob","job":"Illuminate\\Queue\\CallQueuedHandler@call","maxTries":null,"maxExceptions":null,"failOnTimeout":false,"backoff":null,"timeout":null,"retryUntil":null,"data":{"commandName":"App\\Jobs\\DemoJob","command":"O:16:\"App\\Jobs\\DemoJob\":0:{}"}}'
];
// In Laravel Debugbar, this would be logged by QueryCollector.
```

--------------------------------

### Database Cache Operations - Laravel Debugbar

Source: https://laraveldebugbar.com/index

This snippet illustrates SQL queries related to database cache operations as captured by Laravel Debugbar. It includes examples of selecting, deleting, and inserting data into the cache table, along with their respective timings and bound parameters. These queries are essential for understanding cache performance and debugging cache-related issues.

```sql
select * from `cache` where `key` in ('remember')
delete from `cache` where `key` in ('remember', 'illuminate:cache:flexible:created:remember') and `expiration` <= 1738425477
insert into `cache` (`expiration`, `key`, `value`) values (1738425478, 'remember', 's:6:"sdfdsf";') on duplicate key update `expiration` = values(`expiration`), `key` = values(`key`), `value` = values(`value`)
```

--------------------------------

### Log Laravel Job Insertion with QueryCollector

Source: https://laraveldebugbar.com/installation

This snippet demonstrates how Laravel Debugbar's QueryCollector logs the insertion of jobs into the 'jobs' table. It captures the SQL query, its execution time, and the bound parameters, including job details like UUID, display name, and payload. This is useful for monitoring queue processing.

```PHP
<?php
// Example of a job insertion logged by QueryCollector
// QueryCollector.php#181

// Simulating an insert into the jobs table
$query = "insert into `jobs` (`queue`, `attempts`, `reserved_at`, `available_at`, `created_at`, `payload`) values ('default', 0, null, 1738425477, 1738425477, '{"uuid":"b02f18e3-bce4-44ee-87e9-66880aef0626","displayName":"App\\Jobs\\DemoJob","job":"Illuminate\\Queue\\CallQueuedHandler@call","maxTries":null,"maxExceptions":null,"failOnTimeout":false,"backoff":null,"timeout":null,"retryUntil":null,"data":{"commandName":"App\\Jobs\\DemoJob","command":"O:16:\"App\\Jobs\\DemoJob\":0:{}"}}')";
$bindings = [
    'default',
    0,
    null,
    1738425477,
    1738425477,
    '{"uuid":"b02f18e3-bce4-44ee-87e9-66880aef0626","displayName":"App\\Jobs\\DemoJob","job":"Illuminate\\Queue\\CallQueuedHandler@call","maxTries":null,"maxExceptions":null,"failOnTimeout":false,"backoff":null,"timeout":null,"retryUntil":null,"data":{"commandName":"App\\Jobs\\DemoJob","command":"O:16:\"App\\Jobs\\DemoJob\":0:{}"}}'
];
// In a real scenario, Laravel Debugbar would automatically capture this.
?>
```

--------------------------------

### Log Cache Select Operation with QueryCollector

Source: https://laraveldebugbar.com/installation

This snippet illustrates how Laravel Debugbar's QueryCollector logs a 'select' operation on the 'cache' table. It shows the SQL query used to retrieve cache data by key and the bound parameter. This is helpful for diagnosing cache performance and hit/miss rates.

```PHP
<?php
// Example of a cache select query logged by QueryCollector
// QueryCollector.php#181

// Simulating a select from the cache table
$query = "select * from `cache` where `key` in ('not-from-cache')";
$bindings = ['not-from-cache'];
// In a real scenario, Laravel Debugbar would automatically capture this.
?>
```

--------------------------------

### Log Cache Insert/Update Operation with QueryCollector

Source: https://laraveldebugbar.com/installation

This snippet demonstrates how Laravel Debugbar's QueryCollector logs an 'insert on duplicate key update' operation on the 'cache' table. It captures the SQL query for inserting or updating cache entries and the bound parameters, including expiration, key, and value. This aids in understanding cache write patterns.

```PHP
<?php
// Example of a cache insert/update query logged by QueryCollector
// QueryCollector.php#181

// Simulating an insert or update into the cache table
$query = "insert into `cache` (`expiration`, `key`, `value`) values (1738425478, 'from-cache', 's:4:"test";') on duplicate key update `expiration` = values(`expiration`), `key` = values(`key`), `value` = values(`value`)";
$bindings = [
    1738425478,
    'from-cache',
    's:4:"test";'
];
// In a real scenario, Laravel Debugbar would automatically capture this.
?>
```

--------------------------------

### Inspect Request Details - PHP

Source: https://laraveldebugbar.com/usage

This snippet displays details of an incoming HTTP GET request handled by a Laravel application. It includes information such as the URI, middleware, controller, file path, status code, duration, memory usage, full URL, response format, and request headers. It is part of the debugging information provided by Laravel Debugbar.

```php
App\Models\User
    2User.php#?

__

_token
     u9JFPPOjMMb0F01X5kWzhRT1drRZlYqJ4xySWhkW

PHPDEBUGBAR_STACK_DATA
    []

_previous
    array:1 [ "url" => "http://laraveldebugbar.com.test" ]

_flash
    array:2 [ "old" => [] "new" => [] ]

uri
    GET /

middleware
    web

controller
    App\Http\Controllers\DemoController@index

file
    app/Http/Controllers/DemoController.php:15-56

status
    200 OK

duration
    345ms

peak_memory
    24MB

full_url
    http://laraveldebugbar.com.test

response
    text/html; charset=UTF-8

request_format
    html

request_query
    ```
[]

```


request_request
    ```
[]

```


request_headers
    ```

  0 of 0       
array:9 [▼
  "cookie" => array:1 [▶
```

--------------------------------

### Configure Debugbar Editor and Remote Path Mapping (PHP)

Source: https://laraveldebugbar.com/features

This configuration file allows you to set your preferred editor for opening file links in Debugbar. It also enables remote path mapping for environments like Docker or Homestead, allowing Debugbar to correctly link to files on remote servers. Ensure your `remote_sites_path` and `local_sites_path` are correctly set if using remote development.

```php
<?php

/*
    |--------------------------------------------------------------------------
    | Editor
    |--------------------------------------------------------------------------
    |
    | Choose your preferred editor to use when clicking file name.
    |
    | Supported: "phpstorm", "vscode", "vscode-insiders", "vscode-remote",
    |            "vscode-insiders-remote", "vscodium", "textmate", "emacs",
    |            "sublime", "atom", "nova", "macvim", "idea", "netbeans",
    |            "xdebug", "espresso"
    |
    */

    'editor' => env('DEBUGBAR_EDITOR') ?: env('IGNITION_EDITOR', 'phpstorm'),

    /*
    |--------------------------------------------------------------------------
    | Remote Path Mapping
    |--------------------------------------------------------------------------
    |
    | If you are using a remote dev server, like Laravel Homestead, Docker, or
    | even a remote VPS, it will be necessary to specify your path mapping.
    |
    | Leaving one, or both of these, empty or null will not trigger the remote
    | URL changes and Debugbar will treat your editor links as local files.
    |
    | "remote_sites_path" is an absolute base path for your sites or projects
    | in Homestead, Vagrant, Docker, or another remote development server.
    |
    | Example value: "/home/vagrant/Code"
    |
    | "local_sites_path" is an absolute base path for your sites or projects
    | on your local computer where your IDE or code editor is running on.
    |
    | Example values: "/Users/<name>/Code", "C:\\Users\\<name>\\Documents\\Code"
    |
    */

    'remote_sites_path' => env('DEBUGBAR_REMOTE_SITES_PATH'),
    'local_sites_path' => env('DEBUGBAR_LOCAL_SITES_PATH', env('IGNITION_LOCAL_SITES_PATH')),

?>
```

--------------------------------

### Log SQL Insert/Update Query with Bindings - PHP

Source: https://laraveldebugbar.com/usage

This snippet logs a SQL query that inserts data into the 'cache' table, with an 'on duplicate key update' clause. It includes the expiration, key, and value being inserted, along with their bindings. This is a common pattern for caching operations.

```php
insert into `cache` (`expiration`, `key`, `value`) values (1738425478, 'remember', 's:6:"sdfdsf";') on duplicate key update `expiration` = values(`expiration`), `key` = values(`key`), `value` = values(`value`)
Bindings __|
    * 0: 1738425478
    * 1: remember
    * 2: s:6:"sdfdsf";
```

--------------------------------

### Register Twig Extensions for Laravel Debugbar

Source: https://laraveldebugbar.com/usage

This snippet shows how to register the necessary Twig extensions for Laravel Debugbar within your TwigBridge configuration. Ensure you have rcrowe/TwigBridge 0.6.x or later installed. These extensions enhance debugging capabilities within your Twig templates.

```php
'Barryvdh\Debugbar\Twig\Extension\Debug',
'Barryvdh\Debugbar\Twig\Extension\Dump',
'Barryvdh\Debugbar\Twig\Extension\Stopwatch'
```

--------------------------------

### Logging Messages and Timing with Debugbar Facade

Source: https://laraveldebugbar.com/usage

Demonstrates how to log messages using PSR-3 levels and measure the execution time of code blocks with the Debugbar Facade. This requires the Debugbar Facade to be available.

```php
Debugbar::info($object);
Debugbar::error('Error!');
Debugbar::warning('Watch out…');
Debugbar::addMessage('Another message', 'mylabel');

Debugbar::startMeasure('render','Time for rendering');
Debugbar::stopMeasure('render');
Debugbar::addMeasure('now', LARAVEL_START, microtime(true));
Debugbar::measure('My long operation', function() {
    // Do something…
});

try {
    throw new Exception('foobar');
} catch (Exception $e) {
    Debugbar::addThrowable($e);
}
```

--------------------------------

### Profiling Timeline Events in Laravel Debugbar

Source: https://laraveldebugbar.com/index

Shows how to view and interpret timeline events within Laravel Debugbar. This helps in understanding the performance of different parts of your application, such as booting, routing, and specific operations. The timeline provides a visual representation of execution times.

```text
  * Booting (97.34ms)time
  * Routing (1.29ms)
  * My long operation (124ms)
  * Preparing Response (1.91ms)
  * View: welcomeviews
  * 1 x My long operation (41.85%)| 124ms  
---|---  
1 x Booting (32.85%)| 97.34ms  
1 x Preparing Response (0.64%)| 1.91ms  
1 x Routing (0.44%)| 1.29ms  
1 x View (0%)| 0μs  
```

--------------------------------

### Viewing Stack Traces in Laravel Debugbar

Source: https://laraveldebugbar.com/index

Illustrates how Laravel Debugbar displays stack traces for exceptions. This is crucial for debugging errors by showing the sequence of function calls that led to an exception. The stack trace details file names, line numbers, and function names.

```text
  * Something went wrongapp/Http/Controllers/DemoController.php#53RuntimeException```

```

    * 50
    * 51
    * 52
    * 53
    * 54
    * 55
    * 56
    * 57
` 
```

--------------------------------

### Database Feature Lookup - Laravel Debugbar

Source: https://laraveldebugbar.com/index

This snippet showcases SQL queries used for looking up feature flags within the `features` table, as recorded by Laravel Debugbar. It demonstrates how the system queries for specific feature names and scopes, providing the query, bindings, and backtrace for debugging purposes. These queries are crucial for managing application features dynamically.

```sql
select * from `features` where (`name` = 'debugbar' and `scope` = '__laravel_null')
select * from `features` where (`name` = 'new-api' and `scope` = '__laravel_null')
```

--------------------------------

### Log SQL Select Query with Bindings - PHP

Source: https://laraveldebugbar.com/usage

This snippet logs a SQL 'SELECT' query executed by the application, along with its associated bindings. It originates from the QueryCollector in Laravel Debugbar. No external dependencies are explicitly mentioned beyond the Laravel framework.

```php
select * from `cache` where `key` in ('from-cache')
Bindings __|
    * 0: from-cache
```

```php
select * from `cache` where `key` in ('remember')
Bindings __|
    * 0: remember
```

```php
select * from `features` where (`name` = 'debugbar' and `scope` = '__laravel_null')
Bindings __|
    * 0: debugbar
    * 1: __laravel_null
```

```php
select * from `features` where (`name` = 'new-api' and `scope` = '__laravel_null')
Bindings __|
    * 0: new-api
    * 1: __laravel_null
```

--------------------------------

### Log Connection Established Event in Laravel Debugbar

Source: https://laraveldebugbar.com/features

This snippet shows the logging of a 'Connection Established' event by the QueryCollector in Laravel Debugbar. It includes a backtrace, indicating where in the application this event was triggered, useful for debugging connection issues.

```php
    * QueryCollector.php#449debugbar_demo**Connection Established** Backtrace __|
    * Users/barry/Sites/laravel-debugbar/src/DataCollector/QueryCollector.php:449
    * Users/barry/Sites/laravel-debugbar/src/LaravelDebugbar.php:437
    * vendor/laravel/framework/src/Illuminate/Session/SessionManager.php:108
    * vendor/laravel/framework/src/Illuminate/Session/SessionManager.php:95
    * vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php:159  
---|---  
```

--------------------------------

### Implement Stopwatch Tag in Twig

Source: https://laraveldebugbar.com/usage

Shows how to use the `stopwatch` tag in Twig, similar to Symfony/Silex. This allows you to time specific blocks of code within your Twig templates and view the results in the Debugbar's timeline.

```twig
{% stopwatch "foo" %}
    …some things that gets timed
{% endstopwatch %}
```

--------------------------------

### Adding Debug Messages and Exceptions in Laravel Debugbar

Source: https://laraveldebugbar.com/index

Demonstrates how to log debug messages and add exceptions to the Laravel Debugbar. This is useful for tracking the flow of execution and identifying potential issues within your application. It utilizes the `Log::debug()` method and the `debugbar()->addThrowable()` function.

```php
  * info```

  0 of 0       
array:2 [▶
  "name" => "Laravel Debugbar"
  "url" => "https://laraveldebugbar.com"
]

```
LaravelDebugbar.php#1179
  * errorError!LaravelDebugbar.php#1179
  * warningWatch out…LaravelDebugbar.php#1179
  * mylabelAnother messageLaravelDebugbar.php#1179
  * debuglog[15:57:57] LOG.debug: This is a log message.


__infoerrorwarningmylabeldebugnonelog
```

```php
` 


        $user->sendPasswordResetNotification('example'); 
        debugbar()->addThrowable(new RuntimeException('Something went wrong'));          
        return view('welcome');     
    }  ````
```

--------------------------------

### Select from 'cache' Table (PHP) - Second Instance

Source: https://laraveldebugbar.com/collectors

This is a repeat of the 'select from cache' query, indicating a subsequent retrieval attempt for a cache entry. The 'Bindings' show the cache key being queried.

```sql
SELECT * FROM `cache` WHERE `key` IN ('from-cache')
```

--------------------------------

### Inspecting Route and Middleware Stack in Laravel Debugbar

Source: https://laraveldebugbar.com/index

Details how Laravel Debugbar represents the route and middleware stack for a request. This helps in understanding how requests are processed through various layers of middleware and how the route is eventually handled. It lists the files, lines, classes, and functions involved in the request lifecycle.

```text
  0 of 0       
array:51 [▼
  0 => array:6 [▶
    "file" => "vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php"
    "line" => 46
    "function" => "index"
    "class" => "App\Http\Controllers\DemoController"
    "type" => "->"
    "args" => []
  ]
  1 => array:6 [▶
    "file" => "vendor/laravel/framework/src/Illuminate/Routing/Route.php"
    "line" => 265
    "function" => "dispatch"
    "class" => "Illuminate\Routing\ControllerDispatcher"
    "type" => "->"
    "args" => array:3 [▶
      0 => "[object Illuminate\Routing\Route]"
      1 => "[object App\Http\Controllers\DemoController]"
      2 => "index"
    ]
  ]
  2 => array:6 [▶
    "file" => "vendor/laravel/framework/src/Illuminate/Routing/Route.php"
    "line" => 211
    "function" => "runController"
    "class" => "Illuminate\Routing\Route"
    "type" => "->"
    "args" => []
  ]
  3 => array:6 [▶
    "file" => "vendor/laravel/framework/src/Illuminate/Routing/Router.php"
    "line" => 808
    "function" => "run"
    "class" => "Illuminate\Routing\Route"
    "type" => "->"
    "args" => []
  ]
  4 => array:6 [▶
    "file" => "vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php"
    "line" => 144
    "function" => "Illuminate\Routing\{closure}"
    "class" => "Illuminate\Routing\Router"
    "type" => "->"
    "args" => array:1 [▶
      0 => "[object Illuminate\Http\Request]"
    ]
  ]
  5 => array:6 [▶
    "file" => "Users/barry/Sites/laravel-debugbar/src/Middleware/InjectDebugbar.php"
    "line" => 66
    "function" => "Illuminate\Pipeline\{closure}"
    "class" => "Illuminate\Pipeline\Pipeline"
    "type" => "->"
    "args" => array:1 [▶
      0 => "[object Illuminate\Http\Request]"
    ]
  ]
  6 => array:6 [▶
    "file" => "vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php"
    "line" => 183
    "function" => "handle"
    "class" => "Barryvdh\Debugbar\Middleware\InjectDebugbar"
    "type" => "->"
    "args" => array:2 [▶
      0 => "[object Illuminate\Http\Request]"
      1 => "[object Closure]"
    ]
  ]
  7 => array:6 [▶
    "file" => "vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php"
    "line" => 51
    "function" => "Illuminate\Pipeline\{closure}"
    "class" => "Illuminate\Pipeline\Pipeline"
    "type" => "->"
    "args" => array:1 [▶
      0 => "[object Illuminate\Http\Request]"
    ]
  ]
  8 => array:6 [▶
    "file" => "vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php"
    "line" => 183
    "function" => "handle"
    "class" => "Illuminate\Routing\Middleware\SubstituteBindings"
    "type" => "->"
    "args" => array:2 [▶
      0 => "[object Illuminate\Http\Request]"
      1 => "[object Closure]"
    ]
  ]
  9 => array:6 [▶
    "file" => "vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php"
    "line" => 88
    "function" => "Illuminate\Pipeline\{closure}"

```

--------------------------------

### Insert or Update Cache Entry (PHP)

Source: https://laraveldebugbar.com/features

This PHP snippet shows an SQL query for inserting a new cache entry or updating an existing one if the key already exists. This is efficiently handled using `ON DUPLICATE KEY UPDATE` and is monitored by Laravel Debugbar.

```php
<?php
// Example SQL query for inserting/updating cache
$sql = "insert into `cache` (`expiration`, `key`, `value`) values (?, ?, ?) on duplicate key update `expiration` = values(`expiration`), `key` = values(`key`), `value` = values(`value`)";
$bindings = [
    1738425478,
    'from-cache',
    's:4:"test";'
];
// QueryCollector in Laravel Debugbar logs this operation.
```

--------------------------------

### Log SQL Delete Query with Bindings - PHP

Source: https://laraveldebugbar.com/usage

This snippet captures a SQL 'DELETE' query, including the keys and expiration time used in the condition, along with their corresponding bindings. This is likely part of the query logging mechanism within Laravel Debugbar.

```php
delete from `cache` where `key` in ('remember', 'illuminate:cache:flexible:created:remember') and `expiration` <= 1738425477
Bindings __|
    * 0: remember
    * 1: illuminate:cache:flexible:created:remember
    * 2: 1738425477
```

--------------------------------

### Template Rendering Information in Laravel Debugbar

Source: https://laraveldebugbar.com/features

This snippet indicates that one template was rendered. It specifies the template file name ('welcome.blade.php') and notes that it was processed by the Blade engine. This helps in understanding view loading and performance.

```blade
  * welcomewelcome.blade.php#?blade
```

--------------------------------

### Log Database Query Execution in Laravel Debugbar

Source: https://laraveldebugbar.com/features

This snippet demonstrates how the Laravel Debugbar logs the execution of SQL queries. It includes the query itself, any bindings, and the backtrace. This helps in identifying slow or inefficient queries.

```php
    * QueryCollector.php#181debugbar_demo2.34ms`select * from `sessions` where `id` = 'SgZFpA6XSe27szZ2lMzt4QrW5j7Mdeqkm96swgvL' limit 1`
Bindings __|
    * 0: SgZFpA6XSe27szZ2lMzt4QrW5j7Mdeqkm96swgvL  
---|---
Backtrace __|
    * Users/barry/Sites/laravel-debugbar/src/DataCollector/QueryCollector.php:181
    * Users/barry/Sites/laravel-debugbar/src/LaravelDebugbar.php:384
    * vendor/laravel/framework/src/Illuminate/Session/DatabaseSessionHandler.php:97
    * vendor/laravel/framework/src/Illuminate/Session/Store.php:113
    * vendor/laravel/framework/src/Illuminate/Session/Store.php:101  
```

```php
    * QueryCollector.php#181debugbar_demo520μs`select * from `users``
Backtrace __|
    * Users/barry/Sites/laravel-debugbar/src/DataCollector/QueryCollector.php:181
    * Users/barry/Sites/laravel-debugbar/src/LaravelDebugbar.php:384
    * app/Http/Controllers/DemoController.php:17
    * vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php:46
    * vendor/laravel/framework/src/Illuminate/Routing/Route.php:265  
---|---  
```

```php
    * QueryCollector.php#181debugbar_demo440μs`select * from `users` where `name` = 'Barry vd. Heuvel' limit 1`
Bindings __|
    * 0: Barry vd. Heuvel  
---|---
Backtrace __|
    * Users/barry/Sites/laravel-debugbar/src/DataCollector/QueryCollector.php:181
    * Users/barry/Sites/laravel-debugbar/src/LaravelDebugbar.php:384
    * app/Http/Controllers/DemoController.php:18
    * vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php:46
    * vendor/laravel/framework/src/Illuminate/Routing/Route.php:265  
```

--------------------------------

### Configure Storage Settings for Laravel Debugbar History

Source: https://laraveldebugbar.com/features

This configuration snippet defines how Laravel Debugbar stores request data, which is particularly useful for non-browser, redirects, or external requests. It supports various drivers like 'file', 'redis', and 'pdo'. The 'storage.open' setting controls public access to history, which should be used with caution and ideally limited to local environments.

```php
/*
 |--------------------------------------------------------------------------
 | Storage settings
 |--------------------------------------------------------------------------
 |
 | DebugBar stores data for session/ajax requests.
 | You can disable this, so the debugbar stores data in headers/session,
 | but this can cause problems with large data collectors.
 | By default, file storage (in the storage folder) is used. Redis and PDO
 | can also be used. For PDO, run the package migrations first.
 |
 | Warning: Enabling storage.open will allow everyone to access previous
 | request, do not enable open storage in publicly available environments!
 | Specify a callback if you want to limit based on IP or authentication.
 | Leaving it to null will allow localhost only.
 */
'storage' => [
    'enabled'    => true,
    'open'       => env('DEBUGBAR_OPEN_STORAGE'), // bool/callback.
    'driver'     => 'file', // redis, file, pdo, socket, custom
    'path'       => storage_path('debugbar'), // For file driver
    'connection' => null,   // Leave null for default connection (Redis/PDO)
    'provider'   => '', // Instance of StorageInterface for custom driver
    'hostname'   => '127.0.0.1', // Hostname to use with the "socket" driver
    'port'       => 2304, // Port to use with the "socket" driver
]
```

--------------------------------

### Enabling and Disabling Debugbar at Runtime

Source: https://laraveldebugbar.com/usage

Illustrates how to programmatically enable or disable the Laravel Debugbar during script execution. This is useful for controlling when the Debugbar is active, especially in production environments.

```php
\Debugbar::enable();
\Debugbar::disable();
```

--------------------------------

### Use Debug and Dump Twig Functions

Source: https://laraveldebugbar.com/usage

Demonstrates the usage of the `debug()` and `dump()` functions provided by the Laravel Debugbar Twig extensions. The `dump()` function outputs variables using DataFormatter, while `debug()` sends variables to the Message Collector or dumps all context variables if no arguments are provided.

```twig
{{ debug() }}
{{ debug(user, categories) }}
```

--------------------------------

### Add Throwable to Debugbar

Source: https://laraveldebugbar.com/usage

This PHP code demonstrates how to add a `RuntimeException` to the Laravel Debugbar's 'Exceptions' tab. This is useful for tracking and debugging errors that occur during request processing.

```php
`debugbar()->addThrowable(new \RuntimeException('Something went wrong'));`
```

--------------------------------

### Insert into 'cache' Table (PHP)

Source: https://laraveldebugbar.com/collectors

This SQL statement shows an INSERT operation on the 'cache' table, with an 'ON DUPLICATE KEY UPDATE' clause. This handles both inserting new cache entries and updating existing ones if the key already exists. The bindings indicate the expiration time, key, and value being stored.

```sql
INSERT INTO `cache` (`expiration`, `key`, `value`) VALUES (1738425478, 'from-cache', 's:4:"test";') ON DUPLICATE KEY UPDATE `expiration` = VALUES(`expiration`), `key` = VALUES(`key`), `value` = VALUES(`value`)
```

--------------------------------

### Insert Job with Different Payload (PHP)

Source: https://laraveldebugbar.com/features

This PHP snippet illustrates another instance of inserting a job into the `jobs` table, this time with a different payload representing a job named 'App\\Jobs\\SomeLongJob'. It highlights the flexibility in job payload structure.

```php
<?php
// Example SQL query for inserting a different job
$sql = "insert into `jobs` (`queue`, `attempts`, `reserved_at`, `available_at`, `created_at`, `payload`) values (?, ?, null, ?, ?, ?)";
$bindings = [
    'default',
    0,
    1738425477,
    1738425477,
    '{"uuid":"caf682cd-51fc-4b85-b889-cb62d57628a9","displayName":"App\\Jobs\\SomeLongJob","job":"Illuminate\\Queue\\CallQueuedHandler@call","maxTries":null,"maxExceptions":null,"failOnTimeout":false,"backoff":null,"timeout":null,"retryUntil":null,"data":{"commandName":"App\\Jobs\\SomeLongJob","command":"O:20:\"App\\Jobs\\SomeLongJob\":0:{}"}}'
];
// This query is captured and displayed by Laravel Debugbar's QueryCollector.
```

--------------------------------

### Adding Custom Data Collectors

Source: https://laraveldebugbar.com/usage

Shows how to add custom DataCollectors to the Debugbar, either through the Facade or by retrieving the Debugbar instance from the application container. This allows for extending the Debugbar's functionality.

```php
Debugbar::addCollector(new DebugBar\DataCollector\MessagesCollector('my_messages'));
//Or via the App container:
$debugbar = App::make('debugbar');
$debugbar->addCollector(new DebugBar\DataCollector\MessagesCollector('my_messages'));
```

--------------------------------

### Configure AJAX Request Capture in Laravel Debugbar

Source: https://laraveldebugbar.com/features

This configuration snippet controls how Laravel Debugbar captures and displays AJAX requests. It allows enabling/disabling capture, automatic showing of requests, and adding timing information. AJAX requests are identified by the 'X-Requested-With' header or an 'application/json' Accept header.

```php
/*
 |--------------------------------------------------------------------------
 | Capture Ajax Requests
 |--------------------------------------------------------------------------
 |
 | The Debugbar can capture Ajax requests and display them. If you don't want this (ie. because of errors),
 | you can use this option to disable sending the data through the headers.
 |
 | Optionally, you can also send ServerTiming headers on ajax requests for the Chrome DevTools.
 |
 | Note for your request to be identified as ajax requests they must either send the header
 | X-Requested-With with the value XMLHttpRequest (most JS libraries send this), or have application/json as a Accept header.
 |
 | By default `ajax_handler_auto_show` is set to true allowing ajax requests to be shown automatically in the Debugbar.
 | Changing `ajax_handler_auto_show` to false will prevent the Debugbar from reloading.
 */

'capture_ajax' => true,
'add_ajax_timing' => false,
'ajax_handler_auto_show' => true,
'ajax_handler_enable_tab' => true
```
Tokens:
Raw