Hi Tyler, this sounds like the charset used by nxlog isn't correct. How exactly did you configure nxlog? How are you sending messages to Graylog? Do you convert the charset of the log message to UTF-8 before sending it to Graylog?
See https://github.com/Graylog2/graylog2-server/issues/3130 for a possibly related issue. Cheers, Jochen On Tuesday, 24 January 2017 20:48:44 UTC+1, Tyler Dami wrote: > > Hi All, > > I'm a little new to Graylog and I'm have a bit of trouble with importing > messages from a text file using NXLog. > > Currently I am reading a text file using NXLog, and sending it line by > line, where each line is a new log entry, to Graylog. This is working well, > and I see the messages when I search on the source attribute - but Graylog > cannot search the content of the messages. I also cannot extract anything > from the message field, it always says "No Match". Powershell is generating > the text file and I am curious if the encoding is causing an issue in > elasticsearch. > > Has anyone experienced this behavior out of Graylog? > > Thanks! > > Tyler > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/87c7886b-d336-474a-a5ec-d79ad31203ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
