Skip to content

[v11] Manual test Mastra #23688

Description

@RulaKhaled

Manual check that Mastra agent monitoring still looks right against SDK v11 (11.0.0-alpha.1 or newer). Mastra ships its own Sentry exporter rather than living in sentry-javascript, so this is a customer-path / exporter-compat pass — not covered by the greenfield wizard tickets under JS-3386.

Why

v11 renamed gen_ai attributes, dropped some legacy ones, and is moving agent span names to low cardinality. Mastra was not part of the in-repo AI integration updates (JS-3110). Need to confirm the exporter still produces usable traces, or file follow-ups if it is still emitting v10 names/attributes.

Protocol

  • App lives outside the sentry-javascript monorepo
  • Pin @sentry/node@alpha (and whatever Mastra Sentry/OTEL packages the current docs recommend)
  • Run a small Mastra agent that invokes a model and at least one tool
  • Send traces to a real Sentry project (personal free org is enough — not the employee sentry org)
  • Confirm errors still capture if the agent throws

Check

  • Agent / tool / inference spans still show up
  • Span ops and names match v11 conventions (no leftover v10 gen_ai.* names that dashboards would miss)
  • Attributes use the v11 names (gen_ai.provider.name, gen_ai.tool.definitions, gen_ai.tool.call.arguments / result, cache token paths, gen_ai.pipeline.name if applicable) — note anything still on the old names
  • Span streaming on; no sendDefaultPii; dataCollection looks right
  • File follow-ups (Mastra exporter and/or docs) if the exporter is still on v10 conventions

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions