How the Application Monitor Works

The application monitor evaluates applications as follows:

• At design-time—Analyzes the application or specific artifacts in terms of all possible problems that could occur. To determine this worst possible situation, suppression options (such as those used with forms) are ignored. The application monitor provides information about how to fix the design flaws it encounters.

• At runtime—Internal governors perform checks that may prevent users from performing particular actions if the design flaws found are not resolved.

Use the application monitor to analyze the following:

• Block storage plan types

• Dimensions

• Simple forms

• Standalone business rules

• Planning unit hierarchies

• Reporting mappings

• Export data functionality

To optimize the user experience and performance of the application and to ensure that the application monitor provides a warning when thresholds are in danger of exceeding optimal limits, you must set appropriate thresholds for the artifacts listed above. The threshold values you choose are dependent on many factors; for example, hardware, number of users, and so on, and these numbers will change based on your requirements. For example, if you want your application to be restricted to a five-year plan, set the Years threshold to five. Then the application monitor will warn you when this threshold is violated.

The system is highly sensitive to the artifact types monitored by the application monitor. These thresholds must be set based on the limits that were determined during user acceptance testing. See Setting Limits for Application Monitor Warning and Error Thresholds.