Applications at Risk
Use Search to find a template, report or dashboard by name. Search is case insensitive, supports partial entries, and will display a list of potential matches.
As you enter the name in the Search field, up to 10 potential matches are displayed. If the template, report or dashboard is shown, you can select and run it directly from the match list. You can also click All Items in the match list to go directly to the Search Results.
StorageConsole provides different navigation options to slice and examine your collected data. You can explore the data by using the APTARE customizable report templates or by using parts of your IT infrastructure as entry points. The Inventory Navigator serves as a browser for your infrastructure by object type. See also
Exploring Your Inventory.
Use the Reports tab to examine the StorageConsole catalog of templates, dashboards and reports - organized by products along with user-created, and system folders. This report is located here:
Capacity Manager > Application Capacity & Utilization > Applications At Risk
Using this report, you can identify applications that are at risk of running out of storage space. Identify
which applications are expected to run out of storage and
when.NOTE: The Applications at Risk report supports the following applications: SQL Server, MS Exchange, and Oracle Database.
Name | The application at risk. |
Risk Date | The first date of the period for which the usage is projected.The risk date is based on the historical growth of the application’s usage. |
Usage | The projected usage based on the average usage history (or historical average usage for periods in history). |
Projected High-Water Mark | The projected maximum usage based on historical average usage. |
Capacity | The database capacity. |
Current Usage | Database storage already in use. |
Threshold | If a threshold has been set for a particular application—that is, a database threshold—then that threshold is used to determine the risk. If there is no threshold associated with the application’s database, then other thresholds are checked, in the following sequence: Host for the associated LUN/Filesystem/Database, then Host group to which the host belongs, and then the Top-level, global host group. If no threshold settings are found at the above levels, the system defaults are used: 90% for Critical, 70% for Warning, and 30% for Low. Thresholds can be set by an administrator using Admin > Reports > Threshold Policies. |