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

Logging Project Feature Tracking #2168

Open
13 of 27 tasks
kevkevinpal opened this issue Dec 12, 2024 · 0 comments
Open
13 of 27 tasks

Logging Project Feature Tracking #2168

kevkevinpal opened this issue Dec 12, 2024 · 0 comments
Assignees

Comments

@kevkevinpal
Copy link
Contributor

kevkevinpal commented Dec 12, 2024

Goal

The goal is to create more verbose logging in sphinx-tribes such that it give enough information to LLM to effectivly create solutions for both Internal Server Errors and also for Logical Errors in the sphinx-tribes codebase

Phase 1 (Middleware for stacktrace to Jarvis)

Stretch Goal

Phase 2 (Debugger for verbose logging)

Stretch Goal

  • Save the logs for 24 hours somewhere

Phase 3 (Connect debugger logs to middleware)

  • Figure out how to read from the exisitng logs from middleware when 500 Error
  • At this point we need to rethink how jarvis proccess the request instead of just a stacktrace

Phase 4 (Logical Errors)

  • Create new header that is called X_JARVIS_QUESTION
  • Modify logger middleware to send to jarvis if X_JARIVS_QUESTION is not None and include the stacktrace even if successful
  • Modify Jarvis /node/edge/bulk to have an optional question param

Phase 5 (DB sanity checks)

  • Some how check if the db would ever be in a certain state that should not happen

TODO:
Create issues for each one of these tasks and also refine these steps to solve this problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant