Configure Object Aggregation
By default, the hse agent aggregates monitors in a managed object that contains the same values for the object class, instance, and attribute properties. For example, the agent combines all monitors with a class of SysHealth, an instance of CPU, and an attribute of SysTime in an aggregate managed object.
casa
By default, the
CA SystemEDGE
agent aggregates monitors in a managed object that contains the same values for the object class, instance, and attribute properties. For example, the agent combines all monitors with a class of SysHealth, an instance of CPU, and an attribute of SysTime in an aggregate managed object.You can configure the agent to aggregate objects on higher levels when you define
CA SystemEDGE
policy. You can also configure other aspects of agent behavior that are related to object aggregation and the state management model.Follow these steps:
- Click theResourcestab, open theConfigurepane, expandPolicies, and clickSystemEDGE.
- On theAvailable Policiespage, select the policy in theAvailable Policiestable.
- On theSummarypage for the policy, clickControl Settings.
- On theControlspage, clickAggregate Monitors.
- On theAggregate Monitorspage, select one or more check boxes to specify aggregation levels.The check boxes represent higher aggregation levels than the default, up to aggregating all monitors to one top-level agent object. Specifying aggregation levels lets you create a tiered object architecture that propagates status up to the level you specify.
- Configure the following other settings, then clickSave Policy:
- Send legacy traps for all aggregated monitorsSpecifies whether to send legacy traps for all monitors that comprise a managed object. By default, the agent only sends a state change trap for the monitor with the highest severity, even if other monitors in the object experience threshold breaches.
- Execute commands of all aggregated monitorsSpecifies whether to run action commands for all monitors that comprise a managed object. By default, the agent only runs an action command for the monitor with the highest severity, even if other monitors in the object experience threshold breaches.