PHPackages                             alexeyshockov/guzzle-timeline-middleware - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Debugging & Profiling](/categories/debugging)
4. /
5. alexeyshockov/guzzle-timeline-middleware

ActiveLibrary[Debugging & Profiling](/categories/debugging)

alexeyshockov/guzzle-timeline-middleware
========================================

Timeline reports for profiling Guzzle concurrency

17PHPCI failing

Since Jan 21Pushed 6y ago1 watchersCompare

[ Source](https://github.com/alexeyshockov/guzzle-timeline-middleware)[ Packagist](https://packagist.org/packages/alexeyshockov/guzzle-timeline-middleware)[ RSS](/packages/alexeyshockov-guzzle-timeline-middleware/feed)WikiDiscussions master Synced yesterday

READMEChangelogDependenciesVersions (1)Used By (0)

Guzzle Timeline Reports
=======================

[](#guzzle-timeline-reports)

A simple helper for profiling async requests.

Basic timeline report
---------------------

[](#basic-timeline-report)

This report shows all the requests on a global timeline ([example](http://alexey.shockov.com/guzzle-timeline-middleware/report_timeline.html)).

Execution flow reports
----------------------

[](#execution-flow-reports)

If you want to profile Guzzle's concurrency feature, then the execution flow report can help you a lot. It arranges all the requests by virtual "threads", so you are able to see (for example) how good the resource utilization is. [An example report](http://alexey.shockov.com/guzzle-timeline-middleware/report_ex_flow.html).

In your code
------------

[](#in-your-code)

Install as usual, with Composer: `composer require --dev alexeyshockov/guzzle-timeline-middleware`

### Basic usage

[](#basic-usage)

Just add appropriate middleware to your stack:

```
$handler = HandlerStack::create();
// For basic timeline report
$handler->push(TimelineReporter::middleware(__DIR__ . '/timeline.html'), 'timeline_report');
// For execution flow report
$handler->push(ExecutionFlowTimelineReporter::middleware(__DIR__ . '/ex_flow.html'), 'ex_flow_report');

$client = new \GuzzleHttp\Client([
    'handler' => $handler,
]);
```

### Splitting a huge report into chunks

[](#splitting-a-huge-report-into-chunks)

If you profile a long living process with a lot of HTTP requests, it's possible to split the report into chunks. Just use `${NUMBER}` placeholder in your report file name template and pass the max number of entries per report chunk.

```
$handler = HandlerStack::create();
$handler->push(TimelineReporter::middleware(__DIR__ . '/timeline_${NUMBER}.html', null, 250), 'timeline_report');

$client = new \GuzzleHttp\Client([
    'handler' => $handler,
]);
```

###  Health Score

18

—

LowBetter than 8% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity34

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/dbb1137342b76983ce06549ef8a9eb3332c3f35c30a45298c9070bc93b26db95?d=identicon)[alexeyshockov](/maintainers/alexeyshockov)

---

Top Contributors

[![alexeyshockov](https://avatars.githubusercontent.com/u/203120?v=4)](https://github.com/alexeyshockov "alexeyshockov (6 commits)")

### Embed Badge

![Health badge](/badges/alexeyshockov-guzzle-timeline-middleware/health.svg)

```
[![Health](https://phpackages.com/badges/alexeyshockov-guzzle-timeline-middleware/health.svg)](https://phpackages.com/packages/alexeyshockov-guzzle-timeline-middleware)
```

###  Alternatives

[symfony/stopwatch

Provides a way to profile code

2.8k387.2M918](/packages/symfony-stopwatch)[fruitcake/laravel-debugbar

PHP Debugbar integration for Laravel

19.1k662.9k29](/packages/fruitcake-laravel-debugbar)[spatie/ignition

A beautiful error page for PHP applications.

510147.6M69](/packages/spatie-ignition)[jokkedk/webgrind

Webgrind is a Xdebug profiling web frontend in PHP5. It implements a subset of the features of kcachegrind and installs in seconds and works on all platforms. For quick'n'dirty optimizations it does the job.

3.3k193.0k](/packages/jokkedk-webgrind)[koriym/printo

An object graph visualizer.

1421.8M2](/packages/koriym-printo)[soloterm/dumps

A Laravel command to intercept dumps from your Laravel application.

125285.7k3](/packages/soloterm-dumps)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)