Here is an example. It looks like Graylog cannot parse the field for some reason.
On Tuesday, January 24, 2017 at 2:48:44 PM UTC-5, 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/f7951e2f-a0b9-447b-a5a2-358995447b37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
