feat: Filter spans using regex pattern matching in tags

[abhishek-sehgal954]

#222
This is not the complete solution. Some refactoring, improvements and support in druid setup is pending. I wanted to get an initial feedback for this.

So I think there are 2 ways to do this.

1. We create one more operator Pattern in which we give an option to user to select out of (1xx, 2xx, 3xx, 4xx, 5xx), so that we don't get unexpected patterns. This requires little frontend work.

2. We implicitly support it from the backend like I have sort of done in this change. If a user passes 4xx, he/she will get response accordingly.

IMO both are okay, but intuitively would it make more sense to have an explicit operator so that user is sure and know exactly what he/she are searching.

Let me know your thoughts @ankitnayan

[ankitnayan]

@abhishek-sehgal954 I was thinking more like adding regex as an operator and using match(haystack, pattern) similar to what we have done for contains operator using ilike keyword in query at this code block

So users can apply generic regex operations to any of their tags.

[abhishek-sehgal954]

@abhishek-sehgal954 I was thinking more like adding regex as an operator and using match(haystack, pattern) similar to what we have done for contains operator using ilike keyword in query at this code block

So users can apply generic regex operations to any of their tags.

okay, sounds good. will make the change.

[abhishek-sehgal954]

@abhishek-sehgal954 I was thinking more like adding regex as an operator and using match(haystack, pattern) similar to what we have done for contains operator using ilike keyword in query at this code block

So users can apply generic regex operations to any of their tags.

@ankitnayan updated.

[ankitnayan]

@abhishek-sehgal954 seems fine. Below are a few checks for every PR

• We are following https://www.conventionalcommits.org/en/v1.0.0/. Please do the necessary changes

• You should have tested with some sample data

• Docker image must be build and tested locally

Let me know when these are done. We shall include it in checks also soon.

Also, I would change the PR to say something around regex pattern matching enabled for tags since it does more than just searching for status code pattern

[abhishek-sehgal954]

@abhishek-sehgal954 seems fine. Below are a few checks for every PR

• We are following https://www.conventionalcommits.org/en/v1.0.0/. Please do the necessary changes
• You should have tested with some sample data
• Docker image must be build and tested locally

Let me know when these are done. We shall include it in checks also soon.

Also, I would change the PR to say something around regex pattern matching enabled for tags since it does more than just searching for status code pattern

@ankitnayan done.