Thomas Eizinger 46afa52f78 feat(telemetry): pre-resolve Sentry ingest host (#10206) ...

Our Sentry client needs to resolve DNS before being able to send logs or
errors to the backend. Currently, this DNS resolution happens on-demand
as we don't take any control of the underlying HTTP client.

In addition, this will use HTTP/1.1 by default which isn't as efficient
as it could be, especially with concurrent requests.

Finally, if we decide to ever proxy all Sentry for traffic through our
own domain, we have to take control of the underlying client anyway.

To resolve all of the above, we create a custom `TransportFactory` where
we reuse the existing `ReqwestHttpTransport` but provide an already
configured `reqwest::Client` that always uses HTTP/2 with a
pre-configured set of DNS records for the given ingest host.

2025-08-21 03:28:05 +00:00

..

src

feat(telemetry): pre-resolve Sentry ingest host (#10206)

2025-08-21 03:28:05 +00:00

Cargo.toml

chore(rust): simplify stream logs feature (#9780)

2025-07-04 14:51:53 +00:00