@mastra/mcp-docs-server 1.1.35-alpha.19 → 1.1.35-alpha.21

package/.docs/docs/agents/processors.md

@@ -391,6 +391,14 @@ new ToolCallFilter({
 })
 ```
 
+Set `preserveModelOutput: true` to keep compact `toModelOutput` history for filtered completed tool results. The filter keeps only the model-facing output and removes raw tool args and raw results.
+
+```typescript
+new ToolCallFilter({
+  preserveModelOutput: true,
+})
+```
+
 See the [`ToolCallFilter` reference](https://mastra.ai/reference/processors/tool-call-filter) for configuration options and the [Memory Processors](https://mastra.ai/docs/memory/memory-processors) page for pre-memory filtering.
 
 ### `ToolSearchProcessor`

package/.docs/docs/mastra-platform/configuration.md

@@ -55,4 +55,4 @@ MASTRA_PROJECT_ID="<staging-id>" mastra studio deploy --env-file .env.staging --
 MASTRA_PROJECT_ID="<production-id>" mastra studio deploy --env-file .env.production --yes
 ```
 
-Each project has its own Studio URL and its own observability data. When using [`CloudExporter`](https://mastra.ai/docs/observability/tracing/exporters/cloud), set `MASTRA_PROJECT_ID` and `MASTRA_CLOUD_ACCESS_TOKEN` per environment so traces route to the matching Studio project.
+Each project has its own Studio URL and its own observability data. When using [`MastraPlatformExporter`](https://mastra.ai/docs/observability/tracing/exporters/mastra-platform), set `MASTRA_PROJECT_ID` and `MASTRA_CLOUD_ACCESS_TOKEN` per environment so traces route to the matching Studio project.

package/.docs/docs/mastra-platform/overview.md

@@ -75,4 +75,4 @@ Once you're ready to deploy your application to production, use [`mastra studio
 
 Follow the [Studio deployment guide](https://mastra.ai/docs/studio/deployment) and [Server deployment guide](https://mastra.ai/guides/deployment/mastra-platform) for step-by-step instructions.
 
-If you host your Mastra application on your own infrastructure, you can still send observability data to Studio using the [CloudExporter](https://mastra.ai/docs/observability/tracing/exporters/cloud).
+If you host your Mastra application on your own infrastructure, you can still send observability data to Studio using the [MastraPlatformExporter](https://mastra.ai/docs/observability/tracing/exporters/mastra-platform).

package/.docs/docs/observability/logging.md

@@ -35,7 +35,7 @@ You can control which log levels reach observability storage independently from
 ```typescript
 import { Mastra } from '@mastra/core/mastra'
 import { PinoLogger } from '@mastra/loggers'
-import { Observability, DefaultExporter } from '@mastra/observability'
+import { Observability, MastraStorageExporter } from '@mastra/observability'
 
 export const mastra = new Mastra({
   logger: new PinoLogger({ name: 'Mastra', level: 'debug' }),
@@ -43,7 +43,7 @@ export const mastra = new Mastra({
     configs: {
       default: {
         serviceName: 'my-app',
-        exporters: [new DefaultExporter()],
+        exporters: [new MastraStorageExporter()],
         logging: {
           enabled: true, // set to false to disable log forwarding
           level: 'info', // minimum level: 'debug' | 'info' | 'warn' | 'error' | 'fatal'

package/.docs/docs/observability/metrics/overview.md

@@ -54,7 +54,7 @@ import { Mastra } from '@mastra/core/mastra'
 import { LibSQLStore } from '@mastra/libsql'
 import { DuckDBStore } from '@mastra/duckdb'
 import { MastraCompositeStore } from '@mastra/core/storage'
-import { Observability, DefaultExporter, SensitiveDataFilter } from '@mastra/observability'
+import { Observability, MastraStorageExporter, SensitiveDataFilter } from '@mastra/observability'
 
 export const mastra = new Mastra({
   storage: new MastraCompositeStore({
@@ -71,7 +71,7 @@ export const mastra = new Mastra({
     configs: {
       default: {
         serviceName: 'mastra',
-        exporters: [new DefaultExporter()],
+        exporters: [new MastraStorageExporter()],
         spanOutputProcessors: [new SensitiveDataFilter()],
       },
     },
@@ -103,7 +103,7 @@ Mastra auto-instruments agent runs, workflow steps, tool calls, and model genera
 2. **Token usage**: Extracted from the `usage` attribute on model generation spans.
 3. **Cost estimation**: Runs each token metric through an embedded pricing registry that matches by provider and model name.
 
-Before storage, all metric labels pass through a cardinality filter that blocks known high-cardinality values (such as trace IDs and UUIDs) to keep storage efficient. Metrics are then batched by an internal event buffer and flushed to storage by the `DefaultExporter`.
+Before storage, all metric labels pass through a cardinality filter that blocks known high-cardinality values (such as trace IDs and UUIDs) to keep storage efficient. Metrics are then batched by an internal event buffer and flushed to storage by the `MastraStorageExporter`.
 
 ## Next steps
 
@@ -111,4 +111,4 @@ Before storage, all metric labels pass through a cardinality filter that blocks
 - [Tracing overview](https://mastra.ai/docs/observability/tracing/overview)
 - [Studio observability](https://mastra.ai/docs/studio/observability)
 - [Observability overview](https://mastra.ai/docs/observability/overview)
-- [DefaultExporter reference](https://mastra.ai/docs/observability/tracing/exporters/default)
+- [MastraStorageExporter reference](https://mastra.ai/docs/observability/tracing/exporters/mastra-storage)

package/.docs/docs/observability/overview.md

@@ -61,8 +61,8 @@ import { DuckDBStore } from '@mastra/duckdb'
 import { MastraCompositeStore } from '@mastra/core/storage'
 import {
   Observability,
-  DefaultExporter,
-  CloudExporter,
+  MastraStorageExporter,
+  MastraPlatformExporter,
   SensitiveDataFilter,
 } from '@mastra/observability'
 
@@ -82,8 +82,8 @@ export const mastra = new Mastra({
       default: {
         serviceName: 'mastra',
         exporters: [
-          new DefaultExporter(), // Persists traces to storage for Mastra Studio
-          new CloudExporter(), // Sends observability data to hosted Mastra Studio (if MASTRA_CLOUD_ACCESS_TOKEN is set)
+          new MastraStorageExporter(), // Persists observability events to Mastra Storage
+          new MastraPlatformExporter(), // Sends observability events to Mastra Platform (if MASTRA_CLOUD_ACCESS_TOKEN is set)
         ],
         spanOutputProcessors: [
           new SensitiveDataFilter(), // Redacts sensitive data like passwords, tokens, keys
@@ -98,9 +98,9 @@ This enables tracing, log forwarding, and metrics. Mastra also supports external
 
 ## Storage
 
-Not all storage backends support every signal. Traces and logs work with most backends, but metrics require an OLAP-capable store like DuckDB (development) or ClickHouse (production). For the full compatibility list, see [storage provider support](https://mastra.ai/docs/observability/tracing/exporters/default).
+Not all storage backends support every signal. Traces and logs work with most backends, but metrics require an OLAP-capable store like DuckDB (development) or ClickHouse (production). For the full compatibility list, see [storage provider support](https://mastra.ai/docs/observability/tracing/exporters/mastra-storage).
 
-For production environments with high traffic, use composite storage to route the observability domain to a dedicated backend. See [production recommendations](https://mastra.ai/docs/observability/tracing/exporters/default) for details.
+For production environments with high traffic, use composite storage to route the observability domain to a dedicated backend. See [production recommendations](https://mastra.ai/docs/observability/tracing/exporters/mastra-storage) for details.
 
 ## Next steps
 

package/.docs/docs/observability/tracing/exporters/braintrust.md

@@ -105,6 +105,43 @@ new BraintrustExporter({
 })
 ```
 
+## Attach traces to Braintrust evals
+
+When you run Mastra inside Braintrust `Eval()` or `logger.traced()`, pass the Braintrust logger and `currentSpan` resolver to the exporter. Import `currentSpan` from the same `braintrust` package instance that creates the eval or traced span.
+
+This helps Mastra attach its spans under the active Braintrust span when your app and `@mastra/braintrust` resolve different installed copies of the Braintrust SDK.
+
+```typescript
+import { currentSpan, initLogger } from 'braintrust'
+import { BraintrustExporter } from '@mastra/braintrust'
+
+const logger = initLogger({
+  projectName: 'my-project',
+  apiKey: process.env.BRAINTRUST_API_KEY,
+})
+
+const exporter = new BraintrustExporter({
+  braintrustLogger: logger,
+  currentSpan,
+})
+```
+
+Use the configured Mastra instance inside the Braintrust eval task. The `currentSpan` resolver above reads the active span created by `Eval()`.
+
+```typescript
+import { Eval } from 'braintrust'
+import { mastra } from '../mastra'
+
+await Eval('my-project', {
+  data: () => [{ input: 'Say hello', expected: 'Hello' }],
+  task: async input => {
+    const agent = mastra.getAgent('assistant')
+    return (await agent.generate(input)).text
+  },
+  scores: [],
+})
+```
+
 ## Querying Braintrust with returned `spanId`
 
 For Braintrust, use `spanId` as the root span identifier when searching for traces because Braintrust root-span queries are typically faster than trace-id queries.

package/.docs/docs/observability/tracing/exporters/{cloud.md → mastra-platform.md}

@@ -1,8 +1,10 @@
-# Cloud exporter
+# Mastra Platform exporter
 
-The `CloudExporter` sends traces, logs, metrics, scores, and feedback to the Mastra platform. Use it to route observability data from any Mastra app to a hosted project in the Mastra platform.
+The `MastraPlatformExporter` sends traces, logs, metrics, scores, and feedback to the Mastra platform. Use it to route observability data from any Mastra app to a hosted project in the Mastra platform.
 
-> **Self-hosted or standalone apps:** If you host your Mastra application on your own infrastructure (not on Mastra Platform), you still need a deployed Studio project to view traces, logs, and metrics. `CloudExporter` sends data to a Studio project, so one must exist before you can use it.
+> **Note:** `MastraPlatformExporter` was previously called `CloudExporter`. The original `CloudExporter` class is still exported from `@mastra/observability` for backward compatibility, but it is deprecated. New code should use `MastraPlatformExporter`.
+
+> **Self-hosted or standalone apps:** If you host your Mastra application on your own infrastructure (not on Mastra Platform), you still need a deployed Studio project to view traces, logs, and metrics. `MastraPlatformExporter` sends data to a Studio project, so one must exist before you can use it.
 >
 > 1. [Create a Mastra project](https://mastra.ai/guides/getting-started/quickstart) if you don't have one yet.
 > 2. [Deploy Studio](https://mastra.ai/docs/studio/deployment) to the Mastra platform with `mastra studio deploy`.
@@ -10,13 +12,13 @@ The `CloudExporter` sends traces, logs, metrics, scores, and feedback to the Mas
 
 ## Version compatibility
 
-- Use `CloudExporter` with `@mastra/observability@1.8.0` or later.
-- If you use `@mastra/observability@1.8.0` through `1.9.1`, set `MASTRA_CLOUD_TRACES_ENDPOINT=https://observability.mastra.ai` in addition to `MASTRA_CLOUD_ACCESS_TOKEN` and `MASTRA_PROJECT_ID`.
-- Starting in `@mastra/observability@1.9.2`, `CloudExporter` defaults to `https://observability.mastra.ai`, so `MASTRA_CLOUD_TRACES_ENDPOINT` is only required when you want to send telemetry to a different collector.
+- `MastraPlatformExporter` is available starting in `@mastra/observability@1.12.0`. In `1.8.0` through `1.11.x` the same exporter ships only as `CloudExporter`; the constructor signature and environment variables are identical.
+- In `@mastra/observability@1.8.0` through `1.9.1`, set `MASTRA_CLOUD_TRACES_ENDPOINT=https://observability.mastra.ai` in addition to `MASTRA_CLOUD_ACCESS_TOKEN` and `MASTRA_PROJECT_ID`.
+- Starting in `@mastra/observability@1.9.2`, the exporter defaults to `https://observability.mastra.ai`, so `MASTRA_CLOUD_TRACES_ENDPOINT` is only required when you want to send telemetry to a different collector.
 
 ## Quickstart
 
-To connect `CloudExporter`, create an access token, find the destination `projectId`, and add the exporter to your observability config.
+To connect `MastraPlatformExporter`, create an access token, find the destination `projectId`, and add the exporter to your observability config.
 
 ### 1. Create an access token
 
@@ -69,7 +71,7 @@ MASTRA_PROJECT_ID=<your-project-id>
 
 ### 3. Set your environment variables
 
-Set both values in your environment so `CloudExporter` can authenticate and route telemetry to the correct project:
+Set both values in your environment so `MastraPlatformExporter` can authenticate and route telemetry to the correct project:
 
 ```bash
 MASTRA_CLOUD_ACCESS_TOKEN=<your-cloud-access-token>
@@ -88,29 +90,29 @@ If you want to send telemetry somewhere other than Mastra platform, set `MASTRA_
 MASTRA_CLOUD_TRACES_ENDPOINT=https://collector.example.com
 ```
 
-When you pass a base origin, `CloudExporter` derives the matching publish URLs for traces, logs, metrics, scores, and feedback automatically.
+When you pass a base origin, `MastraPlatformExporter` derives the matching publish URLs for traces, logs, metrics, scores, and feedback automatically.
 
-### 4. Enable `CloudExporter`
+### 4. Enable `MastraPlatformExporter`
 
-The following example demonstrates how to add `CloudExporter` to your observability config:
+The following example demonstrates how to add `MastraPlatformExporter` to your observability config:
 
 ```ts
 import { Mastra } from '@mastra/core'
-import { Observability, CloudExporter } from '@mastra/observability'
+import { Observability, MastraPlatformExporter } from '@mastra/observability'
 
 export const mastra = new Mastra({
   observability: new Observability({
     configs: {
       production: {
         serviceName: 'api-server',
-        exporters: [new CloudExporter()],
+        exporters: [new MastraPlatformExporter()],
       },
     },
   }),
 })
 ```
 
-Set `serviceName` on the observability config, not on `CloudExporter` itself.
+Set `serviceName` on the observability config, not on `MastraPlatformExporter` itself.
 
 Use a stable `serviceName` value. In Studio, traces can be filtered by **Deployments → Service Name**, so a consistent name makes traces easier to find.
 
@@ -119,23 +121,23 @@ Visit [Observability configuration reference](https://mastra.ai/reference/observ
 If you prefer, rely entirely on environment variables:
 
 ```ts
-new CloudExporter()
+new MastraPlatformExporter()
 ```
 
-With `MASTRA_CLOUD_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` set, `CloudExporter` sends data to the Mastra platform project you configured. If you also set `MASTRA_CLOUD_TRACES_ENDPOINT`, it sends data to that collector instead.
+With `MASTRA_CLOUD_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` set, `MastraPlatformExporter` sends data to the Mastra platform project you configured. If you also set `MASTRA_CLOUD_TRACES_ENDPOINT`, it sends data to that collector instead.
 
-> **Note:** Visit [CloudExporter reference](https://mastra.ai/reference/observability/tracing/exporters/cloud-exporter) for the full list of configuration options.
+> **Note:** Visit [MastraPlatformExporter reference](https://mastra.ai/reference/observability/tracing/exporters/mastra-platform-exporter) for the full list of configuration options.
 
 ## Recommended configuration
 
-Include `DefaultExporter` if you also want to inspect local traces in Studio or persist observability data to your configured storage.
+Include `MastraStorageExporter` if you also want to inspect local traces in Studio or persist observability data to your configured storage.
 
 ```ts
 import { Mastra } from '@mastra/core'
 import {
   Observability,
-  DefaultExporter,
-  CloudExporter,
+  MastraStorageExporter,
+  MastraPlatformExporter,
   SensitiveDataFilter,
 } from '@mastra/observability'
 
@@ -144,7 +146,7 @@ export const mastra = new Mastra({
     configs: {
       default: {
         serviceName: 'mastra',
-        exporters: [new DefaultExporter(), new CloudExporter()],
+        exporters: [new MastraStorageExporter(), new MastraPlatformExporter()],
         spanOutputProcessors: [new SensitiveDataFilter()],
       },
     },
@@ -154,7 +156,7 @@ export const mastra = new Mastra({
 
 ## Complete configuration
 
-`CloudExporter` defaults to Mastra platform. If you want to send telemetry to a different collector, set `MASTRA_CLOUD_TRACES_ENDPOINT` in your environment or pass `endpoint` in code.
+`MastraPlatformExporter` defaults to Mastra platform. If you want to send telemetry to a different collector, set `MASTRA_CLOUD_TRACES_ENDPOINT` in your environment or pass `endpoint` in code.
 
 ```bash
 MASTRA_CLOUD_TRACES_ENDPOINT=https://collector.example.com
@@ -163,7 +165,7 @@ MASTRA_CLOUD_TRACES_ENDPOINT=https://collector.example.com
 The following example demonstrates how to override the collector endpoint and batching behavior in code:
 
 ```ts
-new CloudExporter({
+new MastraPlatformExporter({
   endpoint: 'https://collector.example.com',
   maxBatchSize: 1000,
   maxBatchWaitMs: 5000,
@@ -173,7 +175,7 @@ new CloudExporter({
 
 ## Viewing data in Mastra Studio
 
-After you enable `CloudExporter`, open your project in [Mastra Studio](https://projects.mastra.ai) to inspect the exported data.
+After you enable `MastraPlatformExporter`, open your project in [Mastra Studio](https://projects.mastra.ai) to inspect the exported data.
 
 - Open the project you set `MASTRA_PROJECT_ID` to and select **Open Studio**.
 - In Studio, go to **Traces** to inspect agent and workflow traces.
@@ -184,7 +186,7 @@ When you deploy with Mastra Studio, set **Deployment → Service Name** to a sta
 
 ## Performance
 
-> **Info:** CloudExporter uses batching to optimize network usage. Events are buffered and sent in batches, reducing overhead while maintaining near real-time visibility.
+> **Info:** MastraPlatformExporter uses batching to optimize network usage. Events are buffered and sent in batches, reducing overhead while maintaining near real-time visibility.
 
 ### Batching behavior
 
@@ -196,4 +198,4 @@ When you deploy with Mastra Studio, set **Deployment → Service Name** to a sta
 ## Related
 
 - [Tracing Overview](https://mastra.ai/docs/observability/tracing/overview)
-- [DefaultExporter](https://mastra.ai/docs/observability/tracing/exporters/default)
+- [MastraStorageExporter](https://mastra.ai/docs/observability/tracing/exporters/mastra-storage)

package/.docs/docs/observability/tracing/exporters/{default.md → mastra-storage.md}

@@ -1,6 +1,8 @@
-# Default exporter
+# Mastra Storage exporter
 
-The `DefaultExporter` persists traces to your configured storage backend, making them accessible through Studio. It's automatically enabled when using the default observability configuration and requires no external services.
+The `MastraStorageExporter` persists traces to your configured storage backend, making them accessible through Studio. It requires no external services.
+
+> **Note:** `MastraStorageExporter` was previously called `DefaultExporter`. The original `DefaultExporter` class is still exported from `@mastra/observability` for backward compatibility, but it is deprecated. New code should use `MastraStorageExporter`.
 
 > **Production Observability:** Observability data can quickly overwhelm general-purpose databases in production. For high-traffic applications, route the observability storage domain to [ClickHouse](https://mastra.ai/reference/storage/clickhouse) through [composite storage](https://mastra.ai/reference/storage/composite). See [Production Recommendations](#production-recommendations) for details.
 
@@ -15,7 +17,7 @@ The `DefaultExporter` persists traces to your configured storage backend, making
 
 ```typescript
 import { Mastra } from '@mastra/core'
-import { Observability, DefaultExporter } from '@mastra/observability'
+import { Observability, MastraStorageExporter } from '@mastra/observability'
 import { LibSQLStore } from '@mastra/libsql'
 
 export const mastra = new Mastra({
@@ -27,7 +29,7 @@ export const mastra = new Mastra({
     configs: {
       local: {
         serviceName: 'my-service',
-        exporters: [new DefaultExporter()],
+        exporters: [new MastraStorageExporter()],
       },
     },
   }),
@@ -36,14 +38,14 @@ export const mastra = new Mastra({
 
 ### Recommended Configuration
 
-Include DefaultExporter in your observability configuration:
+Include MastraStorageExporter in your observability configuration:
 
 ```typescript
 import { Mastra } from '@mastra/core'
 import {
   Observability,
-  DefaultExporter,
-  CloudExporter,
+  MastraStorageExporter,
+  MastraPlatformExporter,
   SensitiveDataFilter,
 } from '@mastra/observability'
 import { LibSQLStore } from '@mastra/libsql'
@@ -58,8 +60,8 @@ export const mastra = new Mastra({
       default: {
         serviceName: 'mastra',
         exporters: [
-          new DefaultExporter(), // Persists traces to storage for Studio
-          new CloudExporter(), // Sends observability data to hosted Mastra Studio (requires MASTRA_CLOUD_ACCESS_TOKEN)
+          new MastraStorageExporter(), // Persists observability events to Mastra Storage
+          new MastraPlatformExporter(), // Sends observability events to Mastra Platform (requires MASTRA_CLOUD_ACCESS_TOKEN)
         ],
         spanOutputProcessors: [new SensitiveDataFilter()],
       },
@@ -79,7 +81,7 @@ Access your traces through Studio:
 
 ## Tracing strategies
 
-DefaultExporter automatically selects the optimal tracing strategy based on your storage provider. You can also override this selection if needed.
+MastraStorageExporter automatically selects the optimal tracing strategy based on your storage provider. You can also override this selection if needed.
 
 ### Available Strategies
 
@@ -92,7 +94,7 @@ DefaultExporter automatically selects the optimal tracing strategy based on your
 ### Strategy Configuration
 
 ```typescript
-new DefaultExporter({
+new MastraStorageExporter({
   strategy: 'auto', // Default - let storage provider decide
   // or explicitly set:
   // strategy: 'realtime' | 'batch-with-updates' | 'insert-only'
@@ -108,7 +110,7 @@ new DefaultExporter({
 
 Different storage providers support different tracing strategies. Some providers support observability for production workloads, while others are intended primarily for local development.
 
-If you set the strategy to `'auto'`, the `DefaultExporter` automatically selects the optimal strategy for the storage provider. If you set the strategy to a mode that the storage provider doesn't support, you will get an error message.
+If you set the strategy to `'auto'`, the `MastraStorageExporter` automatically selects the optimal strategy for the storage provider. If you set an explicit strategy that the storage provider doesn't support, the exporter logs a warning and falls back to the provider's preferred strategy.
 
 ### Providers with Observability Support
 
@@ -167,7 +169,7 @@ For both batch strategies (`batch-with-updates` and `insert-only`), traces are f
 
 ### Error handling
 
-The DefaultExporter includes robust error handling for production use:
+The MastraStorageExporter includes robust error handling for production use:
 
 - **Retry Logic**: Exponential backoff (500ms, 1s, 2s, 4s)
 - **Transient Failures**: Automatic retry with backoff
@@ -213,22 +215,22 @@ class DropAlertExporter extends BaseExporter {
 
 ```typescript
 // Zero config - recommended for most users
-new DefaultExporter()
+new MastraStorageExporter()
 
 // Development override
-new DefaultExporter({
+new MastraStorageExporter({
   strategy: 'realtime', // Immediate visibility for debugging
 })
 
 // High-throughput production
-new DefaultExporter({
+new MastraStorageExporter({
   maxBatchSize: 2000, // Larger batches
   maxBatchWaitMs: 10000, // Wait longer to fill batches
   maxBufferSize: 50000, // Handle longer outages
 })
 
 // Low-latency production
-new DefaultExporter({
+new MastraStorageExporter({
   maxBatchSize: 100, // Smaller batches
   maxBatchWaitMs: 1000, // Flush quickly
 })
@@ -237,6 +239,6 @@ new DefaultExporter({
 ## Related
 
 - [Tracing Overview](https://mastra.ai/docs/observability/tracing/overview)
-- [CloudExporter](https://mastra.ai/docs/observability/tracing/exporters/cloud)
+- [MastraPlatformExporter](https://mastra.ai/docs/observability/tracing/exporters/mastra-platform)
 - [Composite Storage](https://mastra.ai/reference/storage/composite): Combine multiple storage providers
 - [Storage Configuration](https://mastra.ai/docs/memory/storage)

package/.docs/docs/observability/tracing/overview.md

@@ -18,10 +18,11 @@ Traces are created by:
 
 ```ts
 import { Mastra } from '@mastra/core'
+import { LibSQLStore } from '@mastra/libsql'
 import {
   Observability,
-  DefaultExporter,
-  CloudExporter,
+  MastraStorageExporter,
+  MastraPlatformExporter,
   SensitiveDataFilter,
 } from '@mastra/observability'
 
@@ -31,8 +32,8 @@ export const mastra = new Mastra({
       default: {
         serviceName: 'mastra',
         exporters: [
-          new DefaultExporter(), // Persists traces to storage for Studio
-          new CloudExporter(), // Sends observability data to hosted Mastra Studio (if MASTRA_CLOUD_ACCESS_TOKEN is set)
+          new MastraStorageExporter(), // Persists observability events to Mastra Storage
+          new MastraPlatformExporter(), // Sends observability events to Mastra Platform (if MASTRA_CLOUD_ACCESS_TOKEN is set)
         ],
         spanOutputProcessors: [
           new SensitiveDataFilter(), // Redacts sensitive data like passwords, tokens, keys
@@ -55,8 +56,8 @@ This configuration includes:
 
 - **Exporters**:
 
-  - `DefaultExporter` - Persists traces to your configured storage for Studio
-  - `CloudExporter` - Sends observability data to hosted Mastra Studio (requires `MASTRA_CLOUD_ACCESS_TOKEN`)
+  - `MastraStorageExporter` - Persists observability events to Mastra Storage
+  - `MastraPlatformExporter` - Sends observability events to Mastra Platform (requires `MASTRA_CLOUD_ACCESS_TOKEN`)
 
 - **Span Output Processors**: `SensitiveDataFilter` - Redacts sensitive fields
 
@@ -68,8 +69,8 @@ Exporters determine where your trace data is sent and how it's stored. They inte
 
 Mastra provides two built-in exporters:
 
-- **[Default](https://mastra.ai/docs/observability/tracing/exporters/default)** - Persists traces to local storage for viewing in Studio
-- **[Cloud](https://mastra.ai/docs/observability/tracing/exporters/cloud)** - Sends observability data to hosted Mastra Studio for production monitoring and collaboration
+- **[Mastra Storage](https://mastra.ai/docs/observability/tracing/exporters/mastra-storage)** - Persists observability events to Mastra Storage for viewing in Studio
+- **[Mastra Platform](https://mastra.ai/docs/observability/tracing/exporters/mastra-platform)** - Sends observability events to Mastra Platform for production monitoring and collaboration
 
 ### External Exporters
 
@@ -172,7 +173,7 @@ export const mastra = new Mastra({
           type: 'ratio',
           probability: 0.1,
         },
-        exporters: [new DefaultExporter()],
+        exporters: [new MastraStorageExporter()],
       },
     },
   }),
@@ -212,7 +213,7 @@ export const mastra = new Mastra({
       debug: {
         serviceName: 'debug-service',
         sampling: { type: 'always' },
-        exporters: [new DefaultExporter()],
+        exporters: [new MastraStorageExporter()],
       },
     },
     configSelector: (context, availableTracers) => {
@@ -249,7 +250,7 @@ export const mastra = new Mastra({
       development: {
         serviceName: 'my-service-dev',
         sampling: { type: 'always' },
-        exporters: [new DefaultExporter()],
+        exporters: [new MastraStorageExporter()],
       },
       staging: {
         serviceName: 'my-service-staging',
@@ -259,7 +260,7 @@ export const mastra = new Mastra({
       production: {
         serviceName: 'my-service-prod',
         sampling: { type: 'ratio', probability: 0.01 },
-        exporters: [cloudExporter, langfuseExporter],
+        exporters: [mastraObserveExporter, langfuseExporter],
       },
     },
     configSelector: (context, availableTracers) => {
@@ -274,13 +275,13 @@ export const mastra = new Mastra({
 
 #### Maintaining Studio access
 
-When adding external exporters, include `DefaultExporter` and `CloudExporter` to maintain access to Studio:
+When adding external exporters, include `MastraStorageExporter` and `MastraPlatformExporter` to maintain access to Studio:
 
 ```ts
 import {
   Observability,
-  DefaultExporter,
-  CloudExporter,
+  MastraStorageExporter,
+  MastraPlatformExporter,
   SensitiveDataFilter,
 } from '@mastra/observability'
 import { ArizeExporter } from '@mastra/arize'
@@ -295,8 +296,8 @@ export const mastra = new Mastra({
             endpoint: process.env.PHOENIX_COLLECTOR_ENDPOINT,
             apiKey: process.env.PHOENIX_API_KEY,
           }),
-          new DefaultExporter(), // Keep Studio access
-          new CloudExporter(), // Keep Cloud access
+          new MastraStorageExporter(), // Keep Studio access
+          new MastraPlatformExporter(), // Keep Cloud access
         ],
         spanOutputProcessors: [new SensitiveDataFilter()],
       },
@@ -308,8 +309,8 @@ export const mastra = new Mastra({
 This configuration sends traces to all three destinations simultaneously:
 
 - **Arize Phoenix/AX** for external observability
-- **DefaultExporter** for Studio
-- **CloudExporter** for hosted Studio dashboard
+- **MastraStorageExporter** for Studio
+- **MastraPlatformExporter** for hosted Studio dashboard
 
 > **Info:** Remember: A single trace can be sent to multiple exporters. You don't need separate configs for each exporter unless you want different sampling rates or processors.
 
@@ -352,7 +353,7 @@ export const mastra = new Mastra({
     configs: {
       default: {
         serviceName: 'my-service',
-        exporters: [new DefaultExporter()],
+        exporters: [new MastraStorageExporter()],
       },
     },
   }),
@@ -378,7 +379,7 @@ export const mastra = new Mastra({
       default: {
         serviceName: 'my-service',
         requestContextKeys: ['userId', 'environment', 'tenantId'],
-        exporters: [new DefaultExporter()],
+        exporters: [new MastraStorageExporter()],
       },
     },
   }),
@@ -429,7 +430,7 @@ export const mastra = new Mastra({
     configs: {
       default: {
         requestContextKeys: ['user.id', 'session.data.experimentId'],
-        exporters: [new DefaultExporter()],
+        exporters: [new MastraStorageExporter()],
       },
     },
   }),
@@ -667,7 +668,7 @@ export const mastra = new Mastra({
     configs: {
       development: {
         spanOutputProcessors: [new LowercaseInputProcessor(), new SensitiveDataFilter()],
-        exporters: [new DefaultExporter()],
+        exporters: [new MastraStorageExporter()],
       },
     },
   }),
@@ -694,7 +695,7 @@ The following example demonstrates how to combine both options in a single confi
 ```ts
 import { Mastra } from '@mastra/core'
 import { SpanType } from '@mastra/core/observability'
-import { Observability, DefaultExporter } from '@mastra/observability'
+import { Observability, MastraStorageExporter } from '@mastra/observability'
 import { LangfuseExporter } from '@mastra/langfuse'
 
 export const mastra = new Mastra({
@@ -702,7 +703,7 @@ export const mastra = new Mastra({
     configs: {
       default: {
         serviceName: 'my-app',
-        exporters: [new DefaultExporter(), new LangfuseExporter()],
+        exporters: [new MastraStorageExporter(), new LangfuseExporter()],
         excludeSpanTypes: [SpanType.MODEL_CHUNK, SpanType.MODEL_STEP],
         spanFilter: span => {
           if (span.type === SpanType.TOOL_CALL && span.attributes?.success) {
@@ -880,7 +881,7 @@ export const mastra = new Mastra({
           maxArrayLength: 100, // Maximum number of items in arrays (default: 50)
           maxObjectKeys: 75, // Maximum number of keys in objects (default: 50)
         },
-        exporters: [new DefaultExporter()],
+        exporters: [new MastraStorageExporter()],
       },
     },
   }),
@@ -1161,8 +1162,8 @@ Mastra automatically creates spans for:
 
 ### Exporters
 
-- [DefaultExporter](https://mastra.ai/reference/observability/tracing/exporters/default-exporter): Storage persistence
-- [CloudExporter](https://mastra.ai/reference/observability/tracing/exporters/cloud-exporter): Mastra platform integration
+- [MastraStorageExporter](https://mastra.ai/reference/observability/tracing/exporters/mastra-storage-exporter): Storage persistence
+- [MastraPlatformExporter](https://mastra.ai/reference/observability/tracing/exporters/mastra-platform-exporter): Mastra platform integration
 - [ConsoleExporter](https://mastra.ai/reference/observability/tracing/exporters/console-exporter): Debug output
 - [Arize](https://mastra.ai/reference/observability/tracing/exporters/arize): Arize Phoenix and Arize AX integration
 - [Braintrust](https://mastra.ai/reference/observability/tracing/exporters/braintrust): Braintrust integration