[BUG] New LlamaIndex instrumentation (2.0) produces 2 spans per retriever, embedding

[mikeldking]

Since the base model is being called, we now end up with two spans per call to a class. This is non ideal because it can cause double capturing. We should consider finding a solution to capture a single call.

[dosubot]

Hi, @mikeldking. I'm Dosu, and I'm helping the Arize Phoenix team manage their backlog. I'm marking this issue as stale.

Issue Summary

• Problem with LlamaIndex instrumentation (version 2.0) causing two spans per class call.
• Potential double capturing issue identified.
• Suggested solution: Ensure only a single call is captured.
• No further comments or developments have been made.

Next Steps

• Is this issue still relevant to the latest version of the Arize Phoenix repository? If so, please comment to keep the discussion open.
• Otherwise, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!