pip install splunk-ao
Set the following environment variables:
SPLUNK_AO_API_KEY: Your Agent Observability API keySPLUNK_AO_PROJECT: (Optional) Project nameSPLUNK_AO_LOG_STREAM: (Optional) Log stream nameSPLUNK_AO_LOGGING_DISABLED: (Optional) Disable collecting and sending logs to Agent Observability.
Note: if you would like to point to an environment other than app.galileo.ai, you'll need to set the SPLUNK_AO_CONSOLE_URL environment variable.
import os
from splunk_ao import splunk_ao_context
from splunk_ao.openai import openai
# If you've set your SPLUNK_AO_PROJECT and SPLUNK_AO_LOG_STREAM env vars, you can skip this step
splunk_ao_context.init(project="your-project-name", log_stream="your-log-stream-name")
# Initialize the Agent Observability wrapped OpenAI client
client = openai.OpenAI(api_key=os.environ.get("OPENAI_API_KEY"))
def call_openai():
chat_completion = client.chat.completions.create(
messages=[{"role": "user", "content": "Say this is a test"}], model="gpt-4o"
)
return chat_completion.choices[0].message.content
# This will create a single span trace with the OpenAI call
call_openai()
# This will upload the trace to Agent Observability
splunk_ao_context.flush()You can also use the @log decorator to log spans. Here's how to create a workflow span with two nested LLM spans:
from splunk_ao import log
@log
def make_nested_call():
call_openai()
call_openai()
# If you've set your SPLUNK_AO_PROJECT and SPLUNK_AO_LOG_STREAM env vars, you can skip this step
splunk_ao_context.init(project="your-project-name", log_stream="your-log-stream-name")
# This will create a trace with a workflow span and two nested LLM spans containing the OpenAI calls
make_nested_call()Here's how to create a retriever span using the decorator:
from splunk_ao import log
@log(span_type="retriever")
def retrieve_documents(query: str):
return ["doc1", "doc2"]
# This will create a trace with a retriever span containing the documents in the output
retrieve_documents(query="history")Here's how to create a tool span using the decorator:
from splunk_ao import log
@log(span_type="tool")
def tool_call(input: str = "tool call input"):
return "tool call output"
# This will create a trace with a tool span containing the tool call output
tool_call(input="question")
# This will upload the trace to Agent Observability
splunk_ao_context.flush()In some cases, you may want to wrap a block of code to start and flush a trace automatically. You can do this using the splunk_ao_context context manager:
from splunk_ao import splunk_ao_context
# This will log a block of code to the project and log stream specified in the context manager
with splunk_ao_context():
content = make_nested_call()
print(content)splunk_ao_context also allows you specify a separate project and log stream for the trace:
from splunk_ao import splunk_ao_context
# This will log to the project and log stream specified in the context manager
with splunk_ao_context(project="gen-ai-project", log_stream="test2"):
content = make_nested_call()
print(content)You can also use the SplunkAOLogger for manual logging scenarios:
from splunk_ao.logger import SplunkAOLogger
# This will log to the project and log stream specified in the logger constructor
logger = SplunkAOLogger(project="gen-ai-project", log_stream="test3")
trace = logger.start_trace("Say this is a test")
logger.add_llm_span(
input="Say this is a test",
output="Hello, this is a test",
model="gpt-4o",
num_input_tokens=10,
num_output_tokens=3,
total_tokens=13,
duration_ns=1000,
)
logger.conclude(output="Hello, this is a test", duration_ns=1000)
logger.flush() # This will upload the trace to Agent ObservabilityIf you use Agent Control hosted by Splunk, initialize Agent Control with the current Agent Observability log stream as the runtime target:
import agent_control
from splunk_ao import splunk_ao_context, get_agent_control_target
splunk_ao_context.init(project="my-project", log_stream="prod")
target = get_agent_control_target()
agent_control.init(
agent_name="my-agent",
target_type=target.target_type,
target_id=target.target_id,
# server_url, api_key, and api_key_header can be passed here or configured
# through the Agent Control SDK environment variables.
)The helper resolves an explicit log stream ID, SPLUNK_AO_LOG_STREAM_ID, or an
already-initialized splunk_ao_context logger. It does not import the Agent
Control SDK or resolve log stream names over the network. If you use a direct
Agent Control client instead of agent_control.init(...), pass
target.target_type and target.target_id on each evaluation call.
splunk_ao.agent_control resolves targets for Agent Control calls.
splunk_ao.handlers.agent_control bridges Agent Control telemetry into Agent
Observability logging.
OpenAI streaming example:
import os
from splunk_ao.openai import openai
client = openai.OpenAI(api_key=os.environ.get("OPENAI_API_KEY"))
stream = client.chat.completions.create(
messages=[{"role": "user", "content": "Say this is a test"}], model="gpt-4o", stream=True,
)
# This will create a single span trace with the OpenAI call
for chunk in stream:
print(chunk.choices[0].delta.content or "", end="")In some cases (like long-running processes), it may be necessary to explicitly flush the trace to upload it to Agent Observability:
import os
from splunk_ao import splunk_ao_context
from splunk_ao.openai import openai
splunk_ao_context.init(project="your-project-name", log_stream="your-log-stream-name")
# Initialize the Agent Observability wrapped OpenAI client
client = openai.OpenAI(api_key=os.environ.get("OPENAI_API_KEY"))
def call_openai():
chat_completion = client.chat.completions.create(
messages=[{"role": "user", "content": "Say this is a test"}], model="gpt-4o"
)
return chat_completion.choices[0].message.content
# This will create a single span trace with the OpenAI call
call_openai()
# This will upload the trace to Agent Observability
splunk_ao_context.flush()Using the Langchain callback handler:
from splunk_ao.handlers.langchain import SplunkAOCallback
from langchain.schema import HumanMessage
from langchain_openai import ChatOpenAI
# You can optionally pass a SplunkAOLogger instance to the callback if you don't want to use the default context
callback = SplunkAOCallback()
llm = ChatOpenAI(model="gpt-3.5-turbo", temperature=0.7, callbacks=[callback])
# Create a message with the user's query
messages = [HumanMessage(content="What is LangChain and how is it used with OpenAI?")]
# Make the API call
response = llm.invoke(messages)
print(response.content)Create a dataset:
from splunk_ao.datasets import create_dataset
create_dataset(
name="names",
content=[
{"name": "Lola"},
{"name": "Jo"},
]
)Get a dataset:
from splunk_ao.datasets import get_dataset
dataset = get_dataset(name="names")List all datasets:
from splunk_ao.datasets import list_datasets
datasets = list_datasets()Dataset Record Fields:
generated_output: New field for storing model-generated outputs separately from ground truth. This allows you to track both the expected output (ground truth) and the actual model output in the same dataset record. In the UI, this field is displayed as "Generated Output".Example:
from splunk_ao.schema.datasets import DatasetRecord record = DatasetRecord( input="What is 2+2?", output="4", # Ground truth generated_output="The answer is 4" # Model-generated output )
output/ground_truth: The existingoutputfield is now displayed as "Ground Truth" in the Agent Observability UI for better clarity. The SDK supports bothoutputandground_truthfield names when creating records - both are normalized tooutputinternally, ensuring full backward compatibility. You can use either field name, and access the value via theground_truthproperty.Example:
from splunk_ao.schema.datasets import DatasetRecord # Using 'output' (backward compatible) record1 = DatasetRecord(input="What is 2+2?", output="4") assert record1.ground_truth == "4" # Property accessor # Using 'ground_truth' (new recommended way) record2 = DatasetRecord(input="What is 2+2?", ground_truth="4") assert record2.output == "4" # Normalized internally assert record2.ground_truth == "4" # Property accessor
Run an experiment with a prompt template:
from splunk_ao import Message, MessageRole
from splunk_ao.datasets import get_dataset
from splunk_ao.experiments import run_experiment
from splunk_ao.prompts import create_prompt_template
prompt = create_prompt_template(
name="my-prompt",
project="new-project",
messages=[
Message(role=MessageRole.system, content="you are a helpful assistant"),
Message(role=MessageRole.user, content="why is sky blue?")
]
)
results = run_experiment(
"my-experiment",
dataset=get_dataset(name="storyteller-dataset"),
prompt=prompt,
metrics=["correctness"],
project="andrii-new-project",
)Run an experiment with a runner function with local dataset:
import openai
from splunk_ao.experiments import run_experiment
dataset = [
{"name": "Lola"},
{"name": "Jo"},
]
def runner(input):
return openai.chat.completions.create(
model="gpt-4o",
messages=[
{"role": "user", "content": f"Say hello: {input['name']}"}
],
).choices[0].message.content
run_experiment(
"test experiment runner",
project="awesome-new-project",
dataset=dataset,
function=runner,
metrics=['output_tone'],
)Sessions allow you to group related traces together. By default, a session is created for each trace and a session name is auto-generated. If you would like to override this, you can explicitly start a session:
from splunk_ao import SplunkAOLogger
logger = SplunkAOLogger(project="gen-ai-project", log_stream="my-log-stream")
session_id =logger.start_session(name="my-session-name")
...
logger.conclude()
logger.flush()You can continue a previous session by using the same session ID that was previously generated:
from splunk_ao import SplunkAOLogger
logger = SplunkAOLogger(project="gen-ai-project", log_stream="my-log-stream")
logger.set_session(session_id="123e4567-e89b-12d3-a456-426614174000")
...
logger.conclude()
logger.flush()All of this can also be done using the splunk_ao_context context manager:
from splunk_ao import splunk_ao_context
session_id = splunk_ao_context.start_session(name="my-session-name")
# OR
splunk_ao_context.set_session(session_id=session_id)See CONTRIBUTING.md for development setup and guidelines.