For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Copy to LLMGithubGo to App
DocumentationIntegrationsBuilding Self-Improving AgentsSelf-hosting OpikSDK & API reference
DocumentationIntegrationsBuilding Self-Improving AgentsSelf-hosting OpikSDK & API reference
  • Getting Started
    • Home
    • Quickstart
    • Upgrading to Opik 2.0
    • Ollie Agent
    • FAQ
    • Changelog
  • Observability
    • Overview
    • Getting started
    • Concepts
    • Debugging agents with Ollie and Opik Connect
  • Development
    • Overview
    • Agent playground
    • Prompt playground
  • Evaluation
    • Overview
    • Getting started
    • Concepts
  • Production
  • Administration
    • Overview
    • Roles and Permissions
  • Contributing
    • Contribution Overview
LogoLogo
Copy to LLMGithubGo to App
On this page
  • Adding observability to your code
  • Viewing your traces
  • Next steps
Observability

Getting started with Observability

Was this page helpful?
Previous

Tracing Core Concepts

Understanding the fundamental concepts behind Opik's tracing platform
Next
Built with

Opik makes it easy to add observability to your existing LLM application. The fastest way is to let your coding agent do it — install the Opik skill in Claude Code, Cursor, Codex, or any other coding agent and it will instrument your code for you. If you’d rather stay inside Opik, use Opik Connect to have Ollie set up tracing from the dashboard. You can also add tracing manually with the SDK.

Adding observability to your code

AI coding agent
Opik Connect
Manual integration

The fastest way to add observability is to install the Opik skill in your coding agent and let it instrument your code for you. The skill is compatible with Claude Code, Codex, Cursor, OpenCode and any other agent that supports skills.

1

Install the Opik skill

$npx skills add comet-ml/opik-skills
2

Run the integration

Ask your coding agent to instrument your code:

Instrument my agent with Opik using the /instrument command.

The agent will read your code, pick the right Opik integration, and add tracing.

Viewing your traces

After running your application, traces will appear in the Opik dashboard. Each trace captures the full execution path of a request, including all nested spans, inputs, outputs, and timing information.

Opik traces page showing trace details with span tree, outputs, and feedback scores

You can use Ollie to analyze your traces, identify issues in your agent’s behavior, and get actionable suggestions for improvement.

Next steps

  • Concepts — Learn about traces, spans, threads, and feedback scores
  • Log traces — In-depth guide on customizing what gets logged
  • Cost tracking — Monitor token usage and spending