Store dimos logs in memory2 text stream

Open
#2,217 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
observability-sre

Research direction

Start with dimos/memory2/intro.md to understand how mem2 stores and indexes text, then run the documented replay command to observe the current logging output. Trace the existing STDOUT and FILE consumers and determine where a parallel memory consumer would attach. Done means replayed system events are stored in memory with tags for modules, workers, and relevant metadata.

Written by the indexing model from the issue text.

Description

core leshy_navigation

mem2 can store and FTS index text

https://github.com/dimensionalOS/dimos/blob/main/dimos/memory2/intro.md

write a log consumer (parallel with STDOUT/FILE output we have now) that stores in memory, uses tags to mark modules, workers, any other relavant metadata
consider also logging dtop? (can be for the future)

we need this to debug system events when replaying a recording, for example odometry dies mid recording here

git checkout ivan/hkbuilding/recordings
dimos --dtop --replay --replay-db hk_building_park run unitree-go2

and we can't check what happened :)

Synced from DIM-945 by summer

Dominant language
Python
Stars
4.5k
Forks
808
Avg merge
3d 5h
Merged PRs (30d)
233

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dimensionalOS/dimos

All issues in dimensionalOS/dimos

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.