Enhance WebRequestTraceFilter to allow excluding capture of certain request paths(eg /management)

The WebRequestTraceFilter captures and stores all requests currently.

Sometimes, I just want to trace the request mapped in my own Controller, and exclude others that I don’t care about. Based on this feature, it’s easier to integrate more useful features. For a simple example, only captures real user’s request, assigns or get a request-id, then calculates response time, and store the trace result.

I currently defined a TraceRepository bean, rewrite the TraceRepository.add method to exclude certain request paths. But I think it’s better to enhance WebRequestTraceFilter. I would propose adding a collection named ‘excludedPaths’ to TraceProperties, and checking against in WebRequestTraceFilter.doFilterInternal()

[wilkinsona]

Thanks to the changes made for #6309 you can declare your own custom WebRequestTraceFilter bean in 1.4. You can subclass WebRequestTraceFilter and override shouldNotFilter to exclude certain paths.

[lowzj]

great, thanks.