Overview of Module Data Properties
The module data properties provide additional information about the modules. The Attribute Editor in the web console provides the same capabilities as the Attribute Editor in the Java Console, which is described in Chapter 10, Monitoring Data Property Attributes. You can use the Attribute Editor to customize the monitoring criteria for the module data properties. Specifically, the Attribute Editor enables you to perform the following tasks:
-
Set alarm thresholds for defined alarms
-
Specify actions to take when alarm conditions occur
-
Change the interval at which data updates on the screen
-
Define schedules for creating log files of historical data points
The Attribute Editor in the web console has one or more tabs at the top of the page that enable you to switch between different panels. These tabs differ depending on the selected object. The possible tabs are described in the following sections:
Note –
Each Attribute Editor displays one or more of these tabs, depending on the specific object to which an instance of the Attribute Editor applies.
Info Tab in the Web Console Attribute Editor
The Attribute Editor Info page provides additional information about the selected object, such as:
-
Module name, version, and description for the selected module
-
Host name for the host on which the module resides
-
Other information about the specific module, such as folder and variable in which data property information is stored
Alarms Tab in the Web Console Attribute Editor
The Alarms tab enables you to set alarm thresholds only for those data properties that have associated simple alarms. These simple alarms use the rCompare rule, which is described in Appendix D, Sun Management Center Software Rules. The Attribute Editor Alarms page enables you to set alarm thresholds for simple alarms only.
Note –
To set an alarm threshold, you must have the appropriate security permission. For more information, see Chapter 18, Sun Management Center Security.
The alarm management software offers you the following flexibility in setting your alarms:
-
Determine the thresholds that trigger an alarm of a particular severity
-
Determine when alarms are sounded, for example, only on weekdays
Simple alarms are based on thresholds. A monitored data property is greater than, less than, not equal to, or equal to a single threshold value. By contrast, complex alarms are based on a set of conditions. For more information about alarm rules, see Appendix D, Sun Management Center Software Rules.
The following table lists common simple alarm limits for monitored properties. The alarm limits are also displayed in the Parameter Description field. You can set thresholds for one or more of these alarm limits for selected data properties.
Table 17–1 Common Simple Alarm Limits in Sun Management Center Software|
Alarm Limit |
Description |
|---|---|
|
Critical Threshold (>) |
Critical (red) alarm occurs if the value exceeds the limit that is entered in this field. |
|
Alert Threshold (>) |
Alert (yellow) alarm occurs if the value exceeds the limit that is entered in this field. |
|
Caution Threshold (>) |
Caution (blue) alarm occurs if the value exceeds the limit that is entered in this field. |
|
Critical Threshold (<) |
Critical (red) alarm occurs if value is below the limit entered in this field. |
|
Alert Threshold (<) |
Alert (yellow) alarm occurs if value is below the limit entered in this field. |
|
Caution Threshold (<) |
Caution (blue) alarm occurs if value is below the limit entered in this field. |
|
Alarm occurs only during a specified time period. For example, if the value is day_of_week=fri, an alarm occurs only if the alarm condition exists on a Friday. If an alarm condition exists on Tuesday, no alarm is triggered. |
Actions Tab in the Web Console Attribute Editor
The Attribute Editor Actions page enables you to instruct the software to perform a predetermined action if an alarm occurs.
Note –
Acceptable actions include scripts that are stored in the /var/opt/SUNWsymon/bin directory. These scripts execute with root permissions.
For example, you can provide the name of a script in the critical action field. This script might send an email to a system administrator whenever a critical alarm is generated for the Load Average Over the Last 5 Minutes data property.
You can set separate actions for different alarm conditions. You can also define a single action to occur when any change happens to any of the alarm conditions. To define actions, you use the Action buttons on the Actions page.
Note –
The check boxes that are to the right of the Action buttons enable you to specify automatic or manual execution of a specific alarm action. By default, all actions are set for manual execution. Only manual actions can be modified.
Use the Alarm Action Modification dialog box to modify the registered alarm actions. Two buttons in the dialog box (Email and Generic) allow you to choose one of two options for an alarm action.
-
Enables you to specify an address, subject, and message to be sent as email
- Generic
-
Enables you to select generic shell scripts that are installed on the managed node
Refresh Tab in the Web Console Attribute Editor
Use the Refresh page in the Attribute Editor to set the refresh interval for this object. The refresh interval is the interval between the times when the Sun Management Center agent samples the monitored property. For more information, see To Specify How Often the Data Display Updates.
History Tab in the Web Console Attribute Editor
Use the History page in the Attribute Editor to save older data for a monitored property. For example, you might choose to record a history of data points every 120 seconds as identified in the sample interval. You can also specify whether to store this information in a disk file or in the memory cache.
The two types of disk files are circular, which has a maximum of 1000 lines, and text. These files are located in the /var/opt/SUNWsymon/log directory in the file that is specified in the Text File Name field.
A circular disk file is automatically saved under the name history.log. If you do not choose a file name for your text file, data are automatically saved under the name agent_default.history.
If you select memory cache, you must indicate in the Max Size (sample) field the number of data points to save. For example, if you set this field to 1000, only the most current 1000 data points are stored in the memory cache. Any older data points are discarded. These data points can be graphed. See Chapter 9, Viewing Data Properties in a Graph for more information.
Note –
You can view history data in a graph by opening the graph for the specific monitored property. If you have selected memory cache, the graph is displayed with historical data.
- © 2010, Oracle Corporation and/or its affiliates