Spans

​

Core Span Types

​

Span Hierarchy

SESSION
  ├── AGENT
  │     ├── OPERATION/TASK
  │     │     ├── LLM
  │     │     └── TOOL
  │     └── WORKFLOW
  │           └── OPERATION/TASK
  └── LLM (unattributed to a specific agent)

​

Span Attributes

• ID: A unique identifier
• Name: A descriptive name
• Kind: The type of span (SESSION, AGENT, etc.)
• Start Time: When the span began
• End Time: When the span completed
• Status: Success or error status
• Attributes: Key-value pairs with additional metadata

​

LLM Spans

• Model: The specific model used (e.g., “gpt-4”, “claude-3-opus”)
• Provider: The LLM provider (e.g., “OpenAI”, “Anthropic”)
• Prompt Tokens: Number of tokens in the input
• Completion Tokens: Number of tokens in the output
• Cost: The estimated cost of the interaction
• Messages: The prompt and completion content

​

Tool Spans

• Tool Name: The name of the tool used
• Input: The data provided to the tool
• Output: The result returned by the tool
• Duration: How long the tool operation took

​

Operation/Task Spans

• Operation Type: The kind of operation performed
• Parameters: Input parameters to the operation
• Result: The output of the operation
• Duration: How long the operation took

​

Creating Spans

​

Using Decorators

from agentops.sdk.decorators import agent, operation, session, workflow, task

@session
def my_workflow():
    agent_instance = MyAgent()
    return agent_instance.perform_task()

@agent
class MyAgent:
    @operation
    def perform_task(self):
        # Perform the task
        return result

​

Automatic Instrumentation

import agentops
from openai import OpenAI

# Initialize AgentOps
agentops.init(api_key="YOUR_API_KEY")

# Initialize the OpenAI client
client = OpenAI()

# This LLM call will be automatically tracked
response = client.chat.completions.create(
    model="gpt-4",
    messages=[{"role": "user", "content": "Hello!"}]
)

​

Viewing Spans in the Dashboard

1. Timeline View: Shows the sequence and duration of spans
2. Tree View: Displays the hierarchical relationship between spans
3. Details Panel: Provides in-depth information about each span
4. Analytics: Aggregates statistics across spans

​

Best Practices

• Use descriptive names for spans to make them easily identifiable
• Create a logical hierarchy with sessions, agents, and operations
• Record relevant parameters and results for better debugging
• Use consistent naming conventions for span types
• Track costs and token usage to monitor resource consumption