How to UTF-8 decode in Enhanced table like the documents table #322
Replies: 1 comment
-
Well, I'm quite surprised by your question. Personally, I have to deal with with correct encoding reading at source parsing (Filebeat, Logstash) when I read a file. But not after because all is processed in UTF-8 (both Elasticsearch & Kibana). So I don't understand how you can have such a problem. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, Wanted to see if there was a way to get the Enhanced table to decode my subject lines that are sometimes encoded in utf-8. The documents table seems to do this automatically but the enhanced table doesn't seem to be doing the same thing. Is there a way to enable this so my subject lines will display decoded instead of encoded by utf-8?
Beta Was this translation helpful? Give feedback.
All reactions