Can Auto Baselines Be Measured by Duration instead of Response Time?
This is coming up more often for us in the FiServ area. Response time is useless for a lot of customers as Response time might be 600ms, but the real duration is more like 8 minutes. Is there a way to get the Baselines based on Duration instead of Response time? If not, is there any hard reason I can't make it a feature request?
Brian
Discussed offline was our need to do this not for web/page actions but for non-web transactions. I'm updating this with the information we received from Andreas
To begin, for a non-web application, the only application option you'll have is Default Application. All non-web business transactions and auto baselines will be assigned to default application.
As for using PurePath Duration as the measure for the auto baseline, this can be achieved by doing the following:
In the business transaction
- Uncheck the default Response Time and Count checkbox.
- Add Pure Path Duration to the Result list.
Brian
Brian,
the approach you decribe here should not work, and likely doesn't.
As soon as you add a BT to the Application Overview the default resultmeasures Failure Rate and PP Response Time and Count are activated again. Only these measures are used for the Baseline.
Reinhard
Hi Reinhard
Thanks for the clarification. I think the confusion came in because I was told that this might work.
If it doesnt work - then I think we at least have a very good case for an improvement here. Especially financial instititues are interested in Duration vs Response Time. I will forward you a PP that Francis sent me. Please consider this in future Product Development
Andi
I moved this forum post to the dynaTrace APM Forum on "Business Transaction Management"
Hi Brian
Baselines work on the Business Transaction that you configure in the Application Overview Dashboard. By default the BT Web Page Requests is selected which is a Server-Side BT that measures PurePath Respone Time.
Good News is that you can also select a Page-Action-based BT which would return the Page Action Duration as a result and with that the Baseline will be calculated on the Duration.
So - all you need to do is to create a Page-Action-based-BT. You could create a similar one than Web Page Requests where you split by Page Action Name. Or - create a BT that splits by Page Action Name but also filters on the most important Page Actions in the application, e.g: Login, Search, Buy, ...
Hope this makes sense
