I just started using Dynatrace Managed here and I'm having trouble organizing the applications here.
1. Here we have a datacenter with multiple applications. The best way to organize each application on the Dynatrace Managed is to create a Environment for each one?
2. There's a way to change the Environment for where the OneAgent in the hosts send their data? I want the oneagent in some hosts send the data to another environment to organize it.
Solved! Go to Solution.
I will not recommend using various tenants (environments) for each application. This is because if you have certain applications that call each other or the same services, you will not be able to see the entire flow from end to end. I do recommend ensuring that applications that communicate/call each other are in the same tenant (environment). To better organize your applications, i suggest you utilize the tagging feature in Dynatrace. This will help you identify entities that belong to individual applications. See more info on tags here. Also there is the concept of management zones that is in Beta right now that you can take a look at here. Please let me know if you have any questions.
Hello Douglas ,
I will not say complete NO to tenants but want you to analyse your needs first .
Pros of using Tenants for seggregating applications:
1) It is a good option if you want to completely seggregate monitoring of Prod/Non-Prod/QA/etc environments
2) It is a good option if your customer has security concerns like data of one BU/Environment/Vertical shuld not be visible to users of other BU/Environment/Vertical . Because if you try to achieve this using tagging/management zones, it will be a huge effort and difficult to manage as well
Cons of using Tenants for segregating applications
1) If your applications in different environments are communicating with each other and you need to see end-to-end flow , then Using tenants is a bad option(as already mentioned by NJ)
2) If you have operational requirements in your environment to have a holistic view of all hosts , all applications in your entire landscape to be published on one single dashboard , then Using tenants will land you in trouble.
Few points you must consider for your planning:
1) I suggest you to go back to drawing board and have a forecast of your environment complexity and long term needs for operational dashboards.
Once you have an idea of your environment complexity , then you can make a wise decision to use below combinations :
Tenants + Tagging
Tenants + Management Zones + Tagging
Management Zones + Tagging
2) You will also need to identify your problem notification needs & integrations where you need to make use of Alerting profiles as per below link