Skip to main content
The praisonai-ts CLI manages the observability adapters. Only Langfuse delivers traces to a vendor backend; the other 13 external adapters record in memory only, and the CLI marks them [no delivery - in-memory only].
Behaviour change: observability test <tool> now returns success: false and status: "not_delivered" for the 13 non-delivering adapters (previously success: true). CI pipelines that pipe --json | jq .success will now get false for those tools. Only langfuse returns delivered, and console/memory return success: true with status: "recorded".

Quick Start

1

Simple Usage

2

With Configuration

Command Overview

List Observability Tools

Example Output: Non-delivering adapters show and the [no delivery - in-memory only] marker. Langfuse shows ⚠️ until its key is set (then ), because it is the one adapter that can deliver.
JSON Output: Each provider entry now includes a delivers: boolean field. delivers: true means traces reach the vendor backend; delivers: false means the adapter records in memory only.

Observability Doctor

Check environment setup for tools:
Example Output (delivering tool, langfuse):
Example Output (non-delivering tool, weave):
Example Output (all tools):

Observability Test

Test a tool with a real trace:
Example Output (built-in recorder, memory):
JSON Output (memory): success: true but delivered: false \u2014 the trace was recorded locally and never left the process.
Example Output (non-delivering tool, weave):
JSON Output (weave): success: false and status: "not_delivered". CI pipelines that checked .success will now correctly see false for these adapters.

Observability Info

Get feature information:

Options Matrix

Available Tools

Environment Variables

Troubleshooting

My tool shows [no delivery - in-memory only] — what does that mean?

That adapter has no vendor transport. It records spans to memory and sends nothing to the vendor \u2014 setting its env var does not change this. Use langfuse (with npm install langfuse) for real delivery, or console for local development.

Missing API Key

Tool Not Available

Test Failures

SDK Usage

For programmatic observability:

Observability SDK

Code-based observability usage

Telemetry

Performance metrics