Thanks for that useless and unhelpful RTM response. I have read that page several times – and according to it (and the first responder above) what I have tried should work. It does not.
I realize what other’s post may not help and/or you have see/read it already. I also understand your having issues searching. Were all here on our free time so if you could please keep the negative statements down a bit it would be much appreciated. Help us , help you
As for your searching goes, perhaps something like this.
Messages where the field type includes test1 and Not test2,
Thanks for trying – but that syntax doesn’t work either (see screenshot). So it really seems like maybe I need to file a bug report… you are the second responder who seems to agree that what I’m doing should be working.
P.S. I felt that other person was being rude and dismissive by pointing me at a manual that is obviously linked right off the UI. Their response read as “negative” and snarky to me.
Actually, I think I see the issue – the pattern matcher seems to be insisting on complete “words.”
This works:
"DNS" AND NOT "connect.myqdevice.com"
So the pattern “connect” was NOT matching against “connect.myqdevice.com” in the message. A regex appears necessary to do a partial match within a word:
I really do not understand what Graylog/Lucene is doing with these patterns.
Consider these messages (not fragments, these are the entire messages):
kernel: [164141.531234]
kernel: [164141.531234] some trailing text
kernel: [456432.789654]
kernel: [456432.789654] some trailing text
I want to come up with a pattern (regex or otherwise) that will only match the first and third messages but not the second and fourth with the trailing text. I cannot get anything to work.
In a non Graylog/Lucene world, I would use a regex matching on the entire string:
/^.*kernel: \[[0-9]{6}\.[0-9]{6}\]$/
But I can’t come up with whatever magic incantation Lucene seems to want for this.
/[0-9]{6)\.[0-9]{6}/
matches all four messages well enough. But the moment I start trying to put [ or ] into the pattern or trying to anchor to the end of the message text, it fails. For example: