[opentelemetry-instrumentation-google-genai] Use wrapt to monkey patch instead of functools.wraps. Clarify readme tool calling section.

instrumentation/opentelemetry-instrumentation-google-genai/.changelog/151.changed

@@ -0,0 +1 @@
+Use `wrapt` instead of `functools.wraps` to monkey patch the SDK.

instrumentation/opentelemetry-instrumentation-google-genai/README.rst

@@ -67,11 +67,11 @@ Limitations
 ***********
 
 When using the Google GenAI SDK with automatic function calling enabled,
-the OpenTelemetry instrumentation creates a span only for the top-level
-``generate_content`` call.
+the OpenTelemetry instrumentation creates an ``execute_tool`` span for each tool call the SDK executes,
+these spans are nested under the ``generate_content`` span.
 
-Internal model or tool calls triggered automatically by the SDK are executed
-within the SDK internals and are not traced as separate spans.
+Only tool calls that the SDK executes are traced, if you disable the automatic function calling and instead
+do the function calling in your application, our instrumentation cannot trace them.
 
 
 Enabling message content

instrumentation/opentelemetry-instrumentation-google-genai/TODOS.md

@@ -10,7 +10,6 @@ Here are some TODO items required to achieve stability for this package:
    - Including tool invocation information
  - Emit events for safety ratings when they block responses
  - Additional cleanup/improvement tasks such as:
-   - Adoption of 'wrapt' instead of 'functools.wraps'
    - Bolstering test coverage
 
 ## Future

instrumentation/opentelemetry-instrumentation-google-genai/pyproject.toml

@@ -43,6 +43,7 @@ dependencies = [
   "opentelemetry-instrumentation >=0.61b0, <2",
   "opentelemetry-semantic-conventions >=0.61b0, <2",
   "opentelemetry-util-genai >= 0.4b0, <2",
+  "wrapt >= 1.0.0, < 3.0.0",
 ]
 
 [project.optional-dependencies]