19.07.2014 Views

OneSight Administrator Guide

OneSight Administrator Guide

OneSight Administrator Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring Gomez GPN Monitors<br />

this account information, these monitors will be retrieved<br />

automatically.<br />

Monitors – After you click Get Gomez GPN Monitors, the active<br />

monitors configured in your Gomez GPN service account will<br />

be displayed in this list box.<br />

Location – Select the location for collecting the data.<br />

Step – Select the step to use for monitoring.<br />

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

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

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

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

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

let <strong>OneSight</strong> create a unique name using the Gomez GPN<br />

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

for the monitor.<br />

11. On the General tab in the User ID box, type the name of your<br />

Gomez GPN User ID.<br />

12. On the General tab in the Password box, type your Gomez GPN<br />

password.<br />

13. Click Get Gomez GPN Monitors. Using the login information<br />

you have specified, the active monitors configured in your<br />

Gomez GPN service account are identified and listed here. If<br />

you have previously specified this account information, these<br />

monitors will be retrieved automatically.<br />

14. To verify that the monitor will work as configured, click the<br />

Test button. The Monitor Test window provides information<br />

about the success or failure of the test and indicates what may<br />

be causing any problem.<br />

Chapter 5: Configuring Monitors 189

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

Saved successfully!

Ooh no, something went wrong!