Follow the full chain
See parent/child spans across retrieval, tools, model calls, and your application.
Trace every model call. Follow every agent step. Understand token use, latency, and failures before your users find them.
Follow a request from your application through every tool call and model response. See the trace, the timing, and the token use in one place.
Compare reliability and performance against clear targets. Turn live traces into scorecards for success rate, latency, and token budgets.
Save useful production examples into project-scoped trace sets. Review the outcome, model, token use, and timing without storing prompt or completion text.
Browse tracesAgents make systems harder to debug. ObservaAI brings each model call, tool, and error into a single trace so your team can investigate with context.
See parent/child spans across retrieval, tools, model calls, and your application.
Inspect status, timing, provider, model, and safe operational attributes for each step.
Connect token use and latency to the exact request and model that produced them.
Instrument with OpenTelemetry and keep your telemetry portable. Send OTLP/HTTP JSON to a project endpoint, then inspect the same trace across your app.
Create a projectProjects belong to your account. Ingestion uses project keys, dashboards stay scoped, and prompt/completion content is removed before storage by default.
Use OpenTelemetry conventions and keep your telemetry understandable. Instrument once and avoid locking your traces into an opaque format.
When an AI request goes wrong, you need the trace—not another guess.
ObservaAI connects the model call to the application path, token use, and outcome.
Clear answers about instrumentation, data, and the current preview.
Create a free account, make a project, and add an ingestion key. ObservaAI accepts OpenTelemetry trace exports at your project endpoint.
Explore requests, model and provider, input and output tokens, estimated cost, latency, errors, services, and full span timelines.
No. Prompt and completion content is removed before persistence by default. Operational span attributes and names may still contain sensitive values, so review what your instrumentation emits.
The current receiver supports OTLP over HTTP with JSON encoded Protobuf. OTLP binary Protobuf and gRPC are not available yet.
Projects are currently private to the account that created them. Team invitations and shared workspaces are planned for a later release.
Start with one project. Instrument your app. See what happens after every request.