@mastra/loggers 1.0.1 → 1.0.2-alpha.0

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # @mastra/loggers
 
+## 1.0.2-alpha.0
+
+### Patch Changes
+
+- dependencies updates: ([#13237](https://github.com/mastra-ai/mastra/pull/13237))
+  - Updated dependency [`pino-pretty@^13.1.3` ↗︎](https://www.npmjs.com/package/pino-pretty/v/13.1.3) (from `^13.0.0`, in `dependencies`)
+- Updated dependencies:
+  - @mastra/core@1.5.0-alpha.1
+
 ## 1.0.1
 
 ### Patch Changes

package/dist/docs/SKILL.md

@@ -1,34 +1,28 @@
 ---
-name: mastra-loggers-docs
-description: Documentation for @mastra/loggers. Includes links to type definitions and readable implementation code in dist/.
+name: mastra-loggers
+description: Documentation for @mastra/loggers. Use when working with @mastra/loggers APIs, configuration, or implementation.
+metadata:
+  package: "@mastra/loggers"
+  version: "1.0.2-alpha.0"
 ---
 
-# @mastra/loggers Documentation
+## When to use
 
-> **Version**: 1.0.1
-> **Package**: @mastra/loggers
+Use this skill whenever you are working with @mastra/loggers to obtain the domain-specific knowledge.
 
-## Quick Navigation
+## How to use
 
-Use SOURCE_MAP.json to find any export:
+Read the individual reference documents for detailed explanations and code examples.
 
-```bash
-cat docs/SOURCE_MAP.json
-```
+### Docs
 
-Each export maps to:
-- **types**: `.d.ts` file with JSDoc and API signatures
-- **implementation**: `.js` chunk file with readable source
-- **docs**: Conceptual documentation in `docs/`
+- [Logging](references/docs-observability-logging.md) - Learn how to use logging in Mastra to monitor execution, capture application behavior, and improve the accuracy of AI applications.
+- [Observability Overview](references/docs-observability-overview.md) - Monitor and debug applications with Mastra's Observability features.
 
-## Top Exports
+### Reference
 
+- [Reference: Mastra Class](references/reference-core-mastra-class.md) - Documentation for the `Mastra` class in Mastra, the core entry point for managing agents, workflows, MCP servers, and server endpoints.
+- [Reference: PinoLogger](references/reference-logging-pino-logger.md) - Documentation for PinoLogger, which provides methods to record events at various severity levels.
 
 
-See SOURCE_MAP.json for the complete list.
-
-## Available Topics
-
-- [Core](core/) - 1 file(s)
-- [Logging](logging/) - 1 file(s)
-- [Observability](observability/) - 2 file(s)
+Read [assets/SOURCE_MAP.json](assets/SOURCE_MAP.json) for source code references.

package/dist/docs/{SOURCE_MAP.json → assets/SOURCE_MAP.json}

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.1",
+  "version": "1.0.2-alpha.0",
   "package": "@mastra/loggers",
   "exports": {},
   "modules": {}

package/dist/docs/{observability/02-logging.md → references/docs-observability-logging.md}

@@ -1,5 +1,3 @@
-> Learn how to use logging in Mastra to monitor execution, capture application behavior, and improve the accuracy of AI applications.
-
 # Logging
 
 Mastra's logging system captures function execution, input data, and output responses in a structured format.
@@ -10,7 +8,7 @@ When deploying to Mastra Cloud, logs are shown on the [Logs](https://mastra.ai/d
 
 When [initializing a new Mastra project](https://mastra.ai/guides/getting-started/quickstart) using the CLI, `PinoLogger` is included by default.
 
-```typescript title="src/mastra/index.ts"
+```typescript
 import { Mastra } from "@mastra/core/mastra";
 import { PinoLogger } from "@mastra/loggers";
 
@@ -22,9 +20,7 @@ export const mastra = new Mastra({
 });
 ```
 
-> **Note:**
-
-Visit [PinoLogger](https://mastra.ai/reference/logging/pino-logger) for all available configuration options.
+> **Info:** Visit [PinoLogger](https://mastra.ai/reference/logging/pino-logger) for all available configuration options.
 
 ## Customizing logs
 
@@ -34,7 +30,7 @@ Mastra provides access to a logger instance via the `mastra.getLogger()` method,
 
 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 {6-7} title="src/mastra/workflows/test-workflow.ts"
+```typescript
 import { createWorkflow, createStep } from "@mastra/core/workflows";
 import { z } from "zod";
 
@@ -58,7 +54,7 @@ export const testWorkflow = createWorkflow({...})
 
 Similarly, tools have access to the logger instance via the `mastra` parameter. Use this to log tool specific activity during execution.
 
-```typescript {6-7} title="src/mastra/tools/test-tool.ts"
+```typescript
 import { createTool } from "@mastra/core/tools";
 import { z } from "zod";
 
@@ -80,7 +76,7 @@ Logger methods accept an optional second argument for additional data. This can
 
 In this example, the log message includes an object with a key of `agent` and a value of the `testAgent` instance.
 
-```typescript {9} title="src/mastra/workflows/test-workflow.ts"
+```typescript
 import { createWorkflow, createStep } from "@mastra/core/workflows";
 import { z } from "zod";
 
@@ -88,7 +84,7 @@ const step1 = createStep({
   execute: async ({ mastra }) => {
     const testAgent = mastra.getAgent("testAgent");
     const logger = mastra.getLogger();
-    
+
     logger.info("workflow info log", { agent: testAgent });
 
     return {

package/dist/docs/{observability/01-overview.md → references/docs-observability-overview.md}

@@ -1,5 +1,3 @@
-> Monitor and debug applications with Mastra
-
 # 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.
@@ -17,15 +15,15 @@ Specialized tracing for AI operations that captures:
 
 ## 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#storage-provider-support).
+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#production-recommendations) for details.
+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.
 
 ## Quick Start
 
 Configure Observability in your Mastra instance:
 
-```typescript title="src/mastra/index.ts"
+```typescript
 import { Mastra } from "@mastra/core";
 import { PinoLogger } from "@mastra/loggers";
 import { LibSQLStore } from "@mastra/libsql";
@@ -59,8 +57,7 @@ export const mastra = new Mastra({
 });
 ```
 
-> **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-deployer#observability) for a complete example.
+> **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.
 

package/dist/docs/references/reference-core-mastra-class.md

@@ -0,0 +1,66 @@
+# Mastra Class
+
+The `Mastra` class is the central orchestrator in any Mastra application, managing agents, workflows, storage, logging, observability, and more. Typically, you create a single instance of `Mastra` to coordinate your application.
+
+Think of `Mastra` as a top-level registry where you register agents, workflows, tools, and other components that need to be accessible throughout your application.
+
+## Usage example
+
+```typescript
+import { Mastra } from "@mastra/core";
+import { PinoLogger } from "@mastra/loggers";
+import { LibSQLStore } from "@mastra/libsql";
+import { weatherWorkflow } from "./workflows/weather-workflow";
+import { weatherAgent } from "./agents/weather-agent";
+
+export const mastra = new Mastra({
+  workflows: { weatherWorkflow },
+  agents: { weatherAgent },
+  storage: new LibSQLStore({
+    id: 'mastra-storage',
+    url: ":memory:",
+  }),
+  logger: new PinoLogger({
+    name: "Mastra",
+    level: "info",
+  }),
+});
+```
+
+## Constructor parameters
+
+Visit the [Configuration reference](https://mastra.ai/reference/configuration) for detailed documentation on all available configuration options.
+
+**agents?:** (`Record<string, Agent>`): Agent instances to register, keyed by name (Default: `{}`)
+
+**tools?:** (`Record<string, ToolApi>`): Custom tools to register. Structured as a key-value pair, with keys being the tool name and values being the tool function. (Default: `{}`)
+
+**storage?:** (`MastraCompositeStore`): Storage engine instance for persisting data
+
+**vectors?:** (`Record<string, MastraVector>`): Vector store instance, used for semantic search and vector-based tools (eg Pinecone, PgVector or Qdrant)
+
+**logger?:** (`Logger`): Logger instance created with new PinoLogger() (Default: `Console logger with INFO level`)
+
+**idGenerator?:** (`() => string`): Custom ID generator function. Used by agents, workflows, memory, and other components to generate unique identifiers.
+
+**workflows?:** (`Record<string, Workflow>`): Workflows to register. Structured as a key-value pair, with keys being the workflow name and values being the workflow instance. (Default: `{}`)
+
+**tts?:** (`Record<string, MastraVoice>`): Text-to-speech providers for voice synthesis
+
+**observability?:** (`ObservabilityEntrypoint`): Observability configuration for tracing and monitoring
+
+**deployer?:** (`MastraDeployer`): An instance of a MastraDeployer for managing deployments.
+
+**server?:** (`ServerConfig`): Server configuration including port, host, timeout, API routes, middleware, CORS settings, and build options for Swagger UI, API request logging, and OpenAPI docs.
+
+**mcpServers?:** (`Record<string, MCPServerBase>`): An object where keys are registry keys (used for getMCPServer()) and values are instances of MCPServer or classes extending MCPServerBase. Each MCPServer must have an id property. Servers can be retrieved by registry key using getMCPServer() or by their intrinsic id using getMCPServerById().
+
+**bundler?:** (`BundlerConfig`): Configuration for the asset bundler with options for externals, sourcemap, and transpilePackages.
+
+**scorers?:** (`Record<string, Scorer>`): Scorers for evaluating agent responses and workflow outputs (Default: `{}`)
+
+**processors?:** (`Record<string, Processor>`): Input/output processors for transforming agent inputs and outputs (Default: `{}`)
+
+**gateways?:** (`Record<string, MastraModelGateway>`): Custom model gateways to register for accessing AI models through alternative providers or private deployments. Structured as a key-value pair, with keys being the registry key (used for getGateway()) and values being gateway instances. (Default: `{}`)
+
+**memory?:** (`Record<string, MastraMemory>`): Memory instances to register. These can be referenced by stored agents and resolved at runtime. Structured as a key-value pair, with keys being the registry key and values being memory instances. (Default: `{}`)

package/dist/docs/{logging/01-reference.md → references/reference-logging-pino-logger.md}

@@ -1,21 +1,12 @@
-# Logging API Reference
-
-> API reference for logging - 1 entries
-
-
----
-
-## Reference: PinoLogger
-
-> Documentation for PinoLogger, which provides methods to record events at various severity levels.
+# PinoLogger
 
 A Logger instance is created using `new PinoLogger()` and provides methods to record events at various severity levels.
 
-When deploying to Mastra Cloud, logs are displayed on the [Logs](https://mastra.ai/docs/mastra-cloud/observability#logs) page. In self-hosted or custom environments, logs can be directed to files or external services depending on the configured transports.
+When deploying to Mastra Cloud, logs are displayed 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.
 
 ## Usage example
 
-```typescript title="src/mastra/index.ts"
+```typescript
 import { Mastra } from "@mastra/core";
 import { PinoLogger } from "@mastra/loggers";
 
@@ -29,11 +20,21 @@ export const mastra = new Mastra({
 
 ## Parameters
 
+**name:** (`string`): A label used to group and identify logs from this logger.
+
+**level:** (`"debug" | "info" | "warn" | "error"`): Sets the minimum log level. Messages below this level are ignored.
+
+**transports:** (`Record<string, LoggerTransport>`): A map of transport instances used to persist logs.
+
+**overrideDefaultTransports?:** (`boolean`): If true, disables the default console transport.
+
+**formatters?:** (`pino.LoggerOptions['formatters']`): Custom Pino formatters for log serialization.
+
 ## File transport (structured logs)
 
 Writes structured logs to a file using the `FileTransport`. The logger accepts a plain message as the first argument and structured metadata as the second argument. These are internally converted to a `BaseLogMessage` and persisted to the configured file path.
 
-```typescript title="src/mastra/loggers/file-transport.ts"
+```typescript
 import { FileTransport } from "@mastra/loggers/file";
 import { PinoLogger } from "@mastra/loggers/pino";
 
@@ -57,7 +58,7 @@ fileLogger.warn("Low disk space", {
 
 Streams structured logs to a remote Redis list using the `UpstashTransport`. The logger accepts a string message and a structured metadata object. This enables centralized logging for distributed environments, supporting filtering by `destinationPath`, `type`, and `runId`.
 
-```typescript title="src/mastra/loggers/upstash-transport.ts"
+```typescript
 import { UpstashTransport } from "@mastra/loggers/upstash";
 import { PinoLogger } from "@mastra/loggers/pino";
 
@@ -92,7 +93,7 @@ You can create custom transports using the `createCustomTransport` utility to in
 
 Creates a custom transport using `createCustomTransport` and integrates it with a third-party logging stream such as `pino-sentry-transport`. This allows forwarding logs to an external system like Sentry for advanced monitoring and observability.
 
-```typescript title="src/mastra/loggers/sentry-transport.ts"
+```typescript
 import { createCustomTransport } from "@mastra/core/loggers";
 import { PinoLogger } from "@mastra/loggers/pino";
 import pinoSentry from "pino-sentry-transport";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/loggers",
-  "version": "1.0.1",
+  "version": "1.0.2-alpha.0",
   "description": "",
   "type": "module",
   "files": [
@@ -66,7 +66,7 @@
   "license": "Apache-2.0",
   "dependencies": {
     "pino": "^10.1.0",
-    "pino-pretty": "^13.0.0"
+    "pino-pretty": "^13.1.3"
   },
   "devDependencies": {
     "@types/node": "22.19.7",
@@ -76,9 +76,9 @@
     "tsup": "^8.5.1",
     "typescript": "^5.9.3",
     "vitest": "4.0.16",
-    "@internal/lint": "0.0.56",
-    "@mastra/core": "1.1.0",
-    "@internal/types-builder": "0.0.31"
+    "@internal/types-builder": "0.0.34",
+    "@mastra/core": "1.5.0-alpha.1",
+    "@internal/lint": "0.0.59"
   },
   "peerDependencies": {
     "@mastra/core": ">=1.0.0-0 <2.0.0-0"
@@ -88,7 +88,6 @@
   },
   "scripts": {
     "build:lib": "tsup --silent --config tsup.config.ts",
-    "build:docs": "pnpx tsx ../../scripts/generate-package-docs.ts packages/loggers",
     "build:watch": "tsup --watch --silent --config tsup.config.ts",
     "test": "vitest run",
     "lint": "eslint ."

package/dist/docs/README.md

@@ -1,33 +0,0 @@
-# @mastra/loggers Documentation
-
-> Embedded documentation for coding agents
-
-## Quick Start
-
-```bash
-# Read the skill overview
-cat docs/SKILL.md
-
-# Get the source map
-cat docs/SOURCE_MAP.json
-
-# Read topic documentation
-cat docs/<topic>/01-overview.md
-```
-
-## Structure
-
-```
-docs/
-├── SKILL.md           # Entry point
-├── README.md          # This file
-├── SOURCE_MAP.json    # Export index
-├── core/ (1 files)
-├── logging/ (1 files)
-├── observability/ (2 files)
-```
-
-## Version
-
-Package: @mastra/loggers
-Version: 1.0.1

package/dist/docs/core/01-reference.md

@@ -1,41 +0,0 @@
-# Core API Reference
-
-> API reference for core - 1 entries
-
-
----
-
-## Reference: Mastra Class
-
-> Documentation for the `Mastra` class in Mastra, the core entry point for managing agents, workflows, MCP servers, and server endpoints.
-
-The `Mastra` class is the central orchestrator in any Mastra application, managing agents, workflows, storage, logging, observability, and more. Typically, you create a single instance of `Mastra` to coordinate your application.
-
-Think of `Mastra` as a top-level registry where you register agents, workflows, tools, and other components that need to be accessible throughout your application.
-
-## Usage example
-
-```typescript title="src/mastra/index.ts"
-import { Mastra } from "@mastra/core";
-import { PinoLogger } from "@mastra/loggers";
-import { LibSQLStore } from "@mastra/libsql";
-import { weatherWorkflow } from "./workflows/weather-workflow";
-import { weatherAgent } from "./agents/weather-agent";
-
-export const mastra = new Mastra({
-  workflows: { weatherWorkflow },
-  agents: { weatherAgent },
-  storage: new LibSQLStore({
-    id: 'mastra-storage',
-    url: ":memory:",
-  }),
-  logger: new PinoLogger({
-    name: "Mastra",
-    level: "info",
-  }),
-});
-```
-
-## Constructor parameters
-
-Visit the [Configuration reference](https://mastra.ai/reference/configuration) for detailed documentation on all available configuration options.