Exporting transactions recorded in dynaTrace sessions to jmeter
Hello everyone,
I was curious as to if there were any means (standard, or through a configuration or through a development) to export faulty transactions recorded in dynaTrace to some load testing tools like jmeter.
That would be a very interesting functionality for scenarios like this one: imagine that you have found a problem in one of your transactions while monitoring your production environment; let us say the root cause for this problem is within your application code; then you need to modify the code then test using the testing environment to see if the problem has disappeared and test for regressions as well; to test it, you need to replay the faulty transaction (usually this is done with some load testing tool like jmeter) but for this, you need to manually describe the transaction within your load testing tool and you may not replicate the same conditions (session parameters sent, browser-agent type, cookies, data stored, ...) as when the problem occurred in your production environment.
So my question is if there was some way to export that exact transaction recorded in dynaTrace to some format that could be automatically loaded into some load testing tool (jmeter if possible) ? I don't mind if you suggest some way that involves coding a plugin or such.
Thank you for your help.
Youssef
Hello Andi,
Thank you for your reply. Very interesting indeed. Just what we might need. I'll look into it and try.
Youssef Kadri
We have a very powerful REST Interface that allows you to extract data from dynaTrace. I think you have multiple options
a) Automatically store a dynaTrace session for your JMeter Test Runs: Sessions (REST)
b) Extract the raw data from a dashboard for your individual transactions that you want to analyze: Server- and Clientside XML Reporting
Especially option B is probably most interesting for you. When you execute a test with JMeter and put our X-dynaTrace HTTP Header on your requests as explained here - Integration with Web Load Testing and Monitoring Tools - then you get the PurePath ID returned as an HTTP Response Header. You can now take this PurePath ID and use it with the Server-side reporting interface. You can create a dashboard in dynaTrace that for instance has a PurePath, Database or Methods dashlet on it. Then you exeucte the REST Interface to query that dashboard but also specifying that PurePath ID as a filter
Andi
