Hi,
if you have a typical scenario with three environments: Developer, Test (or preproduction) and Production, what's the recomended strategy to monitor these environments, one separated Dyantrace server for each environment or separated system profiles in the same Dynatrace Server?
Thanks! Josep Maria
Answer by Rick B. ·
Separate server at least for production, as it's a separate license type. I've had scenarios where customers have had one server which covered both the test/dev stages and also customers which allocated a separate server for each of their lower environments. Consider in your design not only our normal sizing recommendations but user access patterns to Dynatrace AM itself, whether developers will be doing a lot of analysis on large data sets or memory samples, etc. as these can be strenuous on a system where we're also monitoring a load test on a separate System Profile.
If you're a relatively small shop you can probably get away with one DT server for prod and one for pre-prod (just make sure to check your assumptions against our sizing information in the documentation)
Hope that helps,
Rick B
Answer by Josep C. ·
Hi richard.boyd@dynatrace.com,
your answer helped a lot! So, in a production environment, you suggest to create oen separate system profile to try our monitoring changes in a preproduction environment?
JANUARY 15, 3:00 PM GMT / 10:00 AM ET