On 23/11/15 10:58, Joi Owen wrote: > > I think your best bet is to split that one big text section you're > currently using into separate extracted fields. Use the original > regexp as the control test, the one that decides if a particular log > line is going to be further inspected for the matching field. >
That really doesn't scale. eg I'm inserting our proxy server logs into graylog, and I want to search to find all urls that end in "/73.exe" - eg "/one/73.exe" and "/two/73.exe?id=112". Separating all urls into single-word fields would add nearly infinite numbers of fields - not really an option As you mentioned earlier, the documentation says "Also note that message, full_message, and source are the only fields that can be searched via wildcard by default". So that implies I should be able to make other fields act like the message field So how can I make my "url" field properly searchable? (ie to handle wildcards) Thanks -- 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/56634E6D.3060404%40trimble.com. For more options, visit https://groups.google.com/d/optout.
