test(instrumentation-js): validate Together AI OTel 2.x spans - #370
Merged
fran3cc merged 1 commit intoAug 21, 2026
Merged
Conversation
Nightingalelyy
marked this pull request as ready for review
August 16, 2026 14:23
Contributor
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
nonerelease intent because this change strengthens contract coverage without changing runtime behaviorWhy.
The audit showed that Together AI non-chat spans contain canonical model and usage attributes before export, while the platform does not currently populate those values in its top-level non-chat columns. The correct package-side fix is to lock down the canonical OTLP wire contract rather than add unsupported aliases or change span types.
Impact.
This prevents regressions in non-chat attribute export and makes the remaining ingestion boundary explicit. There is no production runtime or package-version change.
The corresponding example-project fixes are local to
respan-example-projects: exact shared-marker metadata for Vercel AI SDK, awaited Vertex AI shutdown, and complete streamed workflow capture.Validation
Together AI package tests: 9/9
Vercel AI SDK package tests: 47/47
Vertex AI package tests: 7/7
all three package builds and
npm pack --dry-runchecks passedall 18 corresponding examples passed with marker
otel2-fix-js-group-05-20260815T144725ZMCP audit: 18/18 trace trees and 58/58 individual span records inspected; one root per trace, matching counts, no orphans, cycles, or duplicates
release inventory, release intent, and diff checks passed
Full source and paired-example diffs were audited against every applicable document under
contribution/; canonical span fields, OTel attribute shapes, release-intent/version ownership, and package boundaries have no remaining package-owned violation.External follow-ups
Companion examples