Skip to content

feat: store every usage information in conversation #1761

@tusharmath

Description

@tusharmath

Conversation currently only stores the last usage information. This makes it difficult to assess cache hit/miss issues in dumps. Ideally for each request we make we should store the usage information so that we can see - token usage and cost information in detail.

Technical Requirements

  • Store it in the meta field
  • Add a timestamp field in the data.
  • Keep it open for extensions (we might want to add more fields)

Related #1485

Metadata

Metadata

Assignees

No one assigned

    Labels

    state: inactiveNo current action needed/possible; issue fixed, out of scope, or superseded.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions