Skip to content

Observability providers enable monitoring, tracing, and logging of agent operations. This helps you understand agent behavior, track performance, and debug issues in production.

Overview

LLMling-Agent integrates with leading observability platforms:

  • Logfire: Pydantic's observability platform with native support for structured logging
  • Langsmith: LangChain's tracing and evaluation platform
  • AgentOps: Specialized platform for agent monitoring and analytics
  • Arize Phoenix: Open-source observability for LLM applications
  • Custom: Integrate your own observability solution

These integrations provide automatic instrumentation of agent operations, capturing traces, spans, and metrics without code changes.

Configuration Reference

LogfireObservabilityConfig

Configuration for Logfire endpoint.

LogfireObservabilityConfig (YAML)
1
2
3
4
5
6
7
- type: logfire
  token: null  # Logfire token.
  region: us  # Logfire region.
  enabled: true  # Provider enabled state.
  service_name: null
  environment: null
  protocol: http/protobuf

LangsmithObservabilityConfig

Configuration for Langsmith endpoint.

LangsmithObservabilityConfig (YAML)
1
2
3
4
5
6
7
- type: langsmith
  api_key: null  # Langsmith API key.
  project_name: null
  enabled: true  # Provider enabled state.
  service_name: null
  environment: null
  protocol: http/protobuf

AgentOpsObservabilityConfig

Configuration for AgentOps endpoint.

AgentOpsObservabilityConfig (YAML)
1
2
3
4
5
6
- type: agentops
  api_key: null  # AgentOps API key.
  enabled: true  # Provider enabled state.
  service_name: null
  environment: null
  protocol: http/protobuf

ArizePhoenixObservabilityConfig

Configuration for Arize Phoenix endpoint.

ArizePhoenixObservabilityConfig (YAML)
1
2
3
4
5
6
7
8
- type: arize
  api_key: null  # Arize API key.
  space_key: null  # Arize space key.
  model_id: null  # Arize model ID.
  enabled: true  # Provider enabled state.
  service_name: null
  environment: null
  protocol: http/protobuf

CustomObservabilityConfig

Configuration for custom OTEL endpoint.

CustomObservabilityConfig (YAML)
1
2
3
4
5
6
7
- type: custom
  endpoint: https://otel.example.com  # Custom OTEL endpoint URL.
  headers: {}  # Custom headers for the OTEL endpoint.
  enabled: true  # Provider enabled state.
  service_name: null
  environment: null
  protocol: http/protobuf

Key Features

  • Automatic tracing: All agent operations are automatically traced
  • Structured logging: Rich context and metadata for every operation
  • Performance metrics: Token usage, latency, and cost tracking
  • Error tracking: Detailed error capture with stack traces and context
  • Multi-provider support: Use multiple observability platforms simultaneously

Use Cases

  • Development: Debug agent behavior and optimize prompts
  • Production monitoring: Track performance and reliability metrics
  • Cost optimization: Analyze token usage and identify expensive operations
  • Quality assurance: Evaluate agent responses and identify issues
  • Compliance: Maintain audit logs of agent interactions

Configuration Notes

  • Providers can be configured at the manifest level for global observability
  • API keys should be stored in environment variables for security
  • Multiple providers can be active simultaneously
  • Each provider captures different metrics and views of agent behavior
  • Some providers offer additional features like prompt optimization and A/B testing