excluding Web request without referer
Hi,
I have built a measure for a particular URI response time and then set the upper thresold to 5 seconds.
I am using this measure in a BT as a filter condition so that I can filter transactions for this URI exceeding the threshold . ( I am using many such measures in the BT for different URI's so that I can get the filtered output for multiple URI's within a single BT) .
I also have I more requirement.Now I also need to remove those transactions from filtered out that dont have a referer even though these transactions exceed 5 seconds threshold.
Is it possible in dynaTrace. ?
When I click on web request and look at details , I see that dynaTrace is able to capture the referer for the transactions. I need to add this condition as a filter to remove the transactions for my above BT which dont have a referer
Hi. Can anyone help me with the above query?
Hi.
This should be possible using a Web Request Header Measure and checking whether the value contains/or does not contain a certain value. In your case you want to check for the non-existence of the Referer header. I haven't tested this but I think this should be the measure definition that should work. The measure should return the value 1 in case there is no occurence of a referer value
Andi
Hi Andreas,
I have created the measure as suggested above and then included it as a filter condition in the BT. My BT does not return any values .
Also , can you let me know what does " .*" value indicate in the example.
Hi,
Please consider whichever of the following you are trying to do:
- Capture only requests which do have a referer header. Use the following as a filter:
- Capture only requests which do not contain a referer header. Use the following as a filter (same thing but with different threshold):
Also note that if your scenario is 1 (that you want the requests to have referer headers) AND that the referers are significant data AND that there are a finite number of referers (this is important to prevent your BTs from having too many splittings) you can simply use the below measure as a splitting, which will make sure only requests which have headers get evaluated but also group your requests by which referer they had.
I have tried all three locally this morning and they work well.
Rick B
Hi Rick,
Can you please attach the screenshots in reference to your comments above. I believe you missed to attach the screenshots
Hi,
Sorry, I have attached the images. They were working but your organization must block ScreenCast.com.
Thanks,
Rick B
Hi Richard,
Which scenario would I use if I have a specific referer value I want to capture? Scenario 1 or 3?
