@mastra/mcp-docs-server 1.2.15 → 1.2.16-alpha.1

package/.docs/reference/observability/tracing/processors/sensitive-data-filter.md

@@ -2,27 +2,50 @@
 
 # SensitiveDataFilter
 
-A SpanOutputProcessor that redacts sensitive information from span fields.
+`SensitiveDataFilter` is a span output processor that redacts values whose field names match a configured list. [`Observability`](https://mastra.ai/reference/observability/tracing/configuration) applies it to plain observability configurations by default.
 
-## Auto-applied by default
+## Usage example
 
-`Observability` automatically appends a `SensitiveDataFilter` to every configured instance's `spanOutputProcessors` so secrets are redacted before they reach exporters such as the Mastra cloud exporter. The filter runs last (after any user-provided processors) so that sensitive data introduced or surfaced by upstream processors is still redacted. You don't need to add it manually unless you want to customize its options.
-
-To opt out or customize the auto-applied filter, use the `sensitiveDataFilter` option on the [`Observability` registry config](https://mastra.ai/reference/observability/tracing/configuration):
+Configure the automatically applied filter with the top-level `sensitiveDataFilter` option. The filter runs after user-provided span output processors so it can redact values they add or expose.
 
 ```typescript
-import { Observability } from '@mastra/observability'
+import { Mastra } from '@mastra/core/mastra'
+import { Observability, MastraStorageExporter } from '@mastra/observability'
+
+export const mastra = new Mastra({
+  observability: new Observability({
+    configs: {
+      default: {
+        serviceName: 'my-service',
+        exporters: [new MastraStorageExporter()],
+      },
+    },
+    sensitiveDataFilter: {
+      sensitiveFields: ['password', 'authorization', 'customerSecret'],
+      redactionToken: '[HIDDEN]',
+      redactionStyle: 'full',
+    },
+  }),
+})
+```
 
+Passing `sensitiveFields` replaces the default field list. Include every default field you still want to redact.
+
+To disable automatic filtering for all plain configurations, set `sensitiveDataFilter` to `false`:
+
+```typescript
 new Observability({
-  configs: {/* ... */},
-  // disable the auto-applied filter
+  configs: {
+    debug: {
+      serviceName: 'debug-service',
+      exporters: [new MastraStorageExporter()],
+    },
+  },
   sensitiveDataFilter: false,
-  // or customize it
-  // sensitiveDataFilter: { sensitiveFields: ['mySecret'], redactionStyle: 'partial' },
 })
 ```
 
-If a config already includes a `SensitiveDataFilter` in `spanOutputProcessors`, the auto-applied filter is skipped to avoid double redaction. Pre-instantiated `ObservabilityInstance` values aren't modified. Add a `SensitiveDataFilter` to their processors yourself if needed.
+If a plain configuration already contains a `SensitiveDataFilter` in `spanOutputProcessors`, `Observability` uses that instance and doesn't add another. Pre-instantiated `ObservabilityInstance` values aren't modified. Add the processor when constructing those instances if they need filtering.
 
 ## Constructor
 
@@ -30,120 +53,82 @@ If a config already includes a `SensitiveDataFilter` in `spanOutputProcessors`,
 new SensitiveDataFilter(options?: SensitiveDataFilterOptions)
 ```
 
-## `SensitiveDataFilterOptions`
+**sensitiveFields** (`string[]`): Complete list of field names to redact. Matching is case-insensitive and ignores separators. Replaces the default list when provided. (Default: `['password', 'token', 'secret', 'key', 'apikey', 'auth', 'authorization', 'bearer', 'bearertoken', 'jwt', 'credential', 'clientsecret', 'privatekey', 'refresh', 'ssn']`)
+
+**redactionToken** (`string`): Replacement value used for full redaction and short values under partial redaction. (Default: `'[REDACTED]'`)
+
+**redactionStyle** (`'full' | 'partial'`): Controls whether matched values are fully or partially redacted. (Default: `'full'`)
 
 ```typescript
 interface SensitiveDataFilterOptions {
-  /**
-   * List of sensitive field names to redact.
-   * Matching is case-insensitive and normalizes separators
-   * (api-key, api_key, Api Key → apikey).
-   * Defaults include: password, token, secret, key, apikey, auth,
-   * authorization, bearer, bearertoken, jwt, credential,
-   * clientsecret, privatekey, refresh, ssn.
-   */
   sensitiveFields?: string[]
-
-  /**
-   * The token used for full redaction.
-   * Default: "[REDACTED]"
-   */
   redactionToken?: string
-
-  /**
-   * Style of redaction to use:
-   * - "full": always replace with redactionToken
-   * - "partial": show 3 characters from the start and end, redact the middle
-   * Default: "full"
-   */
   redactionStyle?: RedactionStyle
 }
-```
-
-## `RedactionStyle`
 
-```typescript
 type RedactionStyle = 'full' | 'partial'
 ```
 
-## Methods
-
-### process
-
-```typescript
-process(span: AnySpan): AnySpan
-```
+## Redaction styles
 
-Process a span by filtering sensitive data across its key fields: attributes, metadata, input, output, and errorInfo.
+### Full redaction
 
-**Returns:** A new span with sensitive values redacted.
+Full redaction replaces each matched primitive value with `redactionToken`.
 
-### shutdown
+```jsonc
+// Before
+{ "apiKey": "sk-abc123xyz789", "userId": "user_123" }
 
-```typescript
-async shutdown(): Promise<void>
+// After
+{ "apiKey": "[REDACTED]", "userId": "user_123" }
 ```
 
-No cleanup needed for this processor.
+### Partial redaction
 
-## Properties
+Partial redaction preserves the first and last three characters. Values with six or fewer characters use `redactionToken` instead. Non-string primitive values are converted to strings before redaction.
 
 ```typescript
-readonly name = 'sensitive-data-filter';
+const filter = new SensitiveDataFilter({
+  redactionStyle: 'partial',
+})
 ```
 
-## Default sensitive fields
+```jsonc
+// Before
+{ "apiKey": "sk-abc123xyz789" }
 
-When no custom fields are provided:
-
-```typescript
-[
-  'password',
-  'token',
-  'secret',
-  'key',
-  'apikey',
-  'auth',
-  'authorization',
-  'bearer',
-  'bearertoken',
-  'jwt',
-  'credential',
-  'clientsecret',
-  'privatekey',
-  'refresh',
-  'ssn',
-]
+// After
+{ "apiKey": "sk-…789" }
 ```
 
-## Processing behavior
+## Field matching
 
-### Field Matching
+Field names are lowercased and stripped of non-alphanumeric characters before comparison:
 
-- **Case-insensitive**: `APIKey`, `apikey`, `ApiKey` all match
+- `api-key`, `api_key`, `Api Key`, and `apiKey` normalize to `apikey`.
+- Matching is exact after normalization. `token` matches `Token`, but doesn't match `promptTokens`, `tokenCount`, or `authToken`.
 
-- **Separator-agnostic**: `api-key`, `api_key`, `apiKey` are treated identically
+When a matched field contains an object or array, the filter traverses that value and redacts sensitive fields within it rather than replacing the complete structure.
 
-- **Exact matching**: After normalization, fields must match exactly
-
-  - `token` matches `token`, `Token`, `TOKEN`
-  - `token` doesn't match `promptTokens` or `tokenCount`
-
-### Redaction Styles
-
-#### Full Redaction (default)
+## Processing behavior
 
-All matched values replaced with redactionToken.
+`process()` filters these top-level span fields independently:
 
-#### Partial Redaction
+- `attributes`
+- `metadata`
+- `input`
+- `output`
+- `errorInfo`
 
-- Shows first 3 and last 3 characters
-- Values ≤ 6 characters are fully redacted
-- Non-string values are converted to strings before partial redaction
+Within each field, the processor:
 
-### Error handling
+- Traverses nested objects and arrays.
+- Parses and filters JSON strings that contain objects or arrays. It then serializes the filtered value.
+- Leaves invalid JSON strings unchanged.
+- Preserves `Date` instances.
+- Replaces repeated object references with `[Circular Reference]`.
 
-If filtering a field fails, the field is replaced with:
+If filtering fails anywhere within one top-level span field, that complete field is replaced with this marker:
 
 ```typescript
 {
@@ -153,14 +138,41 @@ If filtering a field fails, the field is replaced with:
 }
 ```
 
-### Processed Fields
+## Methods
+
+### Processing
 
-The filter recursively processes:
+#### `process(span)`
 
-- `span.attributes` - Span metadata and properties
-- `span.metadata` - Custom metadata
-- `span.input` - Input data
-- `span.output` - Output data
-- `span.errorInfo` - Error information
+Redacts the supported fields on the supplied span in place and returns the same span.
+
+```typescript
+import type { AnySpan } from '@mastra/core/observability'
+import { SensitiveDataFilter } from '@mastra/observability'
+
+const filter = new SensitiveDataFilter()
+
+export function redactSpan(span: AnySpan): AnySpan {
+  return filter.process(span)
+}
+```
+
+**span** (`AnySpan`): Span whose attributes, metadata, input, output, and error information are filtered.
+
+Returns: `AnySpan`
+
+### Lifecycle
+
+#### `shutdown()`
+
+Completes processor shutdown. The current processor has no resources or state to clean up.
+
+```typescript
+await filter.shutdown()
+```
+
+Returns: `Promise<void>`
+
+## Properties
 
-Handles nested objects, arrays, and circular references safely.
+**name** (`string`): Processor identifier. (Default: `'sensitive-data-filter'`)

package/.docs/reference/observability/tracing/span-filtering.md

@@ -94,4 +94,4 @@ If `spanFilter` throws an error, Mastra keeps the span and logs the error to avo
 
 - [Tracing overview](https://mastra.ai/docs/observability/tracing/overview) for setup and concepts
 - [Configuration API](https://mastra.ai/reference/observability/tracing/configuration) for `ObservabilityInstanceConfig`
-- [Sensitive data filter](https://mastra.ai/docs/observability/integrations/processors/sensitive-data-filter) for redacting span data
+- [Sensitive data filter](https://mastra.ai/reference/observability/tracing/processors/sensitive-data-filter) for redacting span data

package/.docs/reference/storage/overview.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Storage overview
+# Storage
 
 Mastra storage is organized into domains. Each domain owns a set of tables or collections. Depending on your adapter and configuration, you may use all domains or only a subset.
 

package/.docs/reference/templates/overview.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Overview
+# Templates
 
 This reference explains how to use existing Mastra templates and create your own. It also covers contributing templates to the community ecosystem.
 

package/.docs/{guides → reference}/voice/overview.md

@@ -29,7 +29,7 @@ You can then use the following voice capabilities:
 
 Turn your agent's responses into natural-sounding speech using Mastra's TTS capabilities. Choose from multiple providers like OpenAI, ElevenLabs, and more.
 
-For detailed configuration options and advanced features, check out our [Text-to-Speech guide](https://mastra.ai/guides/voice/text-to-speech).
+For detailed configuration options and advanced features, check out our [Text-to-Speech guide](https://mastra.ai/reference/voice/text-to-speech).
 
 **OpenAI**:
 
@@ -304,7 +304,7 @@ Visit the [Murf Voice Reference](https://mastra.ai/integrations/voice/murf) for
 
 ### Speech to Text (STT)
 
-Transcribe spoken content using providers like OpenAI, ElevenLabs, and more. For detailed configuration options and more, check out [Speech to Text](https://mastra.ai/guides/voice/speech-to-text).
+Transcribe spoken content using providers like OpenAI, ElevenLabs, and more. For detailed configuration options and more, check out [Speech to Text](https://mastra.ai/reference/voice/speech-to-text).
 
 You can download a sample audio file from [here](https://github.com/mastra-ai/realtime-voice-demo/raw/refs/heads/main/how_can_i_help_you.mp3).
 
@@ -537,7 +537,7 @@ Visit the [Sarvam Voice Reference](https://mastra.ai/integrations/voice/sarvam)
 
 ### Speech to Speech (STS)
 
-Create conversational experiences with speech-to-speech capabilities. The unified API enables real-time voice interactions between users and AI agents. For detailed configuration options and advanced features, check out [Speech to Speech](https://mastra.ai/guides/voice/speech-to-speech).
+Create conversational experiences with speech-to-speech capabilities. The unified API enables real-time voice interactions between users and AI agents. For detailed configuration options and advanced features, check out [Speech to Speech](https://mastra.ai/reference/voice/speech-to-speech).
 
 **OpenAI**:
 

package/.docs/{guides → reference}/voice/speech-to-speech.md

@@ -54,7 +54,7 @@ const micStream = getMicrophoneStream()
 await agent.voice.send(micStream)
 ```
 
-For a broader overview of voice providers on agents, see [Voice in Mastra](https://mastra.ai/guides/voice/overview).
+For a broader overview of voice providers on agents, see [Voice in Mastra](https://mastra.ai/reference/voice/overview).
 
 ## Use tools in realtime sessions
 

package/.docs/{guides → reference}/voice/speech-to-text.md

@@ -96,4 +96,4 @@ const transcription = await agent.voice.listen(audioStream, {
 console.log(`Transcription: ${transcription}`)
 ```
 
-For a broader overview of voice providers on agents, see [Voice in Mastra](https://mastra.ai/guides/voice/overview).
+For a broader overview of voice providers on agents, see [Voice in Mastra](https://mastra.ai/reference/voice/overview).

package/.docs/{guides → reference}/voice/text-to-speech.md

@@ -4,7 +4,7 @@
 
 Text-to-Speech (TTS) in Mastra offers a unified API for synthesizing spoken audio from text using providers. By incorporating TTS into your applications, you can enhance user experience with natural voice interactions and improve accessibility for users with visual impairments, plus create more engaging multimodal interfaces.
 
-TTS is a core component of any voice application. Combined with STT (Speech-to-Text), it forms the foundation of voice interaction systems. Newer models support STS ([Speech-to-Speech](https://mastra.ai/guides/voice/speech-to-speech)) which can be used for real-time interactions but come at high cost ($).
+TTS is a core component of any voice application. Combined with STT (Speech-to-Text), it forms the foundation of voice interaction systems. Newer models support STS ([Speech-to-Speech](https://mastra.ai/reference/voice/speech-to-speech)) which can be used for real-time interactions but come at high cost ($).
 
 ## Configuration
 
@@ -101,4 +101,4 @@ await new Promise<void>((resolve, reject) => {
 })
 ```
 
-For a broader overview of voice providers on agents, see [Voice in Mastra](https://mastra.ai/guides/voice/overview).
+For a broader overview of voice providers on agents, see [Voice in Mastra](https://mastra.ai/reference/voice/overview).

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @mastra/mcp-docs-server
 
+## 1.2.16-alpha.0
+
+### Patch Changes
+
+- Updated dependencies [[`088e41e`](https://github.com/mastra-ai/mastra/commit/088e41e434ed05f2c674b254f1034ec46a57a7be), [`b2f0013`](https://github.com/mastra-ai/mastra/commit/b2f0013375588d40c03c13e843b99c0ff8872ca5), [`3b541ae`](https://github.com/mastra-ai/mastra/commit/3b541ae5d410c52b80a7e381d84d021cddb9a449), [`ae79e34`](https://github.com/mastra-ai/mastra/commit/ae79e34c0bd8674fc24c7524217bfc4a051c6136), [`a6c4399`](https://github.com/mastra-ai/mastra/commit/a6c4399763590b3dae21a2c81826e89a3b1deee4)]:
+  - @mastra/core@1.59.0-alpha.0
+
 ## 1.2.15
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.2.15",
+  "version": "1.2.16-alpha.1",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -28,8 +28,8 @@
     "jsdom": "^26.1.0",
     "local-pkg": "^1.1.2",
     "zod": "^4.4.3",
-    "@mastra/core": "1.58.0",
-    "@mastra/mcp": "^1.16.0"
+    "@mastra/mcp": "^1.16.0",
+    "@mastra/core": "1.59.0-alpha.0"
   },
   "devDependencies": {
     "@hono/node-server": "^2.0.0",
@@ -46,8 +46,8 @@
     "typescript": "^6.0.3",
     "vitest": "4.1.10",
     "@internal/lint": "0.0.122",
-    "@mastra/core": "1.58.0",
-    "@internal/types-builder": "0.0.97"
+    "@internal/types-builder": "0.0.97",
+    "@mastra/core": "1.59.0-alpha.0"
   },
   "homepage": "https://mastra.ai",
   "repository": {

package/.docs/docs/observability/integrations/exporters/mastra-platform.md

@@ -1,201 +0,0 @@
-> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
-
-# Mastra platform exporter
-
-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.
-
-> **Note:** `MastraPlatformExporter` was previously called `CloudExporter`. The original `CloudExporter` class is still exported from `@mastra/observability` for backward compatibility, but it's 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`.
-> 3. Follow the [quickstart steps below](#quickstart) to create an access token and find your project ID.
-
-## Version compatibility
-
-- `MastraPlatformExporter` is available starting in `@mastra/observability@1.12.0`. In `1.8.0` through `1.11.x` the same exporter includes only as `CloudExporter`. The constructor signature and environment variables are identical.
-- In `@mastra/observability@1.8.0` through `1.9.1`, set `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT=https://observability.mastra.ai` in addition to `MASTRA_PLATFORM_ACCESS_TOKEN` and `MASTRA_PROJECT_ID`.
-- Starting in `@mastra/observability@1.9.2`, the exporter defaults to `https://observability.mastra.ai`, so `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT` is only required when you want to send telemetry to a different collector.
-
-## Quickstart
-
-To connect `MastraPlatformExporter`, create an access token, find the destination `projectId`, and add the exporter to your observability config.
-
-### 1. Create an access token
-
-Run the following command:
-
-```bash
-mastra auth tokens create exporter-token
-```
-
-This command prints a token secret that you can use as `MASTRA_PLATFORM_ACCESS_TOKEN`.
-
-If you already have an access token, copy the **Observability** value from the Mastra platform instead. You can find it in either of these places:
-
-- On the **Projects** page, open the project list and find the **Observability** row on the project card.
-- On the project **Overview** page, find the **Observability** row directly below the deployment URL.
-
-Set the token as an environment variable:
-
-```bash
-MASTRA_PLATFORM_ACCESS_TOKEN=<your-platform-access-token>
-```
-
-### 2. Find your `projectId`
-
-Run the following command:
-
-```bash
-mastra studio deploy list
-```
-
-The output looks similar to this:
-
-```text
-✅ <your-project-name> (<your-project-id>)
-   Latest:   00000000-0000-0000-0000-000000000000 — running
-   URL:      https://260407.studio.mastra.cloud
-```
-
-In this output, the value in parentheses is the `projectId`:
-
-```text
-<your-project-id>
-```
-
-Set it as an environment variable:
-
-```bash
-MASTRA_PROJECT_ID=<your-project-id>
-```
-
-### 3. Set your environment variables
-
-Set both values in your environment so `MastraPlatformExporter` can authenticate and route telemetry to the correct project:
-
-```bash
-MASTRA_PLATFORM_ACCESS_TOKEN=<your-platform-access-token>
-MASTRA_PROJECT_ID=<your-project-id>
-```
-
-If you use `@mastra/observability@1.8.0` through `1.9.1`, also set the Mastra platform collector explicitly:
-
-```bash
-MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT=https://observability.mastra.ai
-```
-
-If you want to send telemetry somewhere other than Mastra platform, set `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT` as well. Pass either a base origin or a full traces publish URL ending in `/spans/publish`.
-
-```bash
-MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT=https://collector.example.com
-```
-
-When you pass a base origin, `MastraPlatformExporter` derives the matching publish URLs for traces, logs, metrics, scores, and feedback automatically.
-
-### 4. Enable `MastraPlatformExporter`
-
-The following example demonstrates how to add `MastraPlatformExporter` to your observability config:
-
-```ts
-import { Mastra } from '@mastra/core'
-import { Observability, MastraPlatformExporter } from '@mastra/observability'
-
-export const mastra = new Mastra({
-  observability: new Observability({
-    configs: {
-      production: {
-        serviceName: 'api-server',
-        exporters: [new MastraPlatformExporter()],
-      },
-    },
-  }),
-})
-```
-
-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.
-
-Visit [Observability configuration reference](https://mastra.ai/reference/observability/tracing/configuration) for the full observability config shape.
-
-If you prefer, rely entirely on environment variables:
-
-```ts
-new MastraPlatformExporter()
-```
-
-With `MASTRA_PLATFORM_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` set, `MastraPlatformExporter` sends data to the Mastra platform project you configured. If you also set `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT`, it sends data to that collector instead. Visit [MastraPlatformExporter reference](https://mastra.ai/reference/observability/tracing/exporters/mastra-platform-exporter) for the full list of configuration options.
-
-## Recommended configuration
-
-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,
-  MastraStorageExporter,
-  MastraPlatformExporter,
-  SensitiveDataFilter,
-} from '@mastra/observability'
-
-export const mastra = new Mastra({
-  observability: new Observability({
-    configs: {
-      default: {
-        serviceName: 'mastra',
-        exporters: [new MastraStorageExporter(), new MastraPlatformExporter()],
-        spanOutputProcessors: [new SensitiveDataFilter()],
-      },
-    },
-  }),
-})
-```
-
-## Complete configuration
-
-`MastraPlatformExporter` defaults to Mastra platform. If you want to send telemetry to a different collector, set `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT` in your environment or pass `endpoint` in code.
-
-```bash
-MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT=https://collector.example.com
-```
-
-The following example demonstrates how to override the collector endpoint and batching behavior in code:
-
-```ts
-new MastraPlatformExporter({
-  endpoint: 'https://collector.example.com',
-  maxBatchSize: 1000,
-  maxBatchWaitMs: 5000,
-  logLevel: 'info',
-})
-```
-
-## Viewing data in Mastra Studio
-
-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.
-- Open the filter menu and use **Deployments → Service Name** to isolate traces from a specific app or deployment.
-- Use the **Logs** page in the project dashboard to inspect exported logs.
-
-When you deploy with Mastra Studio, set **Deployment → Service Name** to a stable value and keep it aligned with the `serviceName` in your observability config. This makes traces easier to filter in Studio through **Deployments → Service Name** when multiple services or deployments send data to the same project.
-
-## Performance
-
-> **Note:** MastraPlatformExporter uses batching to optimize network usage. Events are buffered and sent in batches, reducing overhead while maintaining near real-time visibility.
-
-### Batching behavior
-
-- Events are batched up to `maxBatchSize` (default: 1000).
-- Batches are sent when full or after `maxBatchWaitMs` (default: 5 seconds).
-- Failed batches are retried with exponential backoff.
-- The exporter degrades gracefully if Mastra Studio is unreachable.
-
-## Related
-
-- [Tracing Overview](https://mastra.ai/docs/observability/tracing/overview)
-- [MastraStorageExporter](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage)

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

@@ -1,47 +0,0 @@
-> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
-
-# Integrations overview
-
-Mastra observability integrations control where observability data goes and how it's 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](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage).
-- Hosted Mastra workflow: Add [Mastra platform](https://mastra.ai/docs/observability/integrations/exporters/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](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage): Persist observability data for Studio.
-- [Mastra platform](https://mastra.ai/docs/observability/integrations/exporters/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](https://mastra.ai/integrations/observability/opentelemetry): Integrate Mastra with an existing OpenTelemetry trace.
-- [Datadog bridge](https://mastra.ai/integrations/observability/datadog): Send Mastra traces to Datadog and its LLM Observability product.
-
-## Processors
-
-Processors transform or redact spans before export:
-
-- [Sensitive Data Filter](https://mastra.ai/docs/observability/integrations/processors/sensitive-data-filter): Redact sensitive fields before spans leave the runtime.
-
-## Next steps
-
-- [Configuration](https://mastra.ai/docs/observability/overview)
-- [Tracing](https://mastra.ai/docs/observability/tracing/overview)
-- [Mastra Storage](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage)
-- [OpenTelemetry bridge](https://mastra.ai/integrations/observability/opentelemetry)