Add access to cumulative query times and logs within request lifecycle.

[LogicSatinn]

Currently, whenQueryingForLongerThan only provides access to individual query details, even when multiple queries within a request cumulatively exceed the threshold.

Eg.

DB::whenQueryingForLongerThan(\Carbon\CarbonInterval::milliseconds(500), function (Connection $connection, QueryExecuted $event): void {
        Notification::route('mail', 'mail@example.com')
             ->notify(new QueryTookLongTimeThanExpected(
                 sql: $event->sql,
                   bindings: $event->bindings,
                  executionTime: $event->time,
                   databaseName: $connection->getDatabaseName(),
                  driverName: $connection->getDriverName()
             ));
       });

Problem:

• Multiple short queries in one request can add up to significant DB time
• Individual query logging misses these scenarios
• Current hook triggers with misleading single-query context

Proposal:
Add an event to access:

1. List of all queries executed in current request
2. Cumulative query time
3. Query metadata (bindings, execution time per query)

This would help identify requests with high cumulative DB load without using application monitoring tools.

Thoughts on implementation approach or alternative solutions?

[macropay-solutions]

This will pass when db does not have big data sets and will start sending emails when the db increases in size.
When requests timeout you can see 499 response code in access logs.

Current implementation

    /**
     * The duration of all executed queries in milliseconds.
     *
     * @var float
     */
    protected $totalQueryDuration = 0.0;

Cumulative query time.

So this means all executed queries in a connection instance so at least one of your requests is fulfilled.

List of all queries executed in current request

Query metadata (bindings, execution time per query)

These rise the issue of memory filling in order to cache all queries that a connection executed and then in worker or octane environment you would have to empty that memory.

You could use for that

    /**
     * Enable the query log on the connection.
     *
     * @return void
     */
    public function enableQueryLog()
    {
        $this->loggingQueries = true;
    }
// and 
        if ($this->loggingQueries) {
            $this->queryLog[] = compact('query', 'bindings', 'time');
        }

// and
    /**
     * Get the connection query log.
     *
     * @return array
     */
    public function getQueryLog()
    {
        return $this->queryLog;
    }