What to include in a Transaction ?
Since this protocal sees and records all request separatly...I have consultants who are saying the following below since this content is being cached for us by Akamai...my feeling is this is still part of the end users experence regardless of where it comes from and should be part of the transaction measurement.
Is it right to exclude these Non HTML resourse requests? To me it is just a way to make sure the page loads fast for them while performance testing.
"Only those requests which are critical to the action have been included inside the transaction.
Requests which are related to the NON HTML resources getting downloaded like jsp/css and redirection are not included in transactions."
Re: What to include in a Transaction ?
Regarding to your concern let me tell you that depends of the scenario that you want to emulate. If the real users access to the application constantly all the Non-Html will not download because it will stay on the cache memory, the recomendation is not download it, to recreate a nearly real experience on vusers and real users.