Filter out certain URLs by query parameter
Hi,
I have troubles doing something that I think should be quite easy.
I am trying to split GET requests incoming to a server by their query parameters (there's a dozen queries that repeat all the time, the rest could be mapped to <...>).
So here's what I did:
- I went in the Sensor Configuration pane of the agent group I am interested in and set the Servlets sensor to capture all request parameters (Request Parameter = * in the Parameters and Attributes scroll pane). I am aware of the overhead, and this is not a problem at the moment.
- I went in the measure pane and duplicated "No JS, CSS Request" web requests measure and changed the regex to "(?i).*(?:WSDL|objectid).*". That is, it will be used to filter OUT any request that contains WSDL or objectid anywhere in the URI.
- If I test it, it matches webserver.org/webapp/page?command=dosomething&objectid=12345
- I also duplicated the measure "Complete URI Path" to create one that includes the query (checkbox checked)
- I went to Business Transaction and duplicated the Web Page Requests Business Transaction. I removed all the built-in filters and added my own filter (No WSDL nor objectid) and set it to Aggregate avg.
- I then change the splitting to remove the split by Application and change the split by "Complete Uri Path" to include the query.
- I removed the splitting limits, just to test my new business transaction.
When I open the dashlet for my new Business Transaction, I see that my filter is not working as I see request with queries like "command=dosomething&objectid=12345".
Can we filter on query parameters? Does anyone see what I am doing wrong?
Make sense!! Thank you so much for spotting this!
Hi. I looked into your sessions. There is one thing you need to change
Filter Measure
The objectdid, wsdl, ... are parameters on the Query String - NOT on the URI. Therefore you need to modify your measure definition and change the configuration for URI and Query. Make it so that it says: "URI starts with <empty>" (that will match all URIs) and "Query not regex (?........." (that will match those query strings that dont match your regex
makes sense?
Hi,
I only analyzed new PurePaths coming in, I didn't knew we could analyze existing PP.
Thanks for looking into this. Here two news PurePaths, they are pretty much similar:
And just for reference, here's the BT, filter & splitting measures I described above:
Hi. This all sounds good. Seems you know how BTs are supposed to work really well.
Just to check one thing: After you have created this BT - have you executed requests that resulted in NEW PurePaths and not just opened the BT for your existing PurePaths? If you change or create a new BT only new PurePaths will be analyzed - unless you make the changes on a stored session and do a "Process Configuration Changes". So - just to make sure: have you created new PurePaths?
Feel free to export one of these PurePaths and attach it so that we can have a look at it
Also: It is not necessary to remove the Application Splitting. It will done implicelty anyway as all our BTs are split by Application in order to be able to put it on the AppOverview.
Andi
