Manage events in AppsWatch Base

Events occur when the watch object (Monitor or Service) to which they are attached returns a result that meets user-defined conditions (i.e. exceeds a threshold for duration). Events trigger Alerts and Reactions.

Manage Events

Go to configuration section and select “Events”  from the Top Menu

Manage events in AppsWatch Base (115005376107)_mceclip3

Manage events in AppsWatch Base (115005376107)_mceclip0

The “Events” tab opens;

Manage events in AppsWatch Base (115005376107)_mceclip1

Customize Event window columns by mousing over and clicking the arrow beside any of the column headings at the top of the Events screen, then choosing which columns to display.  By default, all columns are shown, but you can uncheck any columns you don't want to see or check columns you do want to see.  You may also sort any column in ascending or descending order.

Manage events in AppsWatch Base (115005376107)_mceclip2

Add an Event

To add a new Event, click the “Add New Event” button at the top of the Events Tab;

Manage events in AppsWatch Base (115005376107)_mceclip4

The “Add New Event” form opens in a new tab;

Manage events in AppsWatch Base (115005376107)_mceclip5

Event Name: This name appears in drop lists when defining the events for a particular watch object.

Type:  Specify whether this Event is for a Monitor or a Service.

Operator: The mathematical operator used to compare the retrieved value and the threshold
(>, <, >=, <=, +, -, =)

Threshold: Thresholds have different units, depending on the monitoring test performed.  For example, Nodes measures response time in seconds, while a Systems file test measures the size of the file in MB.

Duration: How many seconds the “broken” threshold state must persist before Reactions and Alerts are triggered.  For example, 1 means the state must persist for 1 minute before the Event is triggered.  Enter 0 for no duration (i.e. Event occurs immediately upon threshold being surpassed).

Special note for Duration: Use the format d/f (d=duration; f=check frequency) to specify a check frequency other than the frequency of the Monitor to which this Event is attached.  For example, “3/1” means the state must persist for 3 minutes, and will be checked every 1 minute. 

Reaction #1 and Reaction #2: You can have up to two Reactions per Event. Reaction types are Email, RestartSNMP Trap or Custom Response

Alert message: This message will be shown on the Active Alerts page, and is separate from Reaction E-mail or other messages.  The Alert Message field contains the data you specify.  Include variables to create customized messages that include names and values specific to this Event.  Select from the “Variable” drop down list to incorporate variables into your message.  Use as many variables as you desire in the message. 

Variable: The following variables are available for use in your message:

ObjectAlias: Object monitored or Service alias.  For example, SQLServer_master

GroupName: Object group alias. It is only populated for Nodes and Tasks type monitors. You can find   this field in the Node or Task Edit form.

IncludeFailureImage: If selected, the failure screenshot will be included in the email reaction.

SystemAlias: The name of the System. It is only populated for Systems and SNMP type monitors.

Threshold: Value defined in “Threshold” field of this form.

ValueWatched: The value result of the test.

Duration: Value defined in “Duration” field of this form.

AlertState: Value defined in the “Execute On” field of the Reactions form.

AlertType: Value defined in the Event “Type” field of the watch object.

StartDate: Event's start date and time.

ServiceChildren: Used for Services objects. Service Children and their statuses.

LogMessage: Used for Logs, it displays the Log Message.

Description: Optional text to describe the Event.

Severity (optional): Used in conjunction with “Default For” value to establish this Event as the default for a type of watch object (Monitor or Service).  Next time you add that type of watch object, the “Event” section will be pre-populated with this Severity type.

Default For (optional): Used in conjunction with “Severity” value to establish this Event as the default for a type of watch object (Monitor or Service).  Next time you add that type of watch object, the “Event” section will be pre-populated with this Event.

Complete the “New Event Form” parameters and “Submit”.

Edit an Event

Click the “Edit”icon next to the Event. Event form opens;

Manage events in AppsWatch Base (115005376107)_mceclip6

Manage events in AppsWatch Base (115005376107)_mceclip9

When you are done with editing, click "Submit".

Delete an Event

Click the “Delete” icon next to the Event;

Manage events in AppsWatch Base (115005376107)_mceclip10

Manage events in AppsWatch Base (115005376107)_mceclip12

Click "Yes" to delete the event.

Apply an Event

You can apply an Event to multiple metrics or Services at once by clicking theicon next to the Event.  “Apply Event” Window Opens;

Manage events in AppsWatch Base (115005376107)_mceclip15

Click “Apply” to save your settings.