httpx2 instrumentor/httpx instrumentor support for httpx2

[gloshkajian]

What problem do you want to solve?

Recently, the maintainers of httpx have taken a number of actions that suggest a disinterest in continuing to maintain the project.

• The last release was more than a year and a half ago https://github.com/encode/httpx/releases/tag/0.28.1
• Three months ago, the maintainer closed off issue access/discussions Closing off access. encode/httpx#3784

In response to this, forks have started to emerge, as this kind of behavior from a maintainer represents significant supply chain risk. My (admittedly not the most scientific) examination of the state of play suggests that https://github.com/pydantic/httpx2 is a credible (Pydantic's backing), API equivalent fork of httpx. It's also appearing to be fork of choice (the other competing fork, httpxyz, is encouraging standardization around httpx2 https://tildeweb.nl/~michiel/httpx2.html)

Describe the solution you'd like

I'd like for there to be support for httpx2 instrumentation, similarly to httpx's current instrumentation in this repo.

Describe alternatives you've considered

No response

Additional Context

I'm asking about this because my company has already migrated some http clients using httpx to httpx2, seeing Pydantic's support as a sufficient sign that moving to httpx2 removes the supply chain risk here. However, this means we lose out on auto instrumented httpx spans, since httpx2 is a new namespace that the current instrumentor doesn't know to monkeypatch.

Would you like to implement a fix?

I'd be happy to, assuming the maintainers are okay with it.

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}