Are Elasticsearch regular expressions PRCE comatible?


(Solarwinds) #1

Hi all,

I am using ElasticStack to monitor various process including Java processes. In this particular case, I am searching for Kafka process.

Using online regex tester, I am able to get a match, but my regex never gets hit when querying data in Kibana. Document with full path is already present in ES.

Is such behavior specific to Kibana or Elasticsearch (Lucene query syntax)?

Thanks,


(Solarwinds) #2

Sorry. It looks like that I have posted my question in wrong topic. Can some one please move it to Kibana?


(Christian Dahlqvist) #3

As per the documentation they are not Perl-compatible.


(Solarwinds) #4

Hello Christian. That was quick, I have spent at least one hour going through the exact documentation. So, basically, I should stick with Lucene documentation regarding the regular expressions.


(Christian Dahlqvist) #5

I believe so. Be aware however that using regular expression searches can be very slow and scale badly. It would be a lot faster if you could parse out parts you know are going to be interested in at index time.


(Solarwinds) #6

Yes, I was afraid of that. Both parts, Lucene and slow queries.

To be honest, I am not sure what do you mean under, "parse out parts". I am already filtering the documents in following way:

beat.hostname: "some.hostname" AND system.process.name: java AND system.process.cmdline: myregex_query_that_doesnt_work.


(system) #7

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.