Skip to main content
This guide shows you how to attach configuration details (prompt version, model parameters, hyperparameters) to your traces using the config namespace.
Config vs Prompt Management: The config namespace logs which configuration was used for a given trace. To create and deploy prompt templates, see Managing Prompts.

Quick Start

Use enrich_session() to set the config for the entire trace, or enrich_span() to set it on a specific operation.

On the Session

Set configuration context that applies to the entire user interaction:

On a Span

Attach config to a specific function or LLM call:

Logging a Deployed Prompt

If you use HoneyHive’s Prompt Management to deploy prompts, you can log the fetched configuration on the trace so you know exactly which version produced each response.

Concepts

What Belongs in Config?

The config namespace is for any setting that controls how your application generates a response. This makes it easy to filter and compare traces by configuration in the dashboard.

Config vs Metadata

Both store key-value data. Use the right namespace so you can filter effectively in the dashboard.

Data Types


Learn More

Managing Prompts

Create and test prompts in the Playground

Using Prompts in Code

Fetch deployed prompts via the SDK

Enriching Traces

Full guide to trace enrichment

Schema Reference

All namespaces and data types

SDK Reference

Python SDK

enrich_span() and enrich_session()