Rearch: logging interface

[rihp]

Background

Changes

Documentation

Test Plan

PR Quality Checklist

• [ ] My pull request is atomic and focuses on a single change.
• [ ] I have thoroughly tested my changes with multiple different prompts.
• [ ] I have considered potential risks and mitigations for my changes.
• [ ] I have documented my changes clearly and comprehensively.
• [ ] I have not snuck in any "extra" small tweaks changes

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Ignored (Inspect)			May 5, 2023 7:36pm

[dwrtz]

If I wanted to add additional metadata to a log message, what would be the recommend way to do that? I suppose it could be part of the message string. I'm thinking information like timestamp, user_id, agent_id.

Or perhaps an optional meta field in the LogMessage class. Something like this?

class LogMessage:
  title: str
  message: str
  format: LogFormat
  meta: Optional[dict]

Just thinking out loud here

[dwrtz]

Otherwise this looks great. Being able to have a logger instance per-agent will be a huge win

[anonhostpi]

This is good progress. Keep up the good work!

[rihp]

Made the changes suggested! @dwrtz

[rihp]

We should consider adding a handler for syncing logs from a namespace @collijk @dwrtz @ntindle