On 23/11/15 04:52, Joi Owen wrote: > > Also note that message, full_message, and source are the only fields > that can be searched via wildcard by default." > > I find that if I extract fields that are single words, I can search > for them by exact match, and oddly, I am able to do a field match with > a trailing *, but not a leading one, and not a subset of the word. Ie > I can do exact match, and 'starts with' but nothing else on my > extracted field.
Yeah that's what I'm thinking too. I'd love to hear precisely what are the search options. To formalize what you're saying, it looks to me like graylog can only search under the following constraints: 1. "message" field is "special" and supports wildcards and pseudo-regex 2. timestamp is handled outside the search bar 3. any other field must be a precise match - although you say you can wildcard the end of it (I haven't tested myself because frankly it's pretty useless to me) I'm guessing this is really an elasticsearch limitation? Is there any way for graylog to tell elasticsearch to treat certain other fields the same way as the "message" field? (or at least to match on substrings). If so, it could be exposed via the extractor wizard - eg add "allow substring matches" as a drop-down option? -- Cheers Jason Haar Corporate Information Security Manager, Trimble Navigation Ltd. Phone: +1 408 481 8171 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 -- 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/56522663.8030709%40trimble.com. For more options, visit https://groups.google.com/d/optout.
