Skip to content

LLM request and response traces are not stored in the session service #1920

@sdivakarrajesh

Description

@sdivakarrajesh

Current
Only the events and states are persisted in the opted session service(In my case DatabaseSessionService)

Preferred
Include the LLM request and responses in a separate table for debugging and traceability.

Why
The LLM requests reflect the exact reasons why the agent is not performing as intended. Most of the time, its insufficient information in the context that makes the LLMs "guess" making them unpredictable. This underpins the framework's capabilities as the user's can't see these values as soon as they stop their server or restart their server during re-runs and debugging sessions.

Metadata

Metadata

Labels

tracing[Component] This issue is related to OpenTelemetry tracing

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions