Working with Components and Component Groups

A component is a single data point collected as part of an application profile. Some application profiles can be edited, in which case individual components can be added to or removed from the profile. For editable application profiles, components can also be added to or removed from specific instances as opposed to the entire profile.

Adding components to an application profile helps create the foundation of the application profile. After adding components to an application profile, you must create an application instance to monitor an application on a device.

To add components:

1. Select an application profile displayed, click Edit Application Profile, then click Add components. If the application profile does not allow for the addition/removal of components, View Application Profile is seen in place of Edit Application Profile.

   OR

   Select a specific instance and then click Add components. Individual components can be added to specific instances even if the application profile overall is not editable. The Add Components dialog containing the Component Library appears.

2. Click the icon to the left of the component types you want to add to the application profile or instance. This expands the Component Library to display available component options.
3. Use the up and down arrows to specify the number of components of each type to add.
4. Click Add Selected. Configuration dialogs for each added component appear in the Component grid.
5. Use the Test Device browse button (...) to select a specific device on which to test a component if desired. If no test device is selected, the component is tested on the test device associated with the application profile. Test devices are not saved as part of the application profile.
6. Configure each component as needed. Component configuration fields vary depending upon type. Refer to the Component Library for individual component descriptions and their corresponding configuration fields.
7. Click Save.

To remove a component from an application profile or instance, select Delete from the applicable Options menu.

To test components:

• Click the applicable Test button to test a single component.
• Click Test all to test every component.
• Use the selection boxes at left to select components and then select For selected > Test to test multiple components.

A critical component group is a grouping of components that contains specific logic to allow for complex evaluation of the up/down state of an application. For example, given four components A,B,C and D, the following logic can be applied, so that if A and B are down or C and D are down the application is placed into the down state. ((A and B) or (C and D)). Critical component groups are always considered "critical", in that if a critical component group is evaluated to be in the down state, the entire application is in the down state.

Components can be added to or removed from entire application profiles or specific instances.

For example, you can create a critical component group called Device Utilization and assign the following components to the group:

• CPU Utilization
• Disk Utilization
• Physical Memory Utilization
• Virtual Memory Utilization

You can then assign the following state logic to the critical component group: If CPU Utilization and Virtual Memory Utilization equal Down and Disk Utilization equal Warning, then the component group is Down. Since this component group is considered "critical", the application instance that contains this critical component group would also be Down.

There must be at least two components included in a critical component group. For more information, see Working with critical component groups.

To add a critical component group to an application profile:

1. Select the application profile for which you want to add a critical component group, then click Edit/View Application Profile. The Components list appears.
2. In the Components section, click Add critical component group.

   The Critical Component Group information displays.

3. Enter a unique name and description if desired for the component group, then select a specific state configuration. For example, if CPU Utilization component is down and the Disk Utilization component is down, then the component group is down.
4. Click Save.

To add a critical component group to an application instance:

1. Create an application instance.
2. In the Components section, click Add critical component group. The Critical Component Group information appears.
3. Ensure the critical component group is enabled.
4. Select the desired action policy to be applied and executed when triggered.
5. Select a configuration for the critical component group. For example, if CPU Utilization component is down and the Disk Utilization component is down, then the component group is down. Please note, when a critical component group is added to an application instance, not inherited from the profile, you must add additional unique components for the critical component group to evaluate for application states.
6. Click Save.

To copy components and critical component groups, select Copy from the Options menu of the individual component or critical component group you want to duplicate.

See Also Application Monitoring with WhatsUp Gold Understanding WhatsUp Gold Application Monitoring Terminology Preparing to Monitor Applications Discovering Applications Working with Application Profiles Working with Application Instances Working with Discrete Applications About Action Policies, Actions, and Blackout Policies and WhatsUp Gold Application Monitoring Working with Application Attributes