What trade-offs do I need to consider when configuring my Controller?

[CommunityUser]

Please do not share: Internal use only

What should I be aware of when planning a multi-Controller configuration?

Table of Contents

Overview

Trade-Offs

Use Cases

Overview

Business Owners, Application Owners, Service Owners, IT Operations, and Developers are involved in configuring their organizations' environments with AppDynamics. It is important for them to understand how their applications and infrastructure map to the AppDynamics Controller/Application/Tier hierarchy.

There are many ways to model complex environments within the AppDynamics hierarchy. Quite often, the solution is to configure your environment either:

1. Across multiple Controllers
2. Across multiple Applications

Below we’ve outlined common use cases for when an organization may have multiple Controllers and the associated trade-offs to be aware of. For information on using multiple Applications, see: What trade-offs do I need to consider when configuring my Applications?

Trade-Offs

Depending on how you set up your environment, you will need to make trade-offs regarding visibility. It’s important to understand these choices before implementing AppDynamics to avoid costly changes later. These trade-offs could include:

• Business Transaction (BT) explosion if you split up Data Centers by Tier because each BT may be registered multiple times.
• Having to choose which entity is more important to monitor rather having equal visibility into all of them.

Use Cases For Configuring Multiple Controllers

In some scenarios, it is beneficial to separate your environment into multiple Controllers.

Use Cases	Best Practices for Configuration	Trade-Offs
IT Ops wants try new AppDynamics features in a sandboxed environment with a test application before deploying to a production environment.	Configure your production and test applications in separate Controllers.	App Developers, IT Ops, and/or IT Admins may need to rely on config import/export tools to keep configurations in sync across the production and test environments.
App Developers want to run performance tests on their test applications. IT Ops is concerned that the load will affect production.	Configure production and test applications in separate Controllers so App Developers can run performance tests without putting too much load on production.