Group related requests into conversation Threads so they appear together in observability. Threads are a labeling mechanism and do not store or inject message history.Documentation Index
Fetch the complete documentation index at: https://docs.orq.ai/llms.txt
Use this file to discover all available pages before exploring further.
Quick Start
Configuration
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique thread identifier for grouping requests |
tags | string[] | No | Metadata tags for filtering and categorization |
Best Practices
- Consistent Naming: Use predictable thread ID patterns
- Meaningful Tags: Choose tags that aid in filtering and analysis
- Session Management: Tie thread IDs to user sessions
- Unique IDs: Use UUIDs or composite keys to avoid cross-session overlap
Use Cases
| Scenario | Thread ID Strategy | Tags Example |
|---|---|---|
| User Sessions | user-{userId}-{sessionId} | ["user-session", "support"] |
| Support Tickets | ticket-{ticketId} | ["support", "priority-high"] |
| A/B Testing | test-{variant}-{userId} | ["experiment", "variant-a"] |
| Multi-Step Workflows | workflow-{processId} | ["onboarding", "step-2"] |
Implementation Examples
Session-Based Threading
Assign the samethread.id to all requests in a session to group them together in observability. Your application manages the messages array for each request.
Multi-Language Support
Advanced Patterns
Dynamic Thread Management
Batch Thread Processing
Conversation Flow Tracking
Troubleshooting
| Issue | Cause | Solution |
|---|---|---|
| Requests not grouping together | Different thread IDs used across requests | Use a consistent thread ID for all requests in the same session or workflow |
| Thread overlap | Non-unique thread IDs shared across sessions | Use UUID or timestamp-based IDs |