The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
TES can respond automatically to unusual situations that may arise while running a production schedule. Users can create predefined responses called actions. There are various types of actions ranging from sending an alert to the Tidal Web client to running a specific job when a designated condition occurs.
Certain job or system conditions have been designated by TES as “event triggers.” The occurrence of these conditions can be used to initiate or trigger a job and/or an action a user has defined.
By linking an event trigger to an action or a job, an automatic response called an event is created. When this event is associated with a condition that affects an individual job or all jobs in general, this defined response is known as a job event. If the event is associated with a condition that affects the entire system and not just jobs, this defined response is known as a system event.
Job and/or Action + Event Trigger = Event
Jobs, job events and actions are constructed in dialogs using a three-tier hierarchy. Each job can have any number of job events associated with it, and in turn, each job event can have any number of actions associated with it. A job triggers a job event only when its exception condition becomes true, which then triggers all of its associated actions.
Jobs, job events and actions can all be created separately and linked at any time. The
job-job event-action hierarchy can be linked from the
Job Event Definition
dialog and from the
Job Definition
or
Job Group Definition
dialog. In the
Job Event Definition
dialog, you can assign multiple jobs and actions to a single job event. In the
Job Definition
or
Job Group Definition
dialog, you can assign multiple job events to the job or job group, but you cannot assign actions to job events.
An action is a task or notification that is automatically performed by TES in response to a job event trigger that occurs for a specific job or job group or system event trigger. Actions are customized tasks and messages linked to a job or system event through the Job Event Definition and System Events dialogs. The job or system event is then associated with a job or job group. For example, an action to send email to the owner of a job that failed can be tied to a Job Completed Abnormally job event trigger. Another action that sends an alert message to the console can also be linked to the same job event so that two actions occur simultaneously when the job fails.
Note When multiple actions are defined for a single event, the actions are completed as the conditions to satisfy the event trigger are fulfilled.
From the Actions pane, you can view the actions that belong to you or your workgroups.
The types of actions you can choose from are:
TES lets you use system, job, job event and user-defined variables in action messages, making them applicable to many jobs. For instance, you could create an action called Job Stopped Email Notification , with variables in the message text that will be replaced at runtime with the job name and runtime. When you create a job and want to be notified if it stops during execution, you can associate the action with the job from the Job Event Definition dialog. If the job stops during execution, you receive an email referring to the job that triggered the event. You could even include in the message a variable representing the exit code at the time of completion.
From the Navigator pane, select Definitions>Actions to display the Actions pane. You must select one of the types of actions to display its pane to create or modify an existing action.
The Actions pane contains the following actions:
Note Buttons are only enabled after a type of action has been selected from the Actions pane.
This pane contains the following buttons:
Enter text that you want to search for within the columns displayed into this field.
Note This field at the top right of the grids will only search text columns that are not grayed out.
This pane contains the following columns:
Select Preferences from the View main menu while viewing an Actions pane to display the Actions Preferences dialog for actions.
From an Actions Preferences dialog, you can select which columns are displayed in the pane for the selected type of action and in what order the columns appear.
When you right-click in the Navigator pane while viewing an Actions pane, the Navigator context menu displays.
The Navigator context menu contains the following options:
After selecting a folder associated with one of the six action types, if you right-click in the Actions pane, the Actions context menu displays.
The following describes the items in the Action Types pane context menu. The same menu appears for each type of action.
The Action Definition: Email Message dialog displays when you add or edit an email message action. An email action sends an email message in response to a job event or system event. You can send email to any individual or group with a valid email address in the mail system you have chosen. A user without a valid email address (provided on the Other tab in the User Definition dialog) cannot receive notification from an Email action. The individual receiving the email does not have to be a user of TES. For more information about setting up TES for email, see Getting Started, and the Installation and Configuration Guide.
Note To send email to a TES workgroup, that workgroup (not just the individual members) must have a mailbox, or be defined as a mailing list, in your email system. For help setting up a mailbox or mailing list, see your System or Mail Administrator.
Note When creating an email message for a system event about losing your database connection, do not use variables that will not work without a connection to the database, i.e., <JobName> or <JobStatus>.
Note The To: field can accommodate no more than 1024 characters. If you attempt to enter one or more email addresses whose total characters exceed this limit, your address(es) will be truncated automatically. Your email action will then fail to reach all its intended recipients. The solution is to create a mailing list through the TES Mailing List dialog.
The Mailing List dialog displays by clicking the Browse button in the To: field in the Action Definition: Email dialog. You can select one or more addresses for email actions from this dialog. Each recipient of the email action that is selected will be highlighted in the list of available email addresses in each field.
Note To select multiple consecutive addresses, click the first email address and while holding down the Shift key, click the last consecutive address.
To select multiple non-consecutive email addresses in each field, click individual desired addresses while simultaneously holding down the Ctrl key.
Remove existing recipients in the same way by also clicking their individual addresses while simultaneously holding down the Ctrl key.
TES Email Addresses Use this field to select the email addresses of TES users. In the case that no email address is assigned to a user, their TES user ID appears in the list and is used as a local email address. Email addresses are defined in the Other tab of the User Definition dialog.
You can also use the following variables in this field:
The Action Definition: Alert dialog displays when you add or edit an alert action. An alert action can be assigned one of four severity levels: Critical , Error , Warning and Information.
Note Critical level and Error level alerts can be associated with an alert sound. However, the computer that receives the alert must have a sound card and speakers for the alert sound to be effective. Alert sounds are configured from the Sound tab of the Alerts Preferences dialog.
– Critical – Sends the highest priority alert to the Job Activity pane when the action is triggered.
– Error – Sends a high priority alert to the Job Activity pane when the action is triggered.
– Warning – Sends a medium priority alert to the Job Activity pane when the action is triggered.
– Information – Sends the lowest priority alert to the Job Activity pane when the action is triggered.
The Action Definition: SNMP dialog displays when adding or editing an SNMP Message action. An SNMP action sends a message (also known as a trap) to an SNMP manager when the associated job or system event occurs. The computer which hosts the SNMP manager does not need to have TES installed.
TES uses the SNMP community, port, and host/IP address as set in the Windows SNMP Properties dialog.
By default, the SNMP action sends the trap to just the “public” community but TES can be configured to send SNMP traps to multiple communities and hosts. Older versions of TES used the Master.Props file to configuration the use of SNMP traps. The designated recipients of the SNMP traps are now specified in an XML file called snmpconfig.xml .
To create the configuration file, the following information must be gathered beforehand:
From the information that you have gathered, you must designate a default community, host machine and port number, in that order.
The information in the snmpconfig.xml configuration file is organized as follows, first the default properties and then a listing of the communities and their host members, if any.
The following rules must be followed when creating the snmpconfig.xml file:
An example of an snmpconfig.xml file illustrating the proper file formatting and using the rules stipulated above is shown below. In this example, the default community=public, the default hostname=localhost and the default port number=162.
<?xml version=”1.0” encoding=”UTF–8”?>
<default_community value=”public”/>
<default_host value=”localhost”/>
<host hostname=”trapreceiver.mycompany.com” port=”362”/>
<host hostname=”networkaudit.mycompany.com”/>
Once the configuration file is created, it needs to be placed onto the master.
Step 1 Save the configuration file as snmpconfig.xml.
Place the snmpconfig.xml file into the TES master’s
config
directory.
If you installed the Windows master in the default location, this directory is at
C:\Program Files\Tidal\Scheduler\master\config.
If the Unix master was installed in the default location, this directory is at
/opt/Tidal/master/config
.
After the TES master restarts, it will reconfigure the SNMP settings according to the information in the snmpconfig.xml file. If you previously used the Master.Props file to configure SNMP, that configuration information is overridden. Examine the log file on the master to verify that the configuration was successful. If the snmpconfig.xml file cannot be used, the master will use the configuration specified in the Master.Props file.
The Action Definition: HP OpenView dialog displays when adding or editing an HP OpenView message action. An HP OpenView message action sends an HP OpenView message to an HP OpenView Operations software management node.
Note If you do not type a message here, there will be no content for the HP OpenView message when viewed from the HP OpenView Message Browser.
The Action Definition: Job dialog displays when adding or editing a job action. A job action adds a new job or job group to the production schedule when the associated job or system event occurs.
The Action Definition: Log dialog displays when you add or edit a log message action. A log action posts a message of your choice to the TES log when a job or system event occurs. Optionally, the same message can be recorded to the Unix console if on the Unix platform. The message can be defined as Error , Audit or Diagnostic .
– Log as Windows Event – Enable this option to log events to the console in Windows.
– Event ID – Assign an event number in Scheduler for the logging of the message to the Windows console.
The Action Definition: SAP dialog displays when adding or editing an SAP action. An SAP action sends a notification to the CCMS of a designated SAP instance that a specified event has occurred in TES.
The Action Definition: Variable dialog displays when adding or editing an update variable action. A variable action updates a user-defined variable when the job or system event occurs.
Note Only user-defined variables can be used for variable actions. Therefore, if you have not yet created your own variables, this action will not be available.
– Set Variable Value – Sets the variable’s value to the value given in the Value field. The value can be either a number, date or string.
– Increment Variable Value – If the variable is a number or date, increments the variable’s value. If the variable is a string, appends the new string value to the present string.
– Decrement Variable Value – If the variable is a number or date, decrements the variable’s value. If the variable is a string, then this option is unavailable.
For example, a variable can refer to the name of the primary printer being used. If the printer goes down, a job can track it and issue a job event that sends an email message to users explaining that the primary printer has gone down. The variable update can then be issued to change the default printer name.
You can send an email message to anyone with a valid email address in response to a job event or system event by creating an email action. You cannot send email to a workgroup unless that workgroup (not just the individual members) has a mailbox, or is defined as a mailing list, in your email system.
Note When creating an email message for a system event about losing your database connection, do not use variables that will not work without a connection to the database, i.e., <JobName> or <JobStatus>.
To add an Email Message action:
Step 1 From the Navigator pane, select Definitions>Actions to display the Actions pane.
Step 2 Select the Email folder.
Step 3 Click the Add button or right-click and select Add Action from the context menu to display the Action Definition: Email dialog.
Step 4 In the Action Name field, type a name for this action (up to 30 characters). The name must be unique.
Step 5 To make the action public, select the Public option. When an action is public, the action is available to all TES users, within the bounds of their security policy.
Step 6 Select the desired Owner from the drop-down menu in the Owner field.
Step 8 In the To field, click the Browse button to display the Mailing List dialog and select the recipients of this email action when it is triggered.
Note The From: field will be the name specified in the Mail tab of the System Configuration dialog.
Step 9 In the Subject field, type a subject title for your email message. In this field you have the option of inserting one or more TES variables.
To insert a variable, click where you want to insert the variable, and then click the Variables button and select a variable from the variables context menu.
Step 10 In the Message field, type the message to send when this email action is triggered. In this field you have the option of inserting one or more TES variables.
To insert a variable, click where you want the variable, and then click the Variables button and select a variable from the variables context menu.
Step 11 To enter a description for your email action, click the Description tab, and type your description in the Description field.
Step 12 Click OK to accept the action.
The action displays in the Actions pane and is available from the Job Event Definition and System Events dialogs.
You can send an alert to the Job Activity pane in response to a job event by creating an console alert action.
To add a Console Alert action:
Step 1 From the Navigator pane, select Definitions>Actions to display the Actions pane.
Step 2 Select the Alert folder.
Step 3 Click the Add button or right-click and select Add Action from the context menu to display the Action Definition: Alert dialog.
Step 4 In the Action Name field, type a name for this action (up to 30 characters). The name must be unique.
Step 5 If you wish to make the action public, select the Public option. When an action is public, the action will be available to all TES users, within the bounds of their security policy.
Step 6 Select the desired Owner from the drop-down menu in the Owner field.
Step 8 In the Severity Level section, select the severity level for the alert you are defining. Different severity levels can be represented in different ways. For example, Critical and Error level alerts can be made audible. Alerts of different severity levels appear in different colors on the Job Activity pane by default.
Step 9 In the Alert Message section, type the message to send.
Step 10 In this text field, you have the option of inserting one or more TES variables. Click where you want to insert the variable, and then click Variables to choose a variable from the variables menu.
Step 11 To enter a description for your alert, click the Description tab, and type your description in the Description field.
Step 12 Click OK and the action appears in the Actions pane and is available from the Job Event Definition and System Events dialogs.
You can send an SNMP message (trap) to an SNMP manager in response to a job event or system event by creating an SNMP action.
Step 1 From the Navigator pane, select Definitions>Actions to display the Actions pane.
Step 2 Select the SNMP option.
Step 3 Click the Add button or right-click and select Add Action from the context menu to display the Action Definition: SNMP dialog.
Step 4 In the Action Name field, type a name for this action (up to 30 characters). The name must be unique.
Step 5 If you wish to make the action public, select the Public option. When an action is public, the action will be available to all TES users, within the bounds of their security policy.
Step 6 Select the desired Owner from the drop-down menu in the Owner field.
Step 8 In the Severity Level field, select the severity level for the SNMP message from the drop-down menu. (Refer to your SNMP manager software documentation for an explanation of how the severity level is interpreted.)
Step 9 In the Message field, type the SNMP message. In this field you have the option of inserting one or more TES system variables. Click where you want to insert the variable, and then click Variables to choose a variable from the Variables menu.
Step 10 To enter a description for your SNMP action, click the Description tab, and type your description in the Description field.
Step 11 Click OK and the action appears in the Actions pane and is available from the Job Event Definition and System Events dialogs.
You can submit a new job or job group to the production schedule in response to a job event or system event by creating a new job action. You can specify on which agent it will run, the runtime user, and override the default command parameters in the job or job group that is submitted.
Step 1 From the Navigator pane, select Definitions>Actions to display the Actions pane.
Step 3 Click the Add button or right-click and select Add Action from the context menu to display the Action Definition: Job dialog.
Step 4 In the Action Name field, type a name for this action (up to 30 characters). The name must be unique.
Step 5 If you wish to make the action public, select the Public option. When an action is public, the action will be available to all TES users, within the bounds of their security policy.
Step 6 Select the desired Owner from the drop-down menu in the Owner field.
Step 8 In the Job Name field, click the Browse button to display the Job Search dialog.
Step 9 Select the job or job group to add and click OK .
Step 10 Adding a job group submits all the child jobs with one action. To achieve a similar result, you can assign multiple actions, each adding a separate job, to the same job event or system event.
Step 11 From the Agent drop-down menu, select the agent on which to run the added job or job group. If no agent is selected, the job or job group runs on the agent that is defined in the job or job group definition. To clear an agent, right-click the Agent field, and select Clear Agent from the context menu, or use the Delete key on your keyboard.
Step 12 From the Runtime User drop-down menu, select the runtime user.
a. If no user is defined, the runtime user in the job or job group definition is used. If the runtime user is not defined in the job or job group definition, the owner of the job or job group is used.
b. To clear the runtime user, right-click the Runtime User field and select Clear User from the context menu or use the Delete key on your keyboard.
Step 13 To override the default values (if any) in the Default field, you can enter your own values or assign variables. If an added job contains command parameters, the Override field will display them.
a. Select the parameter to override from the Override field.
b. Type the new value. You can choose from a menu of TES variables using the Variables button.
Note To override the agent used by a job, create a job action for the same job and assign a different agent. You can also use an ordered agent list, which will cause the job to use the next agent in the list if one fails.
Step 14 To enter a description for your job action, click the Description tab, and type your description in the Description field.
Step 15 Click OK and the action appears in the Actions pane and is available from the Job Event Definition and System Events dialogs.
You can post a log message of your choice to the TES log based on a job or system event. You can configure the log message’s text, log level and whether or not it should also be logged in the Windows Event Log.
Step 1 From the Navigator pane, select Definitions>Actions to display the Actions pane.
Step 3 Click the Add button or right-click and select Add Action from the context menu to display the Action Definition: Log dialog.
Step 4 In the Action Name field, type a name for this action (up to 30 characters). The name must be unique.
Step 5 If you wish to make the action public, select the Public option. When an action is public, the action is available to all TES users, within the bounds of their security policy.
Step 6 Select the desired Owner from the drop-down menu in the Owner field.
Step 8 In the Log Level section, select the log level.
– Error – Places the log into the error message class. Use this log level when your message explains an error that occurred.
– Audit – Places the log into the audit message class. Use this log level when your message explains normal activity.
– Diagnostic – Places the log into the diagnostic message class. Use this log level when your message contains detailed information, useful for diagnostic purposes.
Step 9 In the
Windows Event Log
section, select whether you want the message to be logged to the Windows Event Log and assign an event number as an ID for the logging action. You can view these messages using the Windows
Event Viewer
application log.
(If using an Unix master, this section is called the
Unix Console
and if the
Log to Unix Console
option is selected than events are recorded to a log file using the ID number assigned.)
Step 10 In the Log Message field type the message. In this text field you can insert one or more TES variables. Click in the location where you want to insert the variable and then click the Variables button to choose a variable from the variables menu.
Step 11 To enter a description for your log action, click the Description tab and type your description in the Description field.
Step 12 Click OK and the action appears in the Actions pane and is available from the Job Event Definition and System Events dialogs.
You can update a user-defined variable using an action. If the variable is a string, you can update its string value. If it is a number or date variable, you can increment, decrement, or simply change its numerical value. When editing a variable update action, you define which variable to update, the update value, and when to update the variable.
To add a Variable Update action:
Step 1 From the Navigator pane, select Definitions>Actions to display the Actions pane.
Step 2 Select the Variable folder.
Step 3 Click the Add button or right-click and select Add Action from the context menu to display the Action Definition: Variable dialog.
Step 4 In the Action Name field, type a name for this action (up to 30 characters). The name must be unique.
Step 5 If you wish to make the action public, select the Public option. When an action is public, the action is available to all TES users, within the bounds of their security policy.
Step 6 Select the desired owner from the drop-down menu in the Owner field.
Step 8 In the Variable Name field, select the name of the variable to affect with the action. (The variable must have been previously defined.)
Step 9 In the Type of Update field, select how to update the variable:
– Set variable value to – Replaces the existing variable’s value to the value specified in the Value field.
– Increment variable value by – If the variable is of the number or date type, increments the variable by the number in the Value field. If the variable is a string type, appends the string in the Value field to the variable.
– Decrement variable value by – If the variable is of the number or date type, decrements the variable by the number in the Value field. If the variable is a string type, replaces the variable by the string in the Value field. (For string variables only, the Set variable to option and the Decrement variable value by option have the same result.)
Step 10 In the Value field, type either a numeric value or a string to use for the update.
* The date format corresponds to the format configured in the operating system of the master.
Step 11 In the When to Update field, select when the variable should update, before or after all other actions. If you want to use the variable’s updated value in other actions that are triggered by the same event, select the before other actions option. For example, if you wanted to track how many times a job completes normally, you could create a variable called Comp_Norm . Then, you would have a variable update action increment Comp_Norm before other actions. You could then notify users how many times the job completed successfully with an email action that includes the Comp_Norm variable.
To change an action’s ownership:
Step 1 From the Navigator pane, select Definitions>Actions to display the Actions pane.
Step 2 Select the folder for the type of action you want to see: Email , Alert , SNMP , Job , Log or Variable .
Step 3 Double-click the action whose properties you want to change, or right-click the action and select Edit Action from the context menu or select the action and click the Edit button on the TES toolbar.
Step 4 In the Owner drop-down list, select a different owner.
You can delete an action that you no longer need. When you delete an action, it is removed from all associated job events and system events.
Step 1 From the Navigator pane, select Definitions>Actions to display the Actions pane.
Step 2 Select the folder for the type of action you want to delete: Email , Alert , SNMP , Job , Log or Variable .
Step 3 Right-click the action and select Delete Action from the context menu or select the action and click the Delete button on the TES toolbar.
Step 4 Click OK in the confirmation dialog to delete the action.
To view an action’s properties:
Step 1 From the Navigator pane, select Definitions>Actions to display the Actions pane.
Step 2 Select the folder for the type of action you want to see: Email , Alert , SNMP , Job , Log or Variable .
Step 3 Double-click the action whose properties you want to view, or right-click the action and select Edit Action from the context menu or select the action and click the Edit button on the TES toolbar.
The Alerts pane lists the console alerts that were generated by alert actions. Alerts are a special type of action to bring specific conditions to the attention of the TES operator. Alerts can also be used as a diagnostic tool to decipher the cause of the abnormal condition. For more information about alert actions, see “Action Definition: Alert Dialog” section . More information on an alert is available by double-clicking it to display its Alert Detail dialog.
The Alerts pane displays all console alerts that are present on the system, up to the alert retention history as defined on the Master tab in the System Configuration dialog.
Note From the Navigator pane, select Operations>Alerts to display the Alerts pane.There cannot be any data in this pane until at least one alert action has been defined and triggered.
– Red status light – One or more Critical or Error alerts have not yet been acknowledged.
– Yellow status light – One or more Warning alerts have not yet been acknowledged, or one or more Critical , Error or Warning alerts have not yet been closed.
– Green status light – There are alerts present, but none need to be closed or there are no alerts present; alert actions may have been defined, but none have been triggered.
Note Time – The date and time that the job event occurred triggering the alert. Alerts do not display for jobs that have been purged from history.
– Open – The alert is new or has not yet been acknowledged or the status of the alert has been reset to open from an acknowledged or closed state. To reset the status of an alert to open, double-click the alert record to open the Alert Detail dialog, then select Open from the Status field drop-down menu.
– Acknowledged – The alert has been acknowledged. To acknowledge an alert, right-click the alert and select Acknowledge from the context menu or double-click the alert record to open the Alert Detail dialog, then select Acknowledge from the Status field drop-down menu. To acknowledge multiple alerts at the same time, hold down the Shift key or the Ctrl key on your keyboard while clicking your selections.
– Closed – The alert has been closed. To close an alert, right-click the alert and select Close from the context menu or double-click the alert record to open the Alert Detail dialog and then select Closed from the Status field drop-down menu.
If you select Preferences from the View main menu while viewing the Alerts pane, the Alerts Preferences dialog displays.
From the Columns tab of the Alerts Preferences dialog, you can select which columns are displayed in the Alerts pane and in what order they appear.
On the Colors tab of the Alerts Preferences dialog, select the color to be used for alerts of that type from the drop-down menu in the Critical Alert , Error Alert , Warning Alert and Information Alert fields.
On the Sound tab of the Alerts Preferences dialog, specify the following:
Note Audible Critical/Error Alerts – Specify if Critical and Error level alerts should be audible. If several alerts occur in less than 30 seconds apart, the alert will sound only once.You must specify a .wav file in the Wave File field for the Audible Critical/Error Alerts option to take affect. Most Windows installations will include some .wav files.
When you right-click in the Navigator pane while viewing the Alerts pane, the Navigator context menu displays.
The Alerts Navigator context menu contains the following options:
When you right-click in the Alerts pane, the Alerts context menu displays.
The Alerts pane context menu contains the following options:
The Alert Detail dialog displays when you double-click an alert record in the Alerts pane. Alerts are generated by alert actions that are associated with job or system events.
This dialog contains the following elements:
The Alert Filter dialog displays when you select Filter from the Alerts pane context menu. Use the Alert Filter dialog to limit the alerts that you see according to different parameters.
This dialog contains the following elements:
Note If Critical and Error alerts are filtered out, any associated audible alert will not sound.
Step 1 From the Navigator pane, select Operations>Alerts to display the Alerts pane.
Step 2 Right-click the alert that you want to acknowledge and select Acknowledge from the context menu. To acknowledge more than one alert at the same time, hold down the Shift or the Ctrl key on your keyboard while clicking your selections.
Double-click the alert to acknowledge to display its Alert Detail dialog.
Step 3 From the Status drop-down menu, select Acknowledged . You may also want to type notes in the Response field. TES’s auditing mechanism will log the change in status of the alert.
Step 4 Click OK to close the dialog and save the changes.
Step 1 From the Navigator pane, select Operations>Alerts to display the Alerts pane.
Step 2 You can right-click the alert and select Close from the context menu or double-click the alert to display the Alert Detail dialog and select the Closed option.
You can define which alerts the Alerts pane displays by using the Alerts Filter dialog. You can filter alerts by status and severity level, or include alerts generated on the current day only or from a specified range of days.
Step 1 From the Navigator pane, select Operations>Alerts to display the Alerts pane.
Step 2 Click the Filter button on the TES toolbar or right-click and select Filter from the context menu to display the Alerts Filter dialog with all the available alert types.
a. To filter alerts based on status, select Open , Acknowledged and/or Closed .
b. To filter alerts based on severity level, select from the following: Critical , Error , Warning or Information
c. To filter alerts based on date, select from Current Day or Date range from... to...
Step 3 Click OK . The Alerts pane displays only alerts that fall within the parameters set in the Alert Filter dialog.
Note For more information about the Alert Filter dialog, see “Alert Filter Dialog” section.
Step 1 From the Navigator pane, select Operations>Alerts to display the Alerts pane.
Step 2 From the View main menu, select Preferences or right-click the Alerts pane and select Preferences from the context menu to display the Alerts Preferences dialog.
Step 4 Select the column and click the up or down arrows to arrange the titles into the desired order.
To select/deselect all alert filters:
Step 1 Right-click in the Statuses or Levels section of the Alert Filter dialog.
Note Select Check All or Uncheck All from the context menu.Selecting Check All or Uncheck All does not affect the Days section.
You can sort the alerts displayed in the Alerts pane to change the order in which they are listed.
From the Navigator pane, select Operations>Alerts to display the Alerts pane.
Note To sort console alerts by job number, click the Job column heading. The alerts are sorted numerically in descending order by job occurrence number. Clicking column headings more than once toggles the sort order between ascending and descending.