config namespace.
Quick Start
Useenrich_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.Full example: fetch prompt and log config
Full example: fetch prompt and log config
Concepts
What Belongs in Config?
Theconfig 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.
| Category | Example keys |
|---|---|
| Model selection | model, provider, fallback_model |
| Prompt versioning | prompt_name, prompt_version, prompt_id |
| Hyperparameters | temperature, max_tokens, top_p, frequency_penalty |
| System behavior | system_prompt, tool_choice, response_format |
| Routing | ab_variant, rollout_percentage, feature_flag |
Config vs Metadata
Both store key-value data. Use the right namespace so you can filter effectively in the dashboard.| Namespace | Use for | Example |
|---|---|---|
config | Settings that control generation | model, temperature, prompt_version |
metadata | Context about the request | request_id, endpoint, environment |
Data Types
| Type | Example |
|---|---|
| String | "model": "gpt-4o" |
| Number | "temperature": 0.7 |
| Boolean | "stream": true |
| Object | "hyperparameters": {"top_p": 0.9} |
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

