Cisco Cisco Workload Automation 6.3 Betriebsanweisung

Events

Event Types



 – The date and time (in 24 hour format) when the event occurred.



 – The date and time (in 24 hour format) when the triggered action actually occurs. Normally this time will 

be the same as the Trigger Time but if there is some lag time built into the associated action, the Run Date will be 
later.



 – The instance number of the job that was triggered by the event. (job event only)



 – The name of the job triggered by the event. (job event only)



 – The connection that the event monitor is watching. This could be the connection to a master, to a 

database or to an agent.



 – The current status of the event trigger. There are several statuses used.

 – The event trigger is scheduled for the current day 

– The event trigger is scheduled for the current day but has been suspended using the 

 option in the 

 context menu in the 

 pane.

– The event trigger is scheduled for the current day but is currently outside of the event 

monitor’s specified time windows and is thus inactive.

You can drill down to get additional information about each event instance listed in this 

 tab. Right-click 

any of the listed event triggers to either update the information with the 

 option or you can display details about 

the trigger with the 

 option.

Trigger Details Dialog

The 

 dialog displays more information about an event instance that occurred. The 

 

dialog displays by selecting an event trigger listed in an 

dialog and right-clicking and selecting the 

 option. 

Trigger Details Dialog - Details Tab

The 

 tab displays basic run information about the event trigger. 

This tab contains the following elements:



 – The date and time when the conditions that triggered the event occurred. 



 – The date and time that the event actually occurred. Most of the time this date and time will match the 

information in the 

 field. Sometimes though there is a lag time between when the conditions defined 

as the event occur and when the actual event occurs. An example would be an event such as compiling a production 
day schedule. The event condition might be the start of a new production day at the designated time yet there might 
still be some period of time pass before the actual compilation of a new schedule occurs as the master takes care 
of prerequisite maintenance tasks. 



 – The current status of the event.

Trigger Details Dialog - Triggered Actions Tab 

The 

 tab provides information about the action(s) that the event initiated:



 – The date and time when the action was triggered.



– The date and time that the action actually ran. Most of the time this date and time will match the 

information in the 

 field. Sometimes though there is a lag time between when the action is triggered 

and when the action actual runs.



 – The type of action that ran.