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
Manual check that Mastra agent monitoring still looks right against SDK v11 (
11.0.0-alpha.1or newer). Mastra ships its own Sentry exporter rather than living insentry-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
sentry-javascriptmonorepo@sentry/node@alpha(and whatever Mastra Sentry/OTEL packages the current docs recommend)sentryorg)Check
gen_ai.*names that dashboards would miss)gen_ai.provider.name,gen_ai.tool.definitions,gen_ai.tool.call.arguments/result, cache token paths,gen_ai.pipeline.nameif applicable) — note anything still on the old namessendDefaultPii;dataCollectionlooks right