Request watcher

[barryvdh]

So basically with the new Http Events, we can do something similar to laravel/telescope#1073
Maybe we can combine it with https://github.com/hannesvdvreken/guzzle-debugbar to provide a base request logger and just a method to wrap Guzzle Clients manually (eg debugbar()->trackRequests($client))

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If this issue is still present on the latest version of this library on supported Laravel versions, please let us know by replying to this issue so we can investigate further.
Thank you for your contribution! Apologies for any delayed response on our side.

[barryvdh]

I think we can use the events from the HttpClient. For Guzzle, those can be used with this handler: https://gist.github.com/barryvdh/a04ab1628558d6ac41a036a238ee090b

[barryvdh]

It's probably cleanest to extend the Guzzle client to use the Laravel events (as the example above does) and then just hook into those requests. That would work for the HttpClient from Laravel out of the box, and doesn't require Debugbar specific handlers for Guzzle.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If this issue is still present on the latest version of this library on supported Laravel versions, please let us know by replying to this issue so we can investigate further.
Thank you for your contribution! Apologies for any delayed response on our side.

[uyab]

Any update on this?

[jonnywilliamson]

Currently tearing my hair out on trying to get the guzzle-debug bar to work when using the Laravel Http Client Pool. It's fine if it's just simple requests, but any request coming from a pool is not being logged.

Came in in hope it might have been implemented directly with the laravel debug bar! No luck!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If this issue is still present on the latest version of this library on supported Laravel versions, please let us know by replying to this issue so we can investigate further.
Thank you for your contribution! Apologies for any delayed response on our side.