We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Now that we have support for unordered_writes, we should replace out_of_order errors & metrics with entry_too_far_behind
unordered_writes
out_of_order
entry_too_far_behind
cc #1544
The text was updated successfully, but these errors were encountered:
Do we want to rename this even though ingestion of out of order data is opt in via ingester config?
Sorry, something went wrong.
@owen-d Is there an ETA on the release with this awesome feature just yet?
two thoughts, we should make out of order the default and remove the ability to disable it, remove the config entirely.
We should consider using different limit reasons based on if the feature is enabled
Closed by #4592
No branches or pull requests
Now that we have support for
unordered_writes
, we should replaceout_of_order
errors & metrics withentry_too_far_behind
cc #1544
The text was updated successfully, but these errors were encountered: