"not contains" measure is not working
Hi,
I'm trying to create a business transaction which will filter out purepaths that don't contain a call to a specific external service within them
For example:
Get all pages that start with the URL : /{x-url}/
Which don’t contain an external call to : {y-url}
I’ve tried the “not contains” and “not starts” to create a measure and added the upper sever as 1. But still It seems the filter is not working as expected as I'm seeing all pages starting with /{x-url} that contain all kind of external calls. I tried to play around with it but have not succeded yet.
Can you please help me with this?
Thanks,
Solmaz
What type of Measure do you use? Are you using the Web Request Count measure? or are you using a different one?
If you create a Web Request Count Measure it wil return the number of URLs on a single PurePath that "do not contain" the URL pattern. The measure therefore will return a value like 0, 1, 2, 3, 4 ... (the number of URLs on that PP that DO NOT match the URL Pattern). Here is what I would do in your case. I would create a Web Request Count measure with "CONTAINS URL" -> so - create one that actually counts whether the PurePath makes a call to that Web Service. Then specify the Lower Severe Threshold with 0 and use this as a Filter. This will mean that you get a BT where every PurePath that has 0(ZERO) calls to that URL will be part of that BT
Hope this makes sense
This is great Andreas!
I did as you suggested and it's working now 
thanks for your quick respond!
I assume you use a "Web Request Count" Measure? Have you tried charting this measure? Does it return the value you expect? Did you specify the option "all" occurences and not just entry point?
So to clarify I have two measures that I'm using in my Business Transaction as filters:
1.Get all pages that start with the URL : /{x-url}/
2.don’t contain an external call to : {y-url}
so the first one gets my actual URL stem as expected but #2 is literally doing nothing as it's returning the same number of counts as all the web requests coming in the application. It's not filtering out the {y-url} at all. It's somehow always evaluating as true.
Yes I did specify "all" and I played around with it by changing it to entry points. Still not working.
Here is a comment from my co-worker that thinks it's the reason for this:
"In the Measure configuration dialog box, there is a setting called “Upper severe” (under thresholds). Your current filter has the setting as 1. That means that if there is 1 URI that doesn’t start with “ {y-url}”, then the measure is true. The purepaths for {x-url} have a lot of URI that don’t start with “ {y-url}”, including the entry URL. So your measure always evaluate to true.
Try this…try to change the “Upper severe” to 2,3,4(one at a time and run that BT)."
I tried his recommendation.Still not working..
any ideas?
thanks,
Solmaz
