@mastra/core 1.18.0 → 1.18.1-alpha.1

package/dist/docs/references/docs-observability-logging.md

@@ -1,99 +0,0 @@
-# Logging
-
-Mastra's logging system captures function execution, input data, and output responses in a structured format.
-
-When deploying to Mastra Cloud, logs are shown on the [Logs](https://mastra.ai/docs/mastra-cloud/observability) page. In self-hosted or custom environments, logs can be directed to files or external services depending on the configured transports.
-
-## Configuring logs with `PinoLogger`
-
-When [initializing a new Mastra project](https://mastra.ai/guides/getting-started/quickstart) using the CLI, `PinoLogger` is included by default.
-
-```typescript
-import { Mastra } from '@mastra/core/mastra'
-import { PinoLogger } from '@mastra/loggers'
-
-export const mastra = new Mastra({
-  logger: new PinoLogger({
-    name: 'Mastra',
-    level: 'info',
-  }),
-})
-```
-
-> **Info:** Visit [PinoLogger](https://mastra.ai/reference/logging/pino-logger) for all available configuration options.
-
-## Customizing logs
-
-Mastra provides access to a logger instance via the `mastra.getLogger()` method, available inside both workflow steps and tools. The logger supports standard severity levels: `debug`, `info`, `warn`, and `error`.
-
-### Logging from workflow steps
-
-Within a workflow step, access the logger via the `mastra` parameter inside the `execute` function. This allows you to log messages relevant to the step’s execution.
-
-```typescript
-import { createWorkflow, createStep } from "@mastra/core/workflows";
-import { z } from "zod";
-
-const step1 = createStep({
-  execute: async ({ mastra }) => {
-    const logger = mastra.getLogger();
-    logger.info("workflow info log");
-
-    return {
-      output: ""
-    };
-  }
-});
-
-export const testWorkflow = createWorkflow({...})
-  .then(step1)
-  .commit();
-```
-
-### Logging from tools
-
-Similarly, tools have access to the logger instance via the `mastra` parameter. Use this to log tool specific activity during execution.
-
-```typescript
-import { createTool } from '@mastra/core/tools'
-import { z } from 'zod'
-
-export const testTool = createTool({
-  execute: async (inputData, context) => {
-    const logger = context?.mastra.getLogger()
-    logger?.info('tool info log')
-
-    return {
-      output: '',
-    }
-  },
-})
-```
-
-### Logging with additional data
-
-Logger methods accept an optional second argument for additional data. This can be any value, such as an object, string, or number.
-
-In this example, the log message includes an object with a key of `agent` and a value of the `testAgent` instance.
-
-```typescript
-import { createWorkflow, createStep } from "@mastra/core/workflows";
-import { z } from "zod";
-
-const step1 = createStep({
-  execute: async ({ mastra }) => {
-    const testAgent = mastra.getAgent("testAgent");
-    const logger = mastra.getLogger();
-
-    logger.info("workflow info log", { agent: testAgent });
-
-    return {
-      output: ""
-    };
-  }
-});
-
-export const testWorkflow = createWorkflow({...})
-  .then(step1)
-  .commit();
-```

package/dist/docs/references/docs-observability-overview.md

@@ -1,70 +0,0 @@
-# Observability overview
-
-Mastra provides observability features for AI applications. Monitor LLM operations, trace agent decisions, and debug complex workflows with tools that understand AI-specific patterns.
-
-## Key features
-
-### Tracing
-
-Specialized tracing for AI operations that captures:
-
-- **Model interactions**: Token usage, latency, prompts, and completions
-- **Agent execution**: Decision paths, tool calls, and memory operations
-- **Workflow steps**: Branching logic, parallel execution, and step outputs
-- **Automatic instrumentation**: Tracing with decorators
-
-## Storage requirements
-
-The `DefaultExporter` persists traces to your configured storage backend. Not all storage providers support observability—for the full list, see [Storage Provider Support](https://mastra.ai/docs/observability/tracing/exporters/default).
-
-For production environments with high traffic, we recommend using **ClickHouse** for the observability domain via [composite storage](https://mastra.ai/reference/storage/composite). See [Production Recommendations](https://mastra.ai/docs/observability/tracing/exporters/default) for details.
-
-## Quickstart
-
-Configure Observability in your Mastra instance:
-
-```typescript
-import { Mastra } from '@mastra/core'
-import { PinoLogger } from '@mastra/loggers'
-import { LibSQLStore } from '@mastra/libsql'
-import {
-  Observability,
-  DefaultExporter,
-  CloudExporter,
-  SensitiveDataFilter,
-} from '@mastra/observability'
-
-export const mastra = new Mastra({
-  logger: new PinoLogger(),
-  storage: new LibSQLStore({
-    id: 'mastra-storage',
-    url: 'file:./mastra.db', // Storage is required for tracing
-  }),
-  observability: new Observability({
-    configs: {
-      default: {
-        serviceName: 'mastra',
-        exporters: [
-          new DefaultExporter(), // Persists traces to storage for Mastra Studio
-          new CloudExporter(), // Sends traces to Mastra Cloud (if MASTRA_CLOUD_ACCESS_TOKEN is set)
-        ],
-        spanOutputProcessors: [
-          new SensitiveDataFilter(), // Redacts sensitive data like passwords, tokens, keys
-        ],
-      },
-    },
-  }),
-})
-```
-
-> **Serverless environments:** The `file:./mastra.db` storage URL uses the local filesystem, which doesn't work in serverless environments like Vercel, AWS Lambda, or Cloudflare Workers. For serverless deployments, use external storage. See the [Vercel deployment guide](https://mastra.ai/guides/deployment/vercel) for a complete example.
-
-With this basic setup, you will see Traces and Logs in both Studio and in Mastra Cloud.
-
-We also support various external tracing providers like MLflow, Langfuse, Braintrust, and any OpenTelemetry-compatible platform (Datadog, New Relic, SigNoz, etc.). See more about this in the [Tracing](https://mastra.ai/docs/observability/tracing/overview) documentation.
-
-## What's next?
-
-- **[Set up Tracing](https://mastra.ai/docs/observability/tracing/overview)**: Configure tracing for your application
-- **[Configure Logging](https://mastra.ai/docs/observability/logging)**: Add structured logging
-- **[API Reference](https://mastra.ai/reference/observability/tracing/instances)**: Detailed configuration options

package/dist/docs/references/docs-observability-tracing-bridges-otel.md

@@ -1,209 +0,0 @@
-# OpenTelemetry bridge
-
-> **Warning:** The OpenTelemetry Bridge is currently **experimental**. APIs and configuration options may change in future releases.
-
-The OpenTelemetry (OTEL) Bridge enables bidirectional integration between Mastra's tracing system and existing OpenTelemetry infrastructure. Unlike exporters that send trace data to external platforms, the bridge creates native OTEL spans that participate in your distributed tracing context.
-
-> **Looking to send traces without existing OTEL infrastructure?:** If you don't have existing OpenTelemetry instrumentation, the [OpenTelemetry Exporter](https://mastra.ai/docs/observability/tracing/exporters/otel) may be simpler — it sends traces directly without requiring an OTEL SDK setup.
-
-## When to use the bridge
-
-Use the OtelBridge when you:
-
-- Have existing OTEL instrumentation in your application (HTTP servers, database clients, etc.)
-- Want Mastra operations to appear as child spans of your existing OTEL traces
-- Need OTEL-instrumented code inside Mastra tools to maintain proper parent-child relationships
-- Are building a distributed system where trace context must propagate across services
-
-## How it works
-
-The OtelBridge provides two-way integration:
-
-**From OTEL to Mastra:**
-
-- Reads from OTEL ambient context (AsyncLocalStorage) automatically
-- Inherits trace ID and parent span ID from active OTEL spans
-- Respects OTEL sampling decisions — if a trace isn't sampled, Mastra won't create spans for it
-- No manual trace ID passing required when OTEL auto-instrumentation is active
-
-**From Mastra to OTEL:**
-
-- Creates native OTEL spans for Mastra operations (agents, LLM calls, tools, workflows)
-- Maintains proper parent-child relationships in distributed traces
-- Allows OTEL-instrumented code (HTTP clients, database calls) within Mastra operations to nest correctly
-
-## Installation
-
-**npm**:
-
-```bash
-npm install @mastra/otel-bridge
-```
-
-**pnpm**:
-
-```bash
-pnpm add @mastra/otel-bridge
-```
-
-**Yarn**:
-
-```bash
-yarn add @mastra/otel-bridge
-```
-
-**Bun**:
-
-```bash
-bun add @mastra/otel-bridge
-```
-
-The bridge works with your existing OpenTelemetry setup. Depending on your configuration, you may also need some of these packages:
-
-- `@opentelemetry/sdk-node` - Core Node.js SDK for OTEL
-- `@opentelemetry/auto-instrumentations-node` - Auto-instrumentation for common libraries
-- `@opentelemetry/exporter-trace-otlp-proto` - OTLP exporter (Protobuf over HTTP)
-- `@opentelemetry/exporter-trace-otlp-http` - OTLP exporter (JSON over HTTP)
-- `@opentelemetry/exporter-trace-otlp-grpc` - OTLP exporter (gRPC)
-- `@opentelemetry/sdk-trace-base` - Base tracing SDK (for BatchSpanProcessor, etc.)
-- `@opentelemetry/core` - Core utilities (for W3CTraceContextPropagator, etc.)
-
-## Configuration
-
-Using the OtelBridge requires two steps:
-
-1. Configure OpenTelemetry instrumentation in your application
-2. Add the OtelBridge to your Mastra observability config
-
-### Step 1: OpenTelemetry Instrumentation
-
-Create an instrumentation file that initializes OTEL. This must run before your application code:
-
-```typescript
-import { NodeSDK } from '@opentelemetry/sdk-node'
-import { getNodeAutoInstrumentations } from '@opentelemetry/auto-instrumentations-node'
-import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-proto'
-import { BatchSpanProcessor } from '@opentelemetry/sdk-trace-base'
-import { W3CTraceContextPropagator } from '@opentelemetry/core'
-
-const sdk = new NodeSDK({
-  serviceName: 'my-service',
-  spanProcessors: [
-    new BatchSpanProcessor(
-      new OTLPTraceExporter({
-        url: process.env.OTEL_EXPORTER_OTLP_ENDPOINT || 'http://localhost:4318/v1/traces',
-      }),
-    ),
-  ],
-  instrumentations: [getNodeAutoInstrumentations()],
-  textMapPropagator: new W3CTraceContextPropagator(),
-})
-
-sdk.start()
-
-export { sdk }
-```
-
-### Step 2: Mastra Configuration
-
-Add the OtelBridge to your Mastra observability config:
-
-```typescript
-import { Mastra } from '@mastra/core'
-import { Observability } from '@mastra/observability'
-import { OtelBridge } from '@mastra/otel-bridge'
-
-export const mastra = new Mastra({
-  observability: new Observability({
-    configs: {
-      default: {
-        serviceName: 'my-service',
-        bridge: new OtelBridge(),
-      },
-    },
-  }),
-  agents: {
-    /* your agents */
-  },
-})
-```
-
-No Mastra exporters are required when using the bridge — traces are sent via your OTEL SDK configuration. You can optionally add Mastra exporters if you want to send traces to additional destinations.
-
-### Running Your Application
-
-Use the `--import` flag to ensure instrumentation loads before your application:
-
-```bash
-tsx --import ./instrumentation.ts ./src/index.ts
-```
-
-## Semantic conventions
-
-The OtelBridge exports Mastra spans using [OpenTelemetry Semantic Conventions for GenAI v1.38.0](https://github.com/open-telemetry/semantic-conventions/tree/v1.38.0/docs/gen-ai). This includes standardized span names (`chat {model}`, `execute_tool {tool_name}`, etc.) and attributes (`gen_ai.usage.input_tokens`, `gen_ai.request.model`, etc.).
-
-For details on span naming and attributes, see the [OpenTelemetry Exporter semantic conventions](https://mastra.ai/docs/observability/tracing/exporters/otel).
-
-## Trace hierarchy
-
-With the OtelBridge, your traces maintain proper hierarchy across OTEL and Mastra boundaries:
-
-```text
-HTTP POST /api/chat (from Hono middleware)
-└── agent.assistant (from Mastra via OtelBridge)
-    ├── chat gpt-5.4 (LLM call)
-    ├── tool.execute search (tool execution)
-    │   └── HTTP GET api.example.com (from OTEL auto-instrumentation)
-    └── chat gpt-5.4 (follow-up LLM call)
-```
-
-## Multi-service distributed tracing
-
-The OtelBridge enables trace propagation across service boundaries. When Service A calls Service B via HTTP, trace context propagates automatically:
-
-```text
-Service A: HTTP POST /api/process
-└── HTTP POST service-b/api/analyze (outgoing call)
-
-Service B: HTTP POST /api/analyze (incoming call - same trace!)
-└── agent.analyzer (Mastra agent inherits trace context)
-    └── chat gpt-5.4
-```
-
-Both services must have:
-
-1. OTEL instrumentation configured
-2. W3C Trace Context propagator enabled
-3. Mastra with OtelBridge configured
-
-## Using tags
-
-Tags help you categorize and filter traces in your OTEL backend. Add tags when executing agents or workflows:
-
-```typescript
-const result = await agent.generate('Hello', {
-  tracingOptions: {
-    tags: ['production', 'experiment-v2', 'user-request'],
-  },
-})
-```
-
-Tags are exported as a JSON string in the `mastra.tags` span attribute for broad backend compatibility. Common use cases include:
-
-- Environment labels: `"production"`, `"staging"`
-- Experiment tracking: `"experiment-v1"`, `"control-group"`
-- Priority levels: `"priority-high"`, `"batch-job"`
-
-## Troubleshooting
-
-If traces aren't displaying or connecting as expected:
-
-- Verify OTEL SDK is initialized before Mastra (use `--import` flag or import at top of entry point)
-- Ensure the OtelBridge is added to your observability config
-- Check that your OTEL backend is running and accessible
-
-## Related
-
-- [Tracing Overview](https://mastra.ai/docs/observability/tracing/overview)
-- [OpenTelemetry Exporter](https://mastra.ai/docs/observability/tracing/exporters/otel) - For sending traces to OTEL backends
-- [OtelBridge Reference](https://mastra.ai/reference/observability/tracing/bridges/otel) - API documentation

package/dist/docs/references/docs-observability-tracing-exporters-arize.md

@@ -1,272 +0,0 @@
-# Arize exporter
-
-[Arize](https://arize.com/) provides observability platforms for AI applications through [Phoenix](https://phoenix.arize.com/) (open-source) and [Arize AX](https://arize.com/generative-ai/) (enterprise). The Arize exporter sends traces using OpenTelemetry and [OpenInference](https://github.com/Arize-ai/openinference/tree/main/spec) semantic conventions, compatible with any OpenTelemetry platform that supports OpenInference.
-
-## Installation
-
-**npm**:
-
-```bash
-npm install @mastra/arize@latest
-```
-
-**pnpm**:
-
-```bash
-pnpm add @mastra/arize@latest
-```
-
-**Yarn**:
-
-```bash
-yarn add @mastra/arize@latest
-```
-
-**Bun**:
-
-```bash
-bun add @mastra/arize@latest
-```
-
-## Configuration
-
-### Phoenix Setup
-
-Phoenix is an open-source observability platform that can be self-hosted or used via Phoenix Cloud.
-
-#### Prerequisites
-
-1. **Phoenix Instance**: Deploy using Docker or sign up at [Phoenix Cloud](https://app.phoenix.arize.com/login)
-2. **Endpoint**: Your Phoenix endpoint URL (ends in `/v1/traces`)
-3. **API Key**: Optional for unauthenticated instances, required for Phoenix Cloud
-4. **Environment Variables**: Set your configuration
-
-```bash
-# Required
-PHOENIX_ENDPOINT=http://localhost:6006/v1/traces  # Or your Phoenix Cloud URL
-
-# Optional
-PHOENIX_API_KEY=your-api-key  # For authenticated Phoenix instances
-PHOENIX_PROJECT_NAME=mastra-service  # Defaults to 'mastra-service'
-```
-
-#### Zero-Config Setup
-
-With environment variables set, use the exporter with no configuration:
-
-```typescript
-import { Mastra } from '@mastra/core'
-import { Observability } from '@mastra/observability'
-import { ArizeExporter } from '@mastra/arize'
-
-export const mastra = new Mastra({
-  observability: new Observability({
-    configs: {
-      arize: {
-        serviceName: 'mastra-service',
-        exporters: [new ArizeExporter()],
-      },
-    },
-  }),
-})
-```
-
-#### Explicit Configuration
-
-You can also pass credentials directly (takes precedence over environment variables):
-
-```typescript
-import { Mastra } from '@mastra/core'
-import { Observability } from '@mastra/observability'
-import { ArizeExporter } from '@mastra/arize'
-
-export const mastra = new Mastra({
-  observability: new Observability({
-    configs: {
-      arize: {
-        serviceName: process.env.PHOENIX_PROJECT_NAME || 'mastra-service',
-        exporters: [
-          new ArizeExporter({
-            endpoint: process.env.PHOENIX_ENDPOINT!,
-            apiKey: process.env.PHOENIX_API_KEY,
-            projectName: process.env.PHOENIX_PROJECT_NAME,
-          }),
-        ],
-      },
-    },
-  }),
-})
-```
-
-> **Quickstart with Docker:** Test locally with an in-memory Phoenix instance:
->
-> ```bash
-> docker run --pull=always -d --name arize-phoenix -p 6006:6006 \
->   -e PHOENIX_SQL_DATABASE_URL="sqlite:///:memory:" \
->   arizephoenix/phoenix:latest
-> ```
->
-> Set `PHOENIX_ENDPOINT=http://localhost:6006/v1/traces` and run your Mastra agent to see traces at [localhost:6006](http://localhost:6006).
-
-### Arize AX Setup
-
-Arize AX is an enterprise observability platform with advanced features for production AI systems.
-
-#### Prerequisites
-
-1. **Arize AX Account**: Sign up at [app.arize.com](https://app.arize.com/)
-2. **Space ID**: Your organization's space identifier
-3. **API Key**: Generate in Arize AX settings
-4. **Environment Variables**: Set your credentials
-
-```bash
-# Required
-ARIZE_SPACE_ID=your-space-id
-ARIZE_API_KEY=your-api-key
-
-# Optional
-ARIZE_PROJECT_NAME=mastra-service
-```
-
-#### Zero-Config Setup
-
-With environment variables set, use the exporter with no configuration:
-
-```typescript
-import { Mastra } from '@mastra/core'
-import { Observability } from '@mastra/observability'
-import { ArizeExporter } from '@mastra/arize'
-
-export const mastra = new Mastra({
-  observability: new Observability({
-    configs: {
-      arize: {
-        serviceName: 'mastra-service',
-        exporters: [new ArizeExporter()],
-      },
-    },
-  }),
-})
-```
-
-#### Explicit Configuration
-
-You can also pass credentials directly (takes precedence over environment variables):
-
-```typescript
-import { Mastra } from '@mastra/core'
-import { Observability } from '@mastra/observability'
-import { ArizeExporter } from '@mastra/arize'
-
-export const mastra = new Mastra({
-  observability: new Observability({
-    configs: {
-      arize: {
-        serviceName: process.env.ARIZE_PROJECT_NAME || 'mastra-service',
-        exporters: [
-          new ArizeExporter({
-            apiKey: process.env.ARIZE_API_KEY!,
-            spaceId: process.env.ARIZE_SPACE_ID!,
-            projectName: process.env.ARIZE_PROJECT_NAME,
-          }),
-        ],
-      },
-    },
-  }),
-})
-```
-
-## Configuration options
-
-The Arize exporter supports advanced configuration for fine-tuning OpenTelemetry behavior:
-
-### Complete Configuration
-
-```typescript
-new ArizeExporter({
-  // Phoenix Configuration
-  endpoint: 'https://your-collector.example.com/v1/traces', // Required for Phoenix
-
-  // Arize AX Configuration
-  spaceId: 'your-space-id', // Required for Arize AX
-
-  // Shared Configuration
-  apiKey: 'your-api-key', // Required for authenticated endpoints
-  projectName: 'mastra-service', // Optional project name
-
-  // Optional OTLP settings
-  headers: {
-    'x-custom-header': 'value', // Additional headers for OTLP requests
-  },
-
-  // Debug and performance tuning
-  logLevel: 'debug', // Logging: debug | info | warn | error
-  batchSize: 512, // Batch size before exporting spans
-  timeout: 30000, // Timeout in ms before exporting spans
-
-  // Custom resource attributes
-  resourceAttributes: {
-    'deployment.environment': process.env.NODE_ENV,
-    'service.version': process.env.APP_VERSION,
-  },
-})
-```
-
-### Batch Processing Options
-
-Control how traces are batched and exported:
-
-```typescript
-new ArizeExporter({
-  endpoint: process.env.PHOENIX_ENDPOINT!,
-  apiKey: process.env.PHOENIX_API_KEY,
-
-  // Batch processing configuration
-  batchSize: 512, // Number of spans to batch (default: 512)
-  timeout: 30000, // Max time in ms to wait before export (default: 30000)
-})
-```
-
-### Resource Attributes
-
-Add custom attributes to all exported spans:
-
-```typescript
-new ArizeExporter({
-  endpoint: process.env.PHOENIX_ENDPOINT!,
-  resourceAttributes: {
-    'deployment.environment': process.env.NODE_ENV,
-    'service.namespace': 'production',
-    'service.instance.id': process.env.HOSTNAME,
-    'custom.attribute': 'value',
-  },
-})
-```
-
-### Custom metadata
-
-Non-reserved span attributes are serialized into the OpenInference `metadata` payload and surface in Arize/Phoenix. You can add them via `tracingOptions.metadata`:
-
-```ts
-await agent.generate(input, {
-  tracingOptions: {
-    metadata: {
-      companyId: 'acme-co',
-      tier: 'enterprise',
-    },
-  },
-})
-```
-
-Reserved fields such as `input`, `output`, `sessionId`, thread/user IDs, and OpenInference IDs are excluded automatically.
-
-## OpenInference semantic conventions
-
-This exporter implements the [OpenInference Semantic Conventions](https://github.com/Arize-ai/openinference/tree/main/spec) for generative AI applications, providing standardized trace structure across different observability platforms.
-
-## Related
-
-- [Tracing Overview](https://mastra.ai/docs/observability/tracing/overview)
-- [Phoenix Documentation](https://docs.arize.com/phoenix)
-- [Arize AX Documentation](https://docs.arize.com/)
-- [OpenInference Specification](https://github.com/Arize-ai/openinference/tree/main/spec)