Keynote integration & multi-step transaction capture
Hi-
I have a question on behalf of a customer (Quintin Paulson @ Central 1 Credit Union) around using dynaTrace with Keynote to reflect the timers/transactions in a dashboard.
He has followed the instructions on requesting the header from: https://apmcommunity.compuware.com/community/display/DOCDT42/Integration+with+Web+Load+Testing+and+Monitoring+Tools
However, the challenge is it only represents the first page... each of their keynote synthetics is a multi-step transaction and thus the timers for Page 2, 3 and beyond are not captured because the header shown under "tagged web requests" only represents the first page.
I have to imagine using multi-step transactions is pretty standard, not only for Keynote users but for Gomez users... so how do we capture the 2nd, 3rd etc.. pages? is there a technique that allows us to do this either in dynaTrace or in the actualy scripts they use with keynote?
appreciate any color or feedback anyone can offer.
Thank you.
~Brendan
The key here is that you need to configure your Keynote/Gomez/... scripts in a way that every Step sends a different dynaTrace HTTP HEader Tag. If they have multiple pages I recommend to e.g: use the Timer Name (=NA) value to represent the current Page. The newly added Script NAme (=SN) and Test Name (=TE) would keep the same value as these synthetic requests essential all come from the same test and Script.
Once that is accomplished you should see the different pages in the Tagged Web Request dashlet.
A tip: the Tagged WEb Request DAshlet by default groups by Timer Name. If you also want to see the values for Script or Test Name you can change the Grouping of this dashlet through the Context Menu -> Group By Option
Andi
Further to the comments from Brendan above.. Is it possible to put threshholds on the error rates?.. My issue is that for "Applications" with low traffic, a single 404 or 500 error can often put the error rate over the norm, and we get a ton of spam emails.. As we have 300+ Applications, quite a few of which have very little traffic we get this quite a bit.
Appreciated.
Starting with dynaTrace 4.2 we have a new dynamic baselining feature. One of the metrics it baselines is the Failure Rate - and - it takes actual throughput into consideration.
So - what you need to do is to define a Business Transaction that covers your monitored transactions, e.g: Split by Tagged Timer Name. You can then put this BT on the new Application Overview Dashboard. dynaTrace will then automatically start baselining each individual BT Result (every split value) and will alert you in case something is out of the norm. And - as I said - our baselining takes throughput into consideration.
More on baselining and the App Overview can be found in the doc and in the dynaLearn Webinars we did:
EMEA Community Member of the Month - November 2018
Announcing Dynatrace's EMEA Community Member of the Month for November 2018, Mathieu C.! Click here to read more! LATAM Community Member of the Month - November 2018
Announcing Dynatrace's LATAM Community Member of the Month for November 2018, Rene S.! Click here to read more!