MSSQL tail ERRORLOG UTF16 encoding issue.
When tailing the MSSQL ERRORLOG file using the latest Fluent Bit version and the configuration from GitHub issue #9468, Fluent Bit initially reads the file correctly. However, when new events are appended, it outputs \u0000 characters instead of readable log text.
Steps to Reproduce
1. Configure Fluent Bit to tail the MSSQL ERRORLOG file as per issue #9468.
2. Start Fluent Bit — the existing log content is parsed correctly.
3. Append new log entries to ERRORLOG.
4. Observe that new entries are output as \u0000 sequences instead of proper text.
Expected Behavior
New log entries should be parsed and output in human-readable text, same as the initial content.
Actual Behavior
Initial file read works fine.
New appended entries contain only \u0000 characters.
Request for Guidance
Has anyone else encountered this issue? Should this be marked as a confirmed bug and opened as a new issue for tracking? Any advice on handling UTF-16 encoded log with offset tails in Fluent Bit would be appreciated.