praisonai-ts CLI manages the observability adapters. Only Langfuse and LangSmith deliver traces to a vendor backend; the other 12 external adapters record in memory only, and the CLI marks them [no delivery - in-memory only].
Quick Start
1
Simple Usage
2
With Configuration
Command Overview
List Observability Tools
❌ and the [no delivery - in-memory only] marker. The delivering adapters (langfuse, langsmith) show ⚠️ until their key is set, then ✅. langsmith becomes ✅ once LANGSMITH_API_KEY is set.
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:Observability Test
Test a tool with a real trace:success: true but delivered: false \u2014 the trace was recorded locally and never left the process.
success: true and delivered: true — the trace reached LangSmith.
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. langsmith is no longer in this list — it delivers once LANGSMITH_API_KEY is set.
Missing API Key
Tool Not Available
Test Failures
SDK Usage
For programmatic observability:Related
Observability SDK
Code-based observability usage
Telemetry
Performance metrics

