19.07.2014 Views

OneSight Administrator Guide

OneSight Administrator Guide

OneSight Administrator Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Setting Up an Alert to Trigger an Action Plan<br />

ht.oneSightEventData.eventDescription.0<br />

GT 2 on http://www.empirix.com<br />

Object ID:<br />

.iso.org.dod.internet.private.enterprises.empirix.oneSig<br />

ht.oneSightEventData.extEventDescription.0<br />

GT 2: Value was 2.823 seconds, threshold is 2 seconds<br />

(10/15/01 3:24 PM)<br />

Event: GT 2<br />

...<br />

Triggering an E-mail Action Plan<br />

To set up an alert to trigger an e-mail action plan:<br />

1. If you have not already created your monitor, create one now.<br />

2. Make sure you have already set up an e-mail action plan that<br />

will let you know when your monitor has a problem.<br />

3. Click the Configure menu, click Monitor Groups, then click<br />

Modify.<br />

4. Click the Monitor you want to associate with an e-mail alert,<br />

then click Modify.<br />

5. On the Alerts tab, you will see at least one preconfigured alert<br />

that notifies you if monitoring cannot be performed. By default,<br />

a failure to monitor changes the status of the monitor on the<br />

Status page to Red (Critical). However, if you want to be<br />

notified about this failure, you must associate the alert with an<br />

action plan.<br />

6. Select the default alert named for the state you associate with<br />

monitor failure (for example, URL Unavailable), and click<br />

Modify.<br />

7. In the Alert Editor, the Respond By option controls what action<br />

is triggered when an alert condition occurs. By default, there is<br />

no action plan associated with this alert condition, so you will<br />

see Respond by .<br />

Chapter 5: Configuring Monitors 443

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!