I have configured a transaction in Enterprise synthetic ,and I could see the C-N-S time for that transaction
I would like to know what is the mechanism it will follow to obtain C-N-S time.
In one of my usecase I could see most of the time its spending on Client tier, where as in reality its not on Client tier more on server tier.
so ,I would like to know how the tool is determining the CNS values ?
Can anyone help me on this ?
Answer by Yuriy L. ·
There are two parts in your post: general information about CNS and a higher than expected client time you are observing.
For the first part I’d recommend that you start with the following documentation and forum pages:
Please also take into account that Dynatrace Network Analyzer (DNA) calls are made through Open Active Script API Methods and Properties calls related to the transactions, rather them directly from the VBA code. In turn, these calls are normally made through the Framework StartTrace and StopTimerAndTrace calls, rather than directly from the script.
Talking about higher than expected client time, while it is difficult to judge without specific information, this is often a consequence of starting the transactions prematurely. Transactions should not include user actions related to filling in information without communication to the server. Please review Representing Transactions in the Script.
Please consider opening a support ticket if you cannot address your problem with the information in the Dynatrace Community.
Answer by Yuriy L. ·
I would like to share the following insights on why the CNS timings (Client-Network-Server) are usually always bigger than the "Transaction Time" metric in Enterprise Synthetic Management (ESM 12.3.6 and CAS 12.3.8). We got this information from our development (special thanks to @Mani Mukherji). Here is an example of what I mean:
The Transaction Time metric is reflected on where you set the respective StartTrace and StopTimerAndTrace timing tags in your Robot script:
StartTrace sends a "StartCNS" request to the DNA module and then starts the timer for the transaction. This ensures that the DNA capture contains the packets that originate at the beginning of the transaction. The DNA module requires some time to start up and that time is captured in the "(C+N+S) - Transaction Time" difference that we see and this is working-as-designed.
The StopTimerAndTrace stops the transaction timer and obtains the CNS values from DNA - there is hardly any overhead in the latter operation and it does not contribute towards the "(C+N+S) - Transaction Time" difference.
There should always be a consistent difference of around 400 ms (on average) between the CNS and the Transaction Time, which is unavoidable and cannot be bridged.
Enterprise synthetic -OnDemandDumps 1 Answer