Prepared By: Srikanth Kota

Employee ID: 171848

Dynatrace for Performance Testing

With the help of Dynatrace we can capture Application level, Infrastructure level(CPU, Hardware, OS level), Database level Statistics.
Using this we can find out the rootcause by which level, which method, which I/O operation causing the issue and which purepath
have the issue.

Dynatrace Working:

• Dynatrace server should be installed on your system and it consists of host and agent . It has a dashboard through which we can
diagnose our system on one place.

• Our server can easily interact with other agent if we want , for that we have to run some command through terminal and then
we can easily watch the user interaction and also we can customize the time.

When the scripting is completed and started execution, Dynatrace can Perform Application Level Monitoring, System level Monitoring and
Database level monitoring.
1. Select your Server and system profile from the drop down.
2. Click on Dashlets, Select purepaths. It will display all the Transactions during the execution.
3. On the right top click on filter icon for Filtering for our particular agents, application, Timeframe.
4. Filter the purepaths based on the highest response time. If that is not meeting the given SLA, We have to drilldown for the root cause.
5. For Application Size analysys, Majorly check for the Errors Dashlet, Purepaths, database dashlet for connection pool size utilization, web
requests and methods
6. Right Click on the purepath, it allows to drilldown the rootcause in Method level, database level, Web Services, Transaction flow.
7. In the Bottom pane it gives the view of Contributors to that purepath,Errors, Tree, Transaction flow and Api distribution.

PUREPATH: It is a round trip of a request. PurePath technology uniquely captures and analyzes every single transaction end to
end across every tier of your application technology stack—beginning at the browser and extending through all services, all the
way down to the code and database level.

first of all you have to differentiate the breakdown of PurePaths and the breakdown of methods:

•PurePath breakdown: this breakdown relates to the sum of all methods/subpaths, NOT the response time and NOT the
duration

•Method breakdown: this breakdown relates to the total time of the method (including called methods)

Monitoring:

For Monitoring Server Health(about CPU, Memory and IO usage), Click on open start center on left slidebar --> Click Monitoring --> Select
“open host health overview”. We can able to monitor the agent CPU health. While executing the load test, If the CPU usage exceeds the given
SLA we report it as abnormal issue.

1. Hard ware level monitoring

Once we selected application --> session-->process level-->thread dump, CPU sampling we can take, memory sampling, transaction flows,
health of each &every process this for one app server.

2. Application level:
-->goto dynatrace client and verify process level and find if any infrastructure level issues if there is any no infrastructure level issues

-->then business flow dash let and where you can check the same transaction.

-->Then Right click on the transaction flow diagram where you can check which layer is taking longer time-->R.C on that-->drilldown--
>purepath.

-->keep the transaction in ascending or descending order you can take the highest response times.

-->R.C on that and go to pure path methods.

-->where you can check the which method are executing and which is taking longer time and which EJB are executing and which is taking
longer time and which servlets are executing and which is taking longer time and which packages are executing and all the internal
information will be available along with which operations is taking longer time.

-->Right Click and copy the details and thread details and paste it to developer.

Data base level:

right click--> drill down--> database exception, or data base hotspotsWhich query is executed

 Check for the pool usage in Database dashlet if it exceeds the expected statistics. Report that.

For knowing errors:

Add dash let-->error & exception through adding this we can check any errors

Errors-->right click --> drill down-->it will show transaction method errors.

To take the thread dump in dynatrace go to session overviewprocess barprocess dialog.

The process Dashboard gives the clear view of Threads running,