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.

Sign up for GitHub

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

Jump to bottom

easily identify commands triggering error responses #1531

Open
romange opened this issue Jul 10, 2023 · 0 comments · May be fixed by #1703
Open

easily identify commands triggering error responses #1531

romange opened this issue Jul 10, 2023 · 0 comments · May be fixed by #1703
Assignees
@talbii
Labels
MANAGED

Comments

@romange
Copy link
Collaborator

romange commented Jul 10, 2023

Often, I can see

# Errorstats
syntax_error:4264
some other error ....

errors in running instances but it's impossible to identify the command that triggered it.

I suggest developing a complementary system with a ring buffer that will store last K commands (or command prefixes) that causes
error responses which can be fetched with "DEBUG ERRORS" or something.
@talbii talbii linked a pull request Aug 15, 2023 that will close this issue
Open
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@talbii talbii

Labels
MANAGED
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

DEBUG ERRORS dragonflydb/dragonfly
2 participants
@romange @talbii