Excon: Retry information

[jabrown85]

Should the Excon instrumentation handle retries better? I believe the way it works now is that retries are basically all smuggled into the same span. I've seen spans that have connect_write timeout reached but are actually successful after a retry. I can tell from custom excon logging that it was successful but the otel shows the first response data mixed with the end time of the last retry.

I wasn't sure which direction the project might want to go. Should each excon invocation be a child span?

[arielvalentin]

Great question @jabrown85 This is what the recommended model for retries should look like:

https://opentelemetry.io/docs/specs/semconv/http/http-spans/#http-client-retries-examples

If Excon is performing retries and we are not modeling it as expected, we would appreciate your help in the form of a PR that models it closer to the examples described in the semantic conventions specification.

[github-actions]

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.