feat(llmobs): submit llmobs payloads from gemini integration

[Yun-Kim]

This PR enables submitting LLMObs spans from the Gemini integration.

generate_content/generate_content_async() calls are traced by the Gemini APM integration. This PR also generates LLMObs span events from those spans and submits them to LLM Observability.

The following data is collected by Gemini LLMObs spans:

• span kind: LLM
• provider: google
• model name
• metadata: collects any of (temperature/max_output_tokens/candidate_count/top_p/top_k) if set on the model instance or in the request itself
• input messages: includes system instruction as a system message (if provided), and history of input messages passed to the model/request (also includes function calls/responses in addition to text messages)
• output_messages: self explanatory (also includes function calls in addition to text responses)
• metrics: token metrics (input/output/total)
• additional span data provided ootb by LLMObs (span duration/error/tags/etc)

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[github-actions]

CODEOWNERS have been resolved as:

releasenotes/notes/feat-llmobs-gemini-b65c714ceef9eb12.yaml             @DataDog/apm-python
tests/contrib/google_generativeai/test_google_generativeai_llmobs.py    @DataDog/ml-observability
ddtrace/contrib/google_generativeai/__init__.py                         @DataDog/ml-observability
ddtrace/contrib/internal/google_generativeai/_utils.py                  @DataDog/ml-observability
ddtrace/contrib/internal/google_generativeai/patch.py                   @DataDog/ml-observability
ddtrace/llmobs/_constants.py                                            @DataDog/ml-observability
ddtrace/llmobs/_integrations/gemini.py                                  @DataDog/ml-observability
ddtrace/llmobs/_utils.py                                                @DataDog/ml-observability
tests/contrib/google_generativeai/conftest.py                           @DataDog/ml-observability
tests/llmobs/_utils.py                                                  @DataDog/ml-observability

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-09-11 21:26:06

Comparing candidate commit cc859e6 in PR branch yunkim/llmobs-gemini with baseline commit c0fd013 in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 353 metrics, 47 unstable metrics.

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: yunkim/llmobs-gemini
Commit report: d6379e6
Test service: dd-trace-py

✅ 0 Failed, 3724 Passed, 5180 Skipped, 53m 46.44s Total duration (1h 13m 21.8s time saved)

[yahya-mouman]

Besides some test CIs are failing for assertions. It looks good to me 👍

[github-actions]

The backport to 2.13 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.13 2.13
# Navigate to the new working tree
cd .worktrees/backport-2.13
# Create a new branch
git switch --create backport-10619-to-2.13
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 dc7e31ecd0e06735d850e5c317f2ee18fed98c32
# Push it to GitHub
git push --set-upstream origin backport-10619-to-2.13
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.13

Then, create a pull request where the base branch is 2.13 and the compare/head branch is backport-10619-to-2.13.