LangGraph SDK Quick Start

Instrument your LangGraph or LangChain application with the Fiddler LangGraph SDK in under 10 minutes.

What You'll Learn

By completing this quick start, you'll:

• Set up monitoring for a LangGraph or LangChain application

• Send your first traces to Fiddler

• Verify data collection in the Fiddler dashboard

• Understand basic conversation tracking

1

Set Up Your Fiddler Application

1. Create your application in Fiddler

   Log in to your Fiddler instance and navigate to GenAI Apps, then select Add Application.

   
2. Copy your Application ID

   After creating your application, copy the Application ID from the application details page. This must be a valid UUID4 format (for example, 550e8400-e29b-41d4-a716-446655440000). You'll need this for Step 3.

   
3. Get Your Access Token

   Go to Settings > Credentials and copy your access token. You'll need this for Step 3. Refer to the documentation for more details.

   

2

Install the Fiddler LangGraph SDK

Standard Installation

For the stable release, install the Fiddler LangGraph SDK using pip:

Copy

pip install fiddler-langgraph

3

Instrument Your Application

Add the Fiddler LangGraph SDK to your LangGraph or LangChain application with just a few lines of code:

Copy

from fiddler_langgraph import FiddlerClient
from fiddler_langgraph.tracing.instrumentation import LangGraphInstrumentor

# Initialize the FiddlerClient. Replace the placeholder values below.
fdl_client = FiddlerClient(
    api_key='<FIDDLER_API_KEY>',  # Your API key
    application_id='<FIDDLER_APPLICATION_ID>',  # Application ID copied from UI in Step 1
    url='<FIDDLER_URL>')  # https://your-instance.fiddler.ai
)

# Instrument your application
instrumentor = LangGraphInstrumentor(fdl_client)
instrumentor.instrument()

# Invoke your agent here
# You MUST instrument your application BEFORE invoking

# Your existing LangGraph code runs normally
# Traces will automatically be sent to Fiddler

Add Context and Conversation Tracking

The main goal of context setting is to enrich the telemetry data sent to Fiddler:

Copy

from fiddler_langgraph.tracing.instrumentation import set_llm_context, set_conversation_id
import uuid

# Set descriptive context for LLM processing
set_llm_context(model, 'Customer support conversation')

# Set conversation ID for tracking multi-turn conversations
conversation_id = str(uuid.uuid4())
set_conversation_id(conversation_id)

For AI engineers: The conversation tracking feature supports multi-turn agent interactions and helps trace decision flows across agent sessions.

4

Run a Complete Example

This example requires an OpenAI API key. You can create or find your key on the API keys page of your OpenAI account.

Here's a complete working example to verify your setup:

Copy

import os
import uuid
from fiddler_langgraph import FiddlerClient
from fiddler_langgraph.tracing.instrumentation import (
    LangGraphInstrumentor,
    set_llm_context,
    set_conversation_id
)
from langchain_openai import ChatOpenAI
from langgraph.prebuilt import create_react_agent

# Initialize the FiddlerClient. Replace the placeholder values below.
fdl_client = FiddlerClient(
    api_key='<FIDDLER_API_KEY>',  # Your API key
    application_id='<FIDDLER_APPLICATION_ID>',  # Application ID copied from UI in Step 1
    url='<FIDDLER_URL>')  # https://your-instance.fiddler.ai
)

# Instrument the application
instrumentor = LangGraphInstrumentor(fdl_client)
instrumentor.instrument()

# Create your agent
model = ChatOpenAI(model="gpt-4o-mini")
agent = create_react_agent(model, tools=[])

# Set descriptive context for this interaction
set_llm_context(model, "Quick start example conversation")

# Generate and set a conversation ID
conversation_id = str(uuid.uuid4())
set_conversation_id(conversation_id)

# Run your agent - automatically instrumented
result = agent.invoke({
    "messages": [{"role": "user", "content": "Hello! How are you?"}]
})

print("Response received:", result)
print("Conversation ID:", conversation_id)

5

Verify Monitoring is Working

1. Run your application using the example above or your own instrumented code

2. Check the Fiddler dashboard: Navigate to GenAI Apps in your Fiddler instance

3. Confirm active status: If Fiddler successfully receives telemetry, your application will show as Active

   

Success Criteria

You should see:

• Application status changed to Active in the Fiddler dashboard

• Trace data appearing within 1-2 minutes of running your example

• Context labels match what you set in your code

• Conversation ID visible in the trace details

Grant Team Access (optional)

Provide access to other users by assigning teams and users to the project that contains your applications. Managing permissions through Teams is recommended as a best practice. For more access control details, refer to the Teams and Users Guide and the Role-based Access Guide.

1. Open the Settings page and select the Access tab

2. For both Users and Teams, select the "Edit" option to the right of the name

3. Add appropriate team members with the required permission levels

Troubleshooting

Common Issues and Solutions

Problem: Application shows as "Inactive"

• Ensure your application executes instrumented code

• Verify that your Fiddler access token and application ID are correct

• Check network connectivity to your Fiddler instance

• Enable console tracer to see if traces are being generated locally:

Problem: Import errors

• Verify Python version is 3.10 or higher

• Ensure LangGraph is installed and compatible (versions >= 0.3.28 and < 0.7.0)

• Try reinstalling the SDK: pip uninstall fiddler-langgraph && pip install fiddler-langgraph

Problem: Invalid Application ID

• Ensure your application ID is in proper UUID4 format

• Copy the ID directly from the Fiddler dashboard

• Verify the application exists in your Fiddler instance

Problem: Network connectivity issues

• Test connectivity: curl -I https://your-instance.fiddler.ai

• Check firewall settings for HTTPS traffic on port 443

• Verify your Fiddler instance URL is correct

Problem: Agent appears as "UNKNOWN_AGENT" in Fiddler UI

• For LangChain applications, ensure you're setting the agent name in the config parameter

  • Example: config={"configurable": {"agent_name": "your_agent_name"}}

Next Steps

Now that your application is instrumented:

1. Explore the data: Check your Fiddler dashboard for traces, metrics, and performance insights

2. Learn advanced features: See our Advanced Usage Guide for complex multi-agent scenarios

3. Review the SDK reference: Check the Fiddler LangGraph SDK Reference for complete documentation

4. Optimize for production: Review configuration options for high-volume applications

Configuration Options

Basic Configuration

Advanced Configuration

Customize Limits for High-Volume Applications

Set limits for your events, spans, and associated attributes. This is helpful for tuning reporting data to manageable numbers for highly attributed and/or high-volume applications.

Sampling Traffic

Set a specific sampling percentage for incoming data.

Environment Variables for Batch Processing

Adjust the following environment variables that the FiddlerClient will use when processing the OpenTelemetry traffic.

Compression Options

The SDK supports data compression to help reduce the overall data volume transmitted over the network. This can help improve network latency.

Environment Variables Reference

Configure OpenTelemetry batch processor behavior through environment variables:

Example: Tuning for high-volume applications

LangChain Application Support

The SDK supports both LangGraph and LangChain applications. While agent names are automatically extracted from LangGraph applications by the SDK, LangChain applications need the agent name to be explicitly set using the configuration parameter:

Troubleshooting

Common Installation Issues

Problem: ModuleNotFoundError: No module named 'fiddler_langgraph'

• Solution: Ensure you've installed the correct package: pip install fiddler*langgraph

Problem: Version conflicts with existing packages

• Solution: Use a virtual environment or update conflicting packages

Common Configuration Issues

Problem: ValueError: application_id must be a valid UUID4

• Solution: Ensure your Application ID is a valid UUID4 format (e.g., 550e8400-e29b-41d4-a716-446655440000)

Example:

Problem: ValueError: URL must have a valid scheme and netloc

• Solution: Ensure your URL includes the protocol (e.g., https://your-instance.fiddler.ai)

Problem: Connection errors or timeouts

• Solution: Check your network connectivity and Fiddler instance URL

Example: Handling connection failures gracefully

Problem: Debugging trace generation

• Solution: Enable console tracer for local debugging:

Problem: ImportError: cannot import name 'LangGraphInstrumentor'

• Solution: Ensure you have the correct import path:

Verification Issues

Problem: Application not showing as "Active" in Fiddler

• Solution: Check the following:

  1. Ensure your application executes instrumented code

  2. Verify that your Fiddler access token and application ID are correct

  3. Check network connectivity to your Fiddler instance

  4. Enable console tracer to see if traces are being generated locally

Next Steps

Now that your application is instrumented:

1. Explore the data: Check your Fiddler dashboard for traces and metrics

2. Learn advanced features: See our Tutorial: Advanced Guide for more complex scenarios

3. Review the SDK: Check the Fiddler LangGraph SDK Reference for complete documentation

4. Optimize for production: Review configuration options for high-volume applications