I am facing an environment where we like to integrate Dynatrace in the continuous integration process. (MS Build). Regularly running load tests, and maybe even automated in the future, is also in scope. But also regular monitoring of the test environment is in scope.
What would dynatrace recommend as server setup?
The regular test environment would require continuous session storage while the CI preferably starts and stops sessions for each test run, but multiple ci agents can run at the same time. How would dynatrace deal with that.
Also the load tests would best be kept in separate sessions which is easier to work with later on.
Do we need 3 different Dynatrace servers or can these things be combined?
Answer by Bert H. ·
We can't use the tagged web requests for the load test as the application has no HTTP binding, but .Net WCF TCP. It's too bad because the tagged web requests work very well.
But indeed, one dynatrace server for the 3 cases would be good for us as automatic session creation is not that crucial for us and sessions can still be created later on.
Answer by Kristof R. ·
I am facing a similar request at a client: for each test run, regardless of the type (unit/performance/load/webapi) we should be able to easily extract a session that matches that test run id. As we tag the tests in AppMon already anyway, an aditional REST interface that can store/export a session for that test id shouldn't be to far a stretch?
Answer by Andreas G. ·
Here is an additional idea: What if you tag your Load Testing Requests with the specific test build information or CI build information or any other type of software build information using our x-Dynatrace header files, e.g: TE (=TEst Name) field. At the end of the each load test you will always be able to look at the data from one particular run as you can filter your dashboards by that TE value. You can then do things like:
a) export a session from the continuous session storage or
b) compare different load tests even though they all come from the continuous session storage
This can also be automated!
Answer by Wiktor B. ·
Dynatrace server can record sessions for multiple system profiles at the same time, so if you have a way to separate your data into system profiles, I think you should be good. In case the ci agents are working on multiple builds of the same code base at the same time, than I think there's no good way to handle that. Even having multiple DT servers would mean that the data would be fragmented; some builds on server #1, some on server #2, etc.
Sending email on completion of test run 2 Answers