BugSnag is now Insight Hub - we're making some changes to how the product looks, but this won't impact the way you use BugSnag or any of your integrations.

Advanced client configuration

Advanced BugSnag client usage for additional control over how and when BugSnag sends notifications.

Customizing transport

If you require using a proxy or a custom timeout length when sending error reports to BugSnag, you can provide a customized HTTP client via Guzzle. First create a service definition for a Guzzle client, for example:

custom_guzzle:
    class: GuzzleHttp\Client
    arguments:
        - { timeout: 5 }

Then add this service to your BugSnag configuration:

bugsnag:
    guzzle: custom_guzzle

You can also register your service as bugsnag.guzzle to avoid having to tell BugSnag about it explicitly:

bugsnag.guzzle:
    class: GuzzleHttp\Client
    arguments:
        - { timeout: 5 }