Hi! Do you have any ideas on what we might be missing and how to fix this? Non-ASCII symbols coming as part of Windows EventLog events (windows_events table) are stored in the result.log file in an encoded format, such as "User":"NT AUTHORITY\\\xD0\xA1\xD0\x98\xD0\xA1\xD0\xA2\xD0\x95\xD0\x9C\xD0\x90". However, the same events may contain decorators with non-ASCII symbols, which are correctly displayed in the same result.log file. When the same query is executed via the Fleet web interface (as a live query), there are no issues with the presentation of the same non-ASCII symbols from the Windows EventLog events.