Healthchecks should use the same http client #2237
Labels
domain: config
Anything related to configuring Vector
domain: networking
Anything related to Vector's networking
have: should
We should have this feature, but is not required. It is medium priority.
type: tech debt
A code change that does not add user value.
Ref #2234
Currently, many of our healthchecks instantiate their own http client. This opens up the possibility for mismatched configs, etc.
We should go through each sink and ensure that, as much as possible, things like http clients are created in
build
and used for both the healthcheck and the sink itself.For non-http-based sinks, we should at least double check that all connection settings are propogated correctly and look for ways to consolidate them.
Todo
tcp healthcheck
with TLS.vector
,datadog
,papertrail
,tcp
,socket
.HttpClient
once.util
so this is actually quite straight forward.splunk_hec
,loki
,logdna
,http
, ...aws
clients once.aws
sinks.The text was updated successfully, but these errors were encountered: