Auto-instrumentation support for okhttp3 http requests

[surbhiia]

Currently, manual instrumentation of okhttp3 and volleyHttp clients is supported. It requires app developers to call a specific api to get the instrumented http client to avail the instrumentation. Adding this issue to capture the requirement for auto-instrumentation of network requests. Two clients we think auto-instrumentation should be supported for are - OkHttp3 and HttpURLConnection.

Others reading this, do comment what http clients you think are most commonly used today and should be supported.

[breedx-splk]

@surbhiia Can we rename this to be just http specific? Network is much much broader, and I like the idea of starting with http.

[surbhiia]

Updated issue title! I'm also working on creating a POC for HttpURLConnection auto-instrumentation using byte buddy android plugin.

[breedx-splk]

@surbhiia Take a look at #64 and let's make sure that we're not duplicating efforts. 😃

[surbhiia]

Yes! Thanks for pointing that out. I had a chat with @LikeTheSalad last week about this. :) HttpURLConnection plugin would be an additional byte buddy plugin like the okhttp3 one in #64 and I will leverage all the base setup done in that PR.

[breedx-splk]

I think it would be great now to close this and to split into new auto-instrumentation enhancement issues, 1 for HttpUrlConnection and 1 for Volley.

[surbhiia]

That'd be better yes! Closing this and creating two new ones. :)

[surbhiia]

Created issues #104 and #105!

[breedx-splk]

Great, thanks!