The Monitor tab shows system state for an object, using visual representations whenever possible. This tab helps users understand usage, alarms, issues, and remediation actions.
Monitor, Manage, and Related Objects Tabs
The following table describes the presentation of object information on the Monitor, Manage, and Related Objects tabs.
|Monitor Tab||Manage Tab||Related Objects|
|Shows system states for the open object||Shows system configurations for the open object||Shows all first-class objects that are peers or children of the open object|
|Primary goal is to support monitoring use cases for the open object||Primary goal is to edit the configuration of the open object||Primary goal is to support navigation to the objects related to the open object|
|Secondary goal is to rollup information that supports the monitoring of peer or children objects||Secondary goal is to add and remove relationships to the open object|
|Favors graphs, charts, time series plots, and tables of numbers||Favors lists, datagrids, and master/detail views||Uses datagrids only|
|Helps users understand usage, alarms, issues, and remediation actions||Allows users to edit the configuration of the open object||Allows users to view the details of related objects and to add and remove relationships to the open object|
|Does not repeat lists from the Related Objects tab||Does not repeat lists from the Related Objects tab||Does not allow diagrams, graphs, and portlets|
- Whenever possible, use visual representations to present monitoring data. These include metrics, charts, and graphs.
- If an object has related features on both the Monitor and Manage tabs, link between the two tabs.
The prescribed set of default subtabs for the Monitor tab are Issues, Tasks, and Events. By integrating with the appropriate vCenter service, the information for these tabs is automatically populated. Other common tabs are Performance, Profile Compliance, Resource Allocation, and Utilization.
- If you have a small number of monitoring tasks, integrate them in an existing subtab. For example, changing the resource allocation of children objects can go in the Resource Allocation subtab. Similarly, actions to remediate compliance issues of the container or its children objects can go in the Profile Compliance tab.
- If your monitoring task won't fit into the existing subtabs, highlight it in its own subtab. However, remember that your solution provides data side-by-side with the data for other solutions. A single custom tab works best, and if your solution needs further division of data, consider using the TOC pattern.
- Place VMware infrastructure and extensions first, followed by your solution extensions.
- Place monitoring actions directly within the tab and in the Actions menu to give users control right where they need it. For example, in the Resources Allocation tab, place actions to change the resource allocation of child objects. In the Profile Compliance tab, place actions to remediate compliance issues of the object and its children.
- Don't allow users to create a related object from within the Monitor tab. Users can perform these actions from the Actions Menu or in the Related Objects tab.