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.

Configuring Event Log Monitors<br />

Report First Alert Encountered for a Trigger – The first alert<br />

that occurs during a sample run for a specific trigger is the<br />

only one sent. Subsequent alerts for the same trigger are<br />

ignored.<br />

Report Last Alert Encountered for a Trigger – The last alert<br />

that occurs during a sample run for a specific trigger is the<br />

only one sent. Previous alerts for the same trigger are<br />

ignored.<br />

Report all Alerts for a Trigger as a bundle – Send all alerts that<br />

occur for a specific trigger during the sample run as one alert<br />

message.<br />

Test – When you add or modify a monitor, you can test General<br />

settings to determine if they are set appropriately. After clicking<br />

the Test button, you will see messages in the status window as<br />

the test runs and when the test completes.<br />

3. Each monitor that you add must have a unique name. You can<br />

let <strong>OneSight</strong> create a unique name using the Event Log<br />

specifications you supply, or you can type in your own name<br />

for the monitor.<br />

4. On the General tab, type in the DNS Name, specifying the name<br />

or IP address of the host that has the event log.<br />

5. Type in the NetBIOS Name.<br />

6. Enter authentication information if necessary.<br />

7. Specify the type of Event Log that is being monitored.<br />

242 <strong>OneSight</strong> <strong>Administrator</strong> <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!