Michael Safyan

I think new, separate issues for "Log Events -> Span Event Connector" and "Span Events -> Logs Connector" would make sense.

Just providing another update, since it has been a while. I was out on vacation last week and had other work to catch up on this past week. I am...

Quick status update: - Believe that the code (for spans and span events) is largely complete, but bugs may turn up as tests are written - Iterating on unit tests...

**Status update:** Still working on writing tests. As per usual, getting progressively from one error to a different kind of error. Now the errors that I'm getting are related to...

Status update: now have the string interpolation logic in OTTL working. Next steps: - Complete end-to-end integration tests of existing logic - Add support for logs and event bodies -...

Status update: - End-to-end integration tests of existing logic now pass To keep the change from growing out of control and to prevent horrible merge conflicts down the road, I'm...

I'm renaming this from `blobattributeuploadconnector` to simply `blobuploadconnector` given that we want to also be able to target event bodies (or sub-paths within them). A renamed version now exists in...

Does this share / reuse the instrumentation in the contrib repo? https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation-genai/opentelemetry-instrumentation-google-genai

I think it would be better to have Traceloop wrap/invoke the OTel Contrib instrumentation. That way, more (joint) effort can be put into improving the (shared) instrumentation for the Google...

Note that there is an instrumentation for the Google Gen AI SDK in the Open Telemetry Python Contrib repo: https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation-genai/opentelemetry-instrumentation-google-genai