Observability for Mistral AI (Python) with Opik
Observability for Mistral AI (Python) with Opik
Mistral AI provides cutting-edge large language models with excellent performance for text generation, reasoning, and specialized tasks like code generation.
This guide explains how to integrate Opik with the Mistral AI Python SDK. By using the track_mistral method provided by Opik, you can easily track and evaluate your Mistral API calls within your Opik projects as Opik will automatically log the input prompt, model used, token usage, and response generated.
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 both opik and mistralai packages installed. This integration targets the Mistral Python SDK v1 (from mistralai import Mistral), version 1.3.0 or newer:
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 Mistral AI
You’ll need to set your Mistral AI API key. You can find or create your Mistral API Key in the console:
Logging LLM calls
In order to log the LLM calls to Opik, you will need to wrap the Mistral client with track_mistral. When making calls with that wrapped client, all calls will be logged to Opik:
track_mistral also wraps the async and streaming methods — chat.complete_async, chat.stream, and chat.stream_async — so those calls are logged the same way, with streamed responses aggregated into a single span.
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 Mistral is called within one of these steps, the LLM call will be associated with that corresponding step:
The trace can now be viewed in the UI with hierarchical spans showing the relationship between different steps.
Streaming
Streamed responses are tracked as well — the chunks are aggregated into a single span with the full output and token usage:
Structured output
chat.parse() (and its async / streaming variants) is tracked too. It delegates
to complete()/stream() internally, so the call is logged as a single
chat_completion_create / chat_completion_stream span with the structured
JSON in the output:
Setting the provider name
By default the provider recorded on each LLM span is mistral, which Opik recognizes for cost tracking. You can override it by passing provider to track_mistral:
Cost Tracking
The track_mistral integration automatically logs token usage and estimated cost for each traced LLM call, based on the model and provider.
Cost information is automatically captured and displayed in the Opik UI, including:
- Cost per trace
- Total cost aggregated at the project level
Supported Methods
track_mistral logs calls to the following methods of the Mistral client:
chat.complete()andchat.complete_async()chat.stream()andchat.stream_async()chat.parse()andchat.parse_async()(structured output)chat.parse_stream()andchat.parse_stream_async()
Using Mistral AI via LiteLLM
If you prefer to route Mistral calls through LiteLLM — for example to use the same code across multiple providers — you can use the LiteLLM integration instead of track_mistral.
To track Mistral calls made through LiteLLM, create the OpikLogger callback and add it to LiteLLM:
If you are using LiteLLM within a function tracked with the @track decorator, pass the current_span_data as metadata to the litellm.completion call: