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
Recent log documents lack the log.offset property which our query relies on.
log.offset
Was fixed on CDSE by adding a random one at write time
This is not k8s so maybe it can simply be enabled: https://vector.dev/docs/reference/configuration/sources/file/#offset_key: TBC
The text was updated successfully, but these errors were encountered:
@bossie is this still an issue?
Sorry, something went wrong.
Yes, because the short-term fix was to simply roll back the changes that broke the logs (= move from filebeat to vector on Terrascope).
The actual fix is to get log.offset in the ES log documents but that's a devops issue.
@JeroenVerstraelen: @tcassaert and @pvbouwel are better suited to take on this issue.
tcassaert
No branches or pull requests
Recent log documents lack the
log.offset
property which our query relies on.Was fixed on CDSE by adding a random one at write time
This is not k8s so maybe it can simply be enabled: https://vector.dev/docs/reference/configuration/sources/file/#offset_key: TBC
The text was updated successfully, but these errors were encountered: