Integrations overview

Mastra observability integrations control where observability data goes and how it is transformed on the way out. Use integrations to store data in Mastra storage, send it to Mastra platform, connect to external observability providers, or redact exported span data.

When to use integrations

• Keep observability available in Studio with MastraStorageExporter.
• Send hosted observability data to Mastra platform with MastraPlatformExporter.
• Forward traces to external providers such as Datadog, Langfuse, or OpenTelemetry backends.
• Redact sensitive values before they leave the runtime.

Choose an integration path

• Studio workflow: Start with Mastra Storage.
• Hosted Mastra workflow: Add Mastra platform.
• External observability stack: Choose one or more exporter pages under the sidebar Exporters section.
• Existing distributed trace context: Use a bridge, then add exporters as needed.

Exporters

Exporters send observability data to a destination:

• Mastra Storage: Persist observability data for Studio.
• Mastra platform: Send hosted observability data to Mastra platform.
• External providers: Use exporter pages for Datadog, Langfuse, OpenTelemetry, and other supported platforms.

Bridges

Bridges connect Mastra to an existing distributed tracing context:

• OpenTelemetry bridge: Integrate Mastra with an existing OpenTelemetry trace.
• Datadog bridge: Integrate Mastra with Datadog tracing and LLM Observability flows.

Processors

Processors transform or redact spans before export:

• Sensitive Data Filter: Redact sensitive fields before spans leave the runtime.

Next steps

• Configuration
• Tracing
• Mastra Storage
• OpenTelemetry bridge