Open andrelec1 opened 5 months ago
From Discord :
jches: Skimming some old NFS mailing list posts, it sounds like this (reading null bytes from a file) is just something that can happen if the file is being read while it's open for writing. You'll probably need to take a similar approach as in that thread, so vector is only reading files that aren't being written to anymore https://www.spinics.net/lists/linux-nfs/msg49803.html
So this not a 'bug' in vector ...
But the file sink need to have a option to simply ignore the fact he read the last line if the line start by Null ...
you can try with this change for similar issue, on v0.38.0 sources https://github.com/tamer-hassan/vector/commit/518d4e17db2a698491cc3927df39de676d7ef523 I built only for windows since this is what I was concerned with.
A note for the community
Problem
.message fields contains a lot of "\u0000", before the real line contains.
Configuration
Version
see on 0.33 and 0.35
Debug Output
Example Data
Additional Context
I have 2 serveur that ouput their log in the same NFS storage. I use a third server to run vector that read the data from the NFS storage.
Someone else having the same issue on the discord, but this guy using a S3 storage instead a NFS. This issues look like a issue about network storage :/
References
https://discord.com/channels/742820443487993987/1194253312212615219 https://discord.com/channels/742820443487993987/1149066915923365898