You can create a number objects to help simplify the monitoring, alerting, and reporting process. Objects represent reusable definitions you can execute to perform specific tasks. Each object you can create belongs to a specific object type.
The main object types appear in the product function tree and are described in the following table:
|
Object Type |
Function and Use |
|
Groups |
A group represents a user-defined set of related objects against which you want to run monitoring and reporting jobs. An object represents a storage resource, such as a computer, fabric, storage subsystem, etc. For example, if you want to scan all of the computers in your Payroll department, create a computer group named Payroll and populate that group with the individual computers from the Payroll department. Then, whenever you want to collect information about those computers, you can simply select the computer group named Payroll when defining a monitoring job. As computers are added or removed from the Payroll department, you can simply update the Payroll computer group to reflect those changes. |
|
Discovery |
Use discovery jobs to find new CIMOMs, Out of Band Fabrics, Windows Domains, and NAS filers that have been introduced into your environment. |
|
Probes |
Use probe jobs to collect statistics on the storage assets in your enterprise, such as computers, disk controllers, hard disks, clusters, fabrics, storage subsystems, LUNs, tape libraries, file systems, etc. The results of probe jobs are stored in the repository and are used to supply the data necessary for generating a number of reports. |
|
Alerts |
Alerts enable you to define conditions for storage-related events that occur within your environment. You can define alerts as part of monitoring jobs, or use the Alerting nodes within the different managers to define resource-specific alerts. For example, you can use the Alerting > Computer Alerts node within Data Manager to alert you if a computer's RAM increased or a new disk was detected. |