Difference between WebServiceByMethod and WebServices
What is the difference between the Built-In Business Transaction called "Web Service By Method" and "Web Services" in the Diagnose Performance section of the cockpit? If I create a dashlet for each... each with the same timeframe I expect the counts and the averages to be the same or very close to one another. For some of our web services the counts and averages are very close but for some they are very far apart.
That makes sense. However, there's still something wrong with the calculation of the average and the error calculation. It seems the issue is in the Web Services By Method dashlet. Below I have pasted 2 pictures showing the same service in both the Web Services BT and Web Service By Method. The name of the service I'm focusing on is called "WCBySpectrumISOGL". Both Web Services BT and Web Service By Method show the same number of calls 1434. But, Web Services (BT) shows no errors and an average of 754.75ms. The Web Services By Method Dashlet shows a .35% failure rate and an average that is 3900.71ms. See below for screen shots. I've also attached an excel report showing the correct average (captured from our web service gateway Oracle Web Services Manager) ~748 ms. I'm very interested in fixing Web Service by Method because I can create a chart with this dashlet. If there were a way to create a chart using the Web Services BT dashlet I'd abandon Web Service by Method.
Thanks in advance for your help.
WCBySpectrum.xls
Hi Frank
The failure rate at the Business Transaction is calculated on transaction level - meaning that in 0.35% of your PurePaths (complete transaction) that match this BT you have errors.
In the Web Service Dashlet you see 0% because this error rate tells you whether there was an error within the web service call itself.
As for the timing. The Avg Time on the Web Service Dashlet shows you the time for this particular web service call. On the BT it is the Avg Time of all Web Service Invocations on that PurePath.
If you can - please do the following
a) Drill from your Business Transaction to your PurePath Dashlet
b) Select a PurePath that shows an error and that has more than one Web Service call.
c) export this purepath and send it over to me (firstname.lastname@dynatrace.com)
Andi
Hi Frank
Great question - hope I can answer this.
Lets assume the following scenario:
You have 100 PurePaths/Transactions. In these 100 PurePaths you have 150 Web Service calls (some PPs only make 1 WS Call, some make two or more).
Web Services Dashlet
This dashlet shows the actual invocations of the Web Services and their response times. This would be 150 web service calls. The timings would show the actual response times of these calls
Web Services By Method Transaction
The Business Transactions analyze all PurePaths, splitts them by Web Service Method name and returns specific results per Splitting (e.g: Failure Rate or Execution Time).
If you open the Business Transaction Dashlet for this BT you will get one entry per Web Service Method Name. The Count column however will show the number of PurePaths that matched the splitting value (Web Service Method Name) - as compared to the actual number of Web Service invocations. I think this is where your numbers dont match up anymore. Its possible that you see the same Web Service being called from lets say 50 PurePaths (thats the count column in the BT Dashlet). If a single PurePath calls the same Web Service multiple times you would however see e.g: 60 invocations in your Web Service Dashlet.
I hope this makes sense. If not - send me an exported sessions and I try to explain based on your data
Andi
