-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Improved Ingester out-of-order error for faster troubleshooting #1008
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I do have concerns about how it changes the behavior of the code when we received errors that aren't out-of-order errors.
My only big concern with merging this, is that I think we need to figure out the return first. That is I don't want to merge this now then convert it to JSON output later. |
This kind of then opens a bigger can of worms around what our API error handling looks like/should look like |
no worries. will work on a JSON return within this pull request |
Hold off just a bit @wardbekker we were discussing a little in slack, but I think we need a strategy for error return types in general. Don't want you to head down a road until we are sure what direction we want to go with this |
This LGTM, we're going to tackle changes to error return types in a future PR, and this is a good improvement to have in the interrim. |
What this PR does / why we need it:
See #963
Which issue(s) this PR fixes:
Fixes #963, although not returning a JSON struct yet, that could be a follow up improvement
Special notes for your reviewer:
First pull request to Loki, love to get your feedback!
Checklist