Observability for Portkey with Opik
Portkey is an enterprise-grade AI gateway that provides a unified interface to access 200+ LLMs with advanced features like smart routing, automatic fallbacks, load balancing, and comprehensive observability.
Gateway Overview
Portkey provides enterprise-grade features for managing LLM API access, including:
- 250+ AI Models: Single consistent API to connect with models from OpenAI, Anthropic, Google, Azure, AWS, and more
- Multi-Modal Support: Language, vision, audio, and image models
- Advanced Routing: Fallbacks, load balancing, conditional routing based on metadata, and provider weights
- Smart Caching: Simple and semantic caching to reduce latency and cost
- Security & Governance: Guardrails, secure key management (virtual keys), role-based access control
- Compliance: SOC2, HIPAA, GDPR compliant with data privacy controls
- Observability: Request/response logging, latency tracking, cost metrics, error rates, and throughput monitoring
Account Setup
Comet provides a hosted version of the Opik platform. Simply create an account and grab your API Key.
You can also run the Opik platform locally, see the installation guide for more information.
Getting Started
Installation
First, ensure you have opik, openai, and portkey-ai packages installed:
Configuring Opik
Configure the Opik Python SDK for your deployment type. See the Python SDK Configuration guide for detailed instructions on:
- CLI configuration:
opik configure - Code configuration:
opik.configure() - Self-hosted vs Cloud vs Enterprise setup
- Configuration files and environment variables
Configuring Portkey
You’ll need a Portkey API key and virtual keys for your LLM providers. You can get these from the Portkey dashboard.
Set your API keys as environment variables:
Or set them programmatically:
Logging LLM Calls
Since Portkey provides an OpenAI-compatible API, we can use the Opik OpenAI SDK wrapper to automatically log Portkey calls as generations in Opik.
Simple LLM Call
Advanced Usage
Using with the @track decorator
If you have multiple steps in your LLM pipeline, you can use the @track decorator to log the traces for each step. If Portkey is called within one of these steps, the LLM call will be associated with that corresponding step:
The trace will show nested LLM calls with hierarchical spans.
Further Improvements
If you have suggestions for improving the Portkey integration, please let us know by opening an issue on GitHub.