Skip to content

fix: Align Google GenAI auto traces with wrappers#1636

Open
Luca Forstner (lforst) wants to merge 5 commits intomainfrom
lforst/google-genai-parity
Open

fix: Align Google GenAI auto traces with wrappers#1636
Luca Forstner (lforst) wants to merge 5 commits intomainfrom
lforst/google-genai-parity

Conversation

@lforst
Copy link
Member

@lforst Luca Forstner (lforst) commented Mar 23, 2026

Align Google GenAI auto-instrumentation with the wrapper trace contract so both paths emit one shared e2e baseline.

  • reuse one Google GenAI e2e assertion path for wrapper and auto-instrumentation
  • point both paths at the same span and payload snapshots
  • keep snapshot normalization limited to shared root labels so real drift still fails loudly
  • remove the duplicate auto-only Google GenAI test and snapshots
  • make Google GenAI auto-instrumentation emit wrapper-matching names, metadata, metrics, and stream behavior

Fixes #1594

@lforst Luca Forstner (lforst) changed the title fix(js): Align Google GenAI auto traces with wrappers fix: Align Google GenAI auto traces with wrappers Mar 23, 2026
…arity

# Conflicts:
#	e2e/scenarios/google-genai-auto-instrumentation-node-hook/__snapshots__/log-payloads.json
#	e2e/scenarios/google-genai-auto-instrumentation-node-hook/__snapshots__/span-events.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Auto-instrumentation and wrapper traces differ for Google GenAI

1 participant