Problems with self-signed certificates

[ElvisIsKing666]

Problems with self-signed certificates

[dstepe]

Enabling the HTTP client configuration would need to start in underlying agent rather than this package. I'm not exactly sure how support client auto-discovery while enabling client configuration (which may vary by client). The 'bring your own client" approach is the compromise. If you want to open an issue we can further explore options.

For this package, we've used a slightly different approach to configure the client. In the standard AppServiceProvider::register() method, you can bind a configured AgentBuilder and provide only the http client:

        $this->app->bind(AgentBuilder::class, function () {
            $builder = new AgentBuilder();

            $builder->withHttpClient(new \Http\Adapter\Guzzle7\Client(new Client(['verify' => false])));

            return $builder;
        });

Do you want to give that a try and see if it works for you? If so, we can suggest this be added to the documentation of this project.

[arkaitzgarro]

Hi @ElvisIsKing666,

As mentioned by @dstepe, this is the way to go. We actually use this approach to reduce the timeout when connecting to Elastic:

$this->app->bind(AgentBuilder::class, function (): AgentBuilder {
    $builder = new AgentBuilder();
    $builder
        ->withHttpClient(new GuzzleClient([
            'timeout' => 1.0,
        ]));

    return $builder;
});

[ElvisIsKing666]

Ah, right, I see now that the original service provider is calling app()->make() to get the AgentBuilder. So all I need to do is just bind a new one with the client configured the way I need it. Thanks for pointing that out.