Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can I correspond the database data in runtime_logging with actual runtime outputs? #2670

Open
Tracked by #7
kev1nzh37 opened this issue May 13, 2024 · 2 comments
Labels
help wanted Extra attention is needed logging related to logging issue

Comments

@kev1nzh37
Copy link

Describe the issue

For example, consider the following runtime output:

kevaaa (to Assistant):

call me sager

--------------------------------------------------------------------------------

>>>>>>>> USING AUTO REPLY...
Assistant(to kevaaa):

Of course, Sager. How can I assist you today?

I can find detailed information about this entry in the database file, but I can't figure out their correlation.

For instance, I want to know from which agent a particular entry in the chat_completions table originated? Who was it responding to? Additionally, the IDs in the agents table do not correspond to any responses.

I would like to use runtime_logging to perfectly reconstruct the output logs. How can I achieve this?

Steps to reproduce

No response

Screenshots and logs

No response

Additional Information

No response

@ekzhu
Copy link
Collaborator

ekzhu commented May 13, 2024

It's not possible now due to the the outputs are not part of the logs. We can add these output events to runtime logging. See #2423

@ekzhu ekzhu added the logging related to logging issue label May 13, 2024
@ekzhu ekzhu added the help wanted Extra attention is needed label May 13, 2024
@lalo
Copy link
Member

lalo commented May 17, 2024

#2526

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed logging related to logging issue
Projects
None yet
Development

No branches or pull requests

3 participants