) This ensures that the HTML tag is not treated as HTML by the destination system From the Enterprise Manager Grid Control, click Preferences at the top of the page By default the General page is selected END LOG_CRITICAL_ALERTS; [IF REPEAT_COUNT EQ "1" AND SEVERITY EQ "CRITICAL" THEN] # emnotificationshort_format_length=155 Passing Corrective Action Execution Status to an OS Command or Script Databases (single instance only) Step 3: Register your PL/SQL procedure as a new notification method Segments Approaching Maximum Extents Count All Objects You can edit an existing rule (or create a new notification rule), then go to the Methods page In the list of Advanced Notification Methods, select your notification method and click 'Assign Method to Rule' To assign multiple rules to a method or methods to a single rule, see Assigning Rules to Methods or Assigning Methods to Rules 15 CREATE TABLE alert_log (target_name VARCHAR2(64), RAW(16) INACTIVE_STATUS #!/bin/ksh MGMT_NOTIFY_COLUMNS G_SEVERITY_NO_BEACONS BLACKOUT END Tue Oct 28 05:00:02 2006 VARCHAR(256) For metrics that monitor a set of objects, the KEY_VALUE indicates the specific object that triggered the severity For example for the Tablespace Space Used (%) metric that monitors tablespace objects, the KEY_VALUE is 'USERS' if the USERS tablespace triggered at warning or critical severity Enterprise Manager supports integration with third-party management tools through the SNMP For example, you can use SNMP to notify a third-party application that a selected metric has exceeded its threshold Agent UnreachableAgent Unreachable Resolved From the Grid Control console, click Preferences By default the General page is selected VARCHAR2(512) Numeric code identifying the severity level See Severity Code table below FAILED_RETRIED_STATUS exit 0 Name of the notification rule that resulted in the execution of the corrective action Repeat steps three through seven for each administrator Agent [MTRIC_NAME_LABEL]=[METRIC_NAME] echo notification rule is $RULE_NAME /u1/results/alertmsgtxt Example 4-9 HP OpenView Script # emnotificationos_cmd_timeout=30 7 Follow the directions on the Edit Schedule Definition: E-mail Addresses page to modify the notification schedule Table 4-5 Metric Severity Attributes Name Datatype Value Specify the administrator who's notification schedule you wish to edit and click Change PL/SQL Procedure Critical Corrective Actions on Target Down Hits (% of requests) 10 echo target name is $TARGET_NAME /u1/results/alertmsgtxt TARGET_NAME To subscribe to a notification rule you create, while creating the rule, go to the Actions page and check the Send Me E-mail option For example: Create the PL/SQL procedure on the repository database using one of the following procedure specifications: Click Edit Schedule Definition The Edit Schedule Definition: Time Period page appears If necessary, modify the rotation schedule Notification methods based on SNMP traps must be configured by an administrator with Super Administrator privileges before any user can then choose to select one or more of these SNMP trap methods while creating/editing a notification rule You can add comments to your script by prefacing a single line of text with two hyphens -- For example, # The maximum size of a short format email PROCEDURE p(job_status_change IN MGMT_NOTIFY_JOB) Description of Figure 4-2 Enabling Repeat Notification for an OS Command Notification Method An e-mail address can have up to 128 characters There is no upper limit with the number of e-mail addresses Archive Area Used (%) All Objects STATE_CHANGE_GUID RAW(16) Name of the Enterprise Manager administrator who owns the rule DBMS Job UpDown Target global unique identifier Request Processing Time (seconds) Passing User-Defined Target Properties to Notification Methods OS Command Listeners -- Code added on 8/3/2009 [IF REPEAT_COUNT NEQ NULL] VARCHAR2(1290) Boolean operators – used in IF-ELSE constructs only SNMP Trap Host Name machine1usoraclecom Value: Warning Run Queue Length (5 minute average) RULE_NAME NUMBER(2) The following table lists all reserved words and operators used when modifying e-mail scripts Listener Availability You can access the out-of-box notification rules by clicking on Preferences on any page in the Enterprise Manager console and clicking Public Rules in the vertical navigation bar If the conditions defined in the out-of-box notification rules meet your requirements, you can simply subscribe to receive e-mail notifications for the conditions defined in the rule by clicking on Subscribe column in the row of the Public Rules table that corresponds to the notification rule that you are interested in Click Apply to save your changes The corrective action name DOWN The notification method based on a PL/SQL procedure must be configured by an administrator with Super Administrator privileges before a user can select it while creating/editing a notification rule NUMBER(2) The statement above will be true when the attributes of the alert match the following condition: When a severity occurs for the target, the notification system creates an instance of the MGMT_NOTIFY_SEVERITY object and populates it with values from the severity The severity codes in Table 4-6 have been defined as constants in the MGMT_GLOBAL package and can be used to determine the type of severity in the severity_code field of the MGMT_NOTIFY_SEVERITY object METRIC_NAME MS Agent time skew (mins)Consecutive metadata upload failure count Name of the Enterprise Manager administrator who owns the notification rule Click Create NUMBER The severity code of the alert that caused the corrective action to run See Table 4-6, Severity Codes Passing corrective action status change attributes (such as new status, job name, job type, notification rule, or rule owner) to PL/SQL procedures or OS commands/scripts allows you to customize automated responses to status changes For example, you many want to call an OS script to open a trouble ticket for an in-house support trouble ticket system if a critical corrective action fails to run In this case, you will want to pass status (for example, Problems or Aborted) to the script to open a trouble ticket and escalate the problem The Short Format (Example 4-4) sends a concise, text e-mail that is limited to a configurable number of characters, thereby allowing the e-mail be received as an SMS message or page The content of the message can be sent entirely in the subject, entirely in the body or split across the subject and body For example, in the last case, the subject could contain the severity type (for example, Critical) and the target name The body could contain the time the severity occurred and the severity message Since the message length is limited, some of this information may be truncated If truncation has occurred there will be an ellipsis end of the message METRIC_VALUE User Name - myadmin UP Kind: OctetString Disk Device Busy (%) Message=Filesystem / has only 7607% available space Value: 12 object(s) are invalid in the SYS schema Step 3: Subscribe to receive e-mail for notification rules Name HP OpenView Console The time when the target status change was last detected and logged in the management repository VIOLATION_CONTEXT Description Notification method to open a trouble ticket in the event NULL VARCHAR2(256) METRIC Metric generating the severity This variable is not set for policy violations Entries in the emomsproperties file define the size and format of the short e-mail Step 4: Assign the notification method to a rule SEVERITY_GUID N/A E-mail customization template scripts support three main operators Troubleshooting Notifications Repository Operations Availability There can be more than one OS Command configured per system The new status of the corrective action See Table 4-9, Corrective Action Status Codes for a list of possible status conditions Attribute Value: 1 1 Environment Variable Description Type of target on which the severity occurred Targets are defined as any monitorable entity, such as Host, Database, Listener, or Oracle HTTP Server You can view the type of a monitored target on the All Targets page TIMEZONE DOWN KEY_VALUE Passing Job Execution Status Information Oracle HTTP Server JOB_OWNER INSERT INTO alert_log (target_name, alert_msg, occured) Control Structure Description You must establish the maximum size your device can support and whether the message is sent in subject, body or both G_SEVERITY_UNKNOWN Two or more attributes can be separated by '|' character For example, Web Cache Availability and Critical States Passing Alert and Policy Violation Information to a PL/SQL Procedure JOB_OWNER Important: Passing Corrective Action Execution Status to an OS Command or Script WHEN OTHERS UNIX: $ENV_VARIABLE Kind: OctetString Command: 4 Step 4: Assign the notification method to a rule Syntax Elements More about Short E-mail Format Other metrics can have any of the following severities: A comma-separated list of name-value pairs that show the policy violation context The owner of the notification rule that caused the PL/SQL notification to be sent The name of the policy rule in the alert that caused the corrective action to run Not set for metric severities Each administrator to which you want to send e-mail notifications must have a valid e-mail address Memory Utilization (%) Reserved Words and Operators Type of alert severity For example, severity types that relate to a target's availability are: Note: Use / to escape and [ or ] if you want to add attribute names, operators, or IF clauses to the actual e-mail Table 4-8 lists all corrective action status change attributes that can be passed: [IF SEVERITY_SHORT EQ W] -- for Warning alert Type=Host To create your own notification rule: Inside the IF block, the values need to be contained within quotation marks " " Enterprise Manager will extract the attribute name and its value based on the position of "EQ" and other key words such as "and", "or" For example, Type of severity For example, severity for a target's (availability) status metric are: RULE_OWNER Critical SUSPENDED_LOCK_STATUS ABORTED_STATUS N/A SEVERITY VARCHAR2(132) Name of the target on which the severity occurred RAW(16) METRIC ERROR START JOB_NAME 4 Notifications Setting Up a Notification Schedule VARCHAR2(128) VARCHAR2(64) HOST For metrics that monitor a set of objects, the KEY_VALUE_NAME indicates the type of object monitored For example for the Tablespace Space Used (%) metric that monitors tablespace objects, the KEY_VALUE_NAME is 'Tablespace Name' Example 4-6 shows information required for the notification method # The maximum number of emails that can be sent in a single connection to an You can use IF & ELSE & ENDIF control structures You can also use multiple conditions using AND or OR Nested IF statements are not supported Note: Name Trouble Ticketing Down NUMBER(2) G_SEVERITY_CLEAR Example 4-12 SNMP Trap Required Information To check NULL value for attributes - used in IF-ELSE constructs only CPU Usage (%) Metric global unique identifier Conventions used to access environmental variables vary depending on the operating system: Table 4-7 Environment Variables The unique id of the corrective action Value: 28-OCT-2006 04:59:10 (US/Eastern GMT) Notification methods based on OS commands must be configured by an administrator with Super Administrator privileges Add this OS command as a notification method that can be called in Notification Rules Log in as a Super Administrator, click Setup and then Notification Methods from the vertical navigation bar From this page, you can define a new notification based on the 'OS Command' type See Adding a Notification Method based on an OS Command or Script Name: 1361411111511161 Step 2: Define Administrators' Notification Schedules From the Edit E-mail Template page, you can modify the content of the e-mail template Enterprise Manager uses to generate e-mail notifications Extensive information on script formatting, syntax, and options is available from the Edit E-mail Template page via imbedded assistance and online help PROCEDURE LOG_CRITICAL_ALERTS(severity IN MGMT_NOTIFY_SEVERITY) Setting repeat notifications globally at the notification method level may not be provide sufficient flexibility For example, you may want to have different repeat notification settings based on the metric type and/or alert severity Enterprise Manager accomplishes this by allowing you to set repeat notifications for individual notification rules Repeat notifications set at the rule level take precedence over those defined at the notification method level Comments may also be placed at the end of a line of text RAW(16) For metrics that monitor a set of objects, the KEY_VALUE indicates the specific object that triggered the severity For example for the Tablespace Space Used (%) metric that monitors tablespace objects, the KEY_VALUE is 'USERS' if the USERS tablespace triggered at warning or critical severity EXECUTING_STATUS Agent Unreachable Resolved Table 4-9 Corrective Action Status Codes 215 AGENTDOWN_STATUS # emnotificationemails_per_connection=20 NUMBER(2) Step 2: Set up a Notification Schedule Step 2: Create the PL/SQL procedure on the Management Repository then Table 4-1 lists all default notification rules These are all owned by the SYSMAN user and are public rules Description Notification method to log trouble ticket for a severity occurrence Value: Invalid Object Owner For metrics that monitor a set of objects, the KEY_VALUE_NAME indicates the type of object monitored For example for the Tablespace Space Used (%) metric that monitors tablespace objects, the KEY_VALUE_NAME is 'Tablespace Name' Specify the e-mail associated with your Enterprise Manager account All e-mail notifications you receive from Enterprise Manager will be sent to the e-mail addresses you specify For each administrator, define an e-mail address This sets up a 24x7 notification schedule for this user that uses all the e-mail addresses specified The unique id of the corrective action execution Attribute Datatype Additional Information Click Subscribe to Rules The Subscribe Attn_your..Credit_score at No cost!. See... it now
