When you first create a business application in AppDynamics, the Default Scope ensures that all tiers for the application have a default automatic discovery rule for every agent type. Because the scope configuration model is highly configurable, the Controller UI enforces validations in the following cases:
- When you change the automatic discovery rules for a scope.
- When you assign or reassign tiers to a scope.
When you attempt to make an invalid change, the Controller prevents the change and displays a message in the Controller UI.
These validations ensure that after configuration updates every tier in your business application has the default automatic discovery rule for its agent type. They also ensure that there is an automatic discovery rule for all agent types to handle any prospective tiers you add to your application.
Existing Tiers
Every existing tier must belong to a scope that includes an automatic transaction detection rule for the tier's agent type. For example, a Java tier must belong to a scope with a Java automatic transaction detection rule.
The following rules apply:
- You can remove a tier from scope only when the tier has an auto-discovery rule from another scope.
- You can remove an automatic transaction detection rule from a scope only when tiers have auto-discovery rule from another scope.
Prospective Tiers
To ensure that any new tier you add to your application has an automatic transaction detection rule available, there must be at least one automatic transaction detection rule for each agent type in a scope of the following types:
- A scope that contains all tiers.
OR - A scope that contains all tiers excluding specific existing tiers.