Hi, I've been trying to use the filters to hide some useless queries from being sent, I'm using Helm to deploy SigNoz, but it was not succesfull so far. Here is an example of a request I got, and here is the code I use to filter it:

processors:
          filter:
            spans:
              exclude:
                match_type: regexp
                attributes:
                  - Key: http.route    
                    Value: .*\/health.*    
                  - Key: http.route    
                    Value: .*\/prometheus.*    
                  - Key: operation                                                                                                                                                                         
                    Value: OperationHandler.handle

It doesn't work so far, even though the string itself

/actuator/health/**

supposed to be caught by the regex

.*\/health.*

cc: @Vishal Sharma

Did you add the processor to the pipeline?

Yes, I got this:

pipelines:    
            traces:    
              receivers: [otlp]    
              processors: [signozspanmetrics/prometheus, batch, filter]    
              exporters: [clickhousetraces]

Looking at your screenshot again, the ``/actuator/health/**`` is not

http.route

tag value rather a operation whose filter criteria is hard coded to simply match the value

OperationHandler.handle

I'll move the filter as you showed. But I'm not sure to understand the meaning of your previous message: it is not

http.route

? But the right sidebar with more details about this trace seems to indicate it is

@Guillaume I get the confusion. The screenshot attached has operation name as

/actuator/health/**

. I marked it in the image in orange. But the screenshot you shared now, has it in

http.route

attribute key

Indeed, it's confusing me 😅 Ok so do you mean like this?

filter:             
            spans:            
              exclude:        
                match_type: regexp      
                attributes:    
                  - Key: http.route     
                    Value: .*\/health.*
                  - Key: operation      
                  - Key: .*\/health.*

https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/filterprocessor#filter-spans-from-traces

filter:             
            spans:            
              exclude:        
                match_type: regexp
                span_names:
                  - .*\/health.*
                attributes:    
                  - Key: http.route     
                    Value: .*\/health.*

as

operation

is not attribute but

name

of span

Oh, right, then my last filter is also wrong:

- Key: operation
                    Value: OperationHandler.handle

should be this in the end:

filter:             
            spans:            
              exclude:        
                match_type: regexp
                span_names:
                  - .*\/health.*
                  - OperationHandler.handle
                attributes:    
                  - Key: http.route     
                    Value: .*\/health.*

yes.. I think so

Hi, sorry for the delay. After setting it up, I could still notice data, through the frontend, with the same pattern as I showed. So I think it did not work this way unfortunately