Custom Spans

While the HoneyHive tracer automatically instruments all of the most common LLM application components, you might sometimes want to trace parts of your code beyond the automated coverage.

To do this, you can use HoneyHive’s manual tracing tools, which we’ll walk through in this guide.

Prerequisites

Please complete the Quickstart and make sure you have initialized your tracer using HoneyHiveTracer.init().

Overview

HoneyHive gives you full customizability over your traces.

You can trace any function in your code and see its inputs, outputs, errors, duration, etc. by decorating it with the @trace decorator.

from honeyhive import trace

@trace
def my_function(param1, param2):
    # Code here
    return result

Enriching Custom Spans

You can enrich your custom spans with additional properties to provide more context to your traces. There are 2 ways to enrich spans in HoneyHive:-

1. Enriching before execution: The decorator-based enrichment below shows how you can enrich static properties before the code executes.

2. Enriching during execution: You can enrich dynamic properties on a session/trace or event/span level using enrich_session and enrich_span functions. Please refer to the Enrich Traces documentation for more details on enrichment during execution.

Enriching Before Execution Using Decorators

Here is an example of how to enrich the Configuration, Metadata, and Event Type fields on the decorator:

from honeyhive import trace

@trace(
    config={
        "event_type": "my_event_type",
        "metadata": {"key": "value"},
    },
    metadata={
        "key": "value",
    },
    event_type="chain",
)
def my_function(param1, param2):
    # Code here
    return result

Enriching During Execution Using enrich_span or enrich_session

You can also enrich your traces and custom spans with various propertires during execution using the enrich_span or enrich_session functions.

Please refer to the Enrich Traces documentation for more details on enrichment during execution. You can find the complete documentation for this in the Python SDK reference.

Best practices

• Use descriptive function names, as they will be used as span names in your traces
• Be mindful of sensitive data when tracing functions - avoid capturing passwords or other secrets

By strategically adding the @trace decorator to key functions in your application, you can gain valuable insights into your custom code’s performance and behavior, complementing HoneyHive’s automatic instrumentation of LLM components.

Visualizing Your Traces

All traces can be visualized in the HoneyHive web app under Data Store in the session’s specified project. The session tree view shows you the execution flow of your trace, as well all the automatically captured and manually enriched attributes.

Next Up: Enrich Your Traces

Here are some ways in which you can enrich your traces: