Add Monitors to a Template or the Policy
Add monitors to the template that are specific to the workload handled by a server or a server group. The following procedure is similar for adding monitors to a policy.
casa
Add monitors to the template that are specific to the workload handled by a server or a server group. The following procedure is similar for adding monitors to a policy.
Follow these steps:
- Click theResourcestab, open theConfigurepane, then expandMonitoring Templatesand appropriate subcategories.
- On theTemplate Listpage, select the template.
- On the Summary page for the selected template, clickMonitors.
- Click the Resources tab and open the Configure pane, then expand Monitoring Templates and the appropriate subcategories.
- On the Template List page, select a template.
- On the Summary page for the template, click the Monitors tab.The Summary page displays a list of monitors that the policy manages.
- Select the monitor to add:
- ThresholdThe agent monitors the servers or the server groups against specified thresholds. The agent sends a trap when thresholds are breached.
- ProcessThe agent monitors a process, service, or process table objects against specified thresholds. The agent sends a trap when thresholds are breached or the state of a process (running or stopped) changes.
- Log FileThe agent monitors UTF-8 encoded system or application log files by searching for strings that are specified as regular expressions. The agent sends a trap when a match occurs.
- Windows EventThe agent monitors the Windows event log entries using different filters (event source). The agent sends a trap when a match occurs.
- HistoryThe agent provides the historical data collection for manager-side baseline and trend analysis. The agent uses the metrics to provide a picture of average system performance during a specific time interval.
- Process GroupThe agent defines a group of processes and monitors that group for changes. If the process group changes, the agent sends a trap.
- On the toolbar for the monitor-specific page, click + (New).A Monitor Details: New dialog opens for the selected monitor.
- On the Monitor Details: New dialog, configure the following settings for the monitor:SettingDescriptionThresholdProcessLog FileWindowsEventHistoryProcessGroupIndexDefines the table index to use.XXXXXXMonitor TypeSpecifies the monitor type to use.XPlatformSpecifies the platform.XXXXXXDescriptionDefines an optional description.XXXXXXObject ClassDefines the object class to monitor. The values refer to the available MIB tables.XXObject Class NameDefines the object class name to use for the object state model.The value is an arbitrary string (for example, FileSystems or Process).XXProcess NameDefines the process name, which is the regular expression (dependent from optional settings) to use for matching processes by name.XObject AttributeDefines the object attribute to monitor. The values refer to the available attributes of the table that is selected as Object Class. The attribute (for example, devCapacity = 1.3.6.1.4.1.546.1.1.1.7.1.14) specifies the initial portion of the MIB object (OID) to monitor with this threshold monitor.XXXObject Attribute NameDefines the object attribute name to use for the object state model.The value is an arbitrary string (for example, MemUsedPercent).XXLog File/ Directory NameDefines the path to the file or the directory to monitor.XSearch FilterDefines the search filter.XEvent LogDefines the event log to read.XEvent TypeSpecifies the event type to match.XObject InstanceDefines the object instance to monitor.For Threshold and History monitors, this value (for example,.3to monitor the third row in the device table devTable) defines the index portion of the MIB object (OID) to monitor.For Threshold monitors in some object classes, the name of the instance can be given (for example, C: instead of.3, or/varfor a Unix machine).For Process monitors, this value is the regular expression (dependent from optional settings) to use to match processes or Windows services by name. Pattern should uniquely match a single process (service). Arguments can be included (see optional settings).XXXObject Instance NameDefines the object instance name to use for the object state model.The value is an arbitrary string (for example, ApacheServer or SysVol_C).XXSource FilterDefines the source filter to use.XDescription FilterDefines the description filter to use.XIntervalDefines the evaluation interval for the monitor.For Threshold, Process, History, and Process Group monitors, define the Interval value in multiples of 30 seconds.For Log File monitors, define the Interval value in minutes.XXXXXBucketsDefines the number of samples to collect.XAdd to Performance CubeSpecifies whether to collect performance cube data.XUser NameDefines the user name to match in addition to process name regular expressions.XGroup NameDefines the group name to match in addition to process name regular expressions.XSeverityFor Threshold and Process monitors, defines the severity to use for the object state model. Define this value on the Threshold Configuration page or the Process Configuration page as appropriate.For Log File and Windows Event monitors, defines the significance of the monitor on a match.For Process Group monitors, defines the significance of the monitor on a group change.XXXXX
- On the Threshold Configuration page and the Process Configuration page, configure the following settings for the monitor:
- OperatorSpecifies the operator to use.
- ValueDefines the value to use.
- Sample TypeSpecifies the sample type to use.
- On the Maintenance Window page, configure the following settings for the monitors:
- StateSpecifies whether the monitor maintenance entry isactiveorinactive.
- Start TimeDefines the time at which the monitor switches off and the maintenance window begins.
- Stop TimeDefines the time at which the monitor switches on and the maintenance window ends.
- On the Optional Settings subtabs for all of the monitorsexceptHistory, specify flags as appropriate.
- (Optional) Repeat the process for other monitors.
- Click Save.The monitor is loaded to the policy or the template.