KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #ai-agents #developer-tools #codex #claude-code #mcp #rust #deepseek-harness #typescript #ai-agent #cli

query-tracer

★ 228 Open GitHub ↗

Find exactly where a specific database query is being called in your Laravel application.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

## Laravel Query Tracer

[![Build Status](https://travis-ci.org/fitztrev/query-tracer.svg?branch=master)](https://travis-ci.org/fitztrev/query-tracer) [![Latest Stable Version](https://poser.pugx.org/fitztrev/query-tracer/v/stable)](https://packagist.org/packages/fitztrev/query-tracer)

Find exactly *where* a specific database query is being called in your Laravel application.

Want to optimize or debug your database queries but not sure where they're being called? See how it works below with [Clockwork](https://github.com/itsgoingd/clockwork):

![](http://i.imgur.com/0cRs7TU.png)

If you use [Debugbar](https://github.com/barryvdh/laravel-debugbar), it has this functionality built-in if you set `debugbar.options.db.backtrace` to `true`.

### Installation

1. Install via composer:

```bash
    composer require fitztrev/query-tracer
    ```

2. Add the service provider to your `config/app.php`:

```php
    'providers' => [
        // ...
        Fitztrev\QueryTracer\Providers\QueryTracerServiceProvider::class,
    ],
    ```

### How does it do it?

It makes use of Laravel's global query scopes to do a backtrace and find where a query originated. Then it puts that info in extraneous but helpful `WHERE` clauses.

By default, it's only enabled when `debug` is on. You can change this behavior for specific models by adding an `enableQueryTracer()` method to your model(s). For example:

```php
public function enableQueryTracer()
{
    return config('app.env') == 'local';
}
```

query-tracer

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README