OneSight Administrator Guide

Administrator Guide 

Empirix OneSight Version 8.1

OneSight Administrator Guide, Version 8.1 

Empirix Inc. 

Copyright Notice 

Copyright © 1997-2012 Empirix Inc. All rights reserved. The 

contents of this document and the associated OneSight suite 

software are the property of Empirix Inc. and are copyrighted. No 

part of this document may be copied or distributed, transmitted, 

transcribed, stored in a retrieval system, or translated into any 

human or computer language, in any form, or by any means, 

electronic, mechanical, magnetic, manual, or otherwise, or disclosed 

to third parties without the express written permission of Empirix 

Inc. 

This Empirix software product also includes copyrighted third party 

software. See the OneSight online help for complete information 

about third party copyrights. 

Trademarks 

Empirix logos are either registered trademarks or trademarks of 

Empirix Inc. in the United States and/or other countries. All other 

names are used for identification purposes only and may be either 

registered trademarks or trademarks of their respective owners. 

Empirix Inc. 

20 Crosby Drive 

Bedford, MA 01730 

Ph: 781-266-3200 

Fax: 781-266-3201 

Web: http://www.empirix.com 

Email: onesight-sales@empirix.com 

USA, Japan, Singapore, UK/Europe 

To contact a local Empirix office, visit our Web site at 

www.empirix.com 

ii

Contents 

Contents 

Preface 

xvii 

About This Guide ............................................................................... xvii 

Related Documentation ..................................................................... xviii 

OneSight Manuals ....................................................................... xviii 

Conventions ..................................................................................... xviiii 

Using Help ....................................................................................... xviiii 

Obtaining Technical Support ................................................................ xx 

C h a p t e r 1 

Introduction 1 

Feature Highlights .................................................................................. 1 

What OneSight Monitors ........................................................................ 2 

Dedicated Monitors ................................................................... 2 

Applications .............................................................................. 3 

Network Devices ....................................................................... 4 

Network Performance ................................................................ 4 

System Requirements ............................................................................. 4 

OneSight Server and Data Collector Requirements ......................... 5 

Additional Requirements ........................................................... 6 

Database Requirements ............................................................. 7 

Client Web Browser Requirements .................................................. 7 

PC Clients .................................................................................. 7 

UNIX Clients ............................................................................. 7 

Notes About Web Browser Requirements................................. 7 

Contact Center Component Requirements ....................................... 8 


Installing OneSight 11 

What OneSight Installs ......................................................................... 11 

Contents 

iii

Contents 

Third-Party Software ..................................................................... 11 

Services .......................................................................................... 12 

Installing OneSight ............................................................................... 12 

Configuring SQL 2005 and 2008 ................................................... 17 

Enabling Mixed Authentication Mode .................................... 17 

Turning on XP_CMDSHELL ................................................. 17 

Changing Session Timeout ................................................................... 18 

Changing the OneSight Server Default Port ........................................ 18 

Enabling SSL for the OneSight Server ................................................. 18 

Updating Profiles After Upgrading OneSight ...................................... 18 

Installing the OneSight Data Collector or Remote Agent .................... 19 

Data Collectors and Remote Agents .............................................. 20 

Should I Install the Data Collector or Remote Agent? .................. 22 

Remote Agent Installation Requirements ...................................... 23 

Installing the Remote Agent on Windows ..................................... 24 

Identifying the Remote Agent Machine to the OneSight Server 

................................................................................................. 26 

Using an Initialization File for Remote Agent Setup .............. 27 

Installing the UNIX Remote Agent ............................................... 27 

Installing the UNIX Remote Agent ......................................... 28 

Running the UNIX Remote Agent .......................................... 30 

Starting and Stopping the UNIX Remote Agent ..................... 31 

Data Collector Installation Requirements ...................................... 32 

Installing the Data Collector on a Windows Machine ................... 32 

Using the JMX Proxy ........................................................................... 35 

Installing JMX Proxy Automatically ............................................. 36 

Installing JMX Proxy Manually .................................................... 37 

Configuring the JMX Proxy .......................................................... 37 

Post Installation .................................................................................... 38 

OneSight Agent Proxy .......................................................................... 39 

Installing the Agent Proxy ............................................................. 40 

Data Collector or Remote Agent Configuration ...................... 42 

OneSight Server Configuration ............................................... 43 

Debugging the Agent Proxy .................................................... 43 

OneSight Default Ports ......................................................................... 46 

Configuring Contact Center Components ............................................ 47 

SNMP ............................................................................................. 49 

Using Perfmon ............................................................................... 50 

iv 

OneSight Administrator Guide

Contents 

To check for SQL objects in Perfmon ..................................... 50 

Using Diskperf ............................................................................... 51 

To execute the Diskperf command .......................................... 51 

To log in to OneSight ........................................................................... 52 

Using OneSight Log In .................................................................. 52 

Using Windows Log In .................................................................. 52 

Uninstalling OneSight .......................................................................... 53 

To Uninstall OneSight using Add/Remove Programs ............. 53 

To Uninstall the Data Collector ............................................... 54 

To Remove the Database ......................................................... 54 

To Remove the Empirix Folder ............................................... 55 

Removing the Data Collector from a Windows machine ..................... 55 

Removing the OneSight Remote Agent ............................................... 55 

Removing Remote Agent from a Windows Machine .................... 55 

Removing the UNIX Remote Agent .............................................. 56 

Uninstalling Agent Proxy ..................................................................... 57 

Starting the OneSight Service .............................................................. 57 

Stopping the OneSight Service ............................................................. 58 

Viewing Version and Database Information ........................................ 58 

How OneSight Determines the License Type ................................ 62 

Database Maintenance .......................................................................... 63 

Using a Remote Database .............................................................. 63 

Automatic Database Backup .......................................................... 65 

Manual Database Backup .............................................................. 66 

Transferring Configuration Data to Another Database .................. 66 

Updating Data Collectors and Remote Agents ..................................... 69 

Configuring the SNMP Agent .............................................................. 74 


Getting Started 75 

Deciding Which Monitors to Use ......................................................... 77 

Tips On Using OneSight ...................................................................... 79 

Shutting Down and Restarting OneSight ....................................... 79 

Opening the OneSight Console From a Remote Machine ............. 79 

Modifying OneSight Profiles ......................................................... 80 

Finding System Information .......................................................... 80 

Interpreting Status and Report Information ................................... 80 

Database Backup ............................................................................ 81 

Contents 

v

Contents 

Tuning OneSight .................................................................................. 81 

Modifying a Profile ........................................................................ 82 


Configuring Monitor Groups 85 

Adding a Monitor Group ...................................................................... 86 

Modifying a Monitor Group ................................................................. 90 

Specifying the Status Chart Data Source .............................................. 96 

Specifying Action Plans ....................................................................... 98 

Specifying Alert Dependencies ............................................................ 99 

Defining Action Plan Alerts ......................................................... 102 

Adding Dependency Nodes ......................................................... 103 

Adding a Smartlink to a Monitor Group ............................................ 104 

Applying Downtime to a Monitor Group ........................................... 106 

Enabling/Disabling a Monitor Group ................................................. 107 

Removing a Monitor Group ............................................................... 108 

Adding Monitors to a Monitor Group ................................................ 109 


Configuring Monitors 113 

Authentication .................................................................................... 115 

Monitor Naming ................................................................................. 115 

Configuring the VQ Inspector Monitor for the Avaya Communication 

Manager .............................................................................................. 116 

Configuring the Avaya Communication Manager ....................... 116 

Configuring the Monitor in OneSight .......................................... 123 

Configuring the Cisco Call Manager Profile Monitor ........................ 129 

Configuring the OSDC.properties File ........................................ 129 

Configuring the Cisco Call Manager ........................................... 130 

Configuring FTP ................................................................... 130 

Configuring SNMP V1 or V2c .............................................. 133 

Configuring SNMP V3 .......................................................... 141 

Configuring the Monitor in OneSight .......................................... 147 

Configuring the IDMC Profile Monitor ............................................. 151 

Configuring OneSight Compound Metric Monitors .......................... 153 

OneSight Compound Metric Operators ....................................... 160 

OneSight Compound Metric Examples ....................................... 164 

vi 


Contents 

Configuring Database Monitors ......................................................... 167 

Database Monitor JDBC Driver Options ..................................... 168 

Creating a Database Monitor ....................................................... 169 

Setting Up Oracle ODBC for OneSight ....................................... 176 

Setting Up DataDirect JDBC Driver for OneSight ...................... 177 

SQL Server Configuration ..................................................... 177 

Data Collector Configuration ................................................ 178 

Monitoring Multiple Rows in a Database .................................... 179 

Configuring DNS Monitors ................................................................ 181 

Configuring Gomez GPN Monitors ................................................... 186 

To Specify Proxy Server Settings ................................................ 190 

Configuring Gomez GPN Profile Monitors ....................................... 191 

To Specify Proxy Server Settings ................................................ 195 

Configuring OneSight Call Statistics Profile Monitors ...................... 196 

Configuring OneSight Probe Monitors .............................................. 201 

Configuring OneSight Voice Transaction Profile Monitors ............... 205 

Configuring JMX Monitors ................................................................ 215 

Configuring Advanced Settings ................................................... 223 

Configuring OneSight Voice Watch Monitors ................................... 225 

Specifying Proxy Server Settings ................................................ 230 

Configuring OneSight Voice Watch Profile Monitors ....................... 231 

Specifying Proxy Server Settings ................................................ 237 

Configuring Event Log Monitors ....................................................... 238 

Configuring FTP Monitors ................................................................. 245 

Configuring Advanced Options ................................................... 251 

Configuring LDAP Monitors ............................................................. 252 

Configuring Log File, Directory Monitors ......................................... 256 

Configuring Mail Monitors ................................................................ 264 

Validating E-Mail Connections ................................................... 271 

Configuring Oracle OpenScript Profile Monitors .............................. 272 

Exporting Scripts ......................................................................... 279 

Setting Command Line Options ................................................... 280 

Specifying Proxy Settings ............................................................ 281 

Configuring Oracle Test for Web Applications Monitors .................. 282 

Exporting Scripts ......................................................................... 291 

Specifying Authentication Data ................................................... 292 

Configuring Perfmon Monitors .......................................................... 293 

Monitoring Multiple Processes With the Same Name ................. 293 

Contents 

vii

Contents 

Creating the Monitor .................................................................... 294 

Configuring Ping Monitors ................................................................ 302 

Configuring Port Monitors ................................................................. 306 

Setting Advanced Options ........................................................... 312 

Configuring Process Monitors ............................................................ 313 

Configuring Service Monitors ............................................................ 318 

Configuring SNMP Monitors ............................................................. 323 

Configuring SNMP Trap Monitors .................................................... 332 

Configuring TCP/IP Socket Monitors ................................................ 338 

Configuring URL Monitors ................................................................ 344 

Specifying Advanced Settings ..................................................... 352 

Specifying Proxy Settings ............................................................ 355 

Configuring OneSight Virtual Agent Monitors .................................. 356 

Configuring State Machines ........................................................ 365 

The State Machine ................................................................. 368 

XML Format .......................................................................... 369 

Example ................................................................................. 370 

Configuring OneSight Voice Quality - Basic Profile Monitors ......... 371 

Configuring OneSight Voice Quality - Advanced Profile Monitors .. 376 

Configuring WMI Monitors ............................................................... 387 

Sample Every Settings ........................................................................ 395 

Advanced Sample Frequency Settings ......................................... 397 

Exporting and Importing Monitors ..................................................... 398 

Exporting Monitors ...................................................................... 399 

Importing Monitors ...................................................................... 400 

Configuring a Profile Monitor ............................................................ 401 

What You Need to Know About Your System ............................ 402 

Applying a Profile to Multiple Systems ....................................... 413 

Using Regular Expressions for Pattern Matching .............................. 415 

Defining Expressions for Good Strings and Bad Strings ............. 416 

Defining Expressions for Metric Performance Data Using the Log 

File Monitor ................................................................................. 416 

Defining Expressions for Metric Performance Data using the 

OneSight Virtual Agent Monitor ................................................. 417 

Adding Alerts to a Monitor ................................................................ 419 

Configuring Monitors Alerts Tab ................................................ 419 

Setting Up an Alert to Trigger an Action Plan ................................... 422 

The Alert Editor ........................................................................... 425 

viii 


Contents 

General Tab Main Settings .................................................... 425 

Sample Failure and Crossed Threshold settings .................... 435 

Notes Tab Settings ................................................................. 439 

Alert Editor Log Profile Metrics .................................................. 439 

Logfile Settings ..................................................................... 439 

NT Event Log Settings .......................................................... 440 

SNMP Trap Settings .............................................................. 441 

Example SNMP Trap Message ............................................. 442 

Triggering an E-mail Action Plan ................................................ 443 

Creating a Threshold-based Alert ................................................ 444 

Editing a Response to an Alert – Dedicated Monitor ......................... 447 

Editing a Response to an Alert – Profile Metric ................................. 449 

Displaying the Windows Event Viewer ............................................. 451 

Configuring the Location From Which the Monitor Will Sample ..... 452 

Adding a SmartLink to a Monitor ...................................................... 453 

Configure Monitor Attributes Tab...................................................... 457 

Configure Monitor Groups Tab .......................................................... 461 

Access Control Tab ............................................................................ 462 

Applying Downtime to a Monitor ...................................................... 463 

Modifying Monitors ........................................................................... 464 

Dedicated Monitors ...................................................................... 464 

Profile Monitors ........................................................................... 464 

Managing Non-operational Profile Metrics ........................... 465 

Enabling/Disabling Monitoring of a System Component ..... 466 

Testing a Dedicated Monitor .............................................................. 467 

Enabling/Disabling a Monitor ............................................................ 471 

Removing a Monitor .......................................................................... 472 

Modifying Alerts for Multiple Monitors ............................................ 472 

Adding Alerts to Multiple Monitors ............................................ 472 

Changing Alert Thresholds for Multiple Alerts ........................... 475 

Deleting Alerts From Multiple Monitors ..................................... 479 

Modifying the Location of Multiple Monitors ................................... 481 

Adding Multiple Dedicated Monitors ................................................ 486 

Globally Changing Proxy Settings ..................................................... 487 


Using Profiles 489 

The Profile Manager ........................................................................... 492 

Contents 

ix

Contents 

Adding, Cloning, and Modifying Profiles ................................... 493 

Entering a Profile’s Main Settings ........................................ 494 

Adding/Removing Metrics From a Profile ............................ 498 

Removing Profiles ....................................................................... 500 

Importing Profiles ........................................................................ 500 

Exporting Profiles ........................................................................ 504 

Global Metric Manager ...................................................................... 504 

Adding/Cloning/Modifying Metrics ............................................ 505 

General Tab Settings .................................................................... 511 

Data Sources Tab Settings ........................................................... 518 

Attributes Tab Settings ................................................................ 518 

Access Control Tab Settings ........................................................ 521 

Adding a Data Source .................................................................. 522 

JDBC Dialog Box .................................................................. 524 

JMX Dialog Box ................................................................... 526 

Log File, Directory Dialog Box ............................................ 527 

NT Event Log Dialog Box .................................................... 532 

Perfmon Dialog Box .............................................................. 535 

Ping Dialog Box .................................................................... 537 

Port Dialog Box ..................................................................... 538 

Process Dialog Box ............................................................... 539 

Service Dialog Box ............................................................... 540 

SNMP Dialog Box................................................................. 542 

SNMP Trap Dialog Box ........................................................ 546 

Socket Dialog Box................................................................. 548 

UNIX System Dialog Box ..................................................... 551 

URL Dialog Box ................................................................... 554 

Virtual Agent Dialog Box ..................................................... 557 

WMI System Dialog Box ...................................................... 561 

Setting a Metric’s Sampling Interval ........................................... 562 

Removing Metrics ........................................................................ 563 

Modifying a Metric’s Data Source ..................................................... 564 


Configuring Systems 565 

Adding Systems .................................................................................. 565 

Adding Multiple Systems ................................................................... 571 

Adding a New Component Type ........................................................ 575 

x 


Contents 

Modifying System Definitions ........................................................... 577 

CPU System Information ............................................................. 577 

Database System Information ...................................................... 579 

Oracle Database System Information .................................... 579 

SQL Database System Information ....................................... 582 

Database Instance System Information ........................................ 586 

Database Log File System Information ....................................... 586 

Disk System Information ............................................................. 586 

File System Information .............................................................. 589 

Interface System Information....................................................... 590 

Load Balancer System Information ............................................. 592 

Service System Information ......................................................... 593 

System Properties Information .................................................... 594 

Port System Information .............................................................. 600 

Process System Information ........................................................ 601 

VM System Information .............................................................. 604 

VMProcess System Information .................................................. 605 

Web Server System Information .................................................. 606 

Adding System Components .............................................................. 608 

Adding Components Manually .................................................... 609 

Adding Components Automatically ............................................ 612 

Discovering Multiple Systems ..................................................... 623 

Modifying the Location of Multiple Systems .............................. 625 

Modifying System Components .................................................. 627 

Removing System Components ................................................... 627 

Changing Passwords ........................................................................... 628 

System Passwords ........................................................................ 628 

Visual Script Passwords ............................................................... 629 

URL Script Passwords ................................................................. 631 

Virtual Agent Passwords .............................................................. 631 


Creating Action Plans 633 

Creating a New Action Plan ............................................................... 635 

Adding Actions to the Plan ................................................................ 638 

Configuring Global Action Options ................................................... 644 

Triggering An Email Action ........................................................ 645 

Replying to an E-mail Alert .................................................. 651 

Contents 

xi

Contents 

Validating Email Connections ............................................... 653 

Adding/Modifying Message Templates ....................................... 654 

Adding a New Alert Message Template ................................ 655 

Modifying an Alert Message Template ................................. 657 

Message Template Variables ................................................. 658 

Triggering a Scripting Action ...................................................... 663 

Triggering an SNMP Action ........................................................ 668 

Triggering an SNMP Set Action .................................................. 675 

Triggering a Delay Action ........................................................... 680 

Triggering a Monitor Action ........................................................ 683 

Triggering a Socket Connection Action ...................................... 686 

Triggering a HTTP Post/Get Action ............................................ 690 

Triggering a Syslog Action .......................................................... 694 

Configuring Global Action Options ................................................... 698 

Configuring Global Email Actions .............................................. 700 

Configuring the Mail Server ........................................................ 704 

Configuring Global Incoming E-Mail Options ............................ 705 

Configuring Global Scripting Options ......................................... 706 

Modifying An Action Plan ................................................................. 707 

Modifying an Email Action ......................................................... 708 

Modifying a Scripting Action ...................................................... 710 

Modifying an SNMP Action ........................................................ 711 

Modifying an SNMP Set Action .................................................. 713 

Modifying a Delay Action ........................................................... 714 

Modifying a Monitor Action ........................................................ 715 

Modifying a Socket Connection Action ...................................... 717 

Modifying an HTTP Post/Get Action .......................................... 718 

Modifying a Syslog Action .......................................................... 719 

Retiring an Action Plan ...................................................................... 720 

Action Plans Not Associated With an Alert ....................................... 720 


Configuring Downtime 723 

Items Available for Downtime Scheduling ........................................ 723 

Scheduling Downtime by Monitor ............................................... 725 

Scheduling Downtime by System ................................................ 729 

Scheduling Downtime by Downtime ........................................... 730 

Putting a Monitor Immediately Into Downtime ................................. 733 

xii 


Contents 

C h a p t e r 1 0 

Configuring Attributes and Views 735 

Configuring Attributes ....................................................................... 735 

Adding Attributes Sets and Values .............................................. 735 

Removing Attributes Sets and Values ......................................... 740 

Assigning Attributes to Objects .......................................................... 741 

Configuring Saved Status Groupings ................................................. 742 

Adding a Saved Status Grouping ................................................. 742 

Modifying a Saved Status Grouping ............................................ 746 

Deleting a Saved Status Grouping ............................................... 746 

Configuring Attribute Matrix Views .................................................. 747 

Adding Attribute Matrix Views ................................................... 748 

Modifying Attribute Matrix Views .............................................. 751 

Deleting Attribute Matrix Views ................................................. 753 

Configuring Custom Status Views ..................................................... 753 

Adding a Custom Status View ..................................................... 754 

Creating Custom Status View Items ............................................ 758 

Creating a Report Item .......................................................... 758 

Creating a Monitor Group or Monitor Item .......................... 760 

Creating a Text Item .............................................................. 765 

Creating an Image Item ......................................................... 767 

Creating a Area Item ............................................................. 770 

Creating a Frame Item ........................................................... 772 

Modifying Items .................................................................... 774 

Deleting Items ....................................................................... 774 

Modifying a Custom Status View ................................................ 774 

Deleting a Custom Status View ................................................... 775 

Custom Status View Example ...................................................... 775 

C h a p t e r 1 1 

Configuring Database Storage and Locations 795 

Specifying When to Delete Database Records ................................... 795 

Configuring Locations ........................................................................ 798 

Modifying Locations .................................................................... 801 

Adding Location Groups ............................................................. 802 

Removing Location Groups .................................................. 803 

Contents 

xiii

Contents 

C h a p t e r 1 2 

Configuring Users 805 

xiv 

Configuring Roles .............................................................................. 805 

Configuration Rights Tab ............................................................ 808 

Alerts Rights ................................................................................ 810 

Reporting Rights .......................................................................... 811 

Status Rights ................................................................................ 812 

Access Control ............................................................................. 813 

Deleting Roles .............................................................................. 813 

Configuring User Groups ................................................................... 814 

Removing User Groups ................................................................ 818 

Adding New Users ............................................................................. 819 

Modifying User Settings .................................................................... 821 

Editing User Rights ...................................................................... 823 

Configuring Global Options ............................................................... 824 

C h a p t e r 1 3 

Configuring Service Level Agreements 827 

Creating SLAs .................................................................................... 829 

Creating SLOs .................................................................................... 833 

Updating SLAs ................................................................................... 840 

Deleting SLAs .............................................................................. 841 

Updating SLOs ................................................................................... 842 

Deleting SLOs .............................................................................. 844 

Configuring Date Intervals ................................................................. 844 

Adding Date Intervals .................................................................. 844 

Modifying Date Intervals ............................................................. 847 

Deleting Date Intervals ................................................................ 847 

C h a p t e r 1 4 

Configuring Custom Reports 849 

Creating Reports Using Report Templates ......................................... 849 

Running a Report Templates Report .................................................. 850 

OneSight Report Templates Example Report .............................. 851 

Report Templates Properties File ....................................................... 851 

Editing the Report Templates Properties File .............................. 852 

About Custom Report Data Sources ............................................ 852 


Contents 

Contents 

Passing Arguments to a SQL Query ............................................ 853 

Creating a Gauge Report .................................................................... 853 

Post-Processing of SQL results using Java ........................................ 854 

Implementation Notes/Caveats ........................................................... 856 

Report Templates Configuration File ................................................. 857 

C h a p t e r 1 5 

Configuring Time Intervals 863 

Creating New Time Intervals ............................................................. 863 

Changing Time Intervals .................................................................... 866 

Deleting Time Intervals ...................................................................... 867 

C h a p t e r 1 6 

Configuring VQ Probes 869 

VQ Probe Self Monitors .............................................................. 870 

Editing VQ Probes .............................................................................. 871 

Configuring a VQ Probe .............................................................. 871 

Configuring a VQ Probe on a G5 or FX/TDM System ............... 880 

Changing or Adding IP Addresses ............................................... 883 

Codec Comparison Chart ............................................................. 884 

Deleting VQ Probes ............................................................................ 884 

Editing Dial Numbers ......................................................................... 885 

C h a p t e r 1 7 

Configuring XMS Systems 887 

Adding XMS Systems ........................................................................ 887 

Modifying XMS Systems ................................................................... 891 

Deleting XMS Systems ...................................................................... 892 

Viewing Call Data Records ................................................................ 893 

C h a p t e r 1 8 

OneSight Utilities 895 

Trace Route ........................................................................................ 895 

Regular Expressions ........................................................................... 896 

MIB Browser ...................................................................................... 898 

Creating Metrics........................................................................... 901 

Support and Diagnostics ..................................................................... 903 

xv

Contents 

C h a p t e r 1 9 

Troubleshooting 905 

Viewing Administration Notifications ............................................... 905 

Troubleshooting Setup ....................................................................... 906 

Out of Disk Space ........................................................................ 906 

Moving the OneSight Database to a Remote SQL Server ........... 907 

Database Installation or Connection Errors ................................. 910 

Installing OneSight Using Windows Terminal Services ............. 910 

Oracle Test for Web Applications Error Messages ............................ 910 

Transaction Errors Detected or Generated by Oracle Test for Web 

Applications Visual Scripts .......................................................... 911 

Errors Detected While Running Oracle Test for Web Applications 

Transaction Monitor .................................................................... 913 

RSWISERV Error codes returned by the Thin agent .................. 916 

HTTP Status Codes and the Win32 Internet API Constants ........ 918 

Thick Client Problems Using an Oracle Test for Web Applications 

Transaction Monitor ........................................................................... 918 

Critical State Error Messages ............................................................. 919 

C h a p t e r 2 0 

Glossary 923 

Index 933 

xvi 


Preface 

Preface 

About This Guide 

Welcome to the OneSight Administrator Guide. This guide explains 

how to use the OneSight to monitor and manage the health of your 

e-business. 

This guide contains the following chapters: 

Chapter 1 – Introduction: provides an overview of the major features 

of OneSight. 

Chapter 2 – Installing OneSight: explains how to install the OneSight 

server, client web browsers, and web components. 

Chapter 3 – Getting Started: provides information that is useful to 

know before you begin using OneSight. 

Chapter 4 – Configuring Monitor Groups: provides instructions for 

configuring and maintaining monitor groups. 

Chapter 5 – Configuring Monitors: provides instructions for 

configuring and maintaining monitors. 

Chapter 6 – Using Profiles: provides instructions for using profiles 

and for adding metrics to profiles. 

Chapter 7 – Configuring Systems: provides instructions for adding 

systems and system components to OneSight. 

Chapter 8 – Creating Action Plans: provides instructions for creating 

and using action plans. 

xvi 


Chapter 9 – Configuring Downtime: provides instructions for 

configuring downtime. 

Chapter 10 – Configuring Attributes: provides instructions for 

configuring attributes. 

Chapter 11 – Configuring Database Storage and Locations: provides 

instructions for specifying when to delete database records, and how 

the Data Collector should behave. 

Chapter 12 – Configuring Users: provides instructions for adding and 

modifying user settings. 

Chapter 13 – Configuring Service Level Agreements: provides 

instructions on creating Service Level Agreements and Service 

Level Objectives. 

Chapter 14 – Configuring Custom Reports – provides instructions for 

creating custom OneSight reports. 

Chapter 15 – Configuring Time Intervals: provides instructions for 

creating time intervals for use with Service Level Objectives and 

action plans. 

Chapter 16 – Configuring VQ Probes: provides instructions on 

configuring Voice Quality (VQ )Probes. 

Chapter 17 – Configuring XMS Systems: provides instructions for 

adding and configuring XMS systems. 

Chapter 18 – OneSight Utilities: provides description for the trace 

route, regular expression, MIB browser, and support utilities. 

Chapter 19 – Troubleshooting: provides troubleshooting information. 

Chapter 20 – Glossary: provides definitions for terms used in 

OneSight. 

xvii

Preface 

Related Documentation 

OneSight Manuals 

OneSight includes a complete set of pdf manuals and online help. 

OneSight includes the following manuals: 

OneSight Operator Guide – explains how to use OneSight to 

monitor and manage the health of your e-business. 

OneSight Administrator Guide – explains how setup, configure, and 

use OneSight to monitor and manage the health of your e-business. 

These documents require the Adobe ® Acrobat ® Reader, version 

4.x (or higher), to open and view the files. You can download the 

free Acrobat Reader from the Adobe Web site: 

http://www.adobe.com/products/acrobat/readstep2.html. 

Additional documentation may be included with other Empirix Inc. 

or third party products used with OneSight. 

xviii 


Conventions 

This guide uses the following typographical conventions to identify 

specific items: 

Convention 

Bold Sans Serif 

Sans Serif 

Fixed-Pitch type 

Arrow between menu options. 

Description 

Menu options and dialog box 

selections. 

File names and Visual Script 

nodes. 

Program code. 

Select each option in sequence. 

Using Help 

The OneSight Web Help System provides setup and usage 

information for the Empirix OneSight. This Web Help System is 

provided to help you use the Empirix OneSight with greater 

efficiency. While this documentation includes information for 

installing, configuring, and using this product, additional 

information may be available in the Knowledgebase section on the 

Empirix.com OneSight Support web page. 

You can access the Web Help System by clicking the Help buttons 

located in the Empirix OneSight Console. Clicking Help opens an 

additional instance of your web browser, from which you view 

configuration and usage documentation. 

As you navigate through the Help system, the topics you see in the 

main portion of the window automatically synchronize with the 

Table of Contents. If the topic you are reading does not appear to 

synchronize correctly, use the scroll bar in the Table of Contents to 

display more of the contents list. 

xix

Preface 

The following features are available using this help system: 

Table of Contents - Use the Table of Contents to navigate to the 

topics you want to view. Click the topic indicator adjacent to any 

topic to view additional documents relating to that topic. 

Search - Use the Search link to access a full-context search engine 

for the OneSight Web Help System. To use the search engine, click 

Search at the top of any Help page. In the search engine, enter a 

keyword into the text box and click Search. A list of topics is 

displayed. 

To view a topic from this list, select it and click Go. The document 

you selected appears in the main Help window. Click Clear to 

empty the list and begin a new search. 

Glossary - To view definitions for words and terms used in Empirix 

OneSight, click Glossary at the top of any Help page. 

Obtaining Technical Support 

If you have questions about OneSight, first look in this guide, the 

online Help, and the release notes delivered with the software. 

Technical Support can be accessed in the following ways: 

Tel. (781) 266-3202 

Online. 

Email 

www.empirix.com 

onesight-support@empirix.com 

If you have questions about the OneSight, first look in the online 

Help and the release notes delivered with the software. 

You can also check our Web site for the latest information about 

upgrades and other issues at http://www.empirix.com. 

xx 


If you wish to contact Empirix Web Test & Monitoring Support, 

please use the following contact numbers and email addresses: 

Tel. 

North America: (781) 266-3202 (8 a.m. to 8 p.m. EST) 

Europe: +44 (0) 1344 668080 (8:30 - 18:00 GMT) 

Japan: 81-(3)-3791-2336 

Fax. North America: (781) 266-3202 

Email 

North America: support@empirix.com 

Europe: europeansupport@empirix.com 

Asia/Pacific: webtest_asiasupport@empirix.com 

Key Requests: To request a software license key, please call (781) 

266-3200 or send your request via email to key@empirix.com. 

xxi


Introduction 

Feature Highlights 

Empirix OneSight monitors and manages the health of your 

business by providing you with a comprehensive and flexible view 

of your mission-critical components. 

OneSight offers the following advantages for ensuring optimal 

performance of your contact center applications and for delivering 

the best possible quality of experience to your end users: 

Holistic View of Your Infrastructure – OneSight tracks the 

performance of your applications, monitoring user transactions 

and the operation of components such as servers and specialized 

technology such as CTI, PBX and voice portals, network devices, 

detecting changes that could jeopardize application performance. 

OneSight provides real-time data that you can use to avoid 

performance problems and rapidly react to problems when they 

occur. 

Realistic User Transactions – OneSight initiates actual user 

transactions for both web and voice interactions from multiple 

points of view. By performing end-to-end tests, it exercises all 

levels of multi-tier applications, detecting bottlenecks that other 

monitoring tools might miss. 

Flexible Alerting and Reporting – When thresholds are crossed, 

OneSight sends intelligent alerts to the appropriate individuals. 

Action plans can be configured to send immediate alerts, phone, 

email, or SNMP traps. In addition, OneSight can take corrective 

1

What OneSight Monitors 

action through an automated response such as a server reboot or 

application restart. Extensive reports and charts identify system 

weaknesses and allow you to isolate a current problem, report on 

uptime, response time, or availability, and spot trends that could 

affect future performance. 

Centralized Configuration – OneSight profiles are pre-built 

collections of configuration information designed to gather the 

most important metrics for a given component, application, or 

system. You can create your own profiles or modify the pre-built 

profiles for your unique needs. 

Scalable and Flexible Architecture – OneSight can handle 

customer contact environments of any size or complexity, 

whether they are hosted on one server or distributed across 

multiple servers, networks, or continents. 


OneSight can monitor many components such as Database, DNS, 

JMX, etc. and comes with many pre-built dedicated and profile 

monitors as listed below. 

Dedicated Monitors 

Database 

DNS 

Event Log 

FTP 

Gomez GPN 

JMX 

Linux 

LDAP 

OneSight Virtual Agent 

OneSight Voice Transaction 

OneSight Voice Watch 

Perfmon 

Ping 

Port 

Process 

Service 

2 OneSight Administrator Guide


Log File, Directory 

Mail 

Applications 

OneSight Call Statistics 

OneSight Probe 

Oracle OpenScript 

Oracle Test for Web 

Applications 

AIX 

Apache for Solaris 

ATG Dynamo 

BEA WebLogic 

CheckPoint Firewall 

ColdFusion Server 

Compaq PC Server 

DB2 

DELL PC Server 

HP-UX 

iPlanet Web Server for 

Windows 

SNMP 

SNMP Trap 

TCP/IP Socket 

URL availability and 

response time 

Voice Quality 

WMI 

Linux 

Microsoft Exchange 

Microsoft IIS 

Microsoft SQL Server 

Microsoft Transaction 

Server 

Microsoft Windows 

Netscape Enterprise Server 

Oracle Database 

RealSystem Server 

(Windows) 

Solaris 

VMWare 

Chapter 1: Introduction 3

System Requirements 

Network Devices 

Cisco Catalyst 4000, 5000, 

6000 Switch 

Cobalt RAQ 4 

Network Performance 

IP throughput 

F5 Big-IP Load Balancer 

RFC1213 Network Devices 

HTTP errors encountered 

HTTP transactions 

throughput 

Any other system elements via supported data 

sources. 


There are three areas to keep in mind when you install OneSight: 

OneSight Server and Data Collector – the machine on which the 

majority of OneSight (the Console, database, and web server) 

software will be installed. 

Client Web Browser – a client machine with a network connection 

to the OneSight Server (and a supported Web browser) that you 

can use to view the OneSight Console. 

Web Components – the parts of your contact center that you want 

OneSight to monitor. 



The following diagram shows these components. 

Client Web 

Browsers 

OneSight 

Server 

Monitored 

Contact Center 

Components 

Web Server 

Client Web 

Browser 

Application Server 

Database Server 

There are two processes that collect data and send it to the 

OneSight server. They are the Data Collector and Remote Agent. 

By default, the Data Collector is installed on the OneSight Server, 

however, it is recommended that you install the Data Collector on 

another machine. Refer to “Installing the OneSight Data 

Collector/Remote Agent” later in this chapter. 

The system requirements for the OneSight Server, client Web 

browser, and Web components are listed in the sections below. 

OneSight Server and Data Collector Requirements 

OneSight should be installed on a separate machine from those you 

want to monitor. Ideally, the OneSight Server should be on the 

same side of the firewall as any monitored Web servers. 

The machine on which you install OneSight (the OneSight Server) 

should meet the following requirements: 

Dual 2 GHz processor (dual core) 

4 GB RAM or more recommended 



Windows 2003/2008 Enterprise Server with Service Pack 2 

(recommended) or higher Server edition. 

Internet Explorer, version 7.0/8.0, or FireFox version 2.0/3.0 

2 x 100 GB with Raid 1 configuration available disk space, 

including 260 MB on the system drive 

The machine on which you install a Data Collector should meet the 

following requirements. 

Intel Xeon, Pentium 4 520 or Pentium M745 CPU 

2 GB RAM or more recommended 

Windows 2003/2008 Enterprise Server with Service Pack 2 

(recommended) or higher Server edition. 

60 GB for the Data Collectors 

Additional Requirements 

The OneSight server machine has the following additional 

requirements: 

Administrative rights on machines on which OneSight is installed 

Network connectivity between the OneSight Server, its client 

browsers, and the web site components it’s monitoring. Ideally, it 

should be on the same subnet (in other words, on the same side of 

the firewall) as any monitored web servers. 

OneSight should be on a separate machine from the monitored 

machines and systems. 

(Optional) Oracle OATS, version 9.1 if running Oracle Test for 

Web Application transactions. Contact Oracle for information on 

obtaining Oracle OATS. 



Database Requirements 

The requirements for the database are the same as the OneSight 

Server with the following exceptions: 

4 x 300 GB with Raid 1 Configuration minimum available disk 

space 

SQL Server 2005/2008 Standard and Enterprise editions 

including SQL Server named instances. (Express edition is not 

supported.) 

Client Web Browser Requirements 

PC Clients 

You can connect to the OneSight Server from a Windows PC or 

UNIX machine and view the OneSight Console using one of the 

following browsers: 

Recommended: Internet Explorer version 7.0 

Firefox, version 2.0 or version 3.0 

UNIX Clients 

Firefox, version 2.0 or version 3.0 

Notes About Web Browser Requirements 

Macromedia’s Flash Plug-in, version 5 or higher, must be 

installed on your machine to view report graphs. OneSight 

reports use PopChart from CORDA Technologies with Flash to 

create the graphs. 

Javascript must be enabled in the browser for OneSight to 

operate. 

Popup blockers must be turned off for OneSight to operate. 

Following is a list of browsers and popup blockers with 



instructions for turning them off or accessing their help for 

instructions. 

Firefox – Select Options from the Tools menu. Uncheck Block 

Popup Windows. 

Internet Explorer – Select Pop-up Blocker from the Tools menu. If 

the pop-up blocker is on, select Turn Off Pop-up Blocker. 

Google – Refer to http://toolbar.google.com/popup_help.html. 

Yahoo – Refer to http://help.yahoo.com/help/us/toolbar/pub/index.html. 

A client screen resolution of 1280x1024 or larger is 

recommended for optimal viewing. 

Contact Center Component Requirements 

Contact center components are the parts of your customer service 

environment that you want OneSight to monitor. OneSight can 

monitor many types of components, including CPUs, URLs, 

databases, and web servers, etc., from a large set of customer 

contact center specific equipment. 

Monitors for Web components are configured using the OneSight 

interface to enter details such as URLs, user names, and passwords. 

Some web components, however, may require extra configuration 

outside of OneSight, because of either their location or the data 

sources OneSight relies on. 

In some situations, installing the OneSight Data Collector or 

Remote Agent may be the best way to receive information about a 

web component. The OneSight Data Collector or Remote Agent can 

collect information more efficiently than some data sources, plus 

they have the ability to run remote scripts to correct problems. 

Installing the Data Collector or Remote Agent is a separate process 

from OneSight Setup and is optional. 



The evaluation procedures included in this document do not require 

additional component configuration, but if you wish to evaluate 

other components, refer to Configuring Web Components in 

Chapter 2. This section also lists web components that may require 

some extra configuration for OneSight to monitor them. For the full 

list of what OneSight supports, refer to What OneSight Monitors in 

this chapter. 

Note: If the monitored web component is on the other side of a 

firewall, non-transparent controller (such as F5’s BIG-IP), router, or 

switch, you may need to do some extra configuration (for example, 

enable a port on a firewall) to allow data to pass from the monitored 

web component to the OneSight server. 



[This page intentionally left blank.] 



Installing OneSight 

This chapter explains how to install OneSight, start and stop the 

OneSight service, view version and database information, perform 

database maintenance, and remove OneSight. 

What OneSight Installs 

Third-Party Software 

OneSight installs onto the Windows machine that you designate as 

the OneSight Server. During installation, the following third-party 

software components are installed: 

Corda’s PopChart for reports 

i-net’s SPRINTA JDBC driver, version 2000 

In addition, we supply installation files for Macromedia’s Flash 8.0 

for reports. The installation files are located in the flash directory of 

the server installation directory. The file names are as follows: 

IE Browsers – install_flash_player_active_x.msi 

Macintosh Browsers – install_flash_player_osx.dmg 

Non-IE Plug-in based Browsers – install_flash_player_plugin.msi 

Windows uninstall for all versions – uninstall_flash_player.exe 

11


Services 

The following services should be up and running when the 

installation is complete: 

Empirix OneSight on the Server machine. The process is 

OSServer.exe. 

Empirix OneSight Data Collector for each Data Collector 

installed either on the Server or monitored machines. There are 

two processes: AHP.exe and OSDC.exe. 

Empirix OneSight NT Remote Agent on the monitored machine. 

The process is AHP.exe. 

Empirix OneSight PopChart on the Server machine. The process 

is OSChart.exe. 


Before you install Empirix OneSight, refer to the OneSight system 

requirements. If you are upgrading OneSight, close the OneSight 

Console before you run OneSight Setup. The OneSight setup will 

uninstall the existing version, then stop. Rerun OneSight Setup to 

continue. 

Otherwise, the installation procedure is the same for both an initial 

install and an upgrade. Upgrading does not require that you remove 

the existing OneSight version first. The machine does not need to 

be rebooted when the install is finished. 

Note: If you are installing OneSight on a new server and you are 

using a restored/existing database, use the same settings as the 

previous installation. If you are not sure of the settings, consult with 

Empirix support or professional services. 

The OneSight server and reports can connect to the database server 

through NTLM authentication using the jTDS driver. OneSight must 



run under a domain account with privileges to access the SQL 

server. In addition the OSServer.properties file must be changes as 

follows to enable a trusted connection: 

# use trusted connection, value: true/false 

# when a trusted connection is used, UserName but 

the current Windows login account will be used to 

connect to database 

Database.TrustedConnection = true 

1. Log on, with administrative privileges, to the Windows 

machine on which you’ll install OneSight. This machine will 

become the OneSight Server. 

2. Open Windows Explorer to the Empirix CD-ROM or the 

directory where you downloaded the OneSight file and doubleclick 

the OneSight .exe file. 

3. Click Next when the Welcome to OneSight Setup dialog box 

appears. 

4. If you are using a database that has been configured with an 

instance name, you may get the following message: 

Setup has identified evidence of a Microsoft SQL Server install but was 

unable to locate expected registry keys. This may indicate that only the 

Client Tools have been installed. 

You will then be asked to provide a path to osql.exe. 

For SQL 2005 and 2008: Mapping a network drive will not 

work. You must install SQL 2005 client tools on the 

OneSight server. Client tools can be installed from the SQL 

2005 installation by selecting the option to install client tools 

only. 

Navigate to its location. For example, C:\Program 

Files\Microsoft SQL Server\80\Tools\Binn. 

Click OK. 

Chapter 2: Installing OneSight 13


Click Next. 

5. Empirix OneSight can use a standard version of Microsoft SQL 

Server 2005 or Microsoft SQL Server 2008 for use as the 

OneSight production database. 

Note: The default password is blank when installing OneSight 

with an SQL database. 

If you have a previous version of Empirix OneSight, you’ll be 

notified of the impact of the database upgrade to your existing 

OneSight configuration. 

Setup allows you to specify the location of the remote SQL 

Server or the drive on which to create database files, and 

reminds you to create Remote Folders for OneSight. 

If SQL Server is already installed on the OneSight Server: 

OneSight Setup will inform you that OneSight will use that 

installation as its database application. Click Next. 

6. Select I accept the License Agreement in the License Agreement 

dialog box and click Next. 

7. Select OneSight Server from the list of features to install and 

click Next. 

8. The SSL Configuration dialog box is displayed. Select either 

HTTP on port or HTTPS on port. The default port numbers are 

displayed for a new installation. The currently configured ports 

are displayed for an upgrade. If you change the port, the current 

configuration is overwritten. 

If you are using HTTPS you can optionally enter SSL certificate 

information. The certificate is created regardless of whether 

data is entered. The server name must be the DNS resolvable 



name of the OneSight server, not ―localhost‖ or an IP address, 

and it must match the name in the OSServer.properties file. 

The SSL Certificate Information is saved to the 

InstallationOptions.properties file. If you reinstall OneSight, the 

dialog box is populated with the information saved in this file. 

Note: If you change the information in the 

InstallationOptions.properties file, the changes do not go into 

effect until you reinstall OneSight. 

Note: If you are upgrading from a version prior to OneSight 

version 8.0 that had SSL certificate information configured for 

HTTPS, that information will not be displayed in this dialog 

because prior to version 8.0 SSL certificate information was 

stored in a different file. 

9. Specify the drive and directory where you want OneSight 

installed in the Destination Folder dialog box. If you have 

limited space on your system drive (C:), you can install 

OneSight on another drive. 

10. Click Next in the Start Installation dialog box. A few minutes 

will pass while OneSight Setup installs OneSight. 

11. If you are using a database configured with an instance name 

you will need to specify the database name and the location of 

various files: 

Enter the database instance name and password, if there is 

one, and click Next. 

Specify the database files folder by navigating to C:\Program 

Files\Microsoft SQL Server\MSSQL&\data and click 

OK. If you are installing OneSight on a different server than 

the SQL server, specify the actual path to the database files 

that are local to the SQL server. For example, C:\Program 

Files\Microsoft SQL Server\Data\… Click Next. 



Specify the log file folder by navigating to C:\Program 

Files\Microsoft SQL Server\MSSQL&\log and click OK. 

Click Next. 

Specify the database backup folder by navigating to 

C:\Program Files\Microsoft SQL Server\MSSQL&\backup 

and click OK. Click Next. 

Note: OneSight does not support a configuration where two 

OneSight installations point to the same database. 

12. The database installation status screen displays while the 

database is installed. 

13. Before you can begin collecting metrics, a Data Collector must 

be installed. OneSight will prompt you to install a Data 

Collector on the OneSight server. Click Yes. 

Note: If the machine name of the OneSight Server contains an 

underscore (―_‖), you must change the host name in the Web 

section of the OSServer.properties file located in the 

Empirix/OneSight/properties folder to reference the IP address 

instead of the machine’s host name. Because of the way Internet 

Explorer handles cookies when the machine name contains an 

underscore, you may not be able to log in if you do not make 

this change. 

14. Click Finish in the final Setup dialog box, then review the 

OneSight ReadMe file while Empirix OneSight prepares its 

database and web server connections. 

15. Start OneSight by clicking Start, pointing to Programs, then 

Empirix OneSight, then clicking OneSight Logon. 

Note: If you run INITDB after an installation failure, check the 

Create UserID check box so that the Empirix Administrator account 

is created successfully. 



Configuring SQL 2005 and 2008 

Enabling Mixed Authentication Mode 

During the SQL installation, select Mixed Mode in the 

Authentication Mode dialog box. 

Turning on XP_CMDSHELL 

For SQL 2005 and 2008, XP_CMDSHELL must be turned on. Run 

the following query: 

EXECUTE sp_configure 'show advanced options', 1 

RECONFIGURE WITH OVERRIDE 

EXECUTE sp_configure 'xp_cmdshell', '1' 


EXECUTE sp_configure 'show advanced options', 0 



Changing Session Timeout 

Changing Session Timeout 

The OneSight Server default session timeout is two hours. If you do 

not do anything for two hours after you log in, the server terminates 

your session. You can change the default session timeout by editing 

the following line in the web.xml file in the conf directory. 

120 

Changing the OneSight Server Default Port 

If you need to change the OneSight server default port, change the 

following line in the OSServer.properties file on the OneSight Server. 

Web.OneSightServer.Port = 8080 

Enabling SSL for the OneSight Server 

When you enable SSL for the OneSight server the default way to 

access the server becomes https://. The process for 

enabling SSL is located in the \empirix\onesight\support\howtohttps.txt 

file on the OneSight server. 

Updating Profiles After Upgrading OneSight 

When you upgrade to a new version of OneSight, newer versions of 

profiles may be installed. Use this procedure to upgrade to the new 

profiles. If you have customized a profile but have not changed the 

name, this procedure replaces the profile. Profiles with altered 

names are not affected by this procedure. 

To save profiles before upgrading, select the profile in the Profile 

Manager and click Clone. A copy of the profile appears in the list. 

Note: A copy of the profile is saved in the profiles list; however, 

only the original version remains as an applied profile. To apply the 


Installing the OneSight Data Collector or Remote Agent 

cloned profile to a system, you must modify existing monitors or 

create new monitors. 

To upgrade to the newer profiles: 

1. Click Import in the Profile Manager. 

2. Select a profile to upgrade and click Import. 

3. Click Yes to upgrade each metric used by your current profile. 

Note: You may be asked to confirm an overwrite of your 

profile. Click Yes to All to upgrade all of the metrics for the 

selected profile. 

Installing the OneSight Data Collector or Remote 

Agent 

The OneSight Data Collectors and Remote Agents respond to 

requests from the OneSight Server to run scripts or submit data 

concerning the machine the agent is installed on. Installing the 

OneSight Data Collector or Remote Agent is a separate process 

from OneSight Server Setup. 

The OneSight Remote Agent can be installed in the following 

environments: 

PCs running Windows 2003/2008 Enterprise Server with Service 

Pack 2 or higher with 20 MB available disk space. 

UNIX workstations running Solaris version 9 or 10, SPARC 

platform only, Linux version 9 or higher, RedHat Enterprise 

version 5 with 20 MB of available disk space (once installed, the 

Remote Agent only needs 6 MB of available disk space). 

The OneSight Data Collector can be installed in the following 

environment: 



PCs running Windows 2003/2008 Enterprise Server with Service 

Pack 2 or higher with 60 GB available disk space. 

For instructions on updating OneSight Data Collectors or Remote 

Agents remotely, refer to ―Updating Data Collectors or Remote 

Agents‖ later in this chapter. 

Data Collectors and Remote Agents 

A Data Collector is installed on a machine and collects data from 

the local machine as well as other remote machines. The Remote 

Agent is installed on a single machine and collects data from that 

machine. Both send the data back to the OneSight server. 



The following diagram illustrates the difference between these two 

processes: 

Remote Agent 

Machine 

Windows 

Machines 

Monitored by the 

Remote Data 

Collector 

Windows 


Server 

Windows 

UNIX Variant 

Remote Data 

Collector Machine 

UNIX Variant 

Windows 

If you only install a Remote Agent, you can only use the following 

mechanisms to monitor Windows : 

Logfile 

Process Monitor 

NTEventLog 

NTService 

Perfmon 

Script 



The Java component of the Data Collector has the following 

additional mechanisms: 

Database 

DNS 

FTP 

Mail 

URL 

Ping 

Port 

SNMP 

SNMP Trap 

Oracle Test for Web 

Applications 

Empirix FarSight 

ComPlus 

Virtual Agent 


Empirix Voice Watch 

Should I Install the Data Collector or Remote Agent? 

You should decide whether or not to install the Data Collector or 

Remote Agent based on the following: 

Discovering components without specifying authentication 

information: To discover components or services on a system, you 

must provide more detailed authentication information when no 

OneSight Data Collector or Remote Agent is present on the 

monitored systems. 

Security: Receiving data from machines outside your firewall can be 

tricky from a security viewpoint. For example, to receive Perfmon 

data through a firewall, you might need to enable the firewall’s 

DCOM port. While doing this may give you valuable performance 

information, it may also make your firewall more vulnerable to 

security attacks. 

Automation: With the OneSight Data Collector or Remote Agent, 

you can run scripts to automate tasks or take corrective action. For 



example, a OneSight Data Collector or Remote Agent on your web 

server could automatically run a script that would restart your web 

server if it were to shut down. 

Logging: If you want to look at logging information for an operating 

system or a web server, the Data Collector or Remote Agent is 

required. In addition, the profile associated with the Apache 

monitor requires the Remote Agent in order to use information from 

the Apache log file. 

Performance: While enabling some data sources, such as Perfmon, 

on the machines you’re monitoring can provide you with important 

data, it may also generate more network traffic than is necessary. 

The OneSight Data Collector or Remote Agent can collect the data 

you need while generating fewer network packets. 

Note: The Linux Remote Agent does not do discovery. Use the 

virtual agent to discover Linux objects. The Linux Remote Agents 

supports Process, and Log File monitors and can be used to run 

remote shell scripts. 

Remote Agent Installation Requirements 

You can install the OneSight Remote Agent in the following 

environments: 

PCs running Windows 

The machine must have at least 20 MB of available disk space. 

To install the OneSight Remote Agent, you must log on with 

administrative rights. 

UNIX, Linux, RedHat, or Solaris Workstations (SPARC platform 

only) 

The machine must have at least 20 MB of available disk space (once 

installed, the Remote Agent only needs 6 MB disk space). 



To install the OneSight Remote Agent, you must log on with 

super-user rights (root access). 

Note: For Linux systems, GNU C++ Runtime Library 3.4 

(libstdc++-3.4) or later is required. You can check that by shell 

command rpm -qa | grep stdc++. If not installed, the message, 

―error while loading shared libraries: libstdc++.so.6,‖ may be 

encountered when starting the Agent. Contact your administrator to 

install or update. 

Installing the Remote Agent on Windows 

Before you install the OneSight Remote Agent, see the OneSight 

Remote Agent requirements. To install the OneSight Remote Agent 

on a Windows machine, you will need to do two things: 

Install the Remote Agent 

Identify the Remote Agent machine to the OneSight Server 

You can use an initialization file (winnt_agent_setup.ini) as a shortcut 

for installing the Remote Agent on multiple machines. 

Note: If you are installing the Remote Agent to monitor disk 

performance on a Windows machine, Diskperf -yv must be 

enabled on that machine. 

To install the Remote Agent: 

1. Copy winnt_agent_setup.exe from the 

Empirix\OneSight\Setup\RemoteAgents folder on the OneSight 

Server to the machine where you want to install the OneSight 

Remote Agent. The Remote Agent cannot be installed on the 

OneSight Server. If the OneSight server software is detected, 

the setup program for the Remote Agent will not continue. 

2. Log on, with administrative privileges, to the Windows 

machine where you want to install the Remote Agent. If the 



currently logged-on user does not have appropriate privileges, 

you will see an error message. 

3. Using Windows Explorer, double-click winnt_agent_setup.exe. 

4. After a few moments, the Welcome to OneSight Remote Agent 

Setup dialog box appears. Click Next. 

5. Read the license agreement and click Accept. 

6. In the Destination Folder dialog box, select where the Remote 

Agent files should be installed. Click Next. 

7. It is recommended that you leave Enable Remote Update enabled 

and click Next. 

8. Click Next in the Start Installation dialog box. A few seconds 

pass while OneSight Remote Agent Setup copies files. 

9. After files have been copied, Setup requests the OneSight 

server name. 

10. In the final Setup dialog box, click Finish. The Remote Agent is 

installed. 

To confirm this: 

Click Start, point to Settings, then click Control Panel. 

Double-click Services. The Services dialog box opens. 

In the Services list, the Empirix OneSight NT Remote Agent 

should be listed, with a Status of Started and a Startup value 

of Automatic. 

To close the Services dialog box, click Close. 

11. Identify the Remote Agent machine to the OneSight Server as 

described below. 



Identifying the Remote Agent Machine to the OneSight 

Server 

1. On the OneSight Server, log in to Empirix OneSight by clicking 

Start, pointing to Programs, then clicking OneSight Logon. 

2. Log in to Empirix OneSight. 

3. On the Configure tab, click Systems. The dialog box now 

shows a Systems list. 

4. If the machine where the Remote Agent is installed is: 

Not listed under Systems: 

Click Add. 

In the Add System dialog box, enter the machine’s name and 

click OK. 

Listed under Systems: 

Highlight the machine’s name in the Systems list and click 

Modify. 

5. In the System Editor, click the Discover Components button. 

6. Select the OneSight Remote Agent for Windows or Remote 

Perfmon check box in the Discover Components Configuration 

dialog box and click OK. You do not need to specify the 

Windows user name, domain, or password settings. Click OK. 

7. In the Discovery Status dialog box, after the Find Finished 

message appears, click Cancel. 

8. Click OK to close the System Editor. 



To create a monitor group based on or including the machine on 

which you installed the Remote Agent, see Configuring a Profile 

Monitor in Chapter 5. 

Using an Initialization File for Remote Agent Setup 

You can speed installation on multiple machines by using an 

initialization file, winnt_agent_setup.ini to specify the OneSight 

Server name. A sample winnt_agent_setup.ini is located on the 

OneSight Server in the same folder as winnt_agent_setup.exe. 

1. Copy winnt_agent_setup.exe and winnt_agent_setup.ini from the 

OneSightEmpirix\Setup\RemoteAgents folder on the OneSight 

Server to a CD-ROM or to a network server. 

2. Edit the winnt_agent_setup.ini. In the Server= line in the [OneSight] 

section, specify the full address of your OneSight server. An IP 

address for the OneSight Server is recommended so that the 

Remote Agent can continue to function when DNS is not 

available. 

3. Run the setup program as described above for each machine 

that requires the OneSight Remote Agent. When you are 

prompted to specify the OneSight Server, the information in the 

.ini file setting is displayed by default. 

Installing the UNIX Remote Agent 

The UNIX Remote Agent gives Empirix OneSight access to UNIX 

system data. This Remote Agent gathers CPU, disk, and memory 

information from a UNIX server running the Solaris 5.8 or higher, 

SPARC platform only, or Linux 9 or higher operating system. It can 

also be used to monitor web server log files and run remote shell 

scripts. 



The UNIX Remote Agent can be installed using a self-extracting 

shell program. 

The OneSightSolaris.tar and OneSightLinux.tar files can be downloaded 

from http://esupport.empirix.com/. You will need a user name and 

password to access the esupport site. Click Request an Account 

when the login page is displayed. 

Each .tar file contains _setup file for installing the UNIX Remote 

Agent. The _setup file is a standalone installation file that prompts 

you for the necessary information. 

The _setup files are: 

sunos_agent_setup – for Remote Agents (AHP/C ++ Agent types 

only) 

linux_agent_setup – for Remote Agents (AHP/C ++ Agent types 

only) 

Installing the UNIX Remote Agent 

The OneSightSolaris.tar and OneSightLinux.tar files can be downloaded 

from http://esupport.empirix.com/. You will need a user name and 

password to access the esupport site. Click Request an Account 

when the login page is displayed. 

Each .tar file contains _setup file for installing the UNIX Remote 

Agent. The _setup file is a standalone installation file that prompts 

you for the necessary information. 

To use the UNIX Remote Agent, run the installer. You can also 

configure the UNIX Remote Agent to start and stop with the UNIX 

server; however, this step is optional. Before you install a OneSight 

Remote Agent, see the OneSight Remote Agent Requirements. 



To install the UNIX Remote Agent on a UNIX server: 

1. Navigate to the Empirix\OneSight\setup\RemoteAgents\Solaris 

folder on the OneSight CD. 

2. Extract the sunos_agent_setup or linux_agent_setup installer file 

using the following commands. 

Solaris: 

Linux: 

tar -xvf OneSightSolaris.tar 

tar –xvf OneSightLinux.tar 

tar –xvf OneSightLinuxAgent.tar 

3. Copy the sunos_agent_setup or linux_agent_setup installer to the 

UNIX machine using FTP or via a network drive. 

4. On the UNIX machine, run the installer. 

Solaris: sh sunos_agent_setup 

Linux: sh linux_agent_setup 

Note: You may need to change the permissions of the installer 

file before it can be executed. For example: 

Solaris: chmod 777 sunos_agent_setup 

Linux: chmod 777 linux_agent_setup 

5. When prompted, enter an installation path for the Remote 

Agent. For example: 

//OneSight 

The installation path must be an absolute path. 

Note: An installation subdirectory is created using the path you 

specify. All files for the Remote Agent are installed to this 

installation subdirectory. For example, //OneSight 



6. When prompted, enter the IP address of the OneSight Server to 

which the Remote Agent will connect. If you are running the 

installer as root, you will be prompted for the name of the 

owner and group for the installed files. For example: 

root 

sys 

The owner will also be the user that the UNIX Remote Agent 

process will run as when it is started via the OneSightAgent 

script. 

Once this information is complete, the installation begins: 

Extracting files from installer . . . 

Uncompressing files . . . 

Installing files into [install-dir] . . . 

(You will see the files being extracted and installed during this period.) 

Writing configuration file . . . 

Writing sample Startup/Shutdown script . . . 

Cleaning up temporary files . . . 

The OneSight Remote Agent was successfully installed in 

//OneSight 

Running the UNIX Remote Agent 

To run the Remote Agent, use one of the following commands: 

OneSightAgent start – This command runs the OneSightAgent 

script supplied by the OneSight Remote Agent package. The 

script, followed by the start command, initializes the UNIX 

Remote Agent (ahp). This script must be run as root. 

OneSightAgent stop – This command stops the UNIX Remote 

Agent (ahp). 



bin/ahp& – This command starts the UNIX Remote Agent 

directly. The ampersand (&) following a command tells the UNIX 

shell to run that program in the background. This is not 

recommended although the Remote Agent will not be restarted 

automatically if it is stopped for some reason such as being reset 

by the OneSight Server. 

Note: Do not run multiple instances of the UNIX Remote Agent 

(ahp) simultaneously. More than one instance of ahp will result in 

loss of data due to competing connections between the OneSight 

Server and the host machine. 

Starting and Stopping the UNIX Remote Agent 

To configure the UNIX Remote Agent to start and stop with the 

server, complete the following steps. 

A note about the initialization and termination process: On the UNIX 

operating system, scripts intended to be used for initialization and 

termination are located in the /etc/init.d directory and linked to files 

in the appropriate rc?.d directories, depending on which priority 

level is intended. To configure the UNIX Remote Agent to start and 

stop with the UNIX server machine, this process must be completed. 

For additional information, refer to the /etc/init.d/README file. 

1. On the UNIX server, navigate to the installation subdirectory 

(for example, [install_dir]/OneSight). This directory was added 

during the sunos_agent_setup or linux_agent_setup installation. 

2. Copy the OneSightAgent file to the /etc/init.d directory. 

3. Using the /etc/init.d/README file as a guide, create a link to the 

OneSightAgent file in the appropriate rc?.d directories. These 

linked files enable the initialization and termination of the 

Remote Agent scripts when the UNIX server is started or 

stopped. For example, 

# ln –s /etc/init.d/OneSightAgent /etc/rc2.d/s99OneSightAgent 

# ln –s /etc/init.d/OneSightAgent /etc/rc1.d/k70OneSightAgent 



4. Start the agent manually or reboot the server to start the Remote 

Agent. 

With the UNIX Remote Agent installed and running, the Empirix 

OneSight Server is able to collect data from this machine. For more 

information regarding the configuration of a UNIX machine, see 

Adding Systems in Chapter 7. 

Data Collector Installation Requirements 

You can install the OneSight Data Collector in the following 

environment: 

PCs running Windows 2003 Server or higher server version 

The machine must have at least 70 MB of available disk space 

and 2 GB of RAM. 

To install the OneSight Data Collector, you must log on with 

administrative rights. 

Installing the Data Collector on a Windows Machine 

To install the OneSight Data Collector on a Windows machine: 

1. Copy collector_setup.exe from the 

Empirix\OneSight\Setup\RemoteAgents folder on the OneSight 

Server to the machine where you want to install the OneSight 

Data Collector. 

2. Log on, with administrative privileges, to the machine where 

you want to install the Data Collector. If the currently loggedon 

user does not have appropriate privileges, you will see an 

error message. 

3. Using Windows Explorer, double-click collector_setup.exe. 



4. After a few moments, the Welcome to OneSight Data Collector 

Setup dialog box appears. Click Next. 

5. Read the license agreement and click Accept. 

6. In the Destination Folder dialog box, select where the Data 

Collector files should be installed. Click Next. 

7. Enter the host name or IP address of the OneSight server and 

click Next. 

8. Leave the default location name for this Data Collector, or 

optionally enter your own unique name. Click Next. 

9. The JMX Proxy dialog box is displayed. Select the application 

server(s) that you are using. If you are not using a JMX monitor 

and do not select anything you will be asked to confirm. 

One proxy can monitor all application servers or the same type 

with the following exceptions: 

WebLogic 9 and WebLogic 10 cannot be monitored by the 

same proxy. You must install two proxies, one for each, if 

you are monitoring both of these application servers. 

WebSphere 6.0 requires the proxy to be configured only for 

it. 

WebLogic 8.1 is monitored by the proxy on JRE1.4. All 

other applications servers are monitored by JRE 1.5. If you 

are monitoring other versions of WebLogic 8.1 you must 

install a Data Collector and proxy for each. 

Refer to, “Using the JMX Proxy,” below for more information. 

Note: You still need to copy the appropriate jar files to the 

appropriate locations as described in “Configuring JMX 

Monitors” in Chapter 5. 



10. It is recommended that you leave Enable Remote Update 

selected. 

11. Click Next in the Start Installation dialog box. A few seconds 

pass while OneSight Data Collector Setup copies files. 

Note: If you are installing the Data Collector to monitor disk 

performance on a Windows machine, Diskperf -yv must be 

enabled on that machine. 

12. In the final Setup dialog box, click Finish. The Data Collector is 

installed. 

To confirm this: 

Click Start, point to Settings, then click Control Panel. 

Double-click Services. The Services dialog box opens. 

In the Services list, Empirix OneSight Data Collector 

should be listed, with a Status of Started and a Startup value 

of Automatic. is the instance number for this Data 

Collector starting with one and incrementing one for every 

Data Collector instance you install. 

To close the Services dialog box, click Close. 


Using the JMX Proxy 


The following diagram shows the relationship between the JMX 

Proxies and the Data Collector. 

Each JMX Proxy runs as a Service. There are three proxies in the 

above diagram, so there would be three services. 

Each JMX Proxy must know which Data Collector it connects to. 

This is done by configuring the Data Collector host and port during 

the JMX Proxy installation. 

Each JMX Proxy is in charge of performing JMX operations to the 

application servers. The Data Collector dispatches the JMX requests 

to a certain proxy. After the proxy gets the data, it sends it back data 

to the Data Collector. 

Each JMX Proxy can get data from one type of application server 

only and only one proxy should run with each type of application 

server. For example, JMX Proxy 1 can get data from JBoss 3, JBoss 

4 and JBoss 5, JMX Proxy 2 can get data from Weblogic 9; and JMX 

Proxy 3 can get data from Weblogic 10. In addition, some 

application servers cannot be monitored by one proxy for all 

versions as described below. In these cases you must install a proxy 

for each version. Since the Data Collector installer only installs one 

JMX Proxy, you must manually install additional proxies. 



WebLogic 9 and WebLogic 10 cannot be monitored by the same 

proxy. You must install two proxies, one for each, if you are 

monitoring both of these application servers. 

WebSphere 6.0 requires the proxy to be configured only for it. 

WebLogic 8.1 is monitored by the proxy on JRE1.4. All other 

application servers are monitored by JRE 1.5. If you are 

monitoring other versions of WebLogic 8.1 you must install a 

Data Collector and proxy for each. 

When installing the Data Collector, you can install JMX Proxy for 

JRE 1.4 or JRE 5.0. JMX Proxy for JRE 1.4 is only for very old 

Application Servers that cannot be monitored by a proxy that runs 

on JRE 5.0, such as Weblogic 8.1. 

Installing JMX Proxy Automatically 

To install the JMX Proxy automatically: 

1. Start the JMX Proxy installer. 

2. Click I Agree to accept the license agreement. 

3. Enter the data collector host and port numbers. 

4. Select which application server the proxy is to monitor and 

click Next. 

5. Select the folder that you want to install the proxy in and click 

Install. 

6. When the installation is finished, the message, ―Empirix 

OneSight JMX proxy for JRE 5.0 is installed. Please start it 

from Service Management Console,‖ is displayed. Click OK. 



To uninstall the JMX Proxy automatically: 

1. Start the JMX Proxy uninstaller. 

2. Click I Agree to accept the license agreement. 

3. Enter the data collector host and port numbers. 

4. Double-click uninstall.exe and follow the wizard to uninstall. 

Installing JMX Proxy Manually 

To install the JMX Proxy manually: 

1. Copy either the Proxy15 or Proxy14 folder located in the 

\JMXProxy folder and rename it to a 

meaningful name. Note that the folder name cannot contain 

spaces. 

2. Edit the service name and description located in the 

\properties\proxy_win_service.properties file in the newly created 

folder. The service.name is the name for the new JMX Proxy 

service and must be unique. The service.description is the 

name that will be displayed in the Services console. 

3. Double click the installService.bat file located in the \bin folder 

in the new proxy folder. This command registers the service 

into Windows. 

4. Open the Services console by clicking Start, Settings, Control 

Panel, Administrative Tools, Services. 

5. Select the new JMX Proxy service and click Start. 

Configuring the JMX Proxy 

The JMX Proxy configuration file is 

\properties\service.properties. It contains the following 


Post Installation 

properties for configuring which data collector this proxy is talking 

to: 

DC.SERVER = 127.0.0.1 

DC.JMXMONITORPORT = 5100 

The following property indicates the application server that this 

proxy will get data from. It contains comma-separated application 

server names. 

PROXY.SupportedJMXServers = weblogic100;jboss50;jboss32 

In the above example, the JMX Proxy will tell the Data Collector 

that it can handle JMX requests to Weblogic 10, JBoss 50 and JBoss 

3. 

The following property is for configuring which network interface 

to use if your server has more than one network adapter. By default, 

it is commented out since the JVM usually selects the correct 

address. 

# PROXY.IP = 127.0.0.1 

The following properties are for configuring the jar library for each 

application server and do not usually need to be changed. 

Agents.JMX.Server.weblogic61.ClassPath = 

classes/weblogic6.1/weblogic.jar 

Agents.JMX.Server.weblogic70.ClassPath = 

classes/weblogic7.0/weblogic.jar 

…… 

Post Installation 

Once OneSight is installed you can verify that the server is 

responding by going to http://:8080 and log in to 

OneSight. You can also verify that the server is running and Data 

Collectors are connected using the support page or Location dialog 


OneSight Agent Proxy 

box on the OneSight Configure tab. Select Support from the Main 

Menu, then select OneSight Server Connections from the Agent 

Diagnostic Support menu. 

If the OneSight Server is not responding, check the OneSight log 

located in the C:\Empirix\OneSight\logs directory. 

For information about the database, check the InstallDatabase.log file 

located in the C:\Empirix\OneSight\logs directory. 


In the default OneSight setup, all Data Collectors and Remote 

Agents make the initial connection back to the OneSight server as 

shown in the following diagram. 


DC1 

Firewall 

Agent1 

Agent2 

DC2 

However, there are situations when this is not desirable, particularly 

when you are trying to monitor behind a firewall or DMZ, or when 

you only want one connection back to the OneSight server. 



The Agent Proxy allows connections to be made from Data 

Collectors and Remote Agents to the OneSight server through a 

single connection from the Agent Proxy to the OneSight Server as 

shown in the following diagram. 

Agent Proxy 

DC1 

Firewall 


Agent1 

Agent2 

DC2 

Note: The Agent Proxy only works with the STD protocol that 

OneSight uses to communicate with the Data Collectors and 

Remote Agents. It will not pass HTTP traffic. 

To install the Agent Proxy you must complete the following steps: 

Install the Agent Proxy 

Configure Data Collectors and Remote Agents 

Configure OneSight 

Debug 

Installing the Agent Proxy 

1. On the proxy machine, create the following directory: 

\Empirix\OneSight\Proxy. 



2. From the OneSight Server, copy the service.exe, proxy.exe and 

proxy.properties files from the \Empirix\OneSight\bin 

directory to the \Empirix\OneSight\Proxy directory on 

the proxy machine. 

3. On the proxy machine, open the proxy.properties file and make 

the following changes: 

Proxy.imagepath = \..\bin\Proxy.exe 

Proxy.startupdir = \..\bin 

To: 

Proxy.imagepath = \..\Proxy\Proxy.exe 

Proxy.startupdir = \..\Proxy 

Note: The directory change must match the directory where the 

proxy.exe file exists, as recommendation above. If you use a 

different directory, make the appropriate changes. 

4. Make any other necessary modifications. For example, you may 

need to change the default proxy listening port or specify a 

password for accessing the proxy. The defaults are port 5007 

and a blank password. 

5. Save the file. 

6. You can now install the proxy as a service. From a command 

window, type the following: 

C:\Empirix\OneSight\Properties>C:\Empirix\OneSight\B 

in> service -install -param proxy.properties 

Note: If there are errors, see the debugging section later in this 

chapter. 

7. Start the proxy service from the services window. The Service 

is listed as Empirix OneSight Agent Proxy. Or you can start the 

service from the command window by typing the following: 



C:\Empirix\OneSight\Properties> net start 

EmpirixAgentProxy 

To stop the service from the command window type the 

following: 

C:\Empirix\OneSight\Properties> net stop 


8. The OneSight Agent Proxy should now be up and running. It 

will create log files with the naming convention 

Proxy_console.txt.X where X will denote a number. The most 

recent or active log file is always the file without a number. 

Data Collector or Remote Agent Configuration 

1. Open the OSDC.Properties file from the 

\Empirix\DataCollector\Properties directory or 

\Program Files\Empirix\OneSight\Properties and locate the 

COMM section. The default looks like this: 

Comm.ServerName = localhost 

#Comm.ServerPort = 5007 

#Comm.ConnectFrom = 192.168.0.102 

Comm.ServerName is the name of the OneSight Server. 

Comm.ServerPort is the port on which the OneSight Server will 

listen for the DataCollector or Remote Agent. 

Comm.ConnectFrom is the external IP address of the OneSight 

Server if it is within a DMZ or is subject to NAT. 

To enable this so the DataCollector uses port 5777 to 

communicate to the OneSight server you would uncomment the 

Comm.ServerPort line so the section looks like this: 

Comm.ServerName = localhost 

Comm.ServerPort = 5777 

#Comm.connectFrom = 192.168.0.102 

2. Save the file and restart the Data Collector. 



3. Repeat for all other Data Collectors that must use the Agent 

Proxy to communicate with the OneSight Server. 

OneSight Server Configuration 

1. Open the OSServer.properties file from the 

[Installdir]\Empirix\OneSight\Properties directory and locate this 

section: 

# -------------- 

# Comm.Proxy..Address 

# Comm.Proxy..Port 

# Comm.Proxy..Password 

# -------------- 

# Specifies a proxy to use for framework 

connections, 

# the port to connect to, and the (optional) 

password. 

# 

#Comm.Proxy.Proxy1.Address = DMZ1 

#Comm.Proxy.Proxy1.Port = 5555 

#Comm.Proxy.Proxy1.Password = sesame 

To enable this so the OneSight server uses port 5777 to 

communicates with the DataCollector you would uncomment 

the Comm.Proxy.Proxy1.Port line so the section looks like 

this. 

#Comm.Proxy.Proxy1.Address = DMZ1 

Comm.Proxy.Proxy1.Port = 5777 

#Comm.Proxy.Proxy1.Password = sesame 

2. Save the file and restart the OneSight Server. 

Debugging the Agent Proxy 

If you encounter errors or need to verify that the Agent Proxy is 

working correctly, you may start the service in debug mode. 



1. If the Agent Proxy service is running, stop the service from the 

command window by typing the following: 

C:\Empirix\OneSight\Proxy> net stop 


2. From a command window, type the following: 

C:\Empirix\OneSight\Proxy> service -debug -param 

proxy.properties 

3. The Agent Proxy will reply with something similar to the 

following: 

Debugging Empirix OneSight Agent Proxy. 

Empirix Service Manager (INFO): started. 

Empirix Service Manager (INFO): The process 'Proxy' 

was started. 

Empirix Service Manager (INFO): All processes have 

been started. 

4. If there are any problems or error messages, they are displayed 

in the command window. The following are typical error 

messages when the Agent Proxy cannot listen on the port 

specified in the proxy.properties file. 

Empirix Service Manager (ERROR): The process 'Proxy' 

unexpectedly quit. (Last error reported by system: 

Cannot create a file when that file already exists. 

(0xb7)) 


was restarted. 


unexpectedly quit. (Last error reported by system: 

Cannot create a file when that file already exists. 

(0xb7)) 


will not run. This service will now stop. (Last 

error reported by system: Cannot create a file when 

that file already exists. (0xb7)) 



5. To stop the debugging, press CTRL-C in the command window 

where the Agent Proxy was started. Messages similar to the 

following messages are displayed: 

Stopping Empirix OneSight Agent Proxy. 


was stopped. 

Empirix Service Manager (INFO): stopped. 

6. When the OneSight server cannot connect to the Agent Proxy, 

there will be information in the OneSight Server log similar to 

the following: 

[Wed Jan 22 18:47:56 EST 2003] 455 Framework 

Critical Error: com.wrq.wam.fw.comm.FwCommException: 

54 172.16.3.32 

at 

com.wrq.wam.fw.comm.RemoteFramework.StartReturnData( 

Native Method) 

at 

com.wrq.wam.fw.ipc.Dispatcher.sendRequest(Dispatcher 

.java:195) 

at 

com.wrq.wam.fw.ipc.RemoteAgentFramework.sendRequest( 

RemoteAgentFramework.java:838) 

at 

com.wrq.wam.fw.ipc.RemoteAgentFramework.sendAggMsg(R 

emoteAgentFramework.java:932) 

at 

com.wrq.wam.fw.agentfw.AgentFramework.checkbacklog(A 

gentFramework.java:687) 

at 

com.wrq.wam.fw.agentfw.AgentFramework$QueueWatcher.r 

un(AgentFramework.java:449) 

at java.lang.Thread.run(Thread.java:536) 


OneSight Default Ports 

OneSight Default Ports 

OneSight uses the following default ports for the OneSight Server, 

Data Collector and Proxy Server. These defaults can be changed by 

editing the OSDC.properties file. 

OneSight Server Ports 

5007 – The port used to listen on from a comm. channel. 

5008 – The JMS Server port. 

7001 – The SNMP agent port. 

8080 – The OneSight Sever with an HTTP connection. 

8443 – The OneSight Server with and HTTPS connection. 

Data Collector Ports 

5006 – The standard port for the Probe agent. 

5100 – The standard port for the JMX Proxy* 

5198 – The standard port for the Oracle Test for Web Applications 

agent debug information in the Oracle Test for Web Applications 

Transaction. The AHP listen port, the port on the Data Collector 

used by the OneSight Server to send inbound messages. 

8080 – The port used when communicating with the agent separated 

by a firewall. The JHP listen port, the port on the Data Collector 

used by the OneSight Server to send inbound messages. 

8081 – The port used when communicating with the agent separated 

by a firewall. 

445, 135, and 139 – The TCP ports that must be open from the Data 

Collector to the system under test to collect Perfmon metrics. 


Configuring Contact Center Components 

135, 445, and any dynamically assigned TCP ports above 1024 – 

The ports that WMI uses to gather statistics. 

Proxy Server Ports 

5007 – The port on which to listen for agents and for servers if no 

server port is separately specified. 

7778 – The port on which to listen for server connections and 

defaults to the agent port. 

*Port 5100 is a listening port that accepts both local host traffic and 

connections from other machines. Therefore it is possible to install 

a JMX Proxy on a different machine with a data collector. The port 

number is also based on the 5100 plus the data collector instance 

number. For example, if multiple data collectors are installed on the 

same machine, data collector 1 may listen on port 5100 and data 

collector 2 may listen on port 5101, etc. 


Contact Center components are configured using the OneSight 

interface to enter details such as URLs, user names, and passwords. 

Some web components, however, may require extra configuration 

outside of OneSight, because of either their location or the data 

sources OneSight relies on. 

In some situations, installing the OneSight Data Collector or 

Remote Agent may be the best way to receive information about a 

web component. The OneSight Data Collector or Remote Agent can 

collect information more efficiently than some data sources, plus it 

has the ability to run remote scripts to correct problems. Installing 

the Data Collector or Remote Agent is a separate process from 

OneSight Setup and is entirely optional. 

The table below lists web components that may require some extra 

configuration for OneSight to monitor them. For the full list of what 

OneSight supports, refer to What OneSight Monitors in Chapter 1. 



Note: If the monitored web component is on the other side of a 

firewall, non-transparent controller (such as F5’s BIG-IP), router, or 

switch, you may need to do some extra configuration (for example, 

enable a port on a firewall) to allow data to pass from the monitored 

web component to the OneSight Server. 

Web Component 

PCs or servers running 

Windows 2003 with 

Service Pack 1 or 

higher, and Windows 

2000 

UNIX workstations 

Web servers running 

Apache version 1.3x 


Microsoft IIS version 

4.0 or 5.0 


Netscape Enterprise 

Server version 3.6, or 

iPlanet 4.0 on UNIX 

Configuration Suggestions 

Either ensure that the OneSight Server 

can access the monitored machine’s 

Perfmon data or install the OneSight Data 

Collector or Remote Agent (for Windows 

2003 or Windows 2000). To receive disk 

performance information, execute the 

Diskperf –y command. 

Install the OneSight Remote Agent. 

Install the OneSight Data Collector or 

Remote Agent (for UNIX) and confirm 

that the OneSight Server or Data 

Collector is on the same subnet as the 

monitored web server. 




Collector or Remote Agent (for 

Windows). Also, confirm that the 

OneSight Server is on the same subnet as 

the monitored web server or Data 

Collector. 

Enable SNMP and confirm that the 

OneSight Server is on the same subnet as 

the monitored web server or Data 

Collector. To monitor an iPlanet web 

server, use the Netscape Enterprise Server 



Web Component 

machines 

Database servers 

running Oracle 

versions 8.0 or 8i 

Database servers 

running Microsoft 

SQL Server, versions 

2000 or 2003 

Switches - Cisco 

Catalyst 

Controllers - F5’s 

BIG-IP 

Configuration Suggestions 

profile. 

See Setting Up Oracle ODBC for 





Collector or Remote Agent (for 

Windows). Also make sure that the 

database server’s Perfmon installation has 

SQL objects. 

Enable SNMP. 

Enable SNMP as described in the BIG-IP 

Administrators Guide. Configure BIG-IP 

to accept SNMP requests from the IP 

address of the OneSight server. 

SNMP 

SNMP (Simple Network Management Protocol) is a basic 

query/response protocol that has become widely used on TCP/IP 

networks. SNMP provides specific performance and configuration 

information SNMP network devices, such as routers, or on hosts, 

such as workstations or mainframes. 

If you want OneSight to monitor SNMP information from any hosts 

or devices, SNMP must be enabled on those machines. Because the 

implementations of SNMP are so varied, SNMP installation 

instructions are not provided here. See the documentation provided 

with your SNMP software for more information. 



Using Perfmon 

Perfmon, or Performance Monitor, is a Microsoft computer 

performance tool that runs on Windows platforms. OneSight can 

use a monitored Windows machine’s Perfmon to gather data about 

that machine—either by using the OneSight Data Collector or 

Remote Agent (installed on the monitored machine) or by giving 

the OneSight Server access to that machine’s Perfmon data, which 

you can do by giving the OneSight Server an account with 

administrative privileges on the monitored machine. 

To check for SQL objects in Perfmon 

OneSight can also use a machine’s Perfmon SQL objects to gather 

data about a Microsoft SQL Server installation (version 2000 or 

2005) on that machine. 

If you use the profiles for Microsoft SQL Server, version 2000 or 

2005 to monitor a database server running either of those database 

applications, the OneSight Server must be able to access the 

server’s Perfmon, and the monitored database server’s Perfmon 

must have SQL objects. To check for SQL objects in Perfmon: 

1. On the OneSight Server, open the Windows Performance 

Monitor. 

2. On the Performance Monitor’s Edit menu, click Add to Chart. 

The Add to Chart dialog box appears. 

3. In the computer box, type two backslashes followed by the 

name of the monitored database server (for example, \\Stella). 

4. In the Object list, search for SQL objects, such as SQL. 

5. If you find SQL objects, OneSight will be able to collect the 

necessary SQL Server information from the machine, click Done 

to close the Add to Chart dialog box. 



Using Diskperf 

If you don’t find SQL objects, OneSight won’t be able to collect the 

necessary SQL Server information from the machine unless you 

reinstall Microsoft SQL Server version 2000 or 2005. If you accept 

the default options during SQL Server Setup, you should get the 

necessary SQL objects installed. 

Diskperf is a command that enables the Windows Perfmon counter 

that measures computer disk performance. 

You will probably have to enable Diskperf on the Windows 2000, 

2003 machines that you intend to monitor. OneSight profiles for 

Windows 2003 and Windows 2000 systems use the Perfmon 

Logical Disk counters. These counters are typically disabled by 

default on Windows 2000 and 2003 machines. 

To execute the Diskperf command 

1. Log on with administrative rights to Windows machine whose 

disk performance you want OneSight to monitor. 

2. At the command line, type one of the following: 

Non-RAID or hardware RAID PCs: diskperf –y 

Software RAID PCs: diskperf –y e 

Windows 2000 and 2003 PCs: diskperf –yv 

Note: the complete list of options for either system can be found 

by running diskperf -? 

3. Press Enter. 

4. Restart the computer. 


To log in to OneSight 

To log in to OneSight 

Using OneSight Log In 

Use the login dialog box to login to the OneSight console. 

1. In the User Name box, type your assigned user name. This entry 

is not case sensitive 

2. In the Password box, type your assigned password. This entry is 

case sensitive. 

3. Click Log In. 

Note: OneSight will log you out automatically after two hours of 

inactivity. You must log back in to OneSight to regain access to all 

OneSight Console pages. 

Using Windows Log In 

Windows Log In lets you use your Windows ID and Windows 

password for authentication. You must be configured as a OneSight 

user and the Allow Windows Login option must be checked for your 

account on the Rights tab of the User Editor. 

If you are logging in to the same physical machine as the OneSight 

server, authentication may fail and you will be asked to enter your 

user name and password as described in the following procedure: 

1. Enter your user name. The user name must be a valid user on 

the domain that the OneSight server is running on. In addition, 

the OneSight server must be part of the same domain as the 

user. 

2. Click Log In. 


Uninstalling OneSight 

Note: If you are using a Firefox browser and you make a mistake 

entering your user name or password causing the log in to fail, 

restart the browser before trying again. 


To remove Empirix OneSight from a Windows server, you need to 

do the following: 

Uninstall OneSight using Add/Remove Programs 

Uninstall the Data Collector 

Remove the database 

Delete the Empirix folder 

To Uninstall OneSight using Add/Remove Programs 

1. On the server where Empirix OneSight is installed, click Start, 

point to Settings, then click Control Panel. 

2. In the Control Panel, double-click Add/Remove Programs. 

3. On the Install/Uninstall tab, highlight Empirix OneSight and 

click Add/Remove. 

4. Click Yes to confirm and follow the uninstall procedure. 

If the Add/Remove Monitor Group dialog box is displayed, 

click Remove All, then, in the confirmation dialog box that 

follows, click Next. 

5. Click Finish in the final dialog box. 

6. Click Close to close the Add/Remove Programs dialog box. 



To Uninstall the Data Collector 

1. On the server where Empirix OneSight is installed, click Start, 

point to Settings, then click Control Panel. 


3. On the Install/Uninstall tab, highlight Empirix OneSight Data 

Collector and click Add/Remove. 

4. Click Yes to confirm and follow the uninstall procedure. 

5. Click Close to close the Add/Remove Programs dialog box. 

To Remove the Database 

1. Stop the OneSight Service. 

2. Run the following program: 

\Setup\InitDB.exe 

3. At the confirmation dialog box, click Continue. 

4. Enter the database administrator username and password, then 

select the Delete Database check box. When asked to confirm, 

click OK. 

5. After the database is deleted, click OK to exit InitDB. 

6. Remove the backup device file (for example, 

OneSight_backup.bak). If you are using a remote SQL server, the 

file is located on the SQL server machine (not the OneSight 

server). 


Removing the Data Collector from a Windows machine 

To Remove the Empirix Folder 

After uninstalling the OneSight Server, delete the OneSight 

folder. 

After uninstalling the Data Collector, delete the data collector 

folder. 

Removing the Data Collector from a Windows 

machine 

1. On the Windows 2003 machine where the Data Collector is 

installed, click Start, point to Settings, then click Control Panel. 


3. On the Install/Uninstall tab, highlight Empirix OneSight Data 

Collector(1) and click Add/Remove. 

4. In the Add/Remove Monitor Group dialog box, click Remove 

All, then, in the confirmation dialog box that follows, click Next. 


6. Click OK to close the Add/Remove Programs dialog box. 

Removing the OneSight Remote Agent 

Removing Remote Agent from a Windows Machine 

1. On the Windows machine where the Remote Agent is installed, 

click Start, point to Settings, then click Control Panel. 


3. On the Install/Uninstall tab, highlight Empirix OneSight NT 

Remote Agent and click Add/Remove. 


Removing the OneSight Remote Agent 

4. In the Add/Remove Monitor Group dialog box, click Remove 

All, then, in the confirmation dialog box that follows, click Next. 


6. Click OK to close the Add/Remove Programs dialog box. 

Removing the UNIX Remote Agent 

When the OneSight UNIX Remote Agent needs to be reinstalled or 

upgraded to the current version, it is recommended that you remove 

the existing agent files from your installation directory. 

The OneSight Remote Agent self-extracting installer only copies 

data into the specified destination directory. If you copy or link to 

script files using directories other than the installation directory (for 

example, the init.d directories), make sure these files are removed as 

well. 

1. On the machine where the UNIX Remote Agent is installed, 

navigate to the OneSight installation directory. 

2. Verify that the OneSight installation directory contains the data 

that you intend to remove. 

3. Ensure that the Remote Agent is no longer running by issuing 

the following command: 

./OneSightAgent stop 

4. Remove the OneSight and support directories, as well as the 

files they contain. For example, running rm -r ../OneSight in 

the destination directory removes the necessary directories and 

files. 

5. Remove any files copied or linked to in directories other than 

the specified OneSight installation directory. 


Uninstalling Agent Proxy 

Note: This step is important if you have configured the UNIX 

Remote Agent to initialize and terminate with the server (for 

example, using the /etc/init.d and /etc/rc* directories). 

6. Reinstall the UNIX Remote Agent, if appropriate. 

Uninstalling Agent Proxy 

1. From a command window, type the following: 

C:\Empirix\OneSight\Proxy> service -remove -param 

proxy.properties 

2. Delete the service.exe, proxy.exe and proxy.properties files from 

the C:\Empirix\OneSight\bin directory. 

Starting the OneSight Service 

To start the OneSight Service: 

1. On the OneSight Server, click Start, then Settings, then click 

Control Panel. 

2. In the Control Panel, double-click Services. (In Windows 2000, 

you must first double-click Administrative Tools and then 

double-click Services.) 

3. In the Services dialog box, highlight Empirix OneSight and 

click Start. 

4. If the Startup value is not ―Automatic,‖ click Startup and select 

Automatic. 

5. Click Close to close the Services dialog box. 

If you are restarting Empirix OneSight, the monitors on the 

OneSight Console’s Status page may be gray until a successful 

sample has occurred. 


Stopping the OneSight Service 

Stopping the OneSight Service 

To stop the OneSight Service: 

1. If you are logged in to the OneSight Console, log out. 

2. On the OneSight Server, click Start, Settings, then Control 

Panel. 

3. In the Control Panel, double-click Services. (In Windows 2000, 

you must first double-click Administrative Tools and then 

double-click Services.) 

4. In the Services dialog box, highlight Empirix OneSight and 

click Close. 

5. Click Close to close the Services dialog box. 

Viewing Version and Database Information 

To view information about your version of Empirix OneSight and 

the OneSight database: 

1. Click the Configure tab. 



2. Select Version & Licensing. 

This dialog box has the following options: 

Product Version – Displays the version of Empirix OneSight 

that you are using. 

Build Number – Displays the build number for the version of 

Empirix OneSight that you are using. 

Database Name – Displays the name of the OneSight database 

that you are using. 

Database Version – Displays the version number of OneSight 

database that you are using. 

Maintenance Expires – Displays the expiration date of the 

installed license. 

Update License – Opens a dialog box for entering a 

new/updated OneSight license. 



Console – Displays the type of Console license that determines 

the OneSight features that are available. 

Basic – Includes all OneSight features except the following: 

Custom Status Views, Attribute Matrix Views, banner menu 

inclusion of these features, and configuration of these 

features. 

Premium – Includes all OneSight features. 

User Seats – Displays the number of user seats available for the 

Console license. 

Licenses for User Group –Shows the number of licenses 

available and in use by the displayed user group. User Group 

licenses can be allocated to specific User Groups using the 

options on the Licenses tab under Configure User Groups. 

Basic Server Licenses – Displays the number of server licenses 

and the number of licenses currently in use. 

Advanced Server Licenses – Displays the number of advanced 

server licenses and the number of licenses currently in use. 

Premium Profile Licenses – Displays the number of premium 

profile licenses and the number of licenses currently in use. 

Monitor Licenses – Displays the number of monitor licenses and 

the number of licenses currently in use. 

Network Device Licenses – Displays the number of Network 

device licenses and the number of licenses currently in use. 

eTEST Visual Script Licenses – Displays the number of e-TEST 

Visual Script licenses and the number of licenses currently in 

use. 

URL Monitor Licenses – Displays the number of URL monitor 

licenses and the number of licenses currently in use. 



OneSight Voice Engine Transaction Licenses – Displays the 

number of OneSight Voice Engine transaction licenses and the 

number of licenses currently in use. 

OneSight Voice Quality Monitor Licenses – Displays the number 

of OneSight Voice Quality Monitor licenses and the number of 

licenses currently in use. 

OneSight Voice Quality Protocol Licenses – Displays the 

protocols that are licensed. For example, ―sip, skinny,‖ etc. 

OneSight Voice Quality Probe Licenses – Displays the number of 

OneSight Voice Quality Probe licenses and the number of 


Voice Watch Transaction Licenses – Displays the number of 

Empirix Voice Watch transaction licenses and the number of 


OneSight Compound Monitor Licenses – Displays the number of 

OneSight Compound Monitor licenses and the number of 


OneSight Call Statistics Licenses – Displays the number of 

OneSight Call Statistics licenses and the number of licenses 

currently in use. 

Service Level Module Licenses – Displays the number of Service 

Level Module licenses and the number of licenses currently in 

use. 

Location Licenses – Displays the number of locations that 

OneSight is configured for and the number of licenses currently 

in use. 



How OneSight Determines the License Type 

Metrics are categorized into the following three types. 

Basic – basic metrics measure basic operating system 

performance such as CPU, Disk, etc. and cannot be modified. 

Premium – premium metrics are metrics defined by the contact 

center and cannot be modified. 

Advanced – All metrics that are not basic or premium. These 

metrics can be modified. 

OneSight determines the license type for a profile applied to a 

system based on the system’s device type: 

Advanced Server – All profiles can be applied to this system. If you 

are using premium metrics, you must define the system as an 

advanced server. Each profile applied to this system consumes one 

advanced server license. In addition, each premium profile applied 

to this system consumes both an advanced server license and a 

premium profile license. 

Basic Server – Only basic profiles such as Windows, Linux, Solaris, 

UNIX, etc., can be applied to this system. The license consumed is 

per system, not per profile. 

Network Device – Only profiles with Ping or SNMP metrics can be 

applied to this system, otherwise a licensing error will occur. The 

license consumed is per system regardless of the number of profiles 

applied. 


Database Maintenance 


This section explains how to move the OneSight database to a 

remote SQL server after setup, how OneSight backs up the database, 

and how to transfer OneSight configuration data to another 

database. 

Using a Remote Database 

When you first run Setup, you can choose to use a remote SQL 

server. However, if you installed Microsoft SQL Server on the 

OneSight Server and then decide to move the OneSight database to 

a remote SQL server, use the steps below. 

To move the database, you will be using Enterprise Manager and 

Query Analyzer, which are Microsoft SQL Server Client Utilities. 

Note: This procedure assumes that the name of the OneSight 

administrative user is ―OneSightAdmin‖ in the database section of 

the OSServer.properties file. The Onesight administrator’s name is 

identified with the property Database.UserName in the 

OSServer.properties file. If you changed this name, you must edit the 

script file OneSightEmpirix\db\sp_CreateUsers.sql and replace all 

occurrences of OneSightAdmin with the name of the OneSight 

administrative user as it appears in the OSServer.properties file. You 

must then execute this script file in a Query Analyzer window to 

modify the stored procedure before executing the procedure in step 

5 below. 

1. Confirm that the remote SQL Server database you intend to use 

has the same character set and sort order. The OneSight 

database is configured as US English, dictionary sort-order, 

case-insensitive. 

2. Stop the Onesight service. 



3. Use Enterprise Manager to back up the OneSight database (by 

default, named OneSight). Move the database backup device 

file, (OneSight_backup.bak, typically located in the mssql7\backup 

folder) to the remote SQL server. If you do not see a backup file 

with this name, use Enterprise Manager to check the path for 

the OneSight_backup device. 

4. Restore the database on the new server from the backup file. 

Note: Make sure you restore the same version of backup that 

you created on the other server. SQL Server supports multiple 

backups in the same device file. 

5. Use Query Analyzer to execute the stored procedure that 

creates the users and logins for the remote SQL server. 

Assuming the default name of OneSight, select the OneSight 

database and execute the following command: 

exec SP_createusers 'OneSight' 

6. Use Enterprise Manager to change the password of the 

OneSightAdmin login on the remote SQL server to agree with 

the password in the database section of the OSServer.properties 

file on the OneSight server. (This is necessary only if you have 

changed the OneSight default password, null, to something 

else.) 

7. Change the SQL Alias machine specification. Open Enterprise 

Manager, then run the Client Network Utility. 

Version 2.0 

The Server alias is the machine name, and the same machine 

name is also specified in the Connection Parameters column. 

Change both of these machine name designations to the 

machine name of the new HWM database machine and edit the 

TCP port number if applicable. 

Version 2.1 and above 

The Server alias named HWMDatabase has the machine name in 



the Connection Parameters column. Change this machine name 

to the machine name for the new HWM database machine and 

edit the TCP port number if applicable. 

Note: By default, the server alias name is HWMDatabase. The 

alias name is based on the specification in the 

Database.ServerAlias value in the database section of the 

\properties\OSServer.properties file for SQL. The Server alias 

string does not need to be changed when moving the database. 

8. Use Query Analyzer to confirm that you can connect to the 

OneSight database on the new server using the OneSight 

administrative user and password as specified in the 

OSServer.properties file on the OneSight Server. 

9. Using Notepad, edit the OSServer.properties file on the OneSight 

Server. Change the ServerName, ServerPort, Detail.DataDirectory, 

and Detail.BackupDirectory properties to reflect the location of the 

remote SQL server. 

10. Restart the OneSight service. 

Automatic Database Backup 

OneSight automatically backs up the entire database file every 

Saturday at 10:41 pm. The location of the backup file and the name 

of the database is defined in the 

/empirix/onesight/properties/OSServer.properties file. OneSight creates a 

*.bak file in the backup directory. You may want to integrate regular 

backups of the OneSight database backup into your company’s 

current data backup routine or procedures. 

Some notable entries in this file include: 

Database.Detail.DatabaseName=hwm001 

Database.Detail.DataDirectory=C:\\Program 

Files\\Microsoft SQL Server\\MSSQL\\Data\\ 



Database.Detail.LogDirectory=C:\\Program 

Files\\Mircrosoft SQL Server\\MSSQL\\Data\\ 

Database.Detail.BackupDirectory=C:\\Program 

Files\\Microsoft SQL Server\\MSSQL\\Backup\\ 

Database.Detail.BackupDeviceName=hwm001_backup 

Select Database from the Configuration tab to access the userdefinable 

parameters for data retention. 

Manual Database Backup 

If you are backing up the OneSight database manually (using the 

SQL Enterprise Manager, for example), stop the OneSight service 

during backup. 

Transferring Configuration Data to Another Database 

This section explains how to transfer OneSight configuration data 

from one database to another. It assumes that you are running SQL 

Server 7 or SQL Server 2000 and that the Data Transformation 

Service (DTS) is available. 

The transfer can be done on a live database if you are not making 

configuration changes during this process. This process should NOT 

be done on a new database on the same machine on which OneSight 

is running because it may adversely affect OneSight performance 

and the data transformation process. 

Caution: This process is valid only for OneSight version 5.1 and 

newer. It assumes that a target database ALREADY exits and that 

the database contains all of the necessary OneSight tables. The 

easiest way to do this is to create a new clean and empty database 

using the initdb.exe utility found in the \Empirix\OneSight\setup 

directory. 

The data transfer outlined here is used to COPY the configuration 

specific tables from the source database and OVERWRITE the tables 



in the newly created target database, while preserving all other 

tables needed for operating OneSight. 

The overall process for copying configuration data requires the 

following two steps: 

1. Create a new/clean database on the target machine using 

initdb.exe. 

2. Copy the configuration files as described below. 

The configuration data will be transferred using the DTS wizard. 

1. Start the DTS wizard by right-clicking on the source database 

(the current OneSight database) and choosing All Tasks 

Export Data. 

2. Select the data source, server name, authentication and database 

name and click Next. 

3. Select the target destination data source, server name, 

authentication and database name for the target OneSight 

database (the database that will be updated with the new 

configuration). Click Next. 

4. Select Copy objects and data between SQL Server databases or 

Transfer objects and data between SQL Server databases. Click 

Next. 

5. Uncheck Copy All Objects and keep the rest of the default 

settings. 

6. Click Select Objects. 

7. Deselect all check boxes except Show All Tables. 

8. Select the following tables only. Selecting other tables will 

transfer data other than configuration information. 



68 OneSight Administrator Guide 

Tbl_AgentDef 

Tbl_AgentFile 

Tbl_AgentProperty 

Tbl_AgentPropertyList 

Tbl_AgentSuptFile 

Tbl_AlertDependencyMonitor 

Tbl_AlertDependencyMonitorList 

Tbl_AlertDependencyNode 

Tbl_AlertRespPlanMap 

Tbl_AppliedMonitor 

Tbl_Atom 

Tbl_AttributeSets 

Tbl_AttributeValues 

Tbl_ChainStep 

Tbl_DBUser 

Tbl_EntityAgent 

Tbl_EntityAttributes 

Tbl_EntityType 

Tbl_EscalationChain 

Tbl_ETestScripts 

Tbl_GlobalSetting 

Tbl_ID 

Tbl_MetricAlertInstanceList 

Tbl_MetricAlertList 

Tbl_MetricAlertType 

Tbl_MetricConfig 

Tbl_MetricConfigInstance 

Tbl_MetricItem 

Tbl_MonitorAttributes 

Tbl_MonitoredEntity 

Tbl_PlanChain 

Tbl_PlanSchedule 

Tbl_Profile 

Tbl_ProfileAttributes 

Tbl_ResponseAction 

Tbl_ResponsePlan 

Tbl_ResponsePlanTemplate 

Tbl_ResponseProperty 

Tbl_SavedReport 

Tbl_ServiceLevelObjective 

Tbl_SLA 

Tbl_TimeInterval 

Tbl_TimeIntervalPeriod 

Tbl_UserExcAttributes

Updating Data Collectors and Remote Agents 

Tbl_ItemAgent 

Tbl_ItemInstCookie 

Tbl_Location 

Tbl_LocationDef 

Tbl_LocationList 

Tbl_MetricAlert 

Tbl_MetricAlertInstance 

Tbl_UserGroup 

Tbl_UserIncAttributes 

Tbl_UserViewAttributeSets 

Tbl_WebApp 

Tbl_WebAppAttributes 

Tbl_WebMonitorMap 

Tbl_WebUserMap 

9. Click OK. 

10. Click Append Data. 

11. Deselect Use default options and click the Options button. 

12. Deselect Copy database users and database roles and click OK. 

13. Click Next. 

14. Select Run immediately and click Next. 

15. Click Finish. The selected tables will be transferred from one 

database to the other. 

16. It is recommended that you make a full database backup of the 

secondary machine. 


You can update Data Collectors and Remote Agents on remote 

machines from the server machine. When you choose to update an 

agent, the new files are downloaded to the remote machine along 

with a script that does the actual update. 



The agent does not need to be removed prior to upgrading nor does 

the machine need to be rebooted after upgrading. The agent is 

stopped, its status is off-line, the update script updates the agent 

with the new files, then restarts the agent. 

Note: The update process may take several minutes. During the time 

that the agent is stopped, no sampling occurs. 

Agents must be running for the remote update to work. The 

following agent types can be updated remotely: 

Remote Agents – Agent Host Processes (AHP) only, and native 

C/C++ agents. 

Data Collectors – AHP and Java Host Process (JHP) together. 

Remote agent update is not supported for agents with a version 

prior to 4.7.465. The OneSight server version is displayed above the 

table on the Agent Update screen. In addition, the Data Collector or 

Remote Agent must have been installed with the auto-update option 

turned on. 

For UNIX, a signed gzipped tar file is sent from the server to the 

agent: 

Solaris - sunos_agent_update.tar.gz.sgn 

Linux - linux_agent_update.tar.gz.sgn 

If these files are not in the correct directory, the server may show 

that it cannot update the Remote Agent. 

If you are updating a VQ Probe, and the status on the Agent Update 

page is, ― No update package available for this version of VQ 

Probe,‖ you will need to run the 

OneSightVQProbePackagesUpdater.exe file on the system where the 

VQ Probe is installed. This file can be downloaded from eSupport. 

Note that this program restarts the Hammer services. 



To update Data Collectors or Remote Agents: 

1. Log in as the OneSight administrator. 

2. Select Agent Update from the Support menu or go to 

agent_update.jsp from the browser window. 

This page has the following options: 

Select – If an agent is not up to date with the OneSight Server 

version a check box is displayed for selecting the agent. 

IP Address – The IP Address of the remote machine. 

Hostname – The host name of the remote machine. 

Operating System – The operating system of the remote 

machine. 

Agent Type – The type of agent, Data Collector or Remote 

Agent collector. 

Instance – The instance number of the agent on the remote 

machine. 

Location – The location name of the Data Collector. 

Agent Version – The version of the agent. Up to date agents are 

displayed in green. Out of date agents are displayed in red. 



Package – Displays ―VQ‖ when the agent is a Voice Quality 

(VQ) Probe. 

Package Version – Displays the VQ Probe version. 

Status – Indicates the status of the agent and of the update 

process. 

Update Available – The agent can be updated and is available. 

Not able to update – The agent can not be updated remotely. 

Physically update the agent using the installation program. 

Up-to-date – The agent is running the same version as the 

Server. 

Not up-to-date – The agent is running a version that is older 

than the OneSight Server. 

No update package available for this version of VQ Probe – 

The data collector is up-to-date and the current version of the 

VQ Probe is too old. Download and run the 

OneSightVQProbePackagesUpdater.exe file from eSupport to 

update the VQ Probe. Note that this program restarts the 

Hammer services. 

Not supported – Remote update is not supported for this older 

versions of agents prior to 4.7.465. 

Downloading – Updated files are being downloaded to the 

remote machine. 

Off-line and/or Installing – The remote agent is not running, or 

the update files are being installed on the remote machine 

and will connect when the installation is complete. The agent 

must initially be running to be updated. 

Update failed – The update failed. Contact Empirix or 

physically update the machine. 



No update package found on server – The update files were 

not found in the agent_update directory on the OneSight 

server. 

Unknown – There is a problem identifying Remote Agents. 

Contact Empirix support for help. 

Update disabled at Agent – Occurs if you uncheck the box for 

enabling agent update during the original installation. 

Internal error 1:AFW is null – There is a problem identifying 

Remote Agents. Contact Empirix support for help. 

AHP is Off-line – The JHP side of the collector is running, but 

the AHP side is not. AHP must be running for the update to 

work. 

3. Select the agents that you want to update. 

4. Click Update. A confirmation page is displayed. 

5. Click Update to continue. You can view the status of the update 

process in the Status field of the Agent Update screen. 

You can review the log file from the update script in the Data 

Collector’s or Remote Agent’s bin directory named 

do_update.bat_console.txt on Windows or ahp_console.txt on 

UNIX. 


Configuring the SNMP Agent 

Configuring the SNMP Agent 

OneSight can publish Monitor, Alert, and internal performance data 

via an SNMP Agent. Select SNMP Agent from the Configure menu. 

Use this dialog to enable and configure the SNMP Agent. 

Enable SNMP Agent – The check box controls whether to enable the 

SNMP Agent. 

Enable Monitor Data – The checkbox can be used to specifically 

enable SNMP access to OneSight Monitor performance data. 

Enable Alert Data – The checkbox can be used to specifically enable 

SNMP access to OneSight Alert data. 

Enable OneSight Internal Data – The checkbox can be used to 

specifically enable SNMP access to OneSight’s internal 

performance data. 

Port – Specifies the port number used on this system by the SNMP 

agent. Typically, this is port 161. 

Community – Specifies the SNMP password of the system. 



Getting Started 

To use OneSight, you must configure at least one monitor group 

and supply information about the web components you want to 

monitor and the action plans you want to use to correct problems 

that are discovered. This chapter provides procedures for creating 

the monitor groups, monitors, and alerts you need to get started with 


Note: If you are not logged on as an administrator, you cannot 

perform these operations. 

Empirix OneSight has these basic elements: 

OneSight Server – This dedicated Windows server is where the 

majority of OneSight software, the OneSight Console, database, 

and web server software, is installed. The Console is browserbased 

and can be accessed either from the OneSight Server or 

from a client machine. 

Contact Channel Components – These are the machines, systems, 

devices, or other parts of your customer service site that you want 

Empirix OneSight to monitor. Empirix OneSight can discover 

these components through an automatic process or you can 

specify these components yourself. 

OneSight needs information about the web components that you 

want to monitor and the action plans that you want to use to correct 

problems that are discovered. To start using OneSight, you must 

add at least one monitor group, supplying information needed to 

monitor and manage that monitor group. 

75

Deciding Which Monitors to Use 

The following picture introduces the fundamental components of a 

OneSight monitor group and shows how they relate to one another. 

When you configure OneSight to monitor your web site, you will 

add these kinds of OneSight components: 

The purpose and relationship of OneSight components is described 

below: 

Monitor Group – A collection of monitors used to measure and 

manage the availability and performance of your web site. Use 

monitor groups to group together monitors in any way that is logical 

to you. 

Monitor – Monitors are added to monitor groups. A monitor checks 

the behavior of a specific web component using a defined set of 

performance standards. OneSight includes monitors for components 



such as URLs that are critical to the web site, monitors for Internet 

servers such as FTP, DNS, or Mail, and monitors for databases, web 

servers and operating systems. 

Alert – One or more alerts are configured for each monitor. An alert 

does three things: 

Defines a problem condition, such as an exceeded threshold or a 

sample failure, that the monitor should detect. 

Specifies what OneSight should do if the problem occurs. When 

the monitor detects this problem condition, the alert can either 

trigger an action plan, change a monitor’s health status, or do 

both. 

Ranks the seriousness of the problem as Critical, Warning, or 

Informational. 

Action Plan – Specifies a sequence of actions that you want 

OneSight to perform if a monitor detects a problem. An action plan 

is invoked by an alert. The alert triggers the action plan to respond 

to problem conditions. Once an action plan is defined, it can be 

assigned to many alerts. 

Action – A specific response that you want OneSight to make. For 

example, sending an e-mail or a SNMP trap notification are possible 

actions. Actions are added to action plans. When an alert triggers an 

action plan, the actions in the plan are performed sequentially. Once 

an action is defined, it can be added to many action plans. 


To monitor the status of servers, URLs, and URL transactions 

associated with your web site, use the monitors listed below. 

Chapter 3: Getting Started 77


If you want to know… 

Is my web site’s URL functioning? 

Is the sequence of URL used in a 

customer transaction working smoothly? 

Is my DNS server resolving domain 

names? 

Is my FTP server transferring requested 

files? 

Is my Mail server up and functioning 

properly? 

Is a machine associated with my web site 

up and running? 

Is the application running on a specific 

port available? 

Are the services on my Windows server 

available? 

I usually check one Perfmon metric to 

figure out what’s going on with a 

particular Windows machine. Can I 

monitor that metric with OneSight? 

Can I check on the results of a query I 

usually run to check on my database? 

Can I check on a specific SNMP metric 

on a single machine? 

Do this... 

Create a URL monitor. 

Create an Oracle Test 

for Web Applications 

Transaction monitor. 

Create a DNS monitor. 

Create an FTP monitor. 

Create a Mail monitor. 

Create a Ping monitor. 

Create a Port monitor. 

Create a Service 

monitor. 

Create a Perfmon 

monitor. 

Create a Database 

monitor. 

Create an SNMP 

monitor. 


Tips On Using OneSight 

Can I check for specific SNMP Trap 

messages? 

How can I monitor multiple system 

components such as operating systems, 

databases, and web servers? 

Create an SNMP Trap 

monitor. 

Create a profile 

monitor. 


Use the guidelines below to implement your monitor groups and use 

OneSight to monitor them: 

Shutting Down and Restarting OneSight 

You can open the OneSight Console and close it at any time, and 

you can log in from remote machines. This does not affect the 

OneSight service that is running continuously. You can start and 

stop OneSight from the Services dialog box in the Windows 

Control Panel. In most cases, this is not necessary. Remember that 

OneSight is gathering time-based data on your monitor group’s 

machines; therefore, stopping OneSight affects that data. 

Opening the OneSight Console From a Remote Machine 

To connect to OneSight from a remote machine, use the following 

URL in your browser: 

http://:8080 



Modifying OneSight Profiles 

If you have already applied a system profile to multiple machines, 

modifying that profile changes the monitoring criteria for all 

machines associated with that profile. At the beginning, it is better 

to apply a profile to a small set of machines and make sure it is 

reflecting status appropriately. After making any necessary 

modifications, you can then apply the updated profile to additional 

machines. 

OneSight profiles for closely related machines share metrics. For 

example, modifying the metric for an NT profile also modifies that 

metric if it is included in the Windows 2000 profile. 

Finding System Information 

You can have OneSight find the data sources and web components 

on the systems in your monitor group, or you can add the 

information yourself. Are you already well informed about the 

makeup of your web site? If so, you can quickly add system 

information yourself. 

Empirix OneSight includes Data Collectors and Remote Agents for 

Windows 2000/2003 and Remote Agents for UNIX (Solaris). A 

profile monitor for a UNIX operating system or an Apache Web 

Server on Solaris requires a UNIX Remote Agent. In addition to 

providing configuration information, be sure to install the UNIX 

Remote Agent in these cases. Data Collectors and Remote Agents 

can also be used to discover system information without providing 

detailed authentication information. 

Interpreting Status and Report Information 

The time of day information in all Empirix OneSight status pages, 

alerts, action plans, and reports are based on the time zone of the 

Empirix OneSight server. If you are connecting to the server from a 


Tuning OneSight 

Database Backup 


browser in a different time zone, no adjustment is made for the 

local time zone. 

The OneSight database stores all user configuration and historical 

sample measurement data. OneSight automatically backs up the 

entire database file every Saturday at 10:41 pm. See Database 

Maintenance in Chapter 2 for more information. 

After you have created a monitor group and set up a few monitors, 

look at the status information displayed on the OneSight Console. 

If you see Warning or Critical, consider which of the following may 

be true: 

There is a problem with the machine you are monitoring. That 

means OneSight is doing exactly what you want it to do. 

There is a problem with the default definition of how this 

monitor should operate. For example, the default definition of a 

problem with a full disk may be set too high for the typical 

amount of disk space you have on these machines. In this case, 

you need to tune OneSight. 

The way you perform this tuning depends on the kind of monitor 

involved: 



Modifying a Profile 

For a dedicated monitor (for example, a Ping monitor), you can 

change the setting for the monitor. Select the monitor in the 

Monitor Group Editor and click Modify. Click the Alerts tab and 

change the settings for the particular alert that is not being 

reported as you wish. Dedicated monitors include a default 

sample failure alert. In most dedicated monitors, you can add 

additional alerts. 

If you are setting up a dedicated monitor, you can use the Test 

button to confirm that your settings will locate and perform the 

initial operation for that monitor. Always use the Test button if 

you are not seeing the results you expect after you add or 

reconfigure a monitor. 

For a profile monitor (for example, a Windows operating system 

monitor), you can specify whether a profile metric should 

monitor a particular system component in the Monitor Editor. 

This is probably the quickest way to address the change for a 

single monitor. However, if you want to make the change for 

multiple machines, use the procedure below. 

Profiles include a default set of metrics for commonly monitored 

monitor groups. OneSight includes a series of default profiles, but 

you can also modify a profile yourself. 

For example, if you want to change the warning about full disk 

space, you can: 

Change the threshold (for example, from 70 percent to 90 

percent) 

Change the kind of notification associated with the threshold 

(warn once, then change back to Good) 

Remember that if you have already applied a system profile to 

multiple machines, modifying that profile changes the monitoring 



criteria for all machines associated with that profile. At the 

beginning, it is better to apply a profile to a small set of machines 

and make sure it is reflecting status appropriately. After making any 

necessary modifications, you can then apply the updated profile to 

additional machines. 

OneSight profiles for closely related machines share metrics. 

Modifying the metric for an NT profile, for example, also modifies 

that metric if it is included in the Windows 2000 profile. Refer to 

Chapter 6 for more information. 






Configuring Monitor Groups 

An Empirix monitor group groups together the various components 

of your web site, such as machines, databases, and web processes, 

and monitors them as an integrated whole. 

The OneSight Console shows the status of your monitor groups. To 

configure a monitor group, you will set up a series of monitors, 

some of which you create by matching a profile (included with 

OneSight) to the web component you want to monitor. For 

OneSight, a web component may be an application (such as Oracle), 

a URL or series of URLs that are critical to your web site, an 

Internet server (such as FTP, DNS, or Mail), or the operating 

systems of the machines that service your web site. 

Part of setting up profile monitors is identifying which machines 

and system components OneSight can monitor. Systems, and 

information about the components on each system, must be 

identified so that OneSight profiles can be used to create monitors 

for the web components running on those machines. OneSight can 

find the systems and system components for you or you can 

manually add information about the systems and system 

components that you want OneSight to monitor. 

The Add Monitor dialog box is where you apply dedicated monitors 

and profiles to web components to create monitors. The Profile 

Manager is where you control which profiles are available to be 

applied. 

Monitor group monitors generate alerts based on events. An event is 

web component performance, such as an exceeded threshold or a 

sample failure, that you want to know about. All monitors generate 

85

Adding a Monitor Group 

at least one type of alert. For many monitors, you can add more 

performance criteria that generate additional kinds of alerts. 

In response to an alert, OneSight can trigger an action plan; change 

a monitor’s health; do both, in some cases; or do nothing. The Alert 

Editor is where you define an alert for a monitor and define the 

response for an alert. The Configure Action Plans page is where 

you manage the action plans used by applied monitors. 


In Empirix OneSight, monitors are always used as part of a monitor 

group. So to use OneSight, you must begin by creating at least one 

monitor group. You can then create monitors either from within a 

monitor group or in the OneSight Monitors configuration. You use 

monitor groups to group together monitors in any way that seems 

logical to you. 

Monitors you create from within a monitor group are automatically 

part of that monitor group and can be added to any other monitor 

group using the Monitors configuration. Monitors you create from 

the Monitors configuration can be added to any existing monitor 

group(s). Refer to Chapter 5 for information on adding monitors. 

Following are the broad steps for adding a monitor group and 

monitors: 

1. Enter the name and a description of the monitor group as 

described below. 

2. Add monitors as described below and in Chapter 5. 

3. Verify that the monitors are performing as expected as 

described in Chapter 5. 

4. For each monitor, specify responses for alerts (optional) as 

described later in this chapter. 



5. Define action plans that are used to respond to alerts (optional) 

as described later in this chapter. 

To create a new monitor group: 

1. Click the Configure menu. 

2. Click Monitor Groups to open the Configure Monitor Groups 

page. 

The Configure Monitor Groups page lists the monitor groups 

that OneSight is currently set up to monitor. You can add, 

modify, enable, disable, or remove monitor groups to configure 

how OneSight will monitor the applications. 

Use these options to identify and manage OneSight monitor 

groups. The Monitor Group list includes all monitor groups that 

are configured for Empirix OneSight. 

Enable – The check box adjacent to each monitor group 

controls whether or not the monitor group is currently in effect. 

When selected, the monitor group is enabled. When cleared, the 

monitor group is disabled. Disabled monitor groups will not 

Chapter 4: Configuring Monitor Groups 87


participate in health monitoring, alerts, or execution of action 

plans. 

Name – The Name column identifies the monitor group. This 

name will appear in all OneSight reports and display pages that 

show the status of this monitor group. 

User Group – Displays the user group to which this monitor 

group belongs. 

Description – Provides information to help you differentiate this 

monitor group from the others that you are monitoring. 

3. Click Add. The Monitor Group Editor opens. 

Use these options to identify the monitor group: 

Name – Type the name you want to use to identify this monitor 

group. This name will appear in all OneSight reports and 

display pages that show the status of this monitor group. 



Description – Type in information that allows you to 

differentiate this monitor group from all other monitor groups 

that you are monitoring with OneSight. 

The Monitor Group Editor has the following tabs for 

configuring the monitor group: 

Monitors – Shows all of the monitors that are in effect for the 

current monitor group. Use options on the Monitors tab to add, 

modify, or remove monitors for your monitor group. You can 

also enable or disable individual monitors. 

Status Chart – Use options on this tab to specify which monitor 

should display on the OneSight Status page as charted data for 

this monitor group. 

Health – Use options on this tab to set up an action plan that is 

triggered when the monitor group goes into a Warning state, an 

action plan that is triggered when the monitor group goes into a 

Critical state, and an action plan that is triggered when the 

monitor group returns to a Good state. 

For web farm management, settings are available that allow you 

to group a single profile monitor type and specify how many 

monitors of this type contribute to the health state of the 

monitor group. 

Alert Dependencies – Use options on this tab to specify which 

other monitor(s) this monitor depends upon for alerts for this 

monitor group. Dependent monitors still display alerts within 

OneSight. However, action plans for dependent monitors are 

suppressed. 

Attributes – Contains the options for specifying which attributes 

are applied to this monitor group for Status page sorting. 

Smartlink – Contains the options for specifying a link to 

associate with the monitor group. 


Modifying a Monitor Group 

Down Time – Contains the options for applying downtime 

schedules to this monitor group. 

4. Type the monitor group’s Name and Description. 

This information appears in the Name and Description columns 

on the Configure Monitor Groups page. This name and 

description are also used throughout OneSight to identify the 


5. Add one or more monitors to the monitor group. Refer to 

Chapter 5. 

6. Click OK. 


If you know which monitor group you want to configure, click 

Modify on the right side of the monitor group name on the OneSight 

Status page. 

To select a monitor group from a list: 




2. Click Monitor Groups to open the Monitor Groups page. 

The Configure Monitor Groups page lists the monitor groups 

that OneSight is currently set up to monitor. You can add, 

modify, enable, disable, or remove monitor groups to configure 

how OneSight will monitor the applications. 

Use these options to identify and manage OneSight monitor 

groups. The Monitor Group list includes all monitor groups that 

are configured for Empirix OneSight. 

Check Box – The check box adjacent to each monitor group 





plans. 

Name – The Name column identifies the monitor group. This 

name will appear in all OneSight reports and display pages that 

show the status of this monitor group. 

Description – Provides information to help you differentiate this 

monitor group from the others that you are monitoring. 



3. Click the monitor group you want to work with, then click 

Modify to open the Monitor Group Editor. 

The Monitors tab lists all of the monitors that are in effect for 

the current monitor group and has the following options to 

identify and manage the monitors that are configured for the 

current monitor group: 

Add New – Displays the Add Monitor dialog box for adding a 

new monitor. 

Add Existing – Displays the Select Existing Monitor dialog box 

for adding an already created monitor to the monitor group. 

Clone – Creates a copy of the selected monitor that can then be 

modified. 

Modify – Displays the configuration dialog box for the selected 

monitor. 

Remove – Removes the selected monitor from the monitor 

group. 



Check All – Selects all monitors. 

Uncheck All – Deselects all monitors. 

Check Box – The check box adjacent to each monitor controls 

whether or not the monitor is currently in effect. When selected, 

the monitor is enabled. When cleared, the monitor is disabled. 

Disabled monitors will not contribute to the measurement of the 

monitor group’s health. 

Monitors Settings – Lists by name the types of monitors that are 

configured for the current monitor group. 

Name – The Name column usually identifies the monitor type 

and the machine, server, or host that is being monitored. You 

can specify a name when you add the monitor to the monitor 

group. 

The Monitor Group Editor has the following tabs for 

configuring the monitor group: 

Monitors – Shows all of the monitors that are in effect for the 

current monitor group. Use options on the Monitors tab to 

add, modify, or remove monitors for your monitor group. 

You can also enable or disable individual monitors. 

Status Chart – Use options on this tab to specify which 

monitor should display on the OneSight Status page as 

charted data for this monitor group. 

Health – Use options on this tab to set up an action plan that 

is triggered when the monitor group goes into a Warning 

state, an action plan that is triggered when the monitor group 

goes into a Critical state, and an action plan that is triggered 

when the monitor group returns to a Good state. 

For web farm management, settings are available that allow 

you to group a single profile monitor type and specify how 



many monitors of this type contribute to the health state of 

the monitor group. 

Alert Dependencies – Use options on this tab to specify which 

other monitor(s) this monitor depends upon for alerts for this 

monitor group. Dependent monitors still display alerts within 

OneSight. However, action plans for dependent monitors are 

suppressed. 

Attributes – Contains the options for specifying which 

attributes are applied to this monitor group for Status page 

sorting. 

Smartlink – Contains the options for specifying a link to 

associate with the monitor group. 

Down Time – Contains the options for applying downtime 

schedules to this monitor group. 



4. Monitors configured as part of another monitor group or using 

the Monitors configuration can be added to any other monitor 

group. To add an existing monitor to the monitor group, click 

Add Existing. Refer to Chapter 5 for instruction on creating a 

new monitor. 


Name – The Name column identifies the monitor. This name 

will appear in all OneSight reports and display pages that show 

the status of this monitor. 


Specifying the Status Chart Data Source 


The OneSight Status page shows the current health of each monitor 

group. Included in the display for each monitor group is a status 

chart. Use options on the Status Chart tab to configure which 

applied monitor supplies data for the chart display on the OneSight 

Status page. 

To specify the Status Chart data source: 

1. Open the Status Chart tab in the Monitor Group Editor using 

one of the following methods: 

On the Status page, click the monitor group to see status 

details. Click the report frame with the text Click to Configure 

Status Chart 

Click the Modify button associated with the monitor group, 

and then click the Status Chart tab. 


Derive Status Chart Data From Monitor – Select any monitor on 

the list to specify that it should supply data for the monitor 

group status chart. 



If you select a profile monitor, you can specify which metric 

within that profile should be used to supply data for the monitor 


Note: If the monitor name contains the following special 

characters, they will not be displayed in the name in the drop 

down list: “”, and “&”. 

Derive Status Chart Data From Metric – The list shows all of the 

metrics available for the selected monitor. Select the metric you 

want to use for the status chart. 

If you selected a dedicated monitor in the Derive Status Chart 

Data From Monitor list, the Derive Status Chart Data From Metric 

setting is unavailable. For dedicated monitors, only a single 

metric source is available to supply data for the status chart. 

2. Select a monitor in the Derive Status Chart Data From Monitor 

list. 

The Monitors list shows all of the monitors that are currently 

set up for this monitor group. Information collected by the 

monitor that is selected will be displayed on the OneSight 

Status page as charted data. 

If you select a profile monitor, use the Derive Status Chart Data 

From Metric setting to specify which metric within that system 

monitor profile should be used to supply data for the monitor 


If you select a dedicated monitor, the Derive Status Chart Data 

From Metric setting is unavailable. For dedicated monitors, only 

a single metric source is available to supply data for the status 

chart. 

3. If you chose to derive data from a profile monitor, select one of 

the profile’s metrics in the Derive Status Chart Data From 

Metric list. 


Specifying Action Plans 

The list shows all of the metrics available for the selected 

monitor. Select the metric you want to use for the status chart. 

Information collected by the metric that is selected is displayed 

on the OneSight Status page and the OneSight Status Details 

page as charted data. 

Specifying Action Plans 

The Health Tab of the Monitor Group Editor is where you specify 

the action plan that is triggered when the monitor group goes into a 

Warning state, Critical state, or returns to a Good state. Additional 

settings are provided to assist with web farm management. Refer to 

Chapter 8 for instructions on creating action plans. 

Use these options to mange monitor group health: 

When the Monitor Group Is in Warning State Respond by – Specify 

how you want to respond when the monitor group enters a Warning 

state by selecting an action plan from the list. Options displayed in 

this list represent previously configured plans. To create a new plan 

for this condition, select from the list. 

When the Monitor Group Is in Critical State Respond by – Specify 

how you want to respond when the monitor group enters a Critical 

state by selecting an action plan from the list. Options displayed in 

this list represent previously configured plans. To create a new plan 


When the Monitor Group Returns to Good State Respond by – 

Specify how you want to respond when the monitor group returns to 

a Good state by selecting an action plan from the list. Options 

displayed in this list represent previously configured plans. To 

create a new plan for this condition, select from 

the list. 


Specifying Alert Dependencies 


The OneSight Alert Dependencies page shows associations between 

systems and devices being monitored in the monitor group. Use the 

options on the Alert Dependencies tab to configure which monitors 

are dependent upon other monitors for action plan alerting 

purposes. 

To open the Alert Dependencies tab in the Monitor Group Editor: 

1. Click the Modify button associated with the monitor group on 

the Status Page. 

2. Click the Alert Dependencies tab. 

The Alert dependencies tree automatically lists all monitors and 

profiles configured for the monitor group in the Monitors page. 

This tab is used to specify which other monitor(s) this monitor 

depends upon for alerts for this monitor group. The Alert 



Dependencies tree provides for the following alerting 

contingencies: 

Allow a single monitor to belong to multiple monitor groups. 

Allow a monitor to be dependent on another. 

Restrict the action plans of dependent monitors based on the 

health of the parent. 

Allow restriction of action plans based on the number of 

monitors with health problems. 

The OneSight Alert Dependencies page lets you configure the 

associations between systems and devices being monitored in 

the monitor group. Use the options on the Alert Dependencies 

tab to configure which monitors are dependent upon other 

monitors for action plan alerting purposes. 

An alert dependency relationship determines which monitor 

Action Plan is triggered for Warning or Critical state alert 

notifications. The Alert Dependency tree can include nested 

monitors. The following list describes parent and dependent 

monitor action plan priority: 

Alerts in reports are not affected. 

Action plans for a monitor or Alert Dependency node are 

prevented from being published if a parent has worse health. 

A Warning action plan would not be triggered if a parent 

node has a Warning or Critical alert. 

A Critical action plan will be triggered if a parent node has a 

Warning alert. 

Dependent monitors still display alerts within the OneSight 

status. The following list describes how the health state color is 

determined for monitors and Alert Dependency nodes: 



Monitor’s color is always the health of the individual 

monitor. 

Color reflects the worst color of dependents and internal 

monitors. 

Dependents health in turn is determined by the health of it’s 

dependent nodes and internal monitors. 

You add nodes and arrange the associations between existing 

monitors and profiles using the arrow buttons on the Alert 

Dependencies page. Select a dependency tree node or monitor 

and then use the arrow buttons to move the node or monitor in 

the tree hierarchy. 

When you add a node to the Alert Dependency tree, you specify 

a name and the number of monitors that must be in a Warning 

or Critical state before that node is in an alert state. The 

following conditions apply to Alert Dependency nodes: 

Number in Warning or Critical state refers ONLY to 

monitors. 

Alert Dependency node holds state for monitors under node. 

Dependency is between nodes. 

The Alert dependency tree has the following icons: 

Closed node – Click the icon or double-click the name to 

expand the node and view child nodes and monitors. 

Open node – Click the icon or double-click the name to collapse 

the node and hide child nodes and monitors. 

Dependency tree node – Use Add Node, Modify, and Remove to 

define nodes and the dependency node responses for the 

monitors below the node. Use the arrow buttons to move 

dependency nodes within the tree hierarchy. 



Monitor node – The Alert dependencies tree automatically lists 

all monitors and profiles configured for the monitor group in 

the Monitors page. Use the arrow buttons to move monitors 

within the tree hierarchy. 

4. Follow the procedures below. 

Defining Action Plan Alerts 

To define action plan alerts for the top level dependency node: 

1. On the Alert Dependencies tab, select the top level monitor 

group name and click Modify. The Dependency Node Editor 

opens. 

The Dependency Node Editor lets you specify the action plan to 

use if the specified number of monitors below the dependency 

tree node go into an alert state. It has the following options: 

Name - Defines a name for the dependency node. 

This dependency node is in good state unless [ # ] monitors are in 

a Critical or Warning state – Specify the number of monitors 

below the dependency node that must be in Warning or Critical 

State before the dependency node triggers the specified action 

plan alert(s). 

2. Specify the Warning State, Critical State, and returning to Good 

State action plan options for the top level node of the 

dependency tree. 



3. Specify the number of monitors below the dependency node 

that must be in Warning or Critical State before the dependency 

node triggers the specified action plan alert(s). 

4. Click OK to close the Dependency Node Editor. 

Adding Dependency Nodes 

To add dependency nodes: 

1. On the Alert Dependencies tab, select the level where you want 

to add the node and click Add Node. The Dependency Node 

Editor opens. 

The Dependency Node Editor lets you specify the action plan to 

use if the specified number of monitors below the dependency 

tree node go into an alert state. It has the following options: 

Name - Defines a name for the dependency node. 

This dependency node is in good state unless [ # ] monitors are in 

a Critical or Warning state – Specify the number of monitors 

below the dependency node that must be in Warning or Critical 

State before the dependency node triggers the specified action 

plan alert(s). 

2. Enter a name for the dependency node. 


Adding a Smartlink to a Monitor Group 

3. Specify the number of monitors below the dependency node 

that must be in Warning or Critical State before the dependency 

node triggers the specified action plan alert(s). 

4. Click OK to close the Dependency Node Editor. 

5. The new dependency node is added at the same level selected in 

step one. 

6. Use the arrow buttons to move dependency nodes and monitors 

to create the tree hierarchy. 


The SmartLink tab lets you specify a URL to associate with the 

monitor group. The URL is available on the Status Details Page. 

URL – Enter the URL that you want to associate with this monitor or 

metric. The URL can include specific substitution variables. 

Rollover Text – Enter the text that you want to display when the 

mouse is rolled over the link on the Status Details page. 

Open in New Browser Window – Select this option to open a new 

browser window when the link is clicked in the Status Details page. 



Substitution Variables – The following substitution variables are 

supported: 

%DateShort% – The locale-specific date that the metric was last 

measured in the format mm/dd/yy. For example, 4/4/01. 

%DateLong% – The locale-specific date that the metric was last 

measured, in long format. For example, Wednesday, April 4, 

2001. 

%TimeShort% – The locale-specific time that the metric was last 

measured, in short format. For example, 1:52 PM. 

%TimeLong% – The locale-specific time that the metric was last 

measured, in long format including the time zone. For example, 

1:52:16 PM PDT. 

%Value% – the numeric value of the metric. For example, 11.701 

seconds. 

%MonitorGroup% – The name of the Monitor Group that contains 

the metric. For example, Business Partner Extranet. If multiple 

Monitor Groups use this metric, the result is a comma delimited 

list. 

%SystemName% – The name of the system that the metric is 

applied against. For example, JBK_P3. For URL monitors, the 

system name is the URL that you are monitoring. For example, 

http://www.empirix.com. This lets you use %SystemName% as 

your SmartLink for a URL monitor. 

%Monitor% – The name of the monitor that the metric is within. 

For example, URL (http://www.empirix.com). 

%Component% – The name of the component that the metric is 

applied against. For example, Disk C:. 


Applying Downtime to a Monitor Group 

%Metric% – The name of the metric. For example, Disk: % Space 

Available. 

%Entity% – The monitored entity ID. 

%Item% – The metric item ID. 

%Location% – The location of the Data Collector that sends out 

the alerts. 

Applying Downtime to a Monitor Group 

The Down Time tab lets you apply downtime to a monitor group. 

Available Downtimes – Lists the downtimes that are available and 

that have not been applied to this monitor group. 

Selected Downtimes – Lists the downtimes that have been applied to 


–Moves the selected downtime into the Selected 

Downtimes list. 


Enabling/Disabling a Monitor Group 

– Moves the selected downtime into the Available 


Downtime Editor – Displays the Downtime Editor for creating and 

applying downtimes. Refer to “Chapter 9” for more information on 

the Downtime Editor. 

Enabling/Disabling a Monitor Group 

To enable or disable a monitor group: 


2. Select Monitor Groups to open the Configure Monitor Groups 

page. 

3. In the Monitor Groups list, the check box that appears next to 

each monitor group’s name determines whether or not that 

monitor group is enabled. 

To disable a monitor group, clear the check box adjacent to 

that monitor group’s name. 


Removing a Monitor Group 

To re-enable a monitor group, select the check box adjacent 

to that monitor group’s name. 

Removing a Monitor Group 

To remove a monitor group: 



page. 

3. In the Monitor Groups list, click the name of the monitor group 

you want to remove. 

4. Click Remove. 

5. A warning dialog box appears, confirming that you want to 

remove the monitor group. Click Yes. 


Adding Monitors to a Monitor Group 


To open the Add Monitor dialog box: 



page. 


you want to work with and click Modify. Or, to create a new 

monitor group, click Add. The Monitor Group Editor opens. 

4. On the Monitors tab, click Add New to open the Add New 

Monitor dialog box or click Add Existing to open the Select 

Existing Monitor dialog box. 



The Add Monitor dialog box lists all the available types of 

dedicated monitors that you can apply to monitor the individual 

metrics or systems for your monitor group. There are also 

profile monitor options. Profile monitors allow you to track and 

manage performance of the back-end systems used for your 

monitor group. When you click a monitor in the Monitor Types 

box, the dialog box displays the options you must use to apply 

that monitor to your monitor group. Refer to Chapter 5 for 

dialog box descriptions. 

Use settings in this dialog box to apply monitors to your 

monitor group. To add a monitor, select the monitor type you 

want to apply and then use the options in the Add Monitor 

dialog box to configure the monitor. 

Monitor Types – The Monitor Types tree lists all of the kinds of 

monitors that can be used for your monitor group. To add a 

monitor to your monitor group, click the monitor type name that 

identifies the kind of process, system component, or activity 

that you want to monitor. 

When you select a dedicated monitor type, the Add Monitor 

dialog box displays the options you must use to apply that 

monitor to your monitor group. When you select a profile 

monitor, the right side of the Add Monitor dialog box lists the 

names of systems that you can use to create a profile monitor. 

Monitor Name – Each monitor that you create must have a 

unique name. In the Monitor Name box, OneSight creates a 

unique name for the current monitor by combining the name of 

the monitor type with the name of the host or system to which 

the monitor applies. To change the default assigned name, type 

a unique monitor name that helps you to identify what this 

monitor does. 

Group Profiles By – Lets you group the available profiles in the 

Monitor Types tree. Use the Profile Manager button or the 



Configure Profiles page to create or modify individual profile 

attributes using the Attributes tab in the Profile Editor. 

The options in the Add Monitor dialog box change 

dynamically, depending on the type of monitor you choose to 

add. For help with the settings for a specific type of monitor, 

select the monitor type you want to apply to your monitor group 

and then click Help in the Add Monitor dialog box. 

To add a dedicated monitor to a monitor group: 

In Empirix OneSight, monitors are always created as part of a 

monitor group. If you have not already created a monitor group, 

create one now. 

Use this procedure to add a dedicated monitor to a monitor group. If 

you want to add a profile monitor, see Configuring a Profile 

Monitor. 

1. In the Monitor Group Editor, on the Monitors tab, click Add to 

open the Add Monitor dialog box. 

2. The Monitor Types box lists all of the types of monitors that 

can be applied to your monitor group. Click the dedicated 

monitor type that identifies the kind of process, system 

component, or activity that you want to monitor. 

This icon identifies the available types of dedicated monitors. 

3. When you select a dedicated monitor type, the Add Monitor 

dialog box displays the options you must use to apply that 

monitor to your monitor group. Use settings on the General tab 

to configure the monitor. 

For example, if you want to monitor whether a host used by 

your monitor group is reachable, select Ping in the Monitor 

Types box and use settings on the General tab to configure a 

Ping monitor for that host. 



4. Each monitor that you add must have a unique name. In the 

Monitor Name box, OneSight creates a unique name for the 

current monitor by combining the name of the monitor type 

with the name of the host or system to which the monitor 

applies. To change the default assigned name, type a unique 

monitor name that helps you to identify what this monitor does. 

5. To verify that the monitor will work as configured, click the 

Test button. The Monitor Test window provides information 

about the success or failure of the test and indicates what may 

be causing any problem. 

6. If the test succeeds, click OK in the Add Monitor dialog box to 

save these basic monitor settings. Then, click OK in the Monitor 

Group Editor to add the monitor to your monitor group. 

Now you are ready to verify that the monitor is performing as 

expected. Refer to the OneSight Operator Guide. 

After you have determined that the monitor performs correctly, you 

can configure additional features: 

Set up an Alert to detect when performance crosses a threshold. 

Set up an Action Plan to notify you if the monitor detects an 

error. 



Configuring Monitors 

The Configure Monitors page lists the monitors that are currently 

configured in OneSight. You can add, modify, enable, disable, or 

remove monitors and configure monitors that you can add to 

monitor groups. Using the Monitors configuration, you can add or 

modify monitors individually without having to know which 

monitor group(s) contain the monitor. 

To open the Configure Monitors page: 


2. Click Monitors to open the Configure Monitors page. 

113

Authentication 

Use these options to identify and manage OneSight monitors. 

The Monitor list can list all monitors that are configured in 

Empirix OneSight or it can be filtered to display only those 

monitors that you are interested in. In addition, the list can be 

sorted by clicking on a column heading. An arrow is displayed 

in the column heading indicating which column is being used to 

sort and the direction of the sort, ascending or descending. 

Show monitors where contains – Select the 

type of filter and enter any specific text, if necessary. For 

example, you can search for all monitors with e-TEST in the 

name. In addition to plain text, you can enter a PERL expression 

in the contains field. 

Show – Filters the monitors and redisplays the list. 

Add – Displays the Add Monitor dialog box for adding a new 

monitor. 

Clone – Creates a copy of the selected monitor that can then be 

modified. 

Modify – Displays the Edit Monitor dialog box for modifying 

the selected monitor. 

Remove – Deletes the selected monitor. 

Check All – Selects all monitors. 

Uncheck All – Deselects all monitors. 

Bulk Modification – Displays the Bulk Modification dialog box 

for adding, changing, and deleting alerts and locations for 

multiple monitors. 

Enable – The check box adjacent to each monitor group 






Monitor Naming 



plans. 

Monitor Symbols 

Monitor is configured but not in use by a monitor group. 

Monitor is in use by one or more monitor groups. 

Name – The Name column identifies the monitor. This name 

will appear in all OneSight reports and display pages that show 

the status of this monitor. 

User Group – Displays the user group to which this monitor 

belongs. 

Type – Shows the type of monitor. 

When you create a monitor, such as Perfmon, and do not leave the 

authentication fields blank, an Authproc folder will be created under 

the Empirix folder. It will contain the OSauth.exe file and the 

OSauth.exe process will be listed in the Task Manager. This file 

provides one central process for authentication. 

Each monitor that you create must have a unique name. In the 

Monitor Name box, OneSight creates a unique name for the current 

monitor by combining the name of the monitor type with the name 

of the host to which the monitor applies. OneSight continues to 

automatically update the monitor name if you change the host 

unless you have changed the default assigned name. Once you have 

changed the default name, OneSight no longer automatically 

updated the name. 

Chapter 5: Configuring Monitors 115

Configuring the VQ Inspector Monitor for the Avaya Communication Manager 

Configuring the VQ Inspector Monitor for the 

Avaya Communication Manager 

The Avaya Communication Manager Profile monitor passively 

monitors call activity on specified extensions to create a metric data 

set for each completed call handled by the Avaya Communication 

Manager. 

For the monitor to work, the Avaya Communication Manager must 

be configured to send RTCP packets and Call Detail Records to the 

OneSight Data Collector. In addition, the extensions to monitor 

must be configured in the Avaya Communication Manager. This 

process is described below. 

Configuring the Avaya Communication Manager 

To configure the Avaya Communication Manager: 

1. Log in to the machine on which your Avaya Communication 

Manager resides by entering https\\ and 

entering your user name and password. 

2. Launch the Native Configuration Manager and log in. 

3. To enable RTCP packet forwarding, enter the command change 

ip-network-region 1 in the Command field. 



4. Set the RTCP Reporting Enabled and Use Default Server 

Parameters fields to Y. 

5. Click ENTER to save your changes. 



6. To configure RTCP options, enter the command change 

system-parameter ip-options. 

7. Enter the IP address of the OneSight Data Collector in the 

Default Server IP Address field and click ENTER. 



8. To enable Call Detail Record observation, enter the change 

node-name-ip command. 

9. Create a new node Name/ IP Address mapping called empirix. 

Enter the IP address of the OneSight Data Collector machine 

and click ENTER. 



10. To create an IP service for call detail recording, enter the 

change ip-service command. 

11. Enter CDR1 in the Service Type field. 

12. Select the previously created empirix in the Remote Node field 

and click ENTER. 



13. To configure Call Detail Record forwarding, enter the change 

system-parameters cdr command. 

14. Set the following fields: 

Primary Output Format – customized 

Primary Output Endpoint – CDR1. This should match the 

previously entered IP service. 

Secondary Output Format – customized 

Secondary Output Endpoint – CDR2. This should match the 

previously entered IP service. 

Intra-switch CDR – y 

Record Outgoing Calls Only - n 



15. Click NEXT PA. 

16. Enter the following data items and their length for customized 

output: 

date – 6 

time – 4 

space – 1 

sec-dur – 5 

space – 1 

dialed-num – 23 

space – 1 

calling-num – 15 

return – 1 

line-feed – 1 

17. Click ENTER. 



18. To specify the extensions to monitor, enter the change intraswitch 

cdr command. 

19. Enter the extensions to monitor and click ENTER. 

20. To check the status of the call detail record link, enter the 

command status cdr. 

Configuring the Monitor in OneSight 

Once the Avaya Communication Manager is configured, you can 

create the monitor in OneSight. 

Note: Because the Data Collector must listen on specific ports for 

incoming RTCP and Call Detail Records, the Avaya Communication 

Manager monitor must use one specific, named location for data 

collection. The location should not be used. 



In addition, only one data collector should be installed on the data 

collector machine. 

In the Add Monitor dialog box, when you click Avaya 

Communication Manager in the Monitor Types box, settings to 

configure a Avaya Communication Manager monitor appear on 

these dialog box tabs: 

General Tab – Contains the options that you can use to create a 

Avaya Communication Manager monitor for your monitor group. 

Locations Tab – Specifies the Data Collector Location from which 

the monitor checks performance. 

SmartLinks Tab – Contains the options for specifying a link to 

associate with a particular monitor or metric. 

Attributes Tab – Contains the options for specifying which attributes 

are applied to this monitor for Status page sorting. 

Monitor Groups Tab – Contains the options that you can use to 

specify which monitor groups the monitor is used with. This tab is 

available when you open the Add Monitor window by selecting 

Monitors from the Configure menu. It is not available when you 

open the Add Monitor window from the Monitor Group Editor. 

Access Control Tab – Contains the options for specifying which user 

groups have read, write, and delete permissions for this monitor. 

Down Time Tab – Contains the options for applying downtime to 

this monitor. 




of the host to which the monitor applies. To change the default 

assigned name, type a unique monitor name that helps you to 

identify what this monitor does. 



To create a VQ Inspector Monitor for the Avaya Communication 

Manager: 

1. On the Monitors Page, click Add to open the Add Monitor 

dialog box. 


can be applied to your monitor group. Click Avaya 

Communication Manager to add a monitor that passively 

monitors Avaya phone call activity. You will use settings on the 

General tab to configure an Avaya Communication Manager 

monitor. 

Avaya CM IP Address – Specifies the IP Address of the Avaya 

Communication Manager. 

Version – Select the SNMP version being used, Snmp_Version1, 

Snmp_Version2c, or Snmp_Version3. 



The following additional fields are displayed for SNMP version 

3: 

Auth Mode – Select the authentication mode. 

NoAuth/NoPriv – No authentication and no privileges. 

Auth/NoPriv – Authentication and no privileges. 

Auth/Priv – Both Authentication and privileges. 

User Name – Enter the user name to use to log in to the SNMP 

version 3 protocol. 

Password – Enter the password to use to log in to the SNMP 


Auth – Select the authentication hashing function to use: MD5 

or SHA. 

Privacy Mode – Select the method to use for encrypting the 

data. 

Privacy Password – If you have selected a privacy mode, 

enter the password. 

Context – Enter the context setting that matches the setting in 

the device that is being monitored. Typically, it is a name that 

describes the device. For example, ―bridge.‖ 

Time Out – The amount of time, in seconds, to wait for data 

from the Avaya Communications Manager before timing out. 

CDR Configuration – The CDR configuration specifies the index 

and length of the fields. This information must match what is 

configured on the CDR System Parameters dialog box in the 

Avaya CM and must take into account spaces. For example, if 

your Avaya CM is configured as follows: 



The index for the date is 1 and its length is 6. The index for 

time must take into consideration the space after the date. The 

index for time would be 8 (1 for the date index, plus 6 for the 

length of the date, plus 1 for the space after the date). The index 

for the duration would be 13 (8 for the time index, plus 4 for the 

length of time, plus 1 for the space after the time.) 

Note: If you change any of these fields, you must restart the 

Data Collector for the changes to take effect. 

Date Start Index and Length – Enter the date start index and 

length. 

Time Start Index and Length – Enter the time start index and 

length. 

Duration Start Index and Length – Enter the duration start 

index and length. 



Called Number Start Index and Length – Enter the called 

number start index and length. 

Calling Number Start Index and Length – Enter the calling 

number start index and length. 

Sample Every: – Specifies how often samples are 

taken for this monitor. Refer to, ―Sample Every Settings,‖ later 

in this chapter for a description of these settings. 

3. Enter the IP Address of the Avaya Communication Manager. 

4. Select the SNMP version being used. 

5. Enter the CDR configuration. You must restart the Data 

Collector for the changes to take effect. 

6. Enter the sampling rate. 

7. Click the Location tab. 

8. Select a specific named location to use for data collecting. 

Note: Because the Data Collector must listen on specific ports 

for incoming RTCP and Call Detail Records, the Avaya 

Communication Manager monitor must use one specific, named 

location for data collection. The location should not 

be used. 

In addition, only one data collector should be installed on the 

data collector machine. 






save these settings. You can now add this monitor to a monitor 


Configuring the Cisco Call Manager Profile Monitor 

group. Refer to “Adding Monitor to a Monitor Group” in 

Chapter 4. 

Configuring the Cisco Call Manager Profile 

Monitor 

The Cisco Call Manager Profile monitor passively monitors call 

activity to create a metric data set for each completed call handled 

by the Cisco Call Manager. 

For the monitor to work, an FTP server must be running on the same 

machine that has the Data Collector for the Cisco Call Manager 

monitor. The Data Collector’s OSDC.properties file must be 

modified to specify the FTP root location and FTP and SNMP must 

be configured on the Cisco Call Manager. 

Configuring the OSDC.properties File 

To specify the location of the FTP server, edit the following section 

in the OSDC.properties file. 

################################################## 

#[Agents.CiscoCallManager] 

################################################## 

Agents.CiscoCM.Java.Library = 

com.wrq.wam.agents.CiscoCallManager.CiscoCallManag 

erMonitor 

Agents.CiscoCM.FTPDirectory = 

C:\\Inetpub\\ftproot\\ 

Agents.CiscoCM.Status = enabled 

Agents.CiscoCM.DebugMode = false 



The FTP server can be installed in any directory, however, it must 

be installed on the machine that has the Cisco Call Manager 

monitor Data Collector. Set Agents.CiscoCM.FTPDirectory to the 

FTP server location. Set the Agents.CiscoCM.Status to enabled. 

Configuring the Cisco Call Manager 

The FTP service and SNMP must be configured and activated on 

the Cisco Call Manager. To configure the Cisco Call Manager: 

Configuring FTP 

1. Log in to the machine on which your Cisco Call Manager reside 

by selecting Cisco Unified Serviceability from the Navigation 

dropdown and entering your user name and password. 

2. Select CDR Management from the Tools menu. 



3. Click the Add new button. 

4. Enter the FTP server information and click Add. Note that the 

Host Name/IP Address must be the host name/IP address of the 

OneSight Data Collector for the Cisco Call Manager monitor. 

5. Select Service Activation from the Tools menu. 



6. Scroll to the CDR Services section and enable the Cisco SOAP – 

CDRonDemand Service and the Cisco CAR Web Service. 



Configuring SNMP V1 or V2c 

1. If you are using SNMP version 1 or 2c, select V1/V2c from the 

SNMP menu, then select Community String. 



2. Click Find. 



3. Click Add New. 

4. Set the Community String to Public. 

5. Select the Accept SNMP Packets from any host option. 



6. Set the Access Privileges field to ReadOnly and click Save. 

7. Select Community String from the SNMP menu, then select 

Notification Destination. 







10. Click Add New in the Host IP Addresses field. 

11. Select the Cisco Call Manager server. 

12. Enter the Host IP Address of the OneSight Data Collector 

where you want to send the information in the Host IP Address 

field. 

13. Enter 161 in the Port Number field. 



14. Select the SNMP version that you are using and click Save. 




16. Make sure that Cisco CallManager SNMP Service is selected in 

the Performance and Monitoring Services list. 



Configuring SNMP V3 

1. If you are using SNMP version 3, select V3 from the SNMP 

menu, then select User. 







4. Enter the user name and password that will be used by 


5. Select MD5 in the Protocol field and click Save. 

6. Select Community String from the SNMP menu, then select 

Notification Destination. 







9. Click Add New in the Host IP Addresses field. 

10. Select the Cisco Call Manager server. 

11. Enter the Host IP Address of the OneSight Data Collector 

where you want to send the information in the Host IP Address 

field. 

12. Enter 161 in the Port Number field. 



13. Select the SNMP version that you are using and click Save. 




15. Make sure that Cisco CallManager SNMP Service is selected in 

the Performance and Monitoring Services list. 

Configuring the Monitor in OneSight 

Once the Cisco Call Manager is configured, you can create the 

monitor in OneSight. 

In the Add Monitor dialog box, when you click Cisco Call Manager 

in the Monitor Types box, settings to configure a Cisco Call 

Manager monitor appear on these dialog box tabs: 


Cisco Call Manager monitor for your monitor group. 

















this monitor. 







To create a Cisco Call Manager profile monitor: 


dialog box. 




can be applied to your monitor group. Click Cisco Call Manager 

to add a monitor that passively monitors Cisco phone call 

activity. You will use settings on the General tab to configure a 

Cisco Call Manager monitor. 

Cisco CM IP Address – Specifies the IP Address of the Cisco 

Call Manager. 

Version – Select the SNMP version being used, Snmp_Version1, 

Snmp_Version2c, or Snmp_Version3. 


3: 










aversion 3 protocol. 


or SHA. 


data. 






Time Out – The amount of time, in seconds, to wait for data 

from the Cisco Call Manager before timing out. 

Port – Specifies the port number used on this system by the 

SNMP agent. Typically, this is port 161. 

Connection Method – Select the connection method to use. 

User Name – Enter the user name to use to log in to the Cisco 

Call Manager. 

Prompt – Specify the command line prompt for the Cisco Call 

Manager. 





Configuring the IDMC Profile Monitor 

3. Enter the IP Address of the Cisco Communication Manager. 

4. Select the SNMP version being used. 

5. Enter the sampling rate. 






save these settings. You can now add this monitor to a monitor 

group. Refer to “Adding Monitor to a Monitor Group” in 

Chapter 4. 


The IDMC (Intelligent Data Mediation and Correlation) Profile 

Monitor monitors Key Performance Indicators (KPIs) that are 

received from Empirix IDMC. 

IDMC profile monitors cannot be created directly in Empirix 

OneSight. Instead, monitors and metrics are created automatically 

based on the configuration information received from the Empirix 

IDMC system. To keep Empirix IDMC and Empirix OneSight 

synchronized with one another, metrics cannot be added in 

OneSight. Metrics can only be edited and deleted. Alerts can be 

added, edited, and deleted. 

Note: After the monitors are created, sampling does not occur until 

the monitors are placed in a monitor group. 

When you choose to edit an IDMC monitor, settings to configure an 

IDMC profile monitor appear on these dialog box tabs: 










specify which monitor groups the monitor is used with. 




this monitor. 

Refer to the, ―Using Empirix OneSight with Empirix IDMC,‖ 

application note for details about how to configure this monitor in 

both Empirix IDMC and Empirix OneSight. 


Configuring OneSight Compound Metric Monitors 

Configuring OneSight Compound Metric 

Monitors 

The OneSight Compound Metric monitor lets you put together data 

from more than one monitor. For example, you can trigger an action 

plan based on the alert state of two metrics or you could calculate 

disk usage across all disks. 

The OneSight Compound Metric monitor has two main 

components: 

References – references are the values used to create expressions. 

There are four types of references: monitor group state, monitor 

state, metric value, and alert state. Monitor group and monitor 

state let you use the color of the status gumball in the expression. 

Metric value lets you use the value of the metric in the 

expression. Alert state lets you use the state of the alert in the 

expression. For example, you could create a reference to the 

retrieval time of a URL, or to the state of a particular monitor. 

Expression – the formula used to calculate the value of the 

OneSight Compound Metric monitor. The result of the formula 

must be numeric. For example, you could create an expression 

that returns 1 if all monitors are in a good state (green) and 0 if at 

least one monitor is in a critical state (red). 

The first thing you do when configuring a OneSight Compound 

Metric monitor is to configure references. Once you configure the 

references, you can create the expression for the Compound 

Monitor. 

In the Add Monitor dialog box, when you click OneSight 

Compound Metric in the Monitor Types box, settings to configure a 

OneSight Compound Metric monitor appear on these dialog box 

tabs: 



Expression Tab – Contains the options that you can use to create a 

OneSight Compound Metric monitor for your monitor group. 

References Tab – Contains the options for creating the references to 

use in the OneSight Compound Metric expression. 

Alerts Tab – Shows what action plan will be used when an alert 

occurs. Options on this tab allow you to set up or modify an action 

plan that responds to alerts generated by the current OneSight 

Compound Metric monitor. You can also configure how an alert 

will affect the monitor group’s health. It can result in a Warning 

state, a Critical state, or can have no impact on health. 













this monitor. 

Each monitor that you create must have a unique name. For 

OneSight Compound Metric monitors you must change the default 

name. To change the default assigned name, type a unique monitor 

name that helps you to identify what this monitor does. 



To create a OneSight Compound Metric monitor: 


dialog box. 


can be applied to your application. Click OneSight Compound 

Metric. 

Options – Displays the valid C language operators that you can 

use at this point in the expression. Select an operator to enter it 

into the expression. Refer to the following sections for a list of 

valid operators and examples. 

– Displays the status of the expression. Every time you 

stop typing, OneSight tries to determine if the expression is 

valid. 



Sample Continuously – Select this option when you want data 

sent whenever the agent has it. 




3. Each monitor that you add must have a unique name. Enter a 

name for the monitor. 

4. Click the References tab. 

Add – Displays the Add Reference dialog box for creating a 

reference. 



Modify – Displays the Modify Reference dialog box for 

modifying the selected reference. 

Remove – Deletes the selected reference. 

Name – Displays the reference name. 

Type – Displays the reference’s type. 

Object – Displays the monitor group, monitor, metric, or alert 

used in this reference. 

5. Click Add. 

Not all fields on this dialog box need to be filled. Only the 

fields required for the type of object selected will be available. 

Name – Enter a name for this reference. Spaces can be included. 

Reference type – Select the type of object you are referencing, 

monitor group, monitor, metric, or alert. 

Group By – Determines how references are selected. Fields are 

displayed based on the selected option. 

Monitor Group – Lets you select based on monitor group. 



Attribute – Lets you select based on attribute values. 

The following fields are displayed when Monitor Group is 

selected in the Group by field. 

Monitor Group – Select the monitor group you want to use or 

the monitor group that contains the monitor, metric, or alert 

you want to reference. 

Monitor – Select the monitor that you want to use or the 

monitor that contains the metric or alert you want to 

reference. 

Metric – Select the metric you want to use or the metric that 

contains the alert you want to reference. 

Entity – Select the entity you want to use. 

Alert – Select the alert that you want to reference. 

The following fields are displayed when Attributes is selected in 

the Group by field. 

Attribute Set – Select the attribute set that you want to filter 

on. 

Attribute Value – Select the attribute values that you want to 

filter on. 

Monitor Type – Select the monitor type. This field is only 

available when Reference Type is Metric Value or Alert State. 

For these reference types, only the same type of metric or 

alert can be compounded. For example, it does not make 

sense to compound a Ping monitor with a Perfmon monitor 

on metric value even though they have the same attribute 

value. 

Metric – Select the metric you want to use or the metric that 

contains the alert you want to reference. 



Alert – Select the alert that you want to reference. 

6. Enter a name for the reference. 

7. Select the object type and complete the fields as they become 

available. 

8. Click OK. 

9. Create as many references are you need, then click the 

Expression tab. 

10. Enter the expression you want to use. Refer to the following 

section for a list of valid operators that can be used in the 

expression. The Options list field contains the options that are 

valid at the current point in the expression. 

For example, if you have created the expressions monitor1, 

monitorgroup1, and metric2, you could compare the status 

(color) of monitor1 to monitorgroup1 and display metric2 if 

they match and zero if they do not match: 

(monitor1 = monitorgroup1) ? metric2 : 0 






save these basic OneSight Compound Metric monitor settings. 

You can now add this monitor to a monitor group. Refer to 

Adding Monitors to a Monitor Group in Chapter 4. 



OneSight Compound Metric Operators 

The following operators can be used to create expressions. 

Operator Description Applies To 

? : 

If the Boolean 

is true select 

the first value 

otherwise 

select the 

second value 

Numeric, 

Color 

+ Addition Numeric 

- Subtraction Numeric 

* Multiplication Numeric 

/ Division Numeric 

( ) Parenthesis Numeric, 

Boolean, 

Color 

abs(val) Absolute Value Numeric 

avg Average Numeric 

ceil(val) Ceiling Numeric 

count(set) 

Calculates the 

number of 

elements in a 

set. 

Numeric, 

Boolean, 

Color 




deltaTimeStamp(metric) 

deltaValue(metric) 


sample 

timestamp 

difference of the 

metric. 


absolute value 

of the difference 

of two sampled 

values of a 

metric. 

Numeric 

Numeric 

false False Numeric, 

Boolean, 

Color 

floor(val) Floor Numeric 

median Median Numeric, 

Boolean, 

Color 

min Minimum Numeric, 

Color 

max Maximum Numeric, 

Color 

power(val1, val2) 

Raise val1 to the 

power of val2 

Numeric 




Reflect(str1,str2,float 

list…) 

Calls class str1’s 

method and str2 

with the parameter 

list. 

Numeric 

round(val) Round Numeric 

sqrt(val) Square Root Numeric 

stddev(val) 

Standard 

Deviation 

Numeric 

true True Numeric, 

Boolean, 

Color 

trunc(val) Truncate Numeric 

valueOverTime(val, 

operator, time_interval) 

Returns the 

average, sum, min, 

or max value for a 

compound metric 

over a relative 

time interval. 

time_interval can 

be specified in 

s(seconds), 

m(minutes), 

h(hours) or 

d(days) and must 

be enclosed in 

quotes. For 

example, ―1d‖. 

Numeric 




(val1, val2, val3) Set Numeric, 

Boolean, 

Color 

OR Boolean or Boolean 

AND Boolean and Boolean 

>= Greater than or 

equal to 

Numeric, 

Color 

> 

Greater than 

Numeric, 

Color 


OneSight Compound Metric Examples 

Monitor States 

This example returns a 1 if monitor1 is in a critical state and 

monitor2 is in a good state is true and a 0 otherwise. In the Add 

Reference dialog box create the following two monitors: 

Monitor 1 

Monitor 2 

Name – monitor1 

Reference Type – Monitor State 

Monitor Group – Select a monitor group 

Monitor – Select a monitor 

No other fields need to be entered. 


Reference Type – Monitor State 




Enter the following expression on the Expression tab: 

(monitor1=red AND monitor2=green)? 1 : 0 

Derived Value based on more than one monitor 

This example creates an expression that returns the average page 

retrieval time for three URL monitors. In the Add Reference dialog 

box create the following three monitors: 

Monitor 1 

Name – url1 

Reference Type – Metric Value 


Monitor – Select a URL monitor 

Metric – Select URL Retrieval Time 

Entity – Select an entity 




Monitor 2 

Monitor 3 

Name – url2 







Name – url3 








Alert State 

avg(url1,url2,url3) 

This example returns 1 if monitor 1 is in a sample failure or monitor 

2 is unavailable. 

In the Add Reference dialog box create the following two monitors: 

Monitor 1 


Reference Type – Alert State 



Metric – Select a metric 


Alert – Select Sample Failure 




Monitor 2 


Reference Type – Alert State 





Alert – Select URL Unavailable 



(monitor1 OR monitor2)? 1 : 0 

Summation of Metric Value using valueOverTime 

This example returns a summation of metric values in the last thirty 

minutes for all compounded Ping monitors tagged with the selected 

attribute value. If the compound monitor’s frequency is five 

minutes, then valueOverTime() will calculate the summation value 

for every five minutes. 

In the Add Reference dialog box create the following two monitors: 

Monitor 1 

Name – attrbasedPingRef 


Group By - Attribute 

Attribute Set – Select an attribute set 

Attribute Value – Select an attribute value 

Monitor Type – URL monitor 




valueOverTime(attrbasedPingRef,sum,”30m”) 


Configuring Database Monitors 


You can set up a monitor that performs a database query for an 

individual machine. The monitor can then provide information on 

the success or failure of that query, measured either by result time 

or by content matching. 

Note: OneSight also includes profile monitors for Oracle and SQL 

Server databases. These profile-based monitors use a set of 

preselected database metrics and allow you to apply the same 

settings to multiple machines. 

At specified time intervals, Empirix OneSight sends a database 

query and records the success or failure of the query based on result 

time or by matching a content string. For example, the monitor can 

perform an SQL Query on a database server using a SELECT 

statement. 

When you click Database in the Monitor Types box in the Add 

Monitor dialog box, settings to configure a Database monitor 

appear on these dialog box tabs: 

JDBC tab – Contains configuration information for the driver used 

to connect to the monitored database. 

Query tab – Contains the query and sampling options for a Database 

monitor. 

Alerts tab – Shows what action plan will be used when an alert 


plan that responds to alerts generated by the current Database 

monitor. You can also configure how an alert will affect the 

monitor group’s health. It can result in a Warning state, a Critical 

state, or can have no impact on health. 


the Database monitor will query the database. 















this monitor. 



monitor by combining the name of the monitor type with the 

database name. To change the default assigned name, type a unique 

monitor name that helps you to identify what this monitor does. 

Database Monitor JDBC Driver Options 

OneSight uses a JDBC driver to connect to your database. When 

you select any Driver other than Custom on the JDBC tab for the 

Database monitor, the appropriate settings for that driver are 

automatically provided. Use these guidelines to select and configure 

the appropriate driver for your database. 

For monitoring enterprise level databases, the native drivers (Oracle 

Thin JDBC driver, Inet Sprinta JDBC driver) are recommended over 

the JDBC:ODBC Bridge option. 

jTDS JDBC Driver for Microsoft SQL Server – This driver option 

applies to SQL databases. This driver is installed automatically as 



part of OneSight. For monitoring enterprise level SQL databases, 

the jTDS JDBC driver is recommended over the JDBC: ODBC Bridge 

option. 

This driver supports NTLM authentication. For this to work, you 

must leave the use name and password fields blank, and the Data 

Collector service must run as a domain account with access to the 

target SQL server. 

Oracle Thin JDBC Driver – This driver option applies to Oracle 

databases. This driver is installed automatically as part of OneSight 

Data collectors. 

Inet Sprinta JDBC Driver for SQL Server – This driver option applies 

to SQL databases. 

Note: This driver is not installed with OneSight. 

JDBC-ODBC Bridge Driver – This driver option is available as an 

option for SQL and Oracle databases and any other database for 

which you have an ODBC driver. This bridge driver is installed 

automatically as part of OneSight. 

SQL Database – The SQL Server ODBC driver is installed with 

MSDE and Microsoft SQL Server. If you do not have either of 

these on the Empirix OneSight server and you are using a 

remotely installed SQL database for OneSight, you need to install 

the SQL Server ODBC driver on the OneSight machine and set up 

an ODBC DSN. The ODBC driver is included with the SQL Server 

Client utilities. 

Oracle Database – You must set up an Oracle ODBC on the 

OneSight machine in order to use this driver. 

Creating a Database Monitor 

You can set up a monitor that performs a database query for an 

individual machine. The monitor can then provide information on 



the success or failure of that query, measured either by result time 

or by content matching. 

To use this monitor, the appropriate driver that allows 

communication between OneSight and the database must be 

installed on the OneSight server. To monitor an SQL Server 

database, the appropriate drivers are automatically installed during 

OneSight setup. 


dialog box. 


can be applied to your monitor group. Click Database to add a 

monitor that issues a database query and checks the results. 

You will use settings on the JDBC tab to configure settings for 

the database connection, and then you will use settings on the 

Query tab to configure the specific database query. 



Use the options on this tab to specify how the Database monitor 

will connect to the database for this query. 

Import/Export – Click this button to display the Import Export 

Monitors dialog box for importing or exporting monitors of this 

type. Refer to ―Exporting and Importing Monitors,‖ later in this 

chapter for more information. 

Driver – Select a driver type from the list: jTDS JDBC Driver for 

Microsoft SQL Server, Oracle Thin JDBC driver, Inet Sprinta 

JDBC driver for Microsoft SQL Server, Sun JDBC:ODBC 

Bridge, or Custom. You must have the appropriate driver 

installed on the OneSight Server in order to set up a Database 

monitor. 

Note: If you are using the : jTDS JDBC Driver for Microsoft 

SQL Server with NTLM authentication, leave the user name and 

password fields blank. 

Driver String – This information will vary depending on the type 

of database that you are monitoring. If you selected any option 

other than Custom, the appropriate string is automatically 

displayed. For example, this is the string for the Oracle Thin 

JDBC driver: 

oracle.jdbc.driver.OracleDriver 

If you selected a Custom driver type, you can type in the Driver 

String yourself. 

Connect String – For most drivers, this string is constructed 

from the information you supplied in the previous fields. The 

structure of the Connect String is different for each driver type, 

but OneSight builds this string for all driver types except a 

Custom driver type. For a Custom driver setting, type in the 

Connect String. 



Connection Settings 

Host – Specify the host name of the machine running the 

database. This is not required for a JDBC:ODBC or Custom 

driver setting. 

Instance – Specify the SQL server instance. 

Port – OneSight displays the default port for the driver you 

selected. For example, the default port for an Oracle Thin 

JDBC driver is 1521. Modify the port number if necessary. 

This is not required for a JDBC:ODBC or Custom driver 

setting. 

Database Name or Database SID – For the Inet Sprinta driver 

for SQL Server, provide the database name. For the Oracle 

Thin JDBC driver, provide the database or server ID. 

System DSN – This field applies to the JDBC:ODBC Bridge 

driver type only. In the Windows Control Panel, locate the 

System DSN in the ODBC Data Sources field to confirm the 

name of the database. The connect string will have the 

following format: 

jdbc:odbc: 


User name – If a user name and password are required for 

access to the database, enter the user name here. The user 

must have system administrator privileges. 

Password – If a user name and password are required for 

access to the database, enter the password here. 

Test – When you add or modify a monitor, you can test JDBC 

and Query settings to determine if they are set appropriately. 

After clicking the Test button, you will see messages in the 

status window as the test runs and when the test completes. 



3. Each monitor that you add must have a unique name. You can 

let OneSight create a unique name, or you can type in your own 


4. On the JDBC tab, select the driver. In this example, select Inet 

Sprinta JDBC Driver for Microsoft SQL Server. The driver 

string com.inet.tds.TdsDriver, is automatically supplied. 

5. For the Host Name, type the name of the OneSight Server. The 

default port, 1433, does not need to be changed. 

6. Type OneSight for the Database Name. 

7. For authentication information, use the database username and 

password for your OneSight SQL Server. 

8. Click the Query tab. 



Use the options on this tab to specify how the Database monitor 

will query the database. 

Note: OneSight does not support multiple queries. 

Query – Enter a valid database statement. For example, you can 

enter the following Oracle SELECT statement: 

select value from v$sysstat where statistic# = 1 

If your database server supports returning a result set from a 

stored procedure you can call the procedure. For example, the 

following SQL Server stored procedure, present in the OneSight 

database, returns a result set (not an output parameter) showing 

the configured OneSight sample rate (samples/minute): 

EmpirixAdmin.p_computeSampleRate 

Report On – Determines the data that is returned. Select query 

time to report on how long it takes the database to retrieve the 

query results. Select Query result to return the actual data 

retrieved by the query. 

Query time – Select query time to see how long it took to 

execute the query. 

Good Content string – Enter the string that you want to match 

in the query. If the query result does not contain this string, 

an error is returned instead of the query time. 

Query result – Select query result to return the actual numeric 

result of the query. If the result does not contain a number, 

use the Advanced button to map strings to numbers that will 

be returned to OneSight. If no Perl expression or string 

mapping is entered, OneSight returns the result. 

Perl Expression – Enter the Perl expression for the value that 

you want to match in the query result. If the query result does 

not contain this value, an error is returned. 



Return the first column of the first row – Select this option to 

return the first column of the first row if there are multiple 

results. 

Loop on result items, returning the first match – Select this 

option to loop on each result and return the first result that 

matches. 

Concatenate result items (space delimited) – Select this option 

to concatenate all results and return the first result that 

matches. Results are space delimited. 

String Mappings – Use this button to display the String 

Mappings dialog box. 

OneSight collects numeric performance data. If you are 

measuring a JDBC result representing a string datatype, it can 

be converted to a number for use in OneSight by using the 

String Mappings field. Specify a semicolon delimited 

mapping of strings to integers. For example, ―false=0;true=1‖ 

converts a false reading to a zero value in OneSight. If you 

only want to display the string on the OneSight status page, 

use a colon, rather than a semi-colon to delimit the values. 

Note that data that has a colon cannot be used in a string 

mapping. 

Scale – If the value that is returned should be scaled for an 

alternate measure, enter the scale and unit of measure here. 

Timeout – Enter the number of seconds after which the query 

will time out. 




Test – When you add or modify a monitor, you can test Query 

and JDBC settings to determine if they are set appropriately. 



After clicking the Test button, you will see messages in the 

status window as the test runs and when the test completes. 

9. On the Query tab, type in the following query string: 

select DBVersion from tbl_dbversion where component=’database’ 

10. The Report on should be Query result. 

Setting Up Oracle ODBC for OneSight 

OneSight uses a JDBC driver to connect to your Oracle database. 

Two options are available. 

JDBC-ODBC Bridge (installed as part of OneSight) 

Oracle Thin JDBC driver 

The procedure below is required only if you are using the JDBC- 

ODBC Bridge to monitor an Oracle database. This requires three 

separate steps: 

1. Install the Oracle Client on the OneSight machine. 

2. Create the Oracle service. 

3. Set up the ODBC DSN. 

Installing the Oracle Client 

Use your Oracle CD to install the Oracle client on the OneSight 

machine. Use the suggested default values. 

Creating the Oracle Service 

1. Open Oracle’s Net8 Easy Config application to create a new 

service. You need to create a service for every Oracle system 

you want to monitor. 



2. Provide a protocol (TCP/IP), a host name or IP address, and the 

SID of the machine. 

3. Test the service. 

Setting up the ODBC DSN 

1. In the Control Panel dialog box, double-click ODBC Data 

Sources. 

2. In the ODBC Data Source Administrator dialog box. Select the 

System DSN tab, then click Add. Select the Oracle ODBC driver. 

3. Enter a Data Source Name, Under Data Source, enter the Oracle 

service name (created in the step above) or type in an IP 

address. In the User field, type in a user name that has 

administrator privileges. 

4. You can use the Oracle ODBC test to confirm the system data 

sources. After opening Oracle ODBC Test, click Connect. Click 

the Machine Data Source tab and select your Data Source. 

Click All Tables to confirm the data you expect is present. 

After completing these procedures, open the OneSight System 

Editor and create a Database component. Click the new component, 

and use the Component and JDBC tabs to fill in the information for 

monitoring the Oracle database. Use the system editor to create this 

component for each system you want to monitor. 

Setting Up DataDirect JDBC Driver for OneSight 

The SQL Server and the data collector for the location being 

monitored must be running under a user account. 

SQL Server Configuration 

1. Stop the SQL Server service. 



2. For SQL Server 2000 use Enterprise Manager. For SQL Server 

2005 use the Management Studio. Go to SQL Server properties. 

3. Select the Security tab. 

4. Allow SQL Server and Windows authentication. 

5. Select run using this account instead of the local system 

account. 

6. Enter the Windows user name and password. 

7. Restart the SQL Server service. 

Data Collector Configuration 

The data collector must be in the same domain as the monitored 

SQL Server. 

1. Copy the following files from the DataDirect lib directory to 

the webapps\ROOT\WEB-INF\lib directory of the OneSight 

DataCollector install directory. This lets the OneSight Data 

Collector to load the required jar files from DataDirect. 

base.jar 

sqlserver.jar 

util.jar 

2. Use one of the following methods to place the OneSight Data 

Collector service in the same active user account as the MSSQL 

user account: 

Run the OneSight Data Collector service under the specified 

user account instead of the local system account. 

Log in to Windows and leave the session logged in so that 

Windows knows the current active user information. 



Monitoring Multiple Rows in a Database 

You can monitor multiple rows in a database by creating a custom 

component, creating a profile, then applying the profile to the 

component. 

To create a custom component: 

1. Select Systems from the Configure menu. 

2. Select the system you want to monitor and click Modify or click 

Add to create a system. 

3. Select Add. 

4. Select Add New Component Type. 

5. Enter a name and description. 

6. Select JDBC and click OK. 

7. Fill in the connection information on the JDBC tab. 

8. In the Query field, enter the query. For example, select 

stor_id from sales. 

9. Click Discover Components. 

10. In the Discover Components Configuration dialog box, select 

JDBC and click OK. 

11. Click Cancel in the Discovery Status window. Discovered 

components are added under the custom type in the components 

tree. 

12. Click OK to save the discovery for the system. 



To create the database profile: 

1. Select Profiles from the Configure menu. 

2. Click Add. 

3. Enter a name and description for the profile. 

4. Select Global Metric Manager. 

5. Click Add. 

6. Enter a name and description for the metric. 

7. In the Sample for Each field on the General tab, select the 

custom component that you created. 

8. On the Data Sources tab, select JDBC as the data source. 

9. Enter the query using the %instance_n% variable. In the 

components tree, each custom node is assigned a value. In this 

example, there is one custom node ―A.‖ It’s value is 1. If there 

were another custom component it’s value would be 2 and so 

forth. Replace the n with the value corresponding to the node 

you want to monitor. In this example, the query is select 

storid from sales where stor_id=’%instance_1%’ 

10. Click OK. 

11. Click Close. 

12. Click OK. 

To apply the profile: 

1. Select Monitors from the Configure menu. 

2. Select Add. 


Configuring DNS Monitors 

3. Expand the Profiles node and select the profile you just created. 


5. Select the system you want to apply it to, and click Next. 

6. Click Finish. 

7. Click OK to exit. 


The DNS monitor checks the Domain Name System (DNS) Server 

via the network. 

At specified time intervals, a DNS monitor verifies that the DNS 

servers are accepting requests and also verifies that the addresses 

for specific domain names can be found. 

If no response is received within a timeout period, or if a DNS 

response indicates any errors or no address found, an alert with an 

error message is generated. Optionally, the IP address returned by 

the DNS server can be compared with an expected IP address 

specified by the user. If they are not equal, an alert with an error 

message is generated. 

The DNS monitor performs the following tasks: 

Verifies that a DNS server is accepting requests. 

Verifies that the addresses for specific domain names can be 

found. 

Ensures that responses occur within a timeout value. 

If a Host address is specified, verifies that the IP address returned 

by the DNS server matched an expected IP address. 



In the Add Monitor dialog box, when you click DNS in the Monitor 

Types box, settings to configure a DNS monitor appear on these 

dialog box tabs: 

General Tab – Contains the options that you can use to create a DNS 

monitor for your monitor group. 



plan that responds to alerts generated by the current DNS monitor. 

You can also configure how an alert will affect the monitor group’s 

health. It can result in a Warning state, a Critical state, or can have 

no impact on health. New alerts cannot be added to DNS monitors. 

Locations Tab – Specifies the Data Collector Location to use as a 

DNS monitor for your monitor group. 













this monitor. 









An apparent web server failure may be caused by a problem with a 

domain name server that translates host names to Internet addresses. 

Create a DNS monitor to evaluate the performance of the domain 

name resolution system for your web site. 

To create a DNS monitor: 


dialog box. 


can be applied to your monitor group. Click DNS to add a 

monitor that checks the availability and responsiveness of a 

specific domain name server. You will use settings on the 

General tab to configure a DNS monitor. 







DNS Server – Specifies the IP address of the DNS server. The 

monitor will verify that this DNS server is accepting requests. 

Host Name – Specifies the host name to look up on the DNS 

server. Depending on your network and system configuration, 

you may need to enter a fully qualified DNS name. 

Host Address – Specifies the IP address of the host that the DNS 

server is looking up. The monitor will verify that the IP address 

returned by the DNS server matches the host address specified 

in this box. This feature is optional. 

Timeout Seconds – Specifies the number of seconds to wait 

for a DNS reply. The value must be between 1 and 30, inclusive. 

If a DNS reply is not received in this amount of time, the DNS 

request is retried. 

Retries – Sets the upper limit for the number of times a DNS 

request is retried after timing out. For example, if Retry is set to 

3, the DNS request will be sent up to four times (the initial try 

plus three retries). After the fourth try, if no response is 

received, the DNS check is treated as a sample failure. 

On Failure – Indicates whether to include additional information 

in an alert when the monitor fails. 

Include Traceroute in alert – Includes a trace route in the alert. 

Include Ping in alert – Includes the results of a ping in the 

alert. This option is faster than including the trace route in 

the alert. 

Do Nothing – Does not include any additional information in 

the alert. 






Test – When you add or modify a monitor, you can test settings 

to determine if they are set appropriately. After clicking the 

Test button, you will see messages in the status window as the 

test runs and when the test completes. 


let OneSight create a unique name using the DNS specifications 

you supply, or you can type in your own name for the monitor. 

4. On the General tab in the DNS Server box, type in the IP 

address of the domain name server that you want to monitor. 

5. Type in a Host Name that the DNS server should resolve. You 

can also type in the IP address of the host name you specify in 

the Host Address box so that the monitor will verify that the IP 

address returned by the DNS server matches the address you 

specify here. 

6. By default, a DNS monitor will check the availability and 

responsiveness of the domain name server every 10 minutes and 

will time out after 10 seconds if the name is not resolved. If you 

want the monitor to sample more or less frequently, change the 

sampling interval. If you want to have the timeout occur earlier 

or later, change the Timeout setting. 






save these basic DNS monitor settings. You can now add this 

monitor to a monitor group. Refer to Adding Monitors to a 

Monitor Group in Chapter 4. 


Configuring Gomez GPN Monitors 


Gomez GPN is Empirix’s hosted service that lets you monitor your 

Web site in real time, using objective performance data gathered 

from points on a global network. The service lets you monitor your 

web site performance from outside of your firewall from a secure 

network that spans five continents. If you have a Gomez GPN 

account, you can create a Gomez GPN monitor to provide external 

measurements from outside your firewall, and then correlate these 

measurements with the performance of internal systems. (See 

www.empirix.com for more information about the Gomez GPN 

service.) 

The Gomez GPN Monitor retrieves data for the monitors you have 

configured within your Gomez GPN service account. Data is 

aggregated for all locations. 

In the Add Monitor dialog box, when you click Gomez GPN in the 

Monitor Types box, settings to configure a Gomez GPN monitor 



Gomez GPN monitor for your monitor group. 

Proxy Tab – Contains the options that you can use to configure a 

Proxy Server to use with a Gomez GPN monitor for your monitor 

group. 



plan that responds to alerts generated by the current Gomez GPN 




















this monitor. 







To create a Gomez GPN monitor: 


dialog box. 




can be applied to your monitor group. Click Gomez GPN to add 

a monitor that checks the availability and responsiveness of a 

selected monitor from the Gomez GPN service. You will use 

settings on the General tab to configure a Gomez GPN monitor. 

User ID – Type the User ID of your Gomez GPN service 

account. 

Password – Type the password of your Gomez GPN service 

account. 

Get Gomez GPN Monitors – After you provide the account 

information (User ID, Password), click Get Gomez GPN 

Monitors to retrieve the active monitors configured in your 

Gomez GPN service account. If you have previously specified 



this account information, these monitors will be retrieved 

automatically. 

Monitors – After you click Get Gomez GPN Monitors, the active 

monitors configured in your Gomez GPN service account will 

be displayed in this list box. 

Location – Select the location for collecting the data. 

Step – Select the step to use for monitoring. 






let OneSight create a unique name using the Gomez GPN 

specifications you supply, or you can type in your own name 

for the monitor. 

11. On the General tab in the User ID box, type the name of your 

Gomez GPN User ID. 

12. On the General tab in the Password box, type your Gomez GPN 

password. 

13. Click Get Gomez GPN Monitors. Using the login information 

you have specified, the active monitors configured in your 

Gomez GPN service account are identified and listed here. If 

you have previously specified this account information, these 

monitors will be retrieved automatically. 








save these basic Gomez GPN monitor settings. You can now 

add this monitor to a monitor group. Refer to Adding Monitors 

to a Monitor Group in Chapter 4. 

To Specify Proxy Server Settings 

Use the options on the Proxy tab to specify proxy server settings. 

Proxy Server Settings – If your network makes use of a proxy server, 

you can specify this information here. Check Use a proxy server and 

add the information below. 

If you find that a OneSight Gomez GPN monitor fails to reach a 

URL when your browser successfully connects to the same URL, 

check your proxy server settings in your browser. For example, in 


Configuring Gomez GPN Profile Monitors 

Internet Explorer, select Internet Options from the Tools menu and 

then click LAN settings on the Connections tab. If proxy server 

settings are configured for your browser, they may also need to be 

configured for the Gomez GPN monitor. 

Proxy Host – The IP address of the proxy server. 

Port – The port of the proxy server. 

Proxy User Name – The username for the proxy server. 

Password – The password for the proxy server. 


Gomez GPN is Empirix’s hosted service that lets you monitor your 

Web site in real time, using objective performance data gathered 

from points on a global network. The service lets you monitor your 

web site performance from outside of your firewall from a secure 

network that spans five continents. If you have a Gomez GPN 

account, you can create a Gomez GPN monitor to provide external 

measurements from outside your firewall, and then correlate these 

measurements with the performance of internal systems. (See 

www.empirix.com for more information about the Gomez GPN 

service.) 

The Gomez GPN profile Monitor retrieves data for the monitors you 

have configured within your Gomez GPN service account. Data is 

aggregated for all locations. 

In the Add Monitor dialog box, when you click Gomez GPN in the 

Monitor Types box, settings to configure a Gomez GPN monitor 



Gomez GPN profile monitor for your monitor group. 




Proxy Server to use with a Gomez GPN profile monitor for your 




plan that responds to alerts generated by the current Gomez GPN 

profile monitor. You can also configure how an alert will affect the 















this monitor. 









To create a Gomez GPN profile monitor: 


dialog box. 


can be applied to your monitor group. Expand the Profiles node 

and click Gomez GPN Profile to add a monitor that checks the 

availability and responsiveness of a selected monitor from the 

Gomez GPN service. You will use settings on the General tab to 

configure a Gomez GPN profile monitor. 

User ID – Type the User ID of your Gomez GPN service 

account. 

Password – Type the password of your Gomez GPN service 

account. 



Get Gomez GPN Monitor – After you provide the account 

information (User ID, Password), click Get Gomez GPN Monitor 

to retrieve the active monitors configured in your Gomez GPN 

service account. If you have previously specified this account 

information, these monitors will be retrieved automatically. 

Info – Displays information about the selected monitor. 


let OneSight create a unique name using the Gomez GPN 




Gomez GPN User ID. 

5. On the General tab in the Password box, type your Gomez GPN 

password. 

6. Click Get Gomez GPN Monitor. Using the login information you 

have specified, the active monitors configured in your Gomez 

GPN service account are identified and listed in the Select 

Gomez GPN Monitor dialog box. 

7. Select the monitor you want to use and click OK. 






save these basic Gomez GPN profile monitor settings. You can 

now add this monitor to a monitor group. Refer to Adding 

Monitors to a Monitor Group in Chapter 4. 



To Specify Proxy Server Settings 

Use the options on the Proxy tab to specify proxy server settings. 




If you find that a OneSight Gomez GPN monitor fails to reach a 






configured for the Gomez GPN monitor. 


Configuring OneSight Call Statistics Profile Monitors 





Configuring OneSight Call Statistics Profile 

Monitors 

OneSight Call Statistics Profile Monitors let you monitor call center 

devices that are configured to talk to the call statistics server. 

In the Add Monitor dialog box, when you click OneSight Call 

Statistics Profile in the Monitor Types box, settings to configure a 

OneSight Call Statistics Profile monitor appear on these dialog box 

tabs: 


OneSight Call Statistics Profile monitor for your call center. 



plan that responds to alerts generated by the current OneSight Call 

Statistics Profile monitor. You can also configure how an alert will 

affect the monitor group’s health. It can result in a Warning state, a 

Critical state, or can have no impact on health. 















this monitor. 

Monitor Name – Each monitor that you create must have a unique 

name. In the Monitor Name box, OneSight creates a unique name 

for the current monitor by combining the name of the monitor type 

with the name of the host to which the monitor applies. To change 

the default assigned name, type a unique monitor name that helps 

you to identify what this monitor does. 

Profile – Lists the profiles that are available to apply to this monitor. 

Multiple profiles may be listed if you have upgraded from a 

previous version of OneSight. 

Modify – Displays the OneSight Profile Editor that lets you add and 

remove metrics, and configure alerts, smartlinks, and attributes for 

this profile. 

To create a OneSight Call Statistics Profile monitor: 


dialog box. 




can be applied to your monitor group. Click OneSight Call 

Statistics. You will use settings on the General tab to configure 

a OneSight Call Statistics Profile monitor. 

Server Name – Type the name or IP address of the OneSight 

Call Statistics server. 

Server Port – Enter the port for the OneSight Call Statistics 

server. 








– lists the devices that are configured to talk to the 

OneSight Call Statistics server. 

Discover Devices – After you provide the Server and Port 

information, click Discover Devices to retrieve the available 

devices. 

String Mappings – Displays the String Mappings dialog box for 

specifying string mappings. 

String Mappings – OneSight collects numeric performance 

data. If you are measuring a OneSight Call Statistics object 

representing a String datatype, it can be converted to a 

number for use in OneSight by using the OneSight Call 

Statistics String Mappings field. Simply specify a semicolon 

delimited mapping of Strings to Integers. For example, 

―false=0;true=1‖; will convert a ―false‖ reading to a 0 value 

in OneSight, and this will be displayed in OneSight Status as 

―false=0‖. If you only want to display the string on the 

OneSight status page, use a colon, rather than a semi-colon to 

delimit the values. 

If you neglect to provide a mapping for a specific string, 

OneSight will consider this a Sample Failure, and report the 

String that was returned. String Mappings can also be used to 

translate a number to a String for display in OneSight Status. 

This is helpful when numbers represent an objects state. 

Note that string matching is case-insensitive and data that has 

a colon cannot be used in string mapping. 

Set Primary Keys – After you select either an entire table or a 

column in the table, click Set Primary Keys to select the row in 

the table. 


let OneSight create a unique name using the OneSight Call 

Statistics specifications you supply, or you can type in your 

own name for the monitor. 



4. On the General tab in the Server name box, type the name or IP 

address of your OneSight Call Statistics server. 

5. Enter the server port. 

6. Click Discover Devices. The available devices and their 

database tables are listed. 

7. Select the device and tables that you want to monitor and click 

Set Primary Keys. The primary keys for the selected table are 

displayed. This dialog box lets you select the row that you want 

to monitor. 

Table name – lists the name of the table. 

Primary Key – lists the primary keys available in the selected 

tables. 

Value – lists the values associated with the key. The selected 

value determines which row you are selecting. 

8. Click the Value field to list the available values. Select a value 

and click OK. 


Configuring OneSight Probe Monitors 

9. Click OK in the Add Monitor dialog box to save these basic 

OneSight Call Statistics Profile monitor settings. You can now 




The OneSight Probe monitor uses a customer created probe, 

referred to as a self-describing probe (SDP) as a data source for 

reporting information for monitoring. The SDP allows unrestricted 

collection of information for metrics that are not known to 

OneSight. Refer to the OneSight Probe Reference Manual for 

details on creating an SDP. 

In the Add Monitor dialog box, when you click OneSight Probe in 

the Monitor Types box, settings to configure a OneSight Probe 

monitor appear on these dialog box tabs: 


OneSight Probe monitor. 



plan that responds to alerts generated by the current OneSight Probe 


















this monitor. 







To create a OneSight Probe monitor: 


dialog box. 




can be applied to your monitor group. Click OneSight Probe to 

add a monitor. You will use settings on the General tab to 

configure a OneSight Probe monitor. 





Collector Host Name – Enter the host name of the data collector 

to which the probe is registered. 








Discover Probes and Metrics – Discovers the probes and metrics 

and populates the list as a tree. 

Info - Displays details about the probe and the metric. 

Metric Type – Select the type of metric. 

Perl Expression Value – Lets you enter a Perl Expression for 

parsing the results. 

Total Records Encountered Since Last Sample – Returns the 

number of records added since the last sample. 

Perl Expression – Enter the Perl Expression to use to parse the 

results. Refer to “Using Regular Expressions for Pattern 

Matching,” later in this chapter for more information. 


let OneSight create a unique name using the OneSight Probe 



4. On the General tab in the Collector Host Name field, enter the 

host name of the data collector to which the probe is registered. 

5. Click Discover Probes and Metrics. The probes and metrics on 

the specified data collector are displayed in a tree view. 

6. Select the metric you want to monitor. 

7. Select the metric type. 






save these basic OneSight Probe monitor settings. You can now 


Configuring OneSight Voice Transaction Profile Monitors 



Configuring OneSight Voice Transaction Profile 

Monitors 

OneSight Voice Transaction Profile Monitor lets you monitor your 

call center in real time, using objective performance data gathered 

from your CallMaster server. If you have your own CallMaster 

server, you can create a OneSight Voice Transaction Profile 

monitor in OneSight to verify the performance of your telephonybased 

voice transaction systems. 

Note: The Hammer CallMaster server and the proxy server must be 

the same version. 

The OneSight Voice Transaction Profile monitor lets you select 

which steps you want to test in the script. 

The OneSight Voice Transaction Profile monitor retrieves data for 

the monitors you have configured within your OneSight Voice 

Engine. 

In the Add Monitor dialog box, when you click OneSight Voice 

Transaction Profile in the Monitor Types box, settings to configure 

a OneSight Voice Transaction Profile monitor appear on these 



OneSight Voice Transaction Profile monitor for your call center. 




Voice Transaction Profile monitor. You can also configure how an 

alert will affect the monitor group’s health. It can result in a 

Warning state, a Critical state, or can have no impact on health. 








this monitor. 



















this profile. 

Note: When you modify alerts for OneSight Voice Transaction 

Profile monitors, you must select Override profile in the Alert Editor 

to make the fields available. Any changes that you make will apply 

to this monitor only, not to the profile itself. 



To create a OneSight Voice Transaction Profile monitor: 


dialog box. 


can be applied to your monitor group. Click OneSight Voice 

Transaction Profile to add a monitor that checks the availability 

and responsiveness of a selected monitor from the OneSight 

Voice Transaction service. You will use settings on the General 

tab to configure a OneSight Voice Transaction Profile monitor. 

Script – Displays the script being used. 

Import – Displays the Import CallMaster script dialog box for 

selecting the script you want to use. 

Edit Steps – Displays the Script Steps dialog box for selecting 

the units to use to evaluate the script steps. 



Parameters – Displays the Input Parameter dialog box for 

entering an input parameter. For example, if you have a script 

that needs to place a call, you can enter one or more numbers in 

the input parameter list. This button is only available when the 

script requires input parameters. 

Voice Resource – Displays the Voice Resource Editor dialog 

box for specifying the CallMaster servers and channels to use 

as voice resources. 

Scenario Name – Specifies the name of the scenario. 

Retries – Specifies the number of times to retry the script if the 

script fails. 




Sample as soon as possible – When you are using the x@y 

format, causes the monitor to sample as soon as it can. For 

example, if you specified 40@5 and the monitor was started at 

12:10, the first sample would normally be at 1:05. If this 

checkbox is selected, the first sample will be at 12:45. 


let OneSight create a unique name using the OneSight Voice 

Transaction specifications you supply, or you can type in your 




4. Click the Import button to display the Import CallMaster script 

dialog box. 

Script – Enter the script path or click Browse. CallMaster 

scripts are SBX format files. 

Browse – Displays the Choose File dialog box for selecting a 

script. 

5. Select the script and click OK. 

This dialog box lets you select the script steps you want to test 

and select the units to use to evaluate the script steps. 

Check All – Selects all of the script steps. 

Uncheck All – Deselects all of the script steps. 

– Click the check box in front of the steps that you 

want to test. 

– Select the units to use to evaluate the steps. 



6. Select the steps that you want to test and click OK. 

7. If the script requires input parameters, the number of 

parameters required is shown in the Parameters field. Click 

Input Parameter to display the Input Parameter Editor. 

This dialog box lets you configure parameters particular to this 

script. The columns displayed are based on the script’s 

requirements. 

Add – Displays the Input Parameter Editor for entering 

parameters that pertain to this script. 

Modify – Displays the Input Parameter Editor for modifying the 

selected parameter set. 

Remove – Deletes the selected parameter set. 

Add from CSV file – Displays the Upload Input Parameter dialog 

box for adding parameters from a Comma Separated Value file. 

The file must be set up so that the first line of the file contains 

the column names, the second line contains the type of data, 

and the third line contains the default values. The input 

parameter data should start on the fourth line and each line 

should only contain one set of input parameter data. Data 

should be surrounded by double quotes. 

Parameters – Displays the configured parameters. 



8. The Input Parameter Editor shows the input parameters that it 

needs. In the example above, the script needs a phone number 

and digit. Click Add to add a parameter. 

Or click Add from CSV file to upload the parameters from a 

Comma Separated Value file. The file must be set up so that the 

first line of the file contains the column names, the second line 

contains the type of data, and the third line contains the default 

values. The input parameter data should start on the fourth line 

and each line should only contain one set of input parameter 

data. Data should be surrounded by double quotes. 

9. Enter the parameters or select the file and click OK. 

10. You can add multiple parameter sets. When you are finished 

adding parameters, click OK. 



11. Click Voice Resource to display the Voice Resource Editor for 

selecting servers and channels to use as voice resources. 

Add – Displays the CallMaster System Editor for adding a 

CallMaster server and for configuring voice groups for the 

server. 

Modify – Displays the Edit CallMaster System dialog box for 

editing the selected system. 

Remove – Deletes the selected system. 

CallMaster Server Name – Displays the configured CallMaster 

system names. 

Port – Displays the CallMaster system port being used. 

Available Voice Group – Displays the voice groups that are 

available for the selected system. 

Selected Voice Group – Displays the voice groups selected for 

testing. 



12. Click Add. 

CallMaster Server Name – Enter the CallMaster server name. 

Port – Enter the port to use. 

About CallMaster – Displays the minimum required CallMaster 

version and the current version and build numbers. 

Add – Displays the Voice Resource Editor for configuring a voice 

group. 

Modify – Displays the Voice Resource Editor for modifying the 

selected voice group. 

Remove – Deletes the selected voice group. 

13. Enter the CallMaster server name and its port that you want to 

use. 



14. Click Add to add a voice group or click OK to return to the 

Voice Resource Editor. If you click Add the following dialog 

box is displayed. 

This dialog box lets you configure voice groups. 

Voice Group – Enter the name of the voice group. 

Channels – Select the channels that you want to include in the 

voice group. 

15. Select the channels you want to use and click OK. 

16. In the Voice Resource Editor select the system and voice 

groups that you want to use and click OK. 




Configuring JMX Monitors 




save these basic OneSight Voice Transaction Profile monitor 

settings. You can now add this monitor to a monitor group. 

Refer to Adding Monitors to a Monitor Group in Chapter 4. 


The JMX monitor lets you determine if a Java application is 

performing properly. The JMX monitor checks the specified JMX 

MBean Attribute values at specified time intervals to confirm that 

the Java application is performing as expected. The JMX monitor 

also provides an easy way to confirm whether or not the JMX 

application is running. 

The JMX monitor connects to the remote JMX application’s MBean 

Server using Java RMI protocol for Weblogic and JBoss and SOAP 

for WebSphere. Once connected to the MBean Server, the JMX 

monitor can get an MBean’s Attribute’s current value. The JMX 

monitor configuration can also discover all available MBeans that 

the MBean Server knows about, making it easy to select the name 

of the MBean and its attribute of interest. 

For the JMX monitor to be able to connect to an MBean Server, the 

JMX-enabled application’s jar file must be copied to the monitoring 

(Data Collector) machine in a default directory location as specified 

in the table below. The jar file on the Data Collector machine must 

be the same version (that is, an exact copy) of the jar file that the 

JMX application is using, otherwise, the JMX monitor will not be 

able to connect to that MBean Server. 

The JMX monitor can concurrently connect to any number of 

MBean Servers and versions with some exceptions as described in 

―Installing the Data Collector on a Windows Machine,‖ in 

Chapter2. During the data collector installation process, you must 

have selected the application server(s) that you are using. If the 



Application 

Server 

BEA 

Weblogic 

8 Serials 

JMX Proxy for the application server you are using has not been 

installed, you will not be able to connect. Refer to “Using the JMX 

Proxy,” in Chapter 2 for information on installing and configuring 

the JMX Proxy. 

The following table lists the supported JMX applications, the jar 

files, and the default directory location that the files must be copied 

to. 

Application 

Name Jar Files Default Directory 

weblogic81 

weblogic.jar 

webservices.jar 

C:\Empirix\DataCollector\ 

JMXProxy\Proxy14\class 

es\weblogic8.1 and 

C:\Empirix\Datacollector\ 

JMXProxy\Proxy14\lib 

BEA 

Weblogic 

9 Serials 

weblogic90 

weblogic.jar 

webservices.jar 



es\weblogic9.0 

BEA 

Weblogic 

10 Serials 

weblogic 

100 

wlclient.jar, wljmxclient.jar 



es\weblogic10.0 

IBM 

WebSpher 

e 6.0 

websphere6 

0 

admin.jar, bootstrap.jar, 

classloader.jar, emf.jar, 

ffdc.jar, 

ibmcertpathprovider.jar, 

ibmjceprovider.jar, j2ee.jar, 

mail-impl.jar, 

management.jar, ras.jar, 

runtimefw.jar, sas.jar, 

security.jar, soap.jar, 

utils.jar, wasjmx.jar, 

wasproduct.jar, 

wsexception.jar, wssec.jar, 

runtime.jar, idl.jar, 

iwsorb.jar 



es\websphere6.0 



IBM 

WebSpher 

e 6.1 

websphere6 

1 

ws_runtime.jar 



es\websphere6.1 and 


JMXProxy\Proxy15\lib 

IBM 

WebSpher 

e 7.0 

websphere7 

0 

com.ibm.we.admin.client_7 

.0.0.jar 


JMXProxy16\lib 

JBoss 3.2 jboss32 jbossall-client.jar C:\Empirix\DataCollector\ 


es\jboss3.2 

JBoss 4 

Serials 

JBoss 5 

Serials 

jboss40 jbossall-client.jar C:\Empirix\DataCollector\ 


es\jboss4.0 

jboss50 jbossall-client.jar C:\Empirix\DataCollector\ 


es\jboss5.0 

Tomcat 5+ Tomcat Not required Not required 

Additional Notes 

WebSphere 7.0 – Set the following line to false in the 

service.properties file: 

Agents.JMX.WLUseReflection = false 

WebLogic 8.1 –Change the following lines in the 

Proxy14\properties\service.properties file: 

PROXY.SupportedJMXServers = weblogic81 

Agents.JMX.WLUseReflection = false 

WebLogic 9.x – Change the following line in the 




PROXY.SupportedJMXServers = weblogic90 //No weblogic 100 

WebLogic 10.x – Change the following line in the 


PROXY.SupportedJMXServers = weblogic100 //No Weblogic 90 

WebSphere 6.0 – Uncomment the following line in the 

Proxy15\properties\proxy_win_service.properties file: 

# JMXProxy.commandline = 

- 

Xbootclasspath/p:\..\classes\websphere6.0\mana 

gement.jar 

Set the following line in the Proxy15\properties\service.properties file 

to disable support to other Application Servers on this JMX Proxy: 

PROXY.SupportedJMXServers = websphere60 

JBoss 3.x – Change the following line in the 


PROXY.SupportedJMXServers = jboss32 



PROXY.SupportedJMXServers = Jboss40 



PROXY.SupportedJMXServers = jboss50 

Tomcat – By default, Tomcat does not support JMX. Refer to 

\support\JMXProxy\Tomcat.doc for more details. 

Change the following line in the 

\properties\service.properties file: 



PROXY.SupportedJMXServers = tomcat 

In the Add Monitor dialog box, when you click JMX in the Monitor 

Types box, settings to configure a JMX monitor appear on these 


General Tab – Contains the options that you can use to create a JMX 

monitor for your call center. 

Advanced Tab – Contains the options that you can use to configure 

authentication information if the web application server requires it. 



plan that responds to alerts generated by the current JMX monitor. 



no impact on health. 















this monitor. 



To create a JMX monitor: 


dialog box. 


can be applied to your monitor group. Click JMX to add a 


selected monitor from the JMX service. You will use settings on 

the General tab to configure a JMX monitor. 





JMX App name – The name of the JMX application. Valid 

entries are those listed or a user-created name in the Data 

Collector’s OSDC.properties file. 



Host Name – The name of the JMX application’s JNDI server. 

Port – The port number of the JMX application’s JNDI server. 

MBean Name – The fully qualified MBean name. This is 

automatically filled in if you select an MBean attribute from the 

Discover MBeans result tree. 

Attribute Name – The Mbean’s attribute name or select it from 

the Discover MBeans result tree. 

Attribute Property – The attribute property or select it from the 

Discover MBeans result tree. 

Operation Name – Specifies the operation that will be called. 

The result from the operation is the sample metric. 

Operation Param – Specifies the parameters for invoking the 

operation. Only simple types are supported. For example, int, 

float, string, etc. 

Description – This is automatically filled in if you select an 

MBean name and attribute from the Discover MBeans result 

tree. 




Discover MBeans – Discovers the MBean names and their 

attributes from the JMX application’s MBean Server. The 

results are displayed below the button. Selecting a node 

automatically fills in the MBean Name, Attribute Name, and 

Description fields. 

of type – Select the type of MBeans to discover or select All 

MBeans to discover all types of MBeans. 

Contains – Enter text to filter the list. 



Test – When you add or modify a monitor, you can test General 

settings to determine if they are set appropriately. After clicking 

the Test button, you will see messages in the status window as 

the test runs and when the test completes. 


let OneSight create a unique name using the JMX specifications 


4. On the General tab, enter the Host Name and Port number of 

the JNDI server. 

5. If required for accessing the JNDI server, enter the username 

and password. 

6. Click Discover MBeans to find all of the MBeans and their 

attributes. 

7. Select an MBean from the result tree to automatically fill in the 

MBean Name, Attribute Name, and Description fields. 






save these basic JMX monitor settings. You can now add this 





Configuring Advanced Settings 

Use the Advanced tab to specify the following settings. 

Scale – Type the multiplier you want applied to the data that’s 

collected. 

Setting Scale to 1 means the data will be reported as it is. If the 

metric measurement is expressed in kilobytes, setting Scale to 1024 

will translate it to bytes. If the metric measurement is expressed in 

milliseconds, setting Scale to .001 will translate it to seconds. 

String Mappings – OneSight collects numeric performance data. If 

you are measuring an object representing a String datatype, it can 

be converted to a number for use in OneSight by using the String 

Mappings field. Simply specify a semicolon delimited mapping of 



Strings to Integers. For example, ―false=0;true=1‖; will convert a 

―false‖ reading to a 0 value in OneSight, and this will be displayed 

in OneSight Status as ―false=0‖. If you only want to display the 

string on the OneSight status page, use a colon, rather than a semicolon 

to delimit the values. 

If you neglect to provide a mapping for a specific string, OneSight 

will consider this a Sample Failure, and report the String that was 

returned. String Mappings can also be used to translate a number to 

a String for display in OneSight Status. This is helpful when 

numbers represent an objects state. 

Note that string matching is case-insensitive and data that has a 

colon cannot be used in string mapping. 

Translation Type – Select No Translation if the value requires no 

further modification. The Rate translation type means that the value 

should be calculated as frequency per minute. 

Unit Measure – To define a Unit Measure, click the arrow to select a 

unit measure (%, bytes, hours, minutes, seconds). You can also type 

in a unit measure such as messages/minute. This measure is a 

display string. It does not perform any data translation. 

MBean Server Requires Authentication – Select this checkbox to 

enter authentication information: 

Username – The username for accessing the JNDI server. 

Password – The password for accessing the JNDI server. 

In addition to the above fields, the following fields are required for 

WebSphere to identify the digital certificate. The WebSphere 

iKeyman utility (normally located in the Program 

Files\IBM\WebSphere\AppServer\bin\ directory) can be used to generate 

the certificate. 


Configuring OneSight Voice Watch Monitors 

Trust Store File – Enter the client-side trust store path and file 

name. This file should be in the datacollector directory. 

Trust Store Password – Enter the trust store file password. 

Key Store File – Enter the client-side key store path and file name. 

This file should be in the datacollector directory. 

Key Store Password – Enter the key store file password. 

If you are using a .p12 key file, you will need to save it as a .jks file. 

Do this by opening the file in the ikeyman utility (normally located 

in the Program Files\IBM\WebSphere\AppServer\bin\ directory) and 

saving it as a .jks file. Use this file name in the Trust Store File and 

Key Store File fields. 


OneSight Voice Watch is Empirix’s hosted service that lets you 

monitor your call center in real time, using objective performance 

data gathered from points around the country. The service lets you 

monitor your call center performance from outside of your firewall. 

If you have a OneSight Voice Watch account, you can create a 

OneSight Voice Watch monitor to provide external measurements 

of your telephony-based voice transaction systems and then 

correlate these measurements with the performance of internal 

systems. (See www.empirix.com for more information about the 

OneSight Voice Watch service.) 

The OneSight Voice Watch Monitor retrieves data for the monitors 

you have configured within your OneSight Voice Watch service 

account. 


Watch in the Monitor Types box, settings to configure a OneSight 

Voice Watch monitor appear on these dialog box tabs: 




OneSight Voice Watch monitor for your call center. 


Proxy Server to use with a OneSight Voice Watch monitor for your 

call center. 




Voice Watch monitor. You can also configure how an alert will 

affect the monitor group’s health. It can result in a Warning state, a 

Critical state, or can have no impact on health. 








this monitor. 
















To create a OneSight Voice Watch monitor: 


dialog box. 



Watch to add a monitor that checks the availability and 

responsiveness of a selected monitor from the OneSight Voice 

Watch service. 

You will use settings on the General tab to configure a 

OneSight Voice Watch monitor. 



User ID – Type the User ID of your OneSight Voice Watch 

service account. 

Password – Type the password of your OneSight Voice Watch 


Server – Enter the name or IP address of the OneSight Voice 

Watch server. 

Get Voice Watch Monitors – After you provide the account 

information (User ID, Password), click Get Voice Watch 

Monitors to retrieve the active monitors configured in your 

OneSight Voice Watch service account. If you have previously 

specified this account information, these monitors will be 

retrieved automatically. 

Monitors – After you click Get Voice Watch Monitors, the active 

monitors configured in your OneSight Voice Watch service 

account will be displayed in this list box. 

Measurement – The steps available for the monitor are listed. 










Watch specifications you supply, or you can type in your own 



OneSight Voice Watch User ID. 



5. On the General tab in the Password box, type your OneSight 

Voice Watch password. 

6. Click Get Voice Watch Monitors. Using the login information 

you have specified, the active monitors configured in your 

OneSight Voice Watch service account are identified and listed 

here. If you have previously specified this account information, 

these monitors will be retrieved automatically. 

7. Select the monitor to use. 






save these basic OneSight Voice Watch monitor settings. You 

can now add this monitor to a monitor group. Refer to Adding 




Specifying Proxy Server Settings 

Use the Proxy tab to specify the proxy server settings. 

Proxy tab settings – Use the options on this tab to specify which 

elements should be used when checking page links, how you want 

to handle cookies, user agent options, and authentication settings. 




If you find that a OneSight Voice Watch monitor fails to reach a 





Configuring OneSight Voice Watch Profile Monitors 



configured for the OneSight Voice Watch monitor. 





Configuring OneSight Voice Watch Profile 

Monitors 

OneSight Voice Watch is Empirix’s hosted service that lets you 

monitor your call center in real time, using objective performance 

data gathered from points around the country. The service lets you 

monitor your call center performance from outside of your firewall. 

If you have a OneSight Voice Watch account, you can create a 

OneSight Voice Watch Profile monitor to provide external 

measurements of your telephony-based voice transaction systems 

and then correlate these measurements with the performance of 

internal systems. (See www.empirix.com for more information about 

the OneSight Voice Watch service.) 

The OneSight Voice Watch Profile monitor tests all of the steps in 

the script. Use the OneSight Voice Watch dedicated monitor if you 

are testing only one step in the script. 

The OneSight Voice Watch Profile Monitor retrieves data for the 

monitors you have configured within your OneSight Voice Watch 



Watch Profile in the Monitor Types box, settings to configure a 



OneSight Voice Watch Profile monitor appear on these dialog box 

tabs: 


OneSight Voice Watch Profile monitor for your call center. 


Proxy Server to use with a OneSight Voice Watch Profile monitor 

for your call center. 




Voice Watch Profile monitor. You can also configure how an alert 

will affect the monitor group’s health. It can result in a Warning 

state, a Critical state, or can have no impact on health. 













this monitor. 














this profile. 

Note: When you modify alerts for OneSight Voice Watch Profile 

monitors, you must select Override profile in the Alert Editor to make 

the fields available. Any changes that you make will apply to this 

monitor only, not to the profile itself. 

To create a OneSight Voice Watch profile monitor: 


dialog box. 



Watch Profile to add a monitor that checks the availability and 

responsiveness of a selected monitor from the OneSight Voice 

Watch service. 



You will use settings on the General tab to configure a 

OneSight Voice Watch Profile monitor. 

User ID – Type the User ID of your OneSight Voice Watch 


Password – Type the password of your OneSight Voice Watch 


Server – Enter the name or IP address of the OneSight Voice 

Watch server. 




Get Voice Watch Monitor – After you provide the account 

information (User ID, Password), click Get Voice Watch Monitor 



to retrieve the active monitors configured in your OneSight 

Voice Watch service account. If you have previously specified 

this account information, these monitors will be retrieved 

automatically. These monitors are displayed in the Select 

OneSight Voice Watch Monitor dialog box for selecting a 

monitor. 



Info – After you select a monitor, you can use this button to 

display the Selected OneSight Voice Watch Monitor 

Information dialog box. This dialog lists the monitor name and 

all of the steps in the script. 



Watch Profile specifications you supply, or you can type in 

your own name for the monitor. 


OneSight Voice Watch User ID. 

5. On the General tab in the Password box, type your OneSight 

Voice Watch password. 

6. Enter the name of IP address of the OneSight Voice Watch 

server. 

7. Click Get Voice Watch Monitor. Using the login information you 

have specified, the active monitors configured in your OneSight 

Voice Watch service account are identified and listed in the 

Select Voice Watch Monitor dialog box. If you have previously 

specified this account information, these monitors will be 

retrieved automatically. 



8. Select the monitor you want to use and click OK. The Script 

Steps dialog box is displayed. 

9. For each step, select the units you want OneSight to use to 

evaluate the script and click OK. 






save these basic OneSight Voice Watch Profile monitor 

settings. You can now add this monitor to a monitor group. 

Refer to Adding Monitors to a Monitor Group in Chapter 4. 



Specifying Proxy Server Settings 

Use the Proxy tab to specify the proxy server settings. 

Proxy tab settings – Use the options on this tab to specify which 

elements should be used when checking page links, how you want 

to handle cookies, user agent options, and authentication settings. 




If you find that a OneSight Voice Watch monitor fails to reach a 





Configuring Event Log Monitors 



configured for the OneSight Voice Watch monitor. 






You can set up an Event Log monitor to determine if the event log 

associated with a monitor group component, such as a web server, 

has information in the log that indicates a problem with your 


At specified time intervals, the Event Log monitor checks the event 

log. 

In the Add Monitor dialog box, when you click Event Log in the 

Monitor Types box, settings to configure an Event Log monitor 


General Tab – Contains the options that you can use to create an 

Event Log monitor for your monitor group. 

Metric Tab – Contains the options for specifying the type of metric. 

Alerts Tab – Displays the options that you can use to define alerts 

and associate them with action plans. You can also configure how 

an Event Log alert will affect the monitor group’s health. It can 

result in a Warning state, a Critical state, or can have no impact on 

health. 

















this monitor. 







To create an Event Log monitor: 


dialog box. 




can be applied to your monitor group. Click Event Log to add a 

monitor that will read your event log. 

Use the options on this tab to specify how the monitor will 

check an event log. 





System Identification – Specifies the system that has the event 

log. 

DNS Name – Specifies the name or IP address of the host that 

has the event log. 

NetBIOS Name – Specifies the NetBIOS name of the host that 

has the event log. 



Authentication – Specifies authentication information. These 

fields can be left blank if a OneSight Data Collector or Remote 

Agent is running on the system being monitored. Otherwise, the 

information is required, and if omitted, can result in the 

inability to find an appropriate agent for data collection. If you 

are monitoring a remote system that is running Windows 

2003/2008 and that does not have a Data Collector or Remote 

Agent running on it, you must authenticate with a domain, not 

directly with the machine. 

User Name – Specifies the user name. 

Domain – Specifies the domain. 

Password – Specifies the password. 

Note: Due to Microsoft Windows limitations, monitors that use 

NetBios (Windows) Authentication must use a single 

username/password combination. 

Event Log – Select whether the Windows event log that is being 

monitored is an Application, System, or Security event log. You 

can also specify a different type of log by typing its name here. 

Inactivity Sample Count – If the Event Log data source detects 

that the monitored event log does not log any new information 

for the number of sample counts you enter here, a sample 

failure will result. 




Alert Collection Mode – Select how you want alerts to be 

processed. 

Report Alerts as they Occur – If multiple alerts occur on the 

same trigger they are all sent. Alerts with the same timestamp 

as a previous alert will not be sent. 



Report First Alert Encountered for a Trigger – The first alert 

that occurs during a sample run for a specific trigger is the 

only one sent. Subsequent alerts for the same trigger are 

ignored. 

Report Last Alert Encountered for a Trigger – The last alert 


only one sent. Previous alerts for the same trigger are 

ignored. 

Report all Alerts for a Trigger as a bundle – Send all alerts that 

occur for a specific trigger during the sample run as one alert 

message. 






let OneSight create a unique name using the Event Log 



4. On the General tab, type in the DNS Name, specifying the name 

or IP address of the host that has the event log. 

5. Type in the NetBIOS Name. 

6. Enter authentication information if necessary. 

7. Specify the type of Event Log that is being monitored. 



8. On the Metric tab, select the type of metric you want to use. 


None – Checks to see if the monitor is operational. 



Number of Matching Records – Returns the number of records 

that match the specified criteria. 

Number of Records in Log – Returns the total number of 

records in the log. 





Time Since Last Modified – Returns the time since the log was 

last modified. 

The following additional fields are displayed when you select a 

metric type of Perl Expression or Number of Matching Records. 


results. 

Match if NT Even Source is – Filter based on NT event source. 

Separate multiple sources with a comma. 

Match if NT Event ID is – Filter based on NT event ID. You can 

enter one ID, multiple IDs separated by commas, or a range of 

IDs. For example, ―1‖ or ―1,2‖ or ―1,2,7-10‖ 

Match if Category is – Filter based on category. You can enter a 

list of strings or a list of number ranges separated by commas. 

Match if Username is – Filter based on Username. You can enter 

a list of strings separated by commas. 

NT Event Type – Select the type of NT event you want to 

monitor. If no type is selected, all event types are monitored. 


specifying string mappings. This button is only available when 

you select a metric type of Perl Expression. 


data. If you are measuring an NT event log response that is a 

string, it can be converted to a number for use in OneSight 

by using the String Mappings field. Simply specify a 

semicolon delimited mapping of Strings to Integers. For 

example, ―false=0;true=1‖; will convert a ―false‖ reading to 

a 0 value in OneSight, and this will be displayed in OneSight 

Status as ―false=0‖. If you only want to display the string on 

the OneSight status page, use a colon, rather than a semicolon 



Configuring FTP Monitors 








9. Enter additional criteria if you have selected Perl Expression or 

Number of Matching Records. 




be causing any problem. Note that the Test button for the Event 

Log Monitor will simply verify that the file exists. 


save these basic Event Log monitor settings. You can now add 

this monitor to a monitor group. Refer to Adding Monitors to a 



An FTP monitor verifies that an FTP server is working properly by 

connecting to it and retrieving a file. You can set up as many FTP 

monitors as you need to determine if your FTP servers are available 

and functioning correctly. 

At specified time intervals, the FTP monitor connects and logs into 

the FTP server, then retrieves the specified file and closes the 

connection. If any error occurs, the connection to the FTP server 

will be closed. 

If an error occurs, the FTP monitor will generate an alert. Some 

possible errors are: 



unknown host name 

unable to connect to server 

timeout 

login failed 

file not found 

In the Add Monitor dialog box, when you click FTP in the Monitor 

Types box, settings to configure an FTP monitor appear on these 


General tab – Contains the options that you can use to create an FTP 


Advanced tab – Contains options that you can use to configure 

advanced connection options, including use of a nonstandard port, 

an account, and passive mode. 

Alerts tab – Shows what action plan will be used when an alert 


plan that responds to alerts generated by the current FTP monitor. 



no impact on health. 


the FTP monitor will interact with a specified FTP server. 















this monitor. 




of the FTP server to which the monitor applies. To change the 

default assigned name, type a unique monitor name that helps you 

to identify what this monitor does. 

To create an FTP monitor: 


dialog box. 




can be applied to your monitor group. Click FTP to add a 

monitor that checks the availability and responsiveness of an 

FTP server. Use settings on the General tab to configure each 

FTP monitor. 

Use the options on this tab to specify how the FTP monitor will 

connect with an FTP server and GET a file. For case-sensitive 

servers, be sure to use the appropriate case when typing the 

values used to communicate with the FTP server. 





Server Address – Specifies the host name or IP address of the 

FTP server. 



When opening a connection, the server name you provide is 

resolved via the Hosts file or a domain name server. If you have 

no domain name server on the local network and do not use a 

Hosts file, you must specify the full IP address of the host FTP 

server. 

User Name – Specifies the name used to log in to the FTP 

server. This must be a valid user name registered on the FTP 

server. When opening an anonymous connection, the user name 

is usually ―anonymous.‖ 

Password – Specifies the password assigned to the specified 

user. Most anonymous FTP servers expect you to supply your e- 

mail address as the password. 

File Name – Specifies the name of the server file that you want 

the FTP monitor to retrieve. The specification should include 

the name of the server folder where the file is located (for 

example: /Maps/Antarctica.html). 

Timeout: Seconds – Specifies the maximum number of 

seconds to wait while trying to establish an FTP server 

connection or for data packets to be transferred from the host. 






the alert. 


the alert. 







and Advanced settings to determine if they are set 

appropriately. After clicking the Test button, you will see 

messages in the status window as the test runs and when the test 

completes. 


let OneSight create a unique name using the FTP specifications 


4. On the General tab, type in the server address of the FTP server 

that you want to monitor. For example: ftp.company.com 

5. Type in a known user name and password for the FTP server. If 

a specific user name and password combination is not known, 

try anonymous as the user name. An e-mail address is often the 

default password. 

6. Type the name of the server file that you want the FTP monitor 

to retrieve. The specification should include the name of the 

server folder where the file is located (for example: 

/Maps/Antarctica.html). 

7. By default, an FTP monitor will check the availability and 

responsiveness of the FTP server every 10 minutes and will time 

out after 120 seconds if the requested file is not found. If you 

want the monitor to sample more or less frequently, change the 

sampling interval. If you want to have the timeout occur earlier 

or later, change the Timeout setting. 






save these basic FTP monitor settings. You can now add this 





Configuring Advanced Options 

When you add an FTP monitor, the Advanced tab displays the 

options that you can use to configure advanced connection options, 

including use of a nonstandard port, an account, and passive mode. 

Account – Specifies the name of the account to log in to on the FTP 

server. Most servers do not require this information. 

When logging in, some servers require the name of the account that 

the user wants to access. For servers with this requirement, you 

cannot work with the files in that account until you supply an 

account name. If your server uses accounts as part of access control, 


Configuring LDAP Monitors 

type the name of the account you want to access. For case-sensitive 

servers, be sure to use the appropriate case when typing the account 

name. 

Typically, anonymous FTP servers do not request an account, so 

this setting can be omitted. When you connect to an FTP site with a 

defined account setting, the account name is sent to the server as the 

last step in the login process. 

Port – Specifies a standard or nonstandard TCP service port number 

or socket for FTP. The standard service port for FTP is 21. 

Use Passive Mode – Passive mode is required for connections 

through some firewalls. When selected, the FTP monitor will send a 

PASV command to communicate with the server in passive mode. A 

separate data connection will be initiated for file transfers. 


You can set up Lightweight Directory Access Protocol (LDAP) 

monitors to test the connection to an LDAP Server. The monitor 

returns the response time for connecting to the LDAP server and can 

optionally authenticate. 

In the Add Monitor dialog box, when you click LDAP in the 

Monitor Types box, settings to configure an LDAP monitor appear 

on these dialog box tabs: 


LDAP monitor for your monitor group. 


and associate them with action plans. You can also configure how a 

LDAP alert will affect the monitor group’s health. It can result in a 



the LDAP monitor checks the specified metric of a specific host. 















this monitor. 







To create an LDAP monitor: 


dialog box. 




can be applied to your monitor group. Click LDAP to add a 

monitor that confirms that a host is responding. Use settings on 

the General tab to configure each LDAP monitor. 

Host – Specify the host name or IP address of the LDAP Server. 

Port – Enter a port number if different from the default. 

Anonymous bind – When selected, the connection to the LDAP 

Server will be Anonymous Bind, otherwise, the connection will 

use simple LDAP authentication. 

Note: SSL and SASL authentication schemes are not available. 

User DN – Enter the distinguished name. 

Password – Enter the password. 



Compare Test (Optional) – Enter this information if you want to 

check to see if an entry contains an attribute with a specified 

value. 

Entry DN – Enter the distinguished name of the entry to use in 

the comparison. 

has attribute name – Enter the attribute to compare against 

the entry. 

with value – Enter the value to compare against the entry. 





let OneSight create a unique name using the LDAP 



4. Enter the host name or IP address of the host to monitor. 

5. Enter the port number if different from the default. 

6. Enter the User DN and password. 

7. Optionally enter comparison test information. 

8. Enter how often to sample. 






save these basic LDAP monitor settings. You can now add this 


Configuring Log File, Directory Monitors 




There are two types of monitors that can be configured: 

Log File 

Directory 

Log File Monitors 

You can set up a Log File monitor to determine if the log file 

associated with a monitor group component, such as a web server, 

has information in the error log that indicates a problem with your 

monitor group. Additionally, some applications publish 

performance data to a text log file, so the Log File Monitor also 

allows you to specify Perl expressions for collecting performance 

data from a log file entry. 

Note: OneSight also includes profile monitors for IIS and Apache 

web servers. These profile-based monitors use a set of preselected 

metrics and allow you to apply the same settings to multiple 

machines. 

At specified time intervals, the Log File monitor checks the log file 

and optionally checks for a particular content string within the log 

file. 

Note: After restarting OneSight, the Log File monitor does not look 

at historical data. 

Log file metrics can be configured in two operating modes: 

One line at a time mode – each line read from the file is treated as 

a single log file entry and is processed individually. 



Arbitrary record-based mode – a Perl expression is used to 

determine where each record in the file starts and ends. The 

expression is applied to the data as it is read, and records are 

picked out as they are found. Entries that exceed the specified 

maximum record size are ignored. 

Note: To use this monitor with a UNIX machine, the UNIX Remote 

Agent must be installed on the monitored machine. 

Directory Monitors 

You can monitor directory existence, size, or the number of files or 

folders in a directory. For metrics that apply to folders, you can 

select whether to return values on the directory and all 

subdirectories or only the topmost directory. 

Directory monitors are useful, for example, if you have an 

application that creates a log file every time it fails. You can count 

the number of files or folders in a directory and generate an alert if 

there were too many log files. 

In the Add Monitor dialog box, when you click Log File, Directory in 

the Monitor Types box, settings to configure a Log File, Directory 

monitor appear on these dialog box tabs: 

General Tab – Contains the options that you can use to create a Log 

File, Directory monitor for your monitor group. 



Log File, Directory alert will affect the monitor group’s health. It 

can result in a Warning state, a Critical state, or can have no impact 

on health. 















this monitor. 







To create a Log File, Directory monitor: 

Note: The Log File monitor requires a OneSight Data Collector or 

Remote Agent to be installed on the same machine as the file being 

monitored. 


dialog box. 




can be applied to your monitor group. Click Log File, Directory 

to add a monitor that will read your text log files for content 

string matches. 





Monitor Type – Specifies the type of monitor you want to create: 

Log File – Select this monitor type to monitor a log file. 

Directory – Select this monitor type to monitor a directory. 

Collector Host Name – Specifies the name or IP address of the 

machine where the log file or socket is being monitored. This is 

the machine that is running the data collector. 



File/Directory Name – Specifies the path to the log file or 

directory that you want to monitor. For example, 

c:\temp|mlog.txt. 

Metric Type – Select the type of metric. The metric types that 

are available depend on the type of monitor you are using: 

Log File Monitor 

Perl Expression – select this option when you want to use a 

Perl expression to collect numerical performance data from a 

log file entry. 

Number of Matching Records – this metric returns the number 

of records that match the entered Perl expression. 

File/Directory Existence – this metric returns a one when the 

file or directory exists, otherwise, it returns a sample failure. 

File/Directory Size – this metric returns the size of the file or 

directory. 

Total Records Encountered Since Last Sample – this metric 

returns the number of records written to the log file since the 

last sample. 

Time Since Last Modified – this metric returns the length of 

time since the log file was changed. 

Directory Monitor 

File/Directory Existence – this metric returns whether the file 

or directory exists. 

File/Directory Size – this metric returns the file or directory 

size. 

Number of Folders – this metric returns the number of folders 

in the directory. 



Number of Files – this metric returns the number of files in the 

directory. 


time since the directory was last modified. 

Perl Expression –Specifies a Perl Expression used to collect 

numerical performance data from a log file entry. The monitor 

checks the last entry whenever the log file changes. This 

returned data can then be used within OneSight, both for 

alerting, using threshold alerts, and reporting. 

To check whether the file exists, use the File/directory exits 

metric type and leave this field blank. 




data. If you are measuring a log file response that is a string, 

it can be converted to a number for use in OneSight by using 

the String Mappings field. Simply specify a semicolon 














Record Type – Specifies the operating mode: 



Each record is one line – select this option to use one line at a 

time operating mode. In this mode each line read from the 

file is treated as a single log file entry and is processed 

individually. 

PERL expression defines record – select this option to use 

arbitrary record-based mode. In this mode a Perl expression 

is used to determine where each record in the file starts and 

ends. The expression is applied to the data as it is read, and 

records are picked out as they are found. Entries that exceed 

the specified maximum record size are ignored. 

If you select Perl expression defines record, the following 

additional fields are displayed: 

Max Record Length – Enter the maximum record length. 

Entries that exceed this length are ignored. 

Record Format (PERL) – Enter the Perl expression defining 

the record, including the delimiter character. 

Unit Measure – Specifies the units to use when displaying the 

metric. 

Inactivity Sample Count – If the Log File data source detects that 

the monitored log file does not log any new information for the 

number of sample counts you enter here, a sample failure will 

result. 

File/Directory Must Exist – Select to check that the file/directory 

exists. 

Directory Range – Specify whether to monitor all directories 

including sub directories or to monitor only the top directory. 

This field applies to all metric types except File/Directory 

Existence monitors. 

Sample Continuously – Select to sample continuously. This field 

is only available when Metric Type is Perl Expression value. 







processed. 







ignored. 




ignored. 



message. 






let OneSight create a unique name using the Log File 



4. On the General tab, specify the type of monitor you want to 

create. 


Configuring Mail Monitors 

5. Enter the Collector Host Name, specifying the name or IP 

address of the host that has the log file to be monitored. 

6. Type in the File Name, specifying the name of the log file you 

want to monitor. 

7. Select the Metric Type. 

8. Type in a Perl Expression to collect performance data from a 

log file entry. If you want to verify that the file exists use the 

File/directory exists metric type and leave this field blank. 

9. On the Alerts tab, add your content string tests using the Pattern 

Match alert. If you have specified a Perl Expression to collect 

performance data, you can also add threshold alerts. 




be causing any problem. Note that the Test button for the Log 

File Monitor will simply verify that the file exists. 


save these basic Log File monitor settings. You can now add 




A Mail monitor verifies that the mail server is accepting requests 

and that e-mails can be sent and retrieved. You can set up as many 

Mail monitors as you need to determine if mail servers used by your 

monitor group are available and functioning correctly. 

At specified time intervals, the Mail monitor sends a standard e- 

mail message using SMTP and then retrieves that same message via 

a POP3 user account. Each e-mail that the Mail monitor sends 

includes a unique key that is checked to insure that the right e-mail 



is retrieved. If the Mail monitor is unable to send and receive the e- 

mail, it generates an alert. 

In the Add Monitor dialog box, when you click Mail in the Monitor 

Types box, settings to configure a Mail monitor appear on these 


General Tab – Contains the options that you can use to create a Mail 


Alerts Tab – Shows what action plan will be used when a Receive 

Mail Failure alert occurs. Options on this tab allow you to set up or 

modify an action plan that responds to Receive Mail Failure alerts 

generated by the current Mail monitor. You can also configure how 

a Receive Mail Failure alert will affect the monitor group’s health. 

It can result in a Warning state, a Critical state, or can have no 

impact on health. New alerts cannot be added to Mail monitors. 


the Mail monitor verifies the mail server is accepting requests and 

that e-mail messages can be sent and retrieved. 















this monitor. 




of the SMTP server to which the monitor applies. To change the 

default assigned name, type a unique monitor name that helps you 

to identify what this monitor does. 

To create a Mail monitor: 


dialog box. 


can be applied to your monitor group. Click Mail to add a 


Mail server. Use settings on the General tab to configure each 

Mail monitor. 



Use the options on this tab to define how often the Mail 

monitor should send a standard e-mail message using a specific 

SMTP server and then retrieve that same message via a 

specified POP3 user account. 

Send Test Message Using Settings – The options in this group 

box specify the server that you want to use to send a test 

message and the e-mail address to which the test message 

should be sent. 

Server (SMTP) – Type the fully qualified host name of the SMTP 





(outgoing) mail server to which the test mail message should 

be sent. You must specify the domain in the server name. For 

example: mailout.yourcompany.com. 

Port (SMTP) – The Mail monitor uses the standard SMTP port 

(25). If you use a nonstandard SMTP port, you can specify it 

here. 

From E-Mail Address – Type the mail address from which the 

test message will be sent (for example, 

mailtest@yourcompany.com). 

To E-Mail Address – Type the mail address to which the test 

message should be sent (for example, 

mailtest@yourcompany.com). This should be the address for the 

POP account that you specify in the Account Name box. 

This server (SMTP) requires authentication – Check this box if 

the server requires authentication. 

Account Name – Enter the account name. For example, 

defghi@gmail.com. 



Password – Enter the password for the account. 

This server requires a secure connection (SSL) –Select this 

checkbox if the server requires an encrypted connection. 

Wait For Seconds Before Checking – Specifies the amount 

of time (in seconds) to wait before attempting to retrieve the 

test message. If the test message is not received in this 

amount of time, the Mail test is retried. 

Check If Test Message Received On settings – The options in 

this group box specify the server and user account that you 

want to use to retrieve the test message. 

Server (POP) – Type the fully qualified host name of the POP 

mail server (incoming) that should receive the test message. 

You must specify the domain in the server name. For 

example: mailin.yourcompany.com. 

Port (POP) – The Mail monitor uses the standard POP port 

(110). If you use a nonstandard POP port, you can specify it 

here. 

Account Name – Type the name of the user account to which 

the test message will be sent (for example, mailtest). This 

should be the account name for the e-mail address that you 

specified in the E-Mail Address box. 

Password – Type the POP mail server password, if necessary, 

for the test mail account. 

This server requires a secure connection (SSL) –select this 

checkbox if the server requires an encrypted connection. The 

target email server must be using SSL and you must place the 

mail server trust certificate in the .keystore file in the Data 

Collector installation directory for all Data Collectors in this 

location. 








the alert. 


the alert. 




Retries – Sets the upper limit for the number of times a Mail 

test is retried. For example, if Retries is set to 3, the Mail 

message will be sent up to four times (the initial try plus three 

retries). After the fourth try, if no response is received, the Mail 

check is treated as a sample failure. 




the test runs and when the test completes. If you see a 501 

(syntax error) message, there may be a problem with your 

OneSight server name. 


let OneSight create a unique name, or you can type in your own 


4. On the General tab, type in the SMTP server address of the mail 

server that you want to monitor. For example: 

smtphost.company.com 

5. Type the mail address to which the test message should be sent 

(for example, mailtest@yourcompany.com). This should be the 



address for the POP account that you specify later in the 

Account Name box. 

6. In the Wait For box, enter the amount of time (in seconds) to 

wait before attempting to retrieve the test message. 

7. In the Server (POP) box, type the fully qualified host name of 

the POP mail server (incoming) that should receive the test 

message. You must specify the domain in the server name. For 

example: mailin.yourcompany.com 

8. In the Account Name box, type the name of the user account to 

which the test message will be sent (for example, mailtest). 

This should be the account name for the e-mail address that you 

specified in the E-mail Address box. 

9. Type the POP mail server password, if necessary, for the test 

mail account. 

10. By default, a Mail monitor will check the availability of the 

mail server every 10 minutes. 

The Retries box sets the upper limit for the number of times a 

mail test is retried. For example, if Retries is set to 3, the mail 

message will be sent up to four times (the initial try plus three 

retries). After the fourth try, if no response is received, the mail 

check is treated as a sample failure. 




be causing any problem. If you see a 501 (invalid syntax error), 

you may have a problem with your OneSight server name. 




save these basic mail monitor settings. You can now add this 



Validating E-Mail Connections 

E-mail servers that check the host name using RFC 810 will not 

accept connections to machines with a name containing an 

underscore. If the machine name of the OneSight server includes an 

underscore, you may have problems associated with e-mail servers 

under the following conditions: 

If you change the default mail server specification in the Global 

Action Options dialog box. 

If you configure a Mail monitor for an e-mail server that enforces 

RFC 810. 

Most e-mail servers do not enforce this RFC. To check for this 

problem on OneSight servers with names that include an 

underscore: 

Test your Mail monitor when you create it. 

Test your e-mail action when you create it. 

SMTP daemons that do not accept this host name return a 501 

(syntax error) message when a connection is attempted. If you see 

an error of this type, you can reconfigure the monitored component 

or the e-mail server or you can install OneSight on a machine that 

has a name without an underscore. 

RFC 810 states that the host name must be ―text string up to 24 

characters drawn from the alphabet (A-Z), digits (0-9), and the 

minus sign (-) and period (.). No blank or space characters are 

permitted as part of a name. No distinction is made between upper 


Configuring Oracle OpenScript Profile Monitors 

and lower case. The first character must be a letter. The last 

character must not be a minus sign or period.‖ 


You can set up an Oracle OpenScript profile monitor to replay your 

scripts previously recorded in Oracle OpenScript and exported as a 

.zip file. OneSight supports functional testing for web and load 

testing for web/http script types. 

Note: The Oracle OpenScript monitor requires the installation of the 

OneSight Data Collector for Windows on the host machine running 

OpenScript. In addition, OpenScript must be installed on all data 

collector locations that are assigned to the monitor. 

Note: Only one functional web test can be run on a data collector at 

one time. 

At specified time intervals, the Oracle OpenScirpt profile monitor 

replays an OpenScript Script and measures its response time. 

In the Add Monitor dialog box, when you click Oracle OpenScript 

in the Monitor Types box, settings to configure an Oracle 

OpenScript monitor appear on these dialog box tabs: 


Oracle OpenScript monitor for your monitor group. 

Advanced Tab – Lets you enter the parameters to use for running 

OpenScript scripts from the command line. 

Proxy Tab – Displays the authentication data that was imported from 

OpenScript when the script was imported. This information is used 

for web sites that require login via a popup dialog box. The 

authentication data automates the login process during script 

playback. 





an Oracle OpenScript alert will affect the monitor group’s health. It 

can result in a Warning state, a Critical state, or can have no impact 

on health. 

You can modify alerts for all Oracle OpenScript monitors by 

modify the Oracle OpenScript profile or you can modify individual 

alerts for a specific monitor by clicking the Alert button on the 

Alerts tab. 

Locations Tab – Specifies the Data Collector Location to use as an 

Oracle OpenScript monitor for your monitor group. 











this monitor. 














this profile. 

Note: When you modify alerts for Oracle OpenScript profile 

monitors, you must select Override profile in the Alert Editor to make 

the fields available. Any changes that you make will apply to this 

monitor only, not to the profile itself. 

1. Click Add in the Monitors Page. The Monitor Types box lists 

all of the types of monitors that can be applied to your monitor 

group. Click Oracle OpenScript. You will use the settings on the 

General Tab to configure the Oracle OpenScript Monitor. 




Script – Displays the name of the script associated with this 

monitor and buttons to import, export, or view properties of the 

Script associated with this monitor. 

Note: It is recommended that the last step in your script is to 

close the browser window to ensure that processes are not left 

open. You can do this either by closing the browser window 

before you stop recording the script or using the right-click 

menu in Oracle OpenScript to add the close browser step. To do 

this, select Add from the right-click menu, select Other, expand 

the browser folder in the tree, and select Close Browser. 

Import – Opens a dialog box for selecting the OpenScript 

Script to import into the OneSight database. The imported 

file must be an Oracle OpenScript .zip file exported from 

OpenScript. This file contains all of the files necessary to run 

the script and can be located anywhere. 

Export – Opens a dialog box for specifying the location 

where you want to export the Script. This button is only 

available when you are modifying a monitor. 

Info – Displays the Script Import Information dialog box 

showing the name of the script and the date it was imported. 

When you have reimported a script, this dialog box also 

displays unmatched pages. 

Pages are matched when both the ordinal and name in the 

reimported script match those in the previously imported 

script. Pages can become unmatched when you add, insert, 

rename, or delete pages in the script in OpenScript. History is 

not available for unmatched scripts. 

For example, if the original script had the following pages: 

[1](/www.google.com) 



[2] Empirix 

[3] Empirix - Products 

And a second login page is added so that the new script has 

the following pages: 

[1](/www.google.com) 

[2] Empirix 

[3] Empirix - Company 

[4] Empirix - Products 

The Empirix – Products page has a different ordinal so it is 

considered unmatched. 

Playback Settings – lets you configure the following options for 

determining how the script is played back. 

Browser Type – This field is only displayed when you have 

imported a script for a functional test. Select the browser type that 

you want to use, either Internet Explorer or Firefox. 

Show/Hide – These buttons are only displayed when the browser 

type is Internet Explorer. It is recommended that you select hide to 

hide the browser during playback. If certain actions in the script 

require the browser to be visible, such as key presses and physical 

mouse clicks, the script will not play back correctly. 

Sample Every: Advanced – Specifies how often 

samples are taken for this monitor. Sample frequency for 

Oracle OpenScript monitors apply to the entire transaction, 

that is, you cannot run one page at a different sample 

frequency than another. This means that alerts should be 

configured at the script level. Refer to, ―Sample Every 

Settings,‖ later in this chapter for a description of these 

settings. 

Timeout Every – Specifies how long the OneSight 

agent should wait for the Oracle OpenScript agent to indicate 



that playback has finished before timing out. Select the unit 

of time: seconds, minutes, or hours. 

Retries – Specifies the number of times to retry running the 

Script before triggering a response plan or reporting a failure 

on the status page. Retries are triggered by the Oracle 

OpenScript alerts that affect the monitor availability. The 

alerts that affect availability are: 

OpenScript Transaction Failure 

Navigation Failure 

Slow Page 

Acquisition Failure 

When a retry is triggered, the entire script is replayed 

immediately. The status page displays a blue triangle icon 

with a plus sign (+) beside it indicating that a retry is 

happening. 

Save Diagnostic Data – lets you select the following options for 

collecting data. 

Save HTML from failing runs* – When selected, the HTML 

source from the last failure is saved for viewing. When you 

view the Status details for the Transaction Monitor, the Last 

Measured column includes a link icon ( ). Click the icon to 

open the retained HTML in the browser. Note that the 

retained HTML does not show page images. 

Save HTML from successful runs* – When selected, the HTML 

source from the last successful Script play back is saved for 

viewing. When you view the Status details for the 

Transaction Monitor, the Last Measured column includes a 

link icon ( ). Click the icon to open the retained HTML in 

the browser. Note that the retained HTML does not show 

page images. 

*The Save HTML from failing runs and Save HTML from 

successful runs options both work with the HTML from failing 

runs and HTML from successful runs option settings in the 



Database storage configuration. When a check box in this form 

is selected, the database will always save the HTML from the 

last failure/successful run—even beyond the time frame 

specified in the corresponding settings in the Database storage 

configuration. If there are multiple failures/successful runs, the 

HTML for runs prior to the last run is saved for as long as 

specified in the Database storage configuration settings. 

2. Click Import to import the OpenScript Script to use with this 

monitor. 

Script – Select the name of the Oracle OpenScript script you 

want to monitor or click the Browse button to locate it. The 

script file must be an Oracle OpenScript .zip file. This file 

contains all of the files necessary to run the script and can be 

located anywhere. 

3. Enter the script path or click Browse to locate the script. 

4. Click OK to import the script. 

5. Specify the properties to use for the transaction monitor: 

Specify the sampling interval. 

Specify the timeout value. 

Specify the number of retries. 

Select options for retaining HTML. 





Exporting Scripts 



7. If the test succeeds, click OK. If you are reimporting a script, 

and page names or ordinals have changed, the Confirm History 

Deletion dialog box is displayed. 

8. Click OK to delete history for the pages that are no longer 

present. Click Cancel to revert to the original script. 

Click the Export button to Export Oracle OpenScript Scripts from 

the OneSight Database. This option is only available when you are 

modifying a monitor. To export a script: 

1. Click Export. The File Download dialog box is displayed. 

2. Click Save. The Save As dialog box is displayed. 

3. Select the folder in which to export the script. 

4. Click Save. 



Setting Command Line Options 

Use the Advanced tab to specify the parameters for running 

OpenScript scripts from the command line. 

Enter the parameters for running OpenScript from the command 

line in the following format: 

-parameter value 

For example, -http.proxyHost hostname 

Refer to the OpenScript User Guide for information about 

OpenScript parameters. Incorrectly entered parameters can cause an 

OpenScript failure. In addition, parameters that are used by 

OneSight to run the script or that can be configured on the General 

tab should not be entered here. OneSight will display a message 

requesting that they be removed from this dialog box. 



Specifying Proxy Settings 

Use the Proxy tab to specify proxy server settings. 

Proxy Server Settings – If your network makes use of a proxy server, you 

can specify this information here. Check Use a proxy server and add the 

information below. 

If you find that a OneSight OpenScript monitor fails to reach a URL 

when your browser successfully connects to the same URL, check your 

proxy server settings in your browser. For example, in Internet Explorer, 

select Internet Options from the Tools menu and then click LAN settings 

on the Connections tab. If proxy server settings are configured for your 

browser, they may also need to be configured for the monitor. 

Use a proxy server – When selected, OneSight uses the specified 

proxy server for this monitor. 


Configuring Oracle Test for Web Applications Monitors 

Host – The name or IP address of the proxy server. 


User Name – The proxy server login user name. 

Password – The proxy server login password. 

Configuring Oracle Test for Web Applications 

Monitors 

You can set up an Oracle Test for Web Applications monitor to 

replay your Visual Scripts previously recorded in Empirix e-Tester 

and saved as e-Manager Enterprise Package (.emePKG) files or 

Visual Scripts previously recording in OATS (Oracle Application 

Testing Suite) and saved as an OATS .otmpkg files. 

With e-Tester and OATS, you can record and test your entire 

application in minutes with reusable, object-oriented Visual Scripts. 

Recorded Visual Scripts automatically capture and test Anchors, 

Elements, Forms, Frames, HTML, Images, Image Maps, Links, 

ActiveX controls, Java Applets, VBScript, and JavaScript. Visual 

Scripts offer the fastest and easiest way to define tests for Web 

transactions. 

Note: The Oracle Test for Web applications monitor requires the 

installation of the OneSight Data Collector for Windows on the host 

machine running e-Tester or OATS. In addition, e-Tester or OATS 

must be installed on all data collector locations that are assigned to 

the monitor. 

At specified time intervals, the Oracle Test for Web Application 

monitor replays a Visual Script and measures the response time of 

the Visual Script. In the monitor configuration, you specify the host 

machine that contains your previously recorded Visual Scripts. The 

OneSight Data Collector for Windows must also be running on the 

specified host machine, since it is the data collector that manages 



the connection between the Visual Script playback engine and the 

OneSight server. 

In the Add Monitor dialog box, when you click Oracle Test for Web 

Applications in the Monitor Types box, settings to configure an 

Oracle Test for Web Applications monitor appear on these dialog 

box tabs: 


Oracle Test for Web Applications monitor for your monitor group. 

Authentication Tab – Displays the authentication data that was 

imported from e-Tester or OATS when the script was imported. This 

information is used for web sites that require login via a popup 

dialog box. The authentication data automates the login process 

during script playback. 



an Oracle Test for Web Applications alert will affect the monitor 

group’s health. It can result in a Warning state, a Critical state, or 

can have no impact on health. 

You can modify alerts for Oracle Test for Web Applications 

monitors by modify the Empirix e-TEST transaction profile or you 

can modify individual alerts for a specific monitor by clicking the 

Alert button on the Alerts tab. 

Locations Tab – Specifies the Data Collector Location to use as an 

Oracle Test for Web Applications monitor for your monitor group. 













this monitor. 












this profile. 

Note: When you modify alerts for Oracle Test for Web Applications 

Profile monitors, you must select Override profile in the Alert Editor 

to make the fields available. Any changes that you make will apply 

to this monitor only, not to the profile itself. 

If you are using a Visual Script that uses client certificates, the 

script may not play in OneSight. This occurs because the certificate 

is associated with the logged in user, therefore, the OneSight Data 

Collector service must also be associated with the user. To associate 

the Data collector service with the logged in user: 

1. Select Start Settings Control Panel Administrative Tools 

Services. 



2. Open the OneSight Data Collector service. 

3. Click the Logon tab. 

4. Select This account in the Log on as section. 

5. Enter the user name and password of the user associated with 

the certificate. 

6. Click OK. 

7. Restart the OneSight Data Collector service. 

To create an Oracle Test for Web Applications Monitor: 

1. Click Add in the Monitors Page. The Monitor Types box lists 

all of the types of monitors that can be applied to your monitor 

group. Click Oracle Test for Web Applications. You will use the 

settings on the General Tab to configure the Oracle Test for 

Web Applications Monitor. 




Visual Script – Displays the name of the script associated with 

this monitor and buttons to import, export, or view properties of 

the Visual Script associated with this monitor. 

Note: OATS version 8.4 or later no longer supports test 

scriptlets. 

Import – Opens a dialog box for selecting the Visual Script to 

import into the OneSight database. The imported file must be 

an e-Manager Enterprise Package (.emePKG) file or an 

OATS.otmpkg file and must be the same version of e-Tester or 

OATS as the version of the software on which it will be run. 

This file contains all of the files necessary to run the script 

and can be located anywhere. 

Export – Opens a dialog box for specifying the location 

where you want to export the Visual Script. 

Info – Displays the Script Import Information dialog box 

showing the name of the script as well as the date it was 

imported. When you have reimported a script, this dialog box 

also displays unmatched pages. 

Pages are matched when both the ordinal and name in the 

reimported script match those in the previously imported 

script. Pages can become unmatched when you add, insert, 

rename, or delete pages in the script in e-Tester or OATS. 

History is not available for unmatched scripts. 

For example, if the original script had the following pages: 

[1]Login 

[2]Welcome 

[3]Register 

And a second login page is added so that the new script has 



the following pages: 

[1]Login 

[2]LoginTwo 

[3]Welcome 

[4]Register 

The Welcome and Register pages have different ordinals so 

they are considered unmatched. 

Playback Settings – lets you configure the following options for 

determining how the script is played back. 

Browser Type – Specifies the type of browser control to use 

when running the Visual Script. Select one of the following: 

Thick – Thick Client mode. The virtual users run 

using full browser capabilities. This mode requires 

more resources and is less scalable than Thin Client, 

and should only be used in special cases. Reasons 

for using Thick client may include Web pages that 

require large amounts of client side processing. 

Thin – Thin Client mode. A less resource intensive 

method that provides a high level of Web 

compatibility and Visual Script verification. Thin 

Client mode consumes fewer system resources per 

process than Thick Client, and is able to run more 

virtual users on a given agent workstation. 

Java Agent – A highly scalable version of the Thin 

Client that executes the e-Tester script in native Java 

code. This agent provides a flexible code interface 

for performing customized scripting operations. 

Use WinInet – This option is only available for Thin agent. Runs 

the script using the Microsoft Win32 Internet (WinInet) 

application programming interface version of the Thin Client 

Agent. 



Use JHTTP – Runs the script using the Empirix version of the 

Thin Client agent (JHTTP). 

Use Databank – When selected, the Visual Script plays back 

using any Data Bank connected to the Visual Script. Data 

Banks are used to hold unlimited amounts of input data that 

can be automatically fed into your script. During Visual 

Script playback, the parameters in the Web page are filled 

with values from the Data Bank file. 

If you want to use the databank feature, select the Use 

Databank check box. When selected, the Visual Script plays 

back using a single data bank record. The record is 

determined by the record pointer of the Data Bank Wizard. 

The record increments after each iteration of the Visual 

Script. 

Download Images – When selected, images, scripts, and style 

sheets in the Web pages recorded to the Visual Script are 

downloaded during play back of the script. Downloading of 

these items affects the overall page response time. However, 

individual download times are not stored or shown as part of 

the monitor status or reporting data. 


taken for this monitor. Sample frequency for Oracle Test for 

Web Applications monitors apply to the entire transaction, 

that is, you cannot run one page at a different sample 

frequency than another. This means that alerts should be 

configured at the script level. Refer to, ―Sample Every 

Settings,‖ later in this chapter for a description of these 

settings. 

Timeout Every – Specifies how long the OneSight 

agent should wait for the e-TEST or OATS agent to indicate 

that playback has finished before timing out. Select the unit 

of time: seconds, minutes, or hours. The value for timeout 

should not be null or a decimal value. 



Retries – Specifies the number of times to retry running the 

Visual Script before triggering a response plan or reporting a 

failure on the status page. Retries are triggered by the Oracle 

Test for Web Applications alerts that affect the monitor 

availability. The alerts that affect availability are: 

Sample Failure 


Page Timeout 

Failure 

When a retry is triggered, the entire script is replayed 

immediately. The status page displays a blue triangle icon 

with a plus sign (+) beside it indicating that a retry is 

happening. 

Save Diagnostic Data – lets you select the following options for 

collecting data. 

Save object download details – When selected, componentlevel 

metrics are collected for individual objects on a page 

and the Object Timer report is enabled. 

Save HTML from failing runs* – When selected, the HTML 

source from the last failure is saved for viewing. When you 

view the Status details for the Transaction Monitor, the Last 

Measured column includes a link icon ( ). Click the icon to 

open the retained HTML in the browser. Note that the 

retained HTML does not show page images. 

Save HTML from successful runs* – When selected, the HTML 

source from the last successful Visual Script play back is 

saved for viewing. When you view the Status details for the 

Transaction Monitor, the Last Measured column includes a 

link icon ( ). Click the icon to open the retained HTML in 

the browser. Note that the retained HTML does not show 

page images. 

*The Save HTML from failing runs and Save HTML from 

successful runs options both work with the HTML from failing 



runs and HTML from successful runs option settings in the 

Database storage configuration. When a check box in this form 

is selected, the database will always save the HTML from the 

last failure/successful run—even beyond the time frame 

specified in the corresponding settings in the Database storage 

configuration. If there are multiple failures/successful runs, the 

HTML for runs prior to the last run is saved for as long as 

specified in the Database storage configuration settings. 

2. Click Import to import the Visual Script to use with this 

monitor. 

Script – Select the name of the script you want to monitor or 

click the Browse button to locate it. The script file must be an 

e-Manager Enterprise Package (.emePKG) file or an OATS 

.otmpkg file. This file contains all of the files necessary to run 

the script and can be located anywhere. 

3. Enter the script path or click Browse to locate the script. 

4. Click OK to import the Visual Script and its authentication data 

into the OneSight database. 

5. Specify the properties to use for the transaction monitor: 

Specify the number of retries. 

Specify the sampling interval. 



Exporting Scripts 

Specify the timeout value. The value for timeout should not 

be null or a decimal value. 

Specify the browser type. 

Select other playback options for databanks, download 

images, save object details, and retain HTML. 





7. If the test succeeds, click OK. If you are reimporting a script, 

and page names or ordinals have changed, the Confirm History 

Deletion dialog box is displayed. 

8. Click OK to delete history for the pages that are no longer 

present. Click Cancel to revert to the original script. 

9. Specify the alert options for the dedicated transaction monitor: 

Set up an action plan to notify you if the transaction fails. 

Set up a threshold-based alert. 

Click the Export button to Export Visual Scripts from the OneSight 

Database. To export a script: 


2. Click Save. The Save As dialog box is displayed. 

3. Select the folder in which to export the script. 




Specifying Authentication Data 

Authentication data for web sites that use popup login dialog boxes 

is imported when you import Visual Scripts. OneSight imports the 

entire set of authentication information, which is shared by all 

scripts in e-TEST or OATS. You can remove realms that are not 

accessed by an individual transaction; however, it is not necessary. 

Use the options on the Authentication tab to modify login data for 

individual transactions. 

Note: To modify password information for all transactions that use a 

given realm/username combination, use the Configure Password 

page. 

Realm – Displays the full Uniform Resource Locator (URL) for the 

Web application that requires a user name and password. 

Username – Displays the username for corresponding URL. 


Configuring Perfmon Monitors 

Add – Displays the Add Realm dialog box for adding a realm. 

Modify – Displays a dialog box for modifying the selected realm. 

Remove – Deletes the selected realm. 


Note: OneSight also includes profile monitors for Windows. This 

profile-based monitor uses a set of preselected metrics and allow 

you to apply the same settings to multiple machines. 

A Perfmon monitor checks on the performance of a specific 

Perfmon metric on a single machine. The monitor must have 

appropriate privileges to access the Perfmon statistics on the 

monitored machine. 

Note: The Perfmon monitor requires a Data Collector or Remote 

Agent that is version 5.1 or higher to discover metrics. 

Monitoring Multiple Processes With the Same Name 

Processes with the same name cannot be distinguished from one 

another in the Instance dropdown. For OneSight PerfMon to 

distinguish processes with multiple instances the following registry 

change must be made: 

1. Click Run from the Start menu. 

2. Enter regedit and click OK. 

3. Locate and then click the following registry subkey: 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfP 

roc\Performance 

4. On the Edit menu click New, and then click DWORD Value. 



5. Right-click New Value #1, click Rename, and then type 

ProcessNameFormat to name the new value. 

6. Right-click ProcessNameFormat, and then click Modify. 

7. In the Data value box, enter 2 (which Enables PID data) and 

click OK. 

8. Exit the Registry Editor. 

Creating the Monitor 

Warning: Serious problems can occur if you modify the registry 

incorrectly. These problems might require the operating system 

to be reinstalled. Modify the registry at your own risk. 


In the Add Monitor dialog box, when you click Perfmon in the 

Monitor Types box, settings to configure a Perfmon monitor appear 


System Tab – Contains the options that you can use to define the 

system identification and authentication settings for a Perfmon 


Object Tab – Specifies the object configuration for a specific 

Perfmon Metric. 



Perfmon alert will affect the monitor group’s health. It can result in 

a Warning state, a Critical state, or can have no impact on health. 


the Perfmon monitor checks a specific metric. 















this monitor. 




of the host and the Perfmon metric. To change the default assigned 

name, type a unique monitor name that helps you to identify what 

this monitor does. 

To create a Perfmon monitor: 


dialog box. 




can be applied to your monitor group. Click Perfmon to add a 

monitor that will measure the performance of a specific 

Perfmon metric on a single machine. 

Use the options on this tab to specify the Windows machine to 

be monitored. 





System Identification – Configure these settings to specify the 

Windows machine that will report the Perfmon metric. 

DNS Name – Specifies the DNS name of the computer. 

NetBIOS name – Specifies the NetBIOS name, or Windows 

computer name, for this machine. 



Authentication – Configure these settings when a OneSight Data 

Collector or Remote Agent is not running on the system being 

monitored. If you are monitoring a remote system that is 

running Windows Server 2003 or newer addition, and that does 

not have a Data Collector or Remote Agent running on it, you 

must use the same user name and password for all monitors on 

a given system. Otherwise, your monitor may fail to connect to 

the OneSight Server. 

User Name – Specifies the logon name that will provide 

access to the monitored machine. The user name and 

password that you specify must have administrative 

privileges on the monitored machine. 

Domain – Specifies the domain or machine name of the user 

name account. 

Password – Specifies the password associated with the user 

name you supply. The user name and password that you 

specify must have administrative privileges on the monitored 

machine. 

Test – When you add or modify a monitor, you can test System 





let OneSight create a unique name using the Perfmon 





4. On the System tab, type in the DNS name, NetBIOS name, user 

name, password, and domain of the machine you want to 

monitor. If you have a OneSight Data Collector or Remote 

Agent installed on the machine you want to monitor, the 

authentication information (Username, Password, and Domain) 

is not required. Click the Object tab. 

Use the options on this tab to specify the Perfmon metric to be 

monitored. 

Use these settings to designate which Perfmon metric you want 

to check. To complete this information, click Discover Perfmon 

Metrics to find available metrics and populate the Object, 

Counter, and Instance dropdown lists. 

Note: Occasionally the Data Collector will not be able to 

discover all metrics on the local machine on which it is 



installed. This is because the data collector runs as the local 

system account and some counters cannot be collected unless 

the Data Collector is set up to run as either the same user or a 

user with administrative rights. 

You can also run Perfmon on the machine you plan to monitor. 

To review individual metrics, select Add Counters from the 

right-click shortcut menu in Perfmon. 

Note: Although the Perfmon application on your local machine 

can provide some guidance, Perfmon metrics can differ among 

various Windows versions, and Perfmon metrics for specific 

applications such as IIS may not be present on your local 

machine. 

Note: Even if you add the.NET CLR Data object SqlClient 

counters will not be collected because this object is not 

supported by Perfmon itself on Windows servers. 

Object – Specifies the Perfmon Object name (for example, 

Processor or Memory). Select or enter the object name. You 

must enter the object name exactly as it is displayed in the 

Perfmon editor. Be careful to check for spaces and case in the 

Object name. 

Counter – Specifies the Perfmon Counter name (for example, % 

Processor Time). Select or enter the counter name. You must 

enter the counter name exactly as it is displayed in the Perfmon 

editor. Be careful to check for spaces and case in the Counter 

name. 

Instance – If the Perfmon metric has an instance associated with 

it, specify or select it here. For example, if you see 0 as the 

instance in the Perfmon metric, type in 0 as the value. If no 

instance is listed, leave this blank. 

Note: LogicalDisk objects may include instances such as 0 => 

C: that reflect a distinction between logical and physical disks. 

In this case, specify C: as the instance. 



Scale – Specifies any custom scaling to be applied to the 

Perfmon metric when reported within OneSight. Typically, the 

default 1.0 scale is appropriate. 

Translation Type – Translation Type controls how a metric’s 

data is displayed on the Alerts page and in Reports. 

No Translation – OneSight will present the data as it is 

provided by the metric’s data source. 

Rate (minutes) – OneSight will present the data as a number, 

per minute. For example, if the time interval between two 

samples was 10 minutes, and 50 errors were found, the Rate 

(minutes) would be five (5) errors per minute. 

Note: Rate (minutes) translates data sources that return their 

values as an endlessly increasing counter. If the data source 

does not return data this way, use No Translation. 

Unit Measure – Select which unit of measurement should be 

associated with this metric and displayed in OneSight Alerts 

and Reports. 

% (percent) – As a percentage 

bytes – this data will be expressed in bytes 

hours – this data will be expressed in hours 

minutes – this data will be expressed in minutes 

seconds – this data will be expressed in seconds 

– this data will be expressed with no unit of 

measurement 






Retries – Sets the upper limit for the number of times a Perfmon 

request is retried. For example, if Retries is set to 3, the 

Perfmon request will be sent up to four times (the initial try 

plus three retries). 

Time Out – Specifies the amount of time (in seconds) to wait for 

a Perfmon reply. If Retries is greater than 0 and a reply is not 

received, a retry attempt is made. For each subsequent retry, the 

timeout value is doubled. For example, if Time Out is 5 and 

Retries is 2, the first request attempt will occur after 5 seconds, 

the second attempt will occur after 10 seconds, and the third 

attempt will occur after 20 seconds. In this example, the total 

timeout period equals 35 seconds. If there is no response after 

this time, a Sample Failure is triggered. 

If Retries is 0, a Sample Failure is triggered when a reply is not 

received in this amount of time. 

Discover Perfmon Metrics – Finds the available metrics and 

populates the Object, Counter, and Instance dropdown lists so that 

you can select the metric you want to monitor. 

5. On the Object tab, use the settings to designate which Perfmon 

metric you want to check. To complete this information, click 

Discover Perfmon Metrics to find available metrics and populate 

the Object, Counter, and Instance dropdown lists. Or run Perfmon 

on the machine you plan to monitor. To review individual 

metrics, select Add to Chart from the Edit menu in Perfmon. 

Note: Although the Perfmon application on your local machine 

can provide some guidance, Perfmon metrics can differ for 

Windows 2000 and 2003 machines, and Perfmon metrics for 

specific applications such as IIS may not be present on your 

local machine. 

6. On the Object tab, select or type in the Perfmon Object, 

Counter, and Instance name. 


Configuring Ping Monitors 

7. On the Object tab, modify the metric translation type and 

sampling parameters as needed. For more information on these 

parameters, see the System Tab description. 






save these basic Perfmon monitor settings. You can now add 




You can set up Ping monitors to determine if hosts used by your 

monitor group are functioning. Ping is an easy way to confirm that a 

host is responding. The Ping monitor sends a Ping request at 

specified time intervals to confirm whether a particular host is 

operational. 

At specified time intervals, the Ping monitor sends an echo request 

to a specified host and waits for a reply. The monitor returns the 

round trip time or sets an alert if the request times out or exceeds a 

threshold. 

In the Add Monitor dialog box, when you click Ping in the Monitor 

Types box, settings to configure a Ping monitor appear on these 


General Tab – Contains the options that you can use to create a Ping 




Ping alert will affect the monitor group’s health. It can result in a 





the Ping monitor checks the availability of a specific host. 













this monitor. 







To create a Ping monitor: 


dialog box. 




can be applied to your monitor group. Click Ping to add a 

monitor that confirms that a host is responding. Use settings on 

the General tab to configure each Ping monitor. 

Use the options on this tab to specify how the Ping monitor will 

make Ping attempts. 





Host Name – Specifies the name or IP address of the host to 

ping. 

Metric – Specifies the metric to use for the Ping monitor. Select 

the metric to use: Average Round Trip Time or Percentage of 

Success. 



Length – Enter the number of bytes that should be included in 

each echo request packet. 

Time to Live – Specify the maximum number of router hops 

permitted. If the echo request takes more than the maximum 

number of hops, it is thrown away and the Ping attempt is 

treated as a failure. 

Timeout (sec) – Specifies the number of seconds to wait for an 

echo reply. The value must be between 1 and 30, inclusive. If 

an echo reply is not received in this amount of time, the Ping 

echo request is retried. 

# of Packets – Specifies how many packets should be included 

in Ping echo requests. This can be used with the Percentage of 

Success metric to specify a threshold. 






the alert. 


the alert. 









Configuring Port Monitors 


let OneSight create a unique name using the Ping specifications 


4. On the General tab, type in the host name for the server you 

want to monitor. This value specifies the name or IP address of 

the host to ping. 

5. All the other settings in the Ping monitor have defaults that will 

allow you to start using a Ping monitor. You can change 

defaults for any of the other settings. 






save these basic Ping monitor settings. You can now add this 




A Port monitor checks on the availability of a specified network 

port. While checking network port availability, the port monitor can 

also check the value returned from a query to ensure that an 

application is available and running correctly. If a port does not 

reply, or if the reply is incorrect (as determined by a text match), an 

alert is triggered. The Port monitor can be used to monitor network 

applications that are not available as part of other OneSight 

monitors. 

The monitor must have appropriate privileges to access the 

specified port on the monitored machine. 



In the Add Monitor dialog box, when you click Port in the Monitor 

Types box, settings to configure a Port monitor appear on these 


General Tab – Contains the options that you can use to create a Port 


Advanced Tab – Contains the options that you can use to specify 

what string should be returned from your query. 



Port alert will affect the monitor group’s health. It can result in a 


Note: This monitor detects and reports on any availability problem 

encountered. You may want to use the Trigger Response if 

Samples Out of Samples Failed setting to control the frequency 

of alerts for this monitor. As a comparison, a busy port will still be 

considered available if an SMTP client (such as an e-mail client or 

delivery server) successfully retries the port, while the Port monitor 

will trigger an alert regardless of the success of a retry attempt. 


the Port monitor queries a specific port. 















this monitor. 




of the host and the port. To change the default assigned name, type 

a unique monitor name that helps you to identify what this monitor 

does. 

To create a Port monitor: 

1. On the Monitors Page, click Add o open the Add Monitor dialog 

box. 




can be applied to your monitor group. Click Port to add a 

monitor that confirms that a port on a host is responding. Use 

settings on the General tab to configure each Port monitor. 

Use the options on this tab to specify the host name and port to 

be monitored. 





Host Address – Specifies the name or IP address of the host. 

Port – Specifies the port you want to monitor. Click the arrow 

to select from a variety of common ports. If the port you want to 

monitor is not listed, select Other and type in the port number. 

Timeout Seconds – Specifies the number of seconds to wait 

for a reply. 








the alert. 


the alert. 









let OneSight create a unique name using the Port specifications 


4. On the General tab, type in the host name or IP address of the 

server you want to monitor. 

5. Select the port that you want to monitor. For example, the 

standard FTP port, 21, allows you to confirm that an FTP 

connection is available. If you don’t see the port you want, click 

Other and type in the port number. 

6. If you want additional information you can also configure a 

string to be sent and a string to be returned from a sample. Click 

the Advanced tab and type the string to be sent to the port (Send 

String) and the string that should be returned (Match String). In 

the following example, the username and password ―test1‖ 



should return a specific string indicating that the user is now 

logged in: 

Send String: test1\0x0a\0x0dtest1 

Match String: 230 User test1 logged in. 

If the string you specify is not found, the monitor status will 

change on the OneSight Console. You can also add an action, 

such as an e-mail, to send an alert if a port is not responding or 

if the string you specified is not found. 






save these basic Port monitor settings. You can now add this 





Setting Advanced Options 

Use the options on this tab to specify the string to use when 

querying the port and the expected response. 

Send String – Specifies the query to be sent to the port. 

By default, a linefeed character (\n or \0x0a) is appended to the 

string you specify. If you want to use an alternate control 

character, simply append the character(s) you prefer. If you do 

not want any control character appended, add the null character 

(\0x00) to the end of the string. If you add any control character, 

the linefeed character will not be added by default and you will 

have to add it manually. For example, ―hello\r\n‖ would be 

―hello\0x0d\0x0a‖. 

To include a pause of 500 ms, add ―\p‖ to the send string. 


Configuring Process Monitors 

Match String – Specifies the string that should be returned. If 

you specify this string, you can trigger an alert and an action 

plan when the string is not returned. String matching is case 

sensitive. 

Maximum Read Length – Specifies maximum length of the string 

to be read from the port when searching for the text specified in 

the Match String box. 






You can set up Process monitors to verify that important processes 

are running. At specified time intervals, the Process monitor checks 

specified system processes for the specified value. The monitor 

returns the value or sets an alert if the request times out or exceeds 

a threshold. 

Note: A Data Collector or Remote Agent must be installed on the 

machine on which the process will be monitored. 

In the Add Monitor dialog box, when you click Process in the 

Monitor Types box, settings to configure a Process monitor appear 



Process monitor for your monitor group. 



Process alert will affect the monitor group’s health. It can result in a 
















this monitor. 







To create a Process monitor: 


dialog box. 




can be applied to your monitor group. Click Process to add a 

monitor that confirms that a process on a host is within the 

specified measurement. Use settings on the General tab to 

configure each Process monitor. 

Use the options on this tab to specify the host name and process 

to be monitored. The process may be specified by process name 

(e.g. httpd) or by process name and commandline string (e.g. 

httpd (./lib/httpd -f)). The agent monitors one of three attributes 

(count, memory usage, and CPU usage) for all processes with the 

given name or commandline. 





DNS Name – Specifies the name or IP address of the host. 



Discover Processes – Click Discover Processes to load all the 

names of processes running on the host machine. The list will 

show most processes twice, once using the generic process 

name and once using the name and the commandline string. 

Each entry in the list, however, is unique. 

Process – Specifies the name of the process you want to 

monitor. Click the arrow to select from all of the running 

processes loaded using the Discover Processes button. If the 

process you want to monitor is not listed, enter the name in the 

text field. 

Measurement – Specifies the process measurement you want to 

monitor. Click the arrow to select either count (number of 

instances), memory usage (in MB), or CPU usage (in percent). 

Method of Aggregation – Specifies the method of aggregation to 

use for monitoring memory or CPU usage. Click the arrow to 

select a method, either Total, Minimum, or Maximum. 

It is common for an application to run multiple processes with 

the same name or even the same commandline. Method of 

Aggregation indicates how to aggregate data about multiple 

processes. 

Total – specifies that the monitor should add the 

measurements from all such processes, for example, 

returning the total memory used by processes named ―httpd‖. 

Minimum – specifies the smallest measurement for all such 

processes, returning, for example, the least CPU usage for all 

such processes. 

Maximum – specifies the largest measurement for all such 

processes, which would help determine, for example, if a 

single httpd process is using most of the CPU. 

Send sample failure if zero processes found – Sends a sample 

failure if no processes are found. 











let OneSight create a unique name using the Process 



4. On the General tab, type in the host name or IP address of the 

server you want to monitor. 

5. Select the process that you want to monitor. If you don’t see the 

process you want, click Other and type in the process name. 

6. Select the measurement that you want to use to monitor the 

process. 

7. Select the method of aggregation that you want to use to 

monitor the process. 

8. Specify the sample frequency. 






save these basic Process monitor settings. You can now add this 




Configuring Service Monitors 


A Service monitor allows you to see status on and be notified of the 

availability of a Windows Service. The Service monitor verifies that 

critical Windows services, such as FTP, DNS, or Telnet are running. 

To use this monitor, the user information you provide must have 

sufficient rights to query status of services on remote machines. 

In the Add Monitor dialog box, when you click Service in the 

Monitor Types box, settings to configure a Service monitor appear 



Service monitor for your monitor group. 

Alerts Tab – Displays the options that you can use to modify an alert 

and associate it with action plans. You can also configure how a 

Service alert will affect the monitor group’s health. It can result in a 


New alerts cannot be added to a Service monitor. 


to monitor the status of a Windows service. 















this monitor. 







A Service monitor determines if a specific service on a Windows 

machine is available. Use this procedure to create a Service 

monitor. The Service monitor verifies that critical Windows 

services, such as FTP, DNS, or Telnet are running. 

To create a Service monitor: 


dialog box. 




can be applied to your monitor group. Click Service to add a 

monitor that confirms that a service on a Windows machine has 

been started. Use settings on the General tab to configure each 

Service monitor. 

Use the options on this tab to specify the Windows information 

about the machine on which you want to monitor services. 





System Identification Settings 

DNS Name – Specifies the DNS name of the Windows 

machine. In many environments, this is the same as the 

NetBIOS name, described below. 



NetBIOS Name – Specifies the NetBIOS name of the 

Windows machine. The NetBIOS name is the Windows 

Computer Name. In Windows 2003, this is on the 

Identification tab in Network Neighborhood properties tab. In 

Windows 2000, it is on the Network Identification tab in My 

Computer properties. 

Authentication Settings – If you are monitoring a remote system 

that is running Windows 2003/2008 and that does not have a 

Data Collector or Remote Agent running on it, you must 

authenticate with a domain, not directly with the machine. If 

you have installed a OneSight Data Collector or Remote Agent 

on the machine you are monitoring, the user name, domain, and 

password are not required. 

User Name – Specifies the name to use for authentication to 

the remote Windows machine. 

Domain – Specifies the domain to use for authentication to 

the remote Windows machine. The Username and Password 

information you supply should be associated with the domain 

to which the user belongs. 

Password – Specifies the password to use for authentication 

to the remote Windows machine. 

Service 

Discover Services – Click Discover Services to add service 

entries to the Service Name list. 

Service Name – After you provide the system information 

(DNS name, NetBIOS name, user name, password, and 

domain authentication), OneSight can find the services on 

that machine. Click the Discover Services button, and then 

click the arrow next to the Service Name box to see a list of 

available services on the specified machine. 











let OneSight create a unique name using the Service 



4. On the General tab, type in the DNS name, NetBIOS name, user 





is not required. 

5. Click Discover Services. Using the login information you have 

specified, the available services on that machine are identified 

and listed here. 

6. Select the service you want to monitor in the Service Name list 

box. 






save these basic Service monitor settings. You can now add this 




Configuring SNMP Monitors 


Creating an SNMP (Simple Network Management Protocol) monitor 

allows OneSight to provide specific performance and configuration 

information on network devices, such as routers, or on hosts, such 

as workstations or mainframes. 

To use this monitor, enable SNMP on the machine you intend to 

monitor. Also, be sure that the MIB data you plan on collecting is 

supported by the SNMP daemon on the monitored machine. 

Note: If you want to gather a variety of SNMP metrics or you want 

to compare the same metric or set of metrics on multiple machines, 

you may want to create a profile monitor for the RFC 1213 Network 

Device profile instead of using this dedicated SNMP monitor. 

In the Add Monitor dialog box, when you click SNMP in the 

Monitor Types box, settings to configure an SNMP monitor appear 



SNMP monitor for your monitor group. 

Advanced Tab – Contains the options for configuring objects. 


and associate it with an action plan. You can also configure how the 

SNMP alert will affect the monitor group’s health. It can result in a 



to monitor a specific SNMP object. 















this monitor. 







To create an SNMP monitor: 


dialog box. 




can be applied to your monitor group. Click SNMP to add a 

monitor that checks an SNMP object. You’ll use settings on the 

General tab to configure an SNMP monitor. 





Host Name – Specifies the name or IP address of the host. 

Community – Specifies the SNMP password of the system. The 

default SNMP community string is public. 



Time Out– Specifies the amount of time (in seconds) to wait for 

an SNMP reply. If Retries is greater than 0 and a reply is not 

received, a retry attempt is made. For each subsequent retry, the 



timeout value is doubled. For example, if Time Out is 5 and 

Retries is 2, the first request attempt will occur after 5 seconds, 

the second attempt will occur after 10 seconds, and the third 


timeout period equals 35 seconds. If there is no response after 

this time, a Sample Failure is triggered. 

If Retries is 0, a Sample Failure is triggered when a reply is not 

received in this amount of time. 

Retries – Sets the upper limit for the number of times an SNMP 

request is retried. For example, if Retries is set to 3, the SNMP 

request will be sent up to four times (the initial try plus three 

retries). 


let OneSight create a unique name based on the Object, or you 

can type in your own name for the monitor. 

4. For the Host Name specification, type in the name or IP address 

of the machine. 

5. Confirm that the other System defaults (community string of 

public, default port 161, etc.) are appropriate for the SNMP 

object you want to monitor. 



6. Click the Advanced tab. 

Metric – Click the arrow next to the Metric box to select from 

the list of common SNMP metrics (for example, HOST- 

RESOURCES-MIB % Disk Space Used). When you select one of 

these metrics, the appropriate object information is 

automatically supplied. In some cases, the settings allow you to 

supply an additional setting, such as a Search for string. 

If the metric you want to monitor is not in this list, use the 

option and complete the items described below. 

Object ID – Specify an Object ID (OID). OneSight only uses 

objects that return numeric values. If the Object ID you enter 

does not begin with a ―.‖, OneSight assumes the OID is within 

the MIB-II (.1.3.6.1.2.1) hierarchy. 



MIB Browser – Displays the MIB browser in a separate window. 

You can view objects in the MIB browser and optionally 

populate the Object ID field on the Advanced tab. 

Action – Select an action: 

Get – Performs a traditional SNMP get operation. If you select 

Get, you must also specify a valid Object ID and append the 

instance identifier to it. 

Table Get – Searches an SNMP table for numeric data 

associated with a particular instance, or row, of the table. If 

you select Table Get, you must also specify a valid Object ID 

(no instance identifier), Search for String, and column to look 

in. 

Instance – Performs a traditional SNMP get operation using the 

instance, or row, identifier you specify here. For scalar objects, 

the instance is always 0. For example, if you want to retrieve 

the MIB-2 sysUpTime (.1.3.6.1.2.1.1.3) object, there is only one 

instance of this object, and scalar SNMP objects require the ―.0‖ 

instance identifier. 

Search for string – Enter the string OneSight will search for in 

the OID column that you specify below. This setting applies 

only if Table Get is selected in the Action field. A regular 

expression can be used. Refer to Using Regular Expressions for 

Pattern Matching for more information. 

In OID column – Enter the column where OneSight will search 

for string you specified above. This setting applies only if Find 

Instance is selected. 


collected. 


metric measurement is expressed in kilobytes, setting Scale to 

1024 will translate it to bytes. If the metric measurement is 



expressed in milliseconds, setting Scale to .001 will translate it 

to seconds. 

Version – Select the SNMP version being used. 


3: 






or SHA. 






data. 






Translation Type – Select No Translation if the value requires no 

further modification. The Rate translation type means that the 

value should be calculated as frequency per minute. 



Unit Measure – To define a Unit Measure, click the arrow to 

select a unit measure (%, bytes, hours, minutes, seconds). You 

can also type in a unit measure such as messages/minute. This 

measure is a display string. It does not perform any data 

translation. 




Divide by Object ID Settings – Use this setting in conjunction 

with the Object ID setting (above) to gather information that is 

best expressed as a ration. The value retrieved by Object ID is 

the dividend and the value retrieved by Divide by Object ID is the 

divisor. (Object ID/Divide by Object ID). 

Enable – Select this check box to enable this setting. 

Object ID – Enter an object ID. For example, in the HOST- 

RESOURCES MIB, disk size (hrStorageSize) and disk in use 

(hrStorageUsed) are two different OIDs which, when 

divided, give you the ration, or portion, of the disk that is in 

use. Using this example, you could enter 25.2.3.1.6 as the 

Object ID and 25.2.3.1.5 as the Divide By Object ID. 




data. If you are measuring an SNMP object representing an 

SNMP String datatype, it can be converted to a number for 

use in OneSight by using the SNMP String Mappings field. 

Simply specify a semicolon delimited mapping of Strings to 

Integers. For example, ―false=0;true=1‖; will convert a 

―false‖ reading to a 0 value in OneSight, and this will be 

displayed in OneSight Status as ―false=0‖. If you only want 

to display the string on the OneSight status page, use a colon, 

rather than a semi-colon to delimit the values. 














7. Click the arrow next to the Metric box to select from the list of 

common SNMP metrics (for example, HOST-RESOURCES-MIB 

% Disk Space Used). The list includes metrics for a variety of 

SNMP MIBs. If you’re using a metric in the HOST-RESOURCES- 

MIB group, the machine you’re monitoring must have SNMP 

and the Host Resources MIB enabled. 

When you select one of these objects, the appropriate object 

information is automatically supplied. In some cases, the 

settings allow you to supply an additional setting, such as a 

Search for String. 

If the metric you want to monitor is not in this list, select the 

option from the Metric list and click MIB Browser to 

find it. In the MIB Browser, select the metric you want to 

monitor, verify that it is accessible by clicking Go. When you 

exit the MIB Browser, you can save the settings to the Object ID 

field. 

8. If necessary, type in the Search for String. This is the string 

OneSight will search for in the OID column specified. In the 

case of Disk: Space in Use, the default, /usr, may be 

appropriate. 


Configuring SNMP Trap Monitors 






save these basic SNMP monitor settings. You can now add this 




Creating an SNMP (Simple Network Management Protocol) Trap 

monitor allows OneSight to check for specific trap messages on 

network devices, such as routers, or on hosts, such as workstations 

or mainframes. A trap is an alarm-triggering event on an agent, such 

as a system reboot. You configure the general filtering criteria for a 

trap on the General tab, and specify any pattern match alerts against 

the trap in the Alerts Editor. When a trap is received, it is parsed for 

the filtering criteria specified in the General tab. If it passes the 

general criteria, the trap is displayed, otherwise, the trap is 

discarded. If alerts search strings are matched, the alert event is 

generated. 

Before configuring an SNMP Trap monitor, the following 

prerequisites must be met: 

The computer sending the trap must have an application that can 

send traps and be configured to send the appropriate traps. 

The computer sending the traps must have the community string 

and destination configured in the SNMP Service. These 

parameters are located on the Traps tab. The trap destination 

should be set to the machine receiving the traps. 

In the Add Monitor dialog box, when you click SNMP Trap in the 

Monitor Types box, settings to configure an SNMP Trap monitor 





SNMP Trap monitor for your monitor group. 


and associate it with an action plan. You can also configure how the 

SNMP Trap alert will affect the monitor group’s health. It can result 

in a Warning state, a Critical state, or can have no impact on health. 













this monitor. 







To create an SNMP Trap monitor: 


dialog box. 




can be applied to your monitor group. Click SNMP Trap to add a 

monitor that monitors for SNMP Trap messages. You’ll use 

settings on the General tab to configure an SNMP Trap monitor. 





Collection Host – Specifies the name or IP address of the host 

with the running OneSight Data Collector to which the traps are 

being sent. 

Mib File – Optionally specifies the name and location of the 

Management Information Base (MIB) file for the SNMP device. 

The MIB file is provided by the SNMP device manufacturer. 

The MIB file allows OneSight to import the OIDs by name 

rather than number. When you specify a MIB file, the Enterprise 

and Trap Type lists will be populated with the OID names 



defined in the MIB file. You can select the names in the 

Enterprise and/or Trap Type lists to define which SNMP Trap to 

monitor. 

The OneSight Server Administrator must copy other SNMP 

device manufacturer MIB files to the MIB file directory of the 

OneSight Server before a filename can be specified in this field 

(OneSight includes a onesight.mib file). If you get an error when 

specifying a MIB file, contact your OneSight Server 

Administrator to verify the SNMP device MIB file is available 

on the OneSight server. 

Note: The MIB file should be both on the OneSight Server and 

the Data Collector machines. On the OneSight server, the MIB 

file should be located in the \mibs 

directory. On the Data Collector, it should be located in the 

\mibs directory. This is 

especially important when the OneSight Server and Data 

Collector are installed on different machines. 

List Mibs – Lists the MIB files in the C:\Empirix\OneSight\mibs\ 

directory on the OneSight server. Use to enter a MIB 

that is not listed. 

Get Values – Gets the values for Enterprise and Trap type from 

the MIB file entered in the Mib File field. 

Upload MIB – Lets you upload a MIB file to the 

C:\Empirix\OneSight\mibs\ directory on the OneSight server. 

Browse – Displays the MIB Browser in a separate window. You 

can view objects and copy and paste them into the Add Monitor 

dialog box. 

Community – Specifies the SNMP password of the system. The 


Enterprise – Specifies the Enterprise criteria to further define 

which SNMP Trap to monitor. Enter a specific Enterprise OID 

or select the criteria from the list defined in the specified MIB 



file. An alert is triggered if the SNMP Trap meets the selected 

criteria. 

Trap Type – Specifies the Trap Type criteria to further define 

which SNMP Trap to monitor. Select the criteria from the list 

defined in the specified MIB file. An alert is triggered if the 

SNMP Trap meets the selected criteria. 

Note: Filtering can only be done on Enterprise ID and trap type; 

it cannot be done based on individual OIDs. 

Reset Trap – Specifies the Trap Type criteria that will reset any 

existing alerts for this monitor. 

Note: You can have the trap reset based on a different OID. This 

is useful for systems that have traps that get issued with their 

own OID when an issue clears. For example, you could have 

two SNMP actions, one of the type OneSight Critical and one of 

the type OneSight Normal. If you set the trap type to OneSight 

Critical and the reset trap to OneSight Normal, the trap will 

reset when a trap is received that is associated with the 

OneSight Normal OID. 

Char set – This field is used for internationalization. If 

necessary, select the character set appropriate for your 

language. 

NameFormat – Select the name format to use. The selected 

name format is used to display the name on the status page and 

on emails. 

FullName – The entire value is used. For example, 

.org.iso.dod.internet.mgmt.mib-2.icmp.icmlnMsgs. 

ShortName – Only the value in the last fields is used. For 

example, if the long name were as shown in the above 

example, the short name would be icmplnMsgs. 








let OneSight create a unique name based on the Object, or you 

can type in your own name for the monitor. 

4. For the Collection Host, type in the name or IP address of the 

SNMP Trap destination host (the host running SNMP 

management software). 

5. For the MIB file, type in the name to specify the Management 

Information Base file for the SNMP device. The MIB file is 

provided by the SNMP device manufacturer. The OneSight 

Server Administrator must copy other SNMP device 

manufacturer MIB files to the MIB file directory of the 

OneSight Server before a filename can be specified in this field 

(OneSight includes a onesight.mib file). If you get an error when 

specifying a MIB file, contact your OneSight Server 

Administrator to verify the SNMP device MIB file is available 

on the OneSight server. 

6. Enter the community string the SNMP object you want to 

monitor. 

7. For the Enterprise, enter a specific Enterprise OID or select the 

criteria from the list defined in the specified MIB file. An alert 

is triggered if the SNMP Trap meets this criteria. 

8. For the Trap Type, enter a specific trap type OID or select the 

criteria from the list defined in the specified MIB file. An alert 

is triggered if the SNMP Trap meets this criteria. 






Configuring TCP/IP Socket Monitors 


save these basic SNMP Trap monitor settings. You can now add 




You can set up a TCP/IP socket monitor to collect data on a TCP/IP 

port on a remote system. The monitor connects to the host and port 

specified and treats the data it receives in the same way as it would 

treat the data in a log file. This is useful, for example, for 

monitoring a serial port via a serial to TCP converter or for 

monitoring a system that has a logging port. 

Note: TCP/IP monitors are shown as Logfile monitors on the status 

page. 

In the Add Monitor dialog box, when you click TCP/IP Socket in the 

Monitor Types box, settings to configure a TCP/IP Socket monitor 



TCP/IP Socket monitor for your monitor group. 



TCP/IP Socket alert will affect the monitor group’s health. It can 

result in a Warning state, a Critical state, or can have no impact on 

health. 















this monitor. 







To create a TCP/IP Socket monitor: 


dialog box. 




can be applied to your monitor group. Click TCP/IP Socket to 

add a monitor that will collect data from a remote TCP/IP port. 

TCP/IP Port – Enter the TCP/IP port that you want OneSight to 

connect to. Data must be being sent down this port. 


Perl Expression – select this option when you want to use a 

Perl expression to collect data. 

Number of Matching Records – this metric returns the number 

of records that matched the entered Perl expression. 


returns the number of records written since the last sample. 


time since data was sent to the channel. 



Perl Expression –Specifies a Perl Expression used to collect 


checks the last entry whenever the log file changes. This 

returned data can then be used within OneSight, both for 

alerting, using threshold alerts, and reporting. 

To check whether the file exists, use the File/directory exits 

metric type and leave this field blank. 




data. If you are measuring a log file response that is a string, 

it can be converted to a number for use in OneSight by using 

the String Mappings field. Simply specify a semicolon 
















time operating mode. In this mode each line read from the 

file is treated as a single log file entry and is processed 

individually. 




arbitrary record-based mode. In this mode a Perl expression 

is used to determine where each record in the file starts and 

ends. The expression is applied to the data as it is read, and 

records are picked out as they are found. Entries that exceed 

the specified maximum record size are ignored. 



Max Record Length – Enter the maximum record length. 

Entries that exceed this length are ignored. 

Record Format (PERL) – Enter the Perl expression defining 

the record, including the delimiter character. 

Unit Measure – Specifies the units to use when displaying the 

metric. 

Inactivity Sample Count – If the data source detects that the 

monitored TCP/IP connection does not receive any new 

information for the number of sample counts you enter here, a 

sample failure will result. 

Sample Continuously – Select to sample continuously. This field 

is only available when Metric Type is Perl Expression value. 





processed. 









ignored. 




ignored. 



message. 






let OneSight create a unique name using the specifications you 

supply, or you can type in your own name for the monitor. 

4. Enter the Remote Host Name, specifying the name or IP address 

of the socket to be monitored. 

5. Enter the TCP port to be monitored. 

6. Select the Metric Type. 

7. Type in a Perl Expression to collect performance data from a 

log file entry. If you want to verify that the file exists use the 

File/directory exists metric type and leave this field blank. 

8. Select the record type. 

9. If you selected PERL Expression defines record, enter the Max 

Record Length and Record Format. 


Configuring URL Monitors 

10. On the Alerts tab, add your content string tests using the Pattern 

Match alert. If you have specified a Perl Expression to collect 

performance data, you can also add threshold alerts. 




be causing any problem. Note that the Test button for the 

TCP/IP Socket Monitor will simply verify that the file exists. 


save these basic TCP/IP Socket monitor settings. You can now 




A URL monitor directs OneSight to determine if a URL that is 

critical to your web site is functioning as it should. A URL monitor 

connects to a specified URL at specified time intervals to confirm 

that the URL is quickly available. You can set up as many URL 

monitors as you need in order to determine if individual web pages 

used by your monitor group are available and functioning correctly. 

When you click URL in the Monitor Types box, settings to 

configure a URL monitor appear on these dialog box tabs: 

General Tab – Contains the options that you can use to create a URL 


Advanced Tab – Allows you to define settings for cookies and user 

agent. 

Proxy Tab – Allows you to define settings for proxy server and 

authentication. 

Alerts Tab – Shows what alerts are currently in effect for the URL 

monitor, whether the alerts contribute to an error condition, and 



what action plan will be used when an alert occurs. Options on this 

tab allow you to add, modify, or delete alerts for the URL monitor. 


to check the access to a specific URL. 













this monitor. 




of the page to which the monitor applies. To change the default 



To create a URL monitor: 


dialog box. 


can be applied to your monitor group. Click URL to add a 



monitor that checks a URL you provide. Use settings on the 

General tab to configure each URL monitor. 

Use the options on this tab to specify how the URL monitor will 

check the response time for access to a specified URL. 





URL Address – Type the URL for the web page you want to 

check. The URL must be specified with the full protocol 

designation of http or https. For example: http://www.empirix.com. 

If you use Get as the HTTP Method (the default), simply include 

any additional parameters you want to include as part of the 

URL string, for example: 

http://search.yahoo.com/bin/search?p=electronics 



Good Content String –This setting is optional. When you check 

for the availability of a web page, you can confirm that the page 

that was reached is the one you expect. If you use this option 

and the specified content is not found, the URL monitor is put 

into a URL Unavailable state and an alert is triggered. You can 

then configure an action, such as an e-mail, to notify you if this 

string is not found on the page by modifying the URL 

Unavailable alert on the Alerts tab. See the Adding Alerts to a 

Monitor for general information about creating an alert. 

Type in a string that is present on the specified web page. The 

string can be any HTML string; it does not have to be a string 

that is visible when viewed with a browser. The string can also 

include a regular expression. 

When you pick a string, you will get the best results if the string 

is: 

Not likely to be overwritten by edits and standard 

maintenance updates. 

Unique to this particular URL. 

Bad Content String – This setting is optional. When you check 

for the availability of a web page, you can specify a string, such 

as an error message, that would be found if the page that was 

reached were not the one you expected. If you use this option, 

the URL monitor status will change and a URL Unavailable alert 

will be triggered when the content you specify is found. You 

can configure an action, such as an e-mail, to notify you if this 

string is found on the page. 

Type in a string that is not present on the specified web page. 

The string can be any HTML string; it does not have to be a 

string that is visible when viewed with a browser. The string 

can also include a regular expression. 



When you pick a string, you will get the best results if the string 

is: 

Typically found on a page that is displayed when a page is 

not available (for example, ―not found‖ or ―timeout‖). 

Not found on the URL you are monitoring. 

Match Content String only when returned HTML is well formatted 

– select this option to match good content and bad content only 

when the return file is HTML. No matching is done for any 

other file type. 

Sample Timeout – Specify the number of seconds that should 

elapse before the monitor times out while attempting to sample. 

This setting is based on the time that elapses after a URL is 

located and the page download process begins. 

Measurement Details 

Retrieve Images – If you want to calculate URL availability 

and access time with retrieval of embedded images (such as 

.gif and .jpeg files and references within tags) included, 

select this check box. 

Retrieve Objects – If you want to calculate URL availability 

and access time with retrieval of embedded objects (such as 

ActiveX objects and Java applets) included, select this check 

box. OneSight measures the time taken to retrieve data used 

by objects, but does not include the time needed to retrieve 

any executable file required in order to interpret the data. 

Content types other than HTML and images are also 

classified as objects. 

HTTP Method Settings 

Get – The default HTTP method is Get. Include any 

additional query strings as part of the URL address. 



Note: Some servers limit the length of URL and query strings 

to about 240 characters. 

Post – The Post method, usually associated with a form, 

allows a much larger amount of information to be associated 

with the request. When you select the Post option, you can 

add Optional HTTP Post Data Items. 

Optional HTTP Post Data Items Settings – If you select Post as 

the HTTP Method, you can add a series of Name-Value pairs. 

Click Add and type in the Name-Value pairs that should be 

included with the URL. 

For example, a URL generated after completing a form may 

appear as follows: 

POST http://www.empirix.com/cgi-bin/guestbook.pl 

...(additional headers) 

name=Harold&nickname=Harry 

To reference this page, add nickname for the Name and Harry 

for the Value. 






the alert. 


the alert. 






Save object download details – When selected, collects data for 

the object timer report. 

Save Diagnostic Data – Saves the selected data in the 

urldetails.jsp file. This data can also be viewed by clicking the 

View URL Details Smartlink on the status details page. 

Save HTML from failing runs – Select this option to save 

HTML from failing runs. 

Save HTML from successful runs – Select this option to save 

HTML from successful runs. 






let OneSight create a unique name using the URL specifications 


4. On the General tab, enter the URL address for the web page you 

want to check. 

5. If you want to check the content on the page, you can configure 

a Good Content String, a Bad Content String, or both. These 

settings are optional. 

In the Good Content String box, enter a string that should be 

present on this web page. 

In the Bad Content String box, enter a string that should not 

be present on this web page 

Note: These strings can be any HTML string; they do not have to 

be strings that are visible when viewed with a browser. 



6. Under HTML Method, select the HTTP method to use for this 

monitor. If you select Get as the HTML Method (the default), 

you can add parameters to the URL string in the URL Address 

for example: 

URL Address: http://search.yahoo.com/bin/search?p=electronics 

7. In the Sample Every box, enter the number of seconds, minutes, 

or hours to control how often the specified URL is monitored 

for availability. 

8. Specify whether to save object download details for the Object 

Timer Report. 






save these basic URL monitor settings. You can now add this 





Specifying Advanced Settings 

Use the Advanced tab to specify cookies, proxy server, authentication, and 

user agent settings. 

Report on – Lets you check the amount of time it takes to download the 

file/content or the size of the file. Once you know the file size you can 

create an alert to check whether the size is greater than expected. 

Download Time – Returns the download time. 

Download File Size – Returns the size of the file. 

Perl Expression – Specifies the Perl Expression to use to retrieve 

the file size or match a string from a url. 



String Mappings – Use this button to display the String Mappings 

dialog box for entering a string that should be returned for the 

query you specified. 


measuring a string representing a string datatype, it can be 

converted to a number for use in OneSight by using the String 

Mappings field. Specify a semicolon delimited mapping of 

strings to integers. For example, ―false=0;true=1‖ converts a false 

reading to a zero value in OneSight. If you only want to display 

the string on the OneSight status page, use a colon, rather than a 

semi-colon to delimit the values. 

Note that data that has a colon cannot be used in string mapping. 

Cookies – OneSight can control how cookies are used as part of this 

monitor. 

No Cookies – Select this option if you want the URL test to 

prevent the use of cookies when accessing the page. 

Support Cookies – Select this option if you want to allow the URL 

monitor to support cookies as part of the URL request. A fresh 

cookie is retrieved each time the test is run. 

Use the Following Cookies Value – Type in a cookie value for the 

page you are monitoring. If you supply a particular value, 

remember that the cookie is saved and can become out of date. 

Refresh cookie requests are ignored. 

Host Header Specification 

Specify an HTTP Host Header – Select this option if you want to 

define an HTTP Host Header. When selected, the monitor uses 

the IP Address specified in the URL Address and the header 

specified in the HTTP Host Header field. When cleared, the 

monitor uses the host specified in the URL Address field. Use this 

option if you have a single IP that hosts multiple web sites. 



HTTP Host Header – Specify the value to look for in the ―Host:‖ 

field in the HTTP Get Request. For example, if you host web sites 

www.mywebsite.com and www.myotherwebsite.com using IP 

address 255.255.001.001, specify http://255.255.001.001 as the 

URL Address and www.mywebsite.com or 

www.myotherwebsite.com as the HTTP Host Header value. 

User Agent – You can specify a particular user agent when you monitor a 

URL. When you configure a User Agent, the browser and operating 

system you specify is added to the header of the URL request. This allows 

you to test pages designed for a specific browser URL or confirm that a 

page designed for multiple browsers works appropriately for each of them. 

If you select a browser from the list, OneSight displays (in parentheses) 

the user agent string that will be inserted in the header of the URL 

request. 

You can also specify a custom string. Select and type in the 

browser and operating system specification you want to include in the 

header of the URL request. 

Retries – Sets the upper limit for the number of times a URL request is 

retried due to any failure. For example, if Retries is set to 3, the URL 

request will be sent up to four times (the initial try plus three retries). 

After the fourth try, if no response is received, the URL check is treated as 

a sample failure. 

Test – When you add or modify a monitor, you can test General and 

Advanced settings to determine if they are set appropriately. After 

clicking the Test button, you will see messages in the status window as the 


To add an HTTP parameter to a URL: 

1. In the Add HTTP Parameter dialog box, type in the name of the 

parameter you want to include with the Get or Post operation. 



2. Type in the value for the parameter. For example, if you wanted 

to reference a page that was reached with the string 

http://search.yahoo.com/bin/search?p=electronics, you would add p 

for the Name and electronics for the Value. 

Specifying Proxy Settings 

Use the Proxy tab to specify proxy server and authentication settings. 

Authentication Settings – Fill in User Name and Password information 

to monitor URLs with HTTP Basic Authentication restrictions. 

User Name – If the URL specified requires a name and password 

for access, enter the name in this field. 

Password – If the URL specified requires a name and password 

for access, enter the password in this field. 


Configuring OneSight Virtual Agent Monitors 




If you find that a OneSight URL monitor fails to reach a URL when your 

browser successfully connects to the same URL, check your proxy server 

settings in your browser. For example, in Internet Explorer, select 

Internet Options from the Tools menu and then click LAN settings on 

the Connections tab. If proxy server settings are configured for your 

browser, they may also need to be configured for the URL monitor. 



Proxy Host – The name or IP address of the proxy server. 


Proxy User Name – The proxy server login user name. 



You can set up OneSight Virtual Agent monitors to run an 

executable program from the command line of the system. You 

specify a Perl expression to return metrics from the command. 

OneSight Virtual Agent is an easy way to execute operating system 

or custom programs on a host and return specific metrics. The 

OneSight Virtual Agent monitor executes at specified time 

intervals. 

At specified time intervals, the OneSight Virtual Agent monitor 

executes the specified command. The monitor sets an alert if unable 

to execute the command. 

Note: If you are using SSH private key files or using SSH with a user 

name and password, you must download the OpenSSH ganymed- 



ssh2-build.jar file from the Cleondris web site at 

http://www.cleondris.ch/opensource/ssh2/. Once downloaded, copy the 

file to the C:\Empirix\DataCollector\webapps\ROOT\WEB-INF\lib 

directory then restart the data collector to load the .jar file. 

If you are using SSH private key files or using SSH with a user name 

and password and the PasswordAuthentication setting in the 

sshd_config file is set to no on the Unix server, OneSight will fail. 

See http://www.cleondris.ch/opensource/ssh2/FAQ.html#passwordauth for 

more information. 

In the Add Monitor dialog box, when you click OneSight Virtual 

Agent in the Monitor Types box, settings to configure a OneSight 

Virtual Agent monitor appear on these dialog box tabs: 


OneSight Virtual Agent monitor for your monitor group. 



OneSight Virtual Agent alert will affect the monitor group’s health. 

It can result in a Warning state, a Critical state, or can have no 

impact on health. 


the OneSight Virtual Agent monitor executes the command. 















this monitor. 







To create a OneSight Virtual Agent monitor: 


dialog box. 




can be applied to your monitor group. Click OneSight Virtual 

Agent to add a monitor that confirms that a host is responding. 

Use settings on the General tab to configure each OneSight 

Virtual Agent monitor. 

Use the options on this tab to specify how the OneSight Virtual 

Agent monitor will attempt to execute the command. 





Description – Specifies a description of the OneSight Virtual 

Agent monitor. 

Host Name – Specifies the name or IP address of the host on 

which to execute the command. 



Operating System – Select the operating system being used on 

the host machine. 

Charset – Specifies the character set to use for the Virtual 

Agent. Select a character set from the list. 

ISO-8859-1 – Latin alphabet for Western European languages 

such as Basque, Catalan, Danish, Dutch, English, Faeroese, 

Finnish, French, German, Icelandic, Irish, Italian, Norwegian, 

Portuguese, Rhaeto-Romanic, Scottish, Spanish, Swedish, 

Albanian, Afrikaans, and Swahili. 

ISO-8859-13 – Baltic Rim languages. 

ISO-8859-15 – Latin alphabet for Western European 

languages. 

ISO-8859-2 – Central and Eastern European languages that 

use a Roman alphabet, including Polish, Czech, Slovak, 

Slovenian, and Hungarian. 

ISO-8859-4 – Latin alphabet for Estonian, Latvian, 

Lithuanian, Greenlandic, and Sami. 

ISO-8859-5 – Most Slavic languages that use a Cyrillic 

alphabet including Belarusian, Bulgarian, Macedonian, 

Russian, Serbian, and Ukranian. 

ISO-8859-7 – Greek. 

ISO-8859-9 – Latin alphabet for Western European languages, 

similar to ISO 8859-1 with the Icelandic letters replaced with 

Turkish letters. It is also used for Kurdish. 

K018-R – Cyrillic 

US-ASCII – United States. 

UTF-16 – Unicode 16 bit. 



UTF-16BE – Unicode big-endian. 

UTF-16LE – Unicode little-endian. 

UTF-8 – Unicode 8 bit mostly used for HTML. 

Windows 1250 – Microsoft Windows Code Page for Central 

European Latin alphabet languages. 

Windows 1251 – Microsoft Windows Code Page for Russian 

and other Cyrillic languages. 

Windows 1252 – Microsoft Windows Code Page for Western 

European languages. 

Windows 1253 – Microsoft Windows Code Page for Greek. 

Windows 1254 – Microsoft Windows Code Page for Turkish. 

Windows 1257 – Microsoft Windows Code Page for Baltic. 

Cp500 – EBCDIC 500 VI. 

Metric – Specifies the metric to measure. If you select a 

predefined metric for one of the operating systems, the 

Command and Perl Expression are automatically entered. If you 

select Custom Setting, you enter the Command and Perl 

Expression manually. 

Command – Specifies the command to execute on the host 

machine. If you select Custom Setting for the Metric, enter the 

path, filename, and command line arguments for the executable 

program. 

If your application requires two levels of telnet/SSH session, 

you can set up your monitor using a shell script that makes use 

of the SSH or RSH commands or you can use a state machine as 

described in “Configuring State Machines”. 



For example, if OneSight can connect to machine1, but the 

command requires data from machine2, then either set up a 

script or an SSH/RSH command to run the second connection. 

The following example uses SSH directly: 

host field: machine1 

command: /usr/local/bin/ssh –1 machine2 

 

Perl Expression – Specifies a Perl expression to use to report the 

data returned from the executable program. See Using Regular 

Expressions for Pattern Matching for more information about 

specifying Perl expressions. 

Process remote server response as a single block – When 

selected, all output is treated as a single block of data. The 

default is to treat output as one line at a time. 

Unit Measure – Specifies the unit of measurement: none, 

percentage, bytes, hours, minutes or seconds. 

Connection Method – Specifies the protocol to use to execute 

the command. Telnet and SSH are not currently supported for 

Windows. You can use the Local protocol to monitor a remote 

machine if you have a Data Collector installed on that machine. 

Port – Specifies the port to use to execute the command. 

User Name – Specify a user name to log into an account on the 

host system. 

Password – Specify the password required to log into the User 

Name account on the system or if you are using a private key 

file, enter the password to use to unlock the key file if it is 

password protected. 

Prompt – Specify the command line prompt for the host 

machine. If you do not specify a command line prompt, 

OneSight will attempt to infer the prompt by parsing the screen 

output. 



Private key file – Enter the name of the private key file if it is 

located in the OneSight installation directory or enter the full 

path to the private key file if it is located elsewhere. 

Note: The private key file must match the server side public 

key. The format must be OpenSSH. The file can be generated 

using ssh-keygen or by exporting an OpenSSH key from 

PuTTYgen. 

Login Procedure – Select the state machine containing the XML 

for logging in. This is useful, for example, when you are 

logging into one machine and then logging in to another 

machine. Refer to “Configuring State Machines,” at the end of 

this section for more information. 

Browse – Opens the Virtual Agent State Machines dialog box 

for editing state machine configurations. 

Command Procedure – Select the state machine containing the 

XML for running a complex command. This is useful, for 

example, when you want to run a different command depending 

on the output of a previous command. Refer to “Configuring 

State Machines,” at the end of this section for more 

information. 

Browse – Opens the Virtual Agent State Machines dialog box 

for editing state machine configurations. 




String Mappings – Displays the String Mappings dialog box. 


measuring a response from a OneSight Virtual Agent that is 

represented a string, it can be converted to a number for use in 

OneSight by using the String Mappings field. Simply specify a 




example, "false=0;true=1" will convert a "false" reading to a 0 

value in OneSight, and this will be displayed in OneSight Status 

as "false=0". If you wish to just display the string in OneSight 

Status, use a colon, rather than a semicolon, to delimit your 

values. 



String that was returned. 

String Mappings can also be used to translate a number to a 

String for display in OneSight Status. This is helpful when 

numbers represent an objects state. 




and Advanced settings to determine if they are set 

appropriately. After clicking the Test button, you will see 

messages in the status window as the test runs and when the test 

completes. 


let OneSight create a unique name using the OneSight Virtual 

Agent specifications you supply, or you can type in your own 


4. On the General tab, type in the host name for the server you 

want to monitor. This value specifies the name or IP address of 

the host on which to execute the command. 

5. Enter the user name and password required to access the host 

machine. 

6. Select the operating system in use on the host machine. 

7. Select the metric to monitor on the host machine. If you select a 

predefined metric for one of the operating systems, the 



Command and Perl Expression are automatically entered. If you 

select Custom Setting, enter the Command and Pearl 

Expression manually. 

8. Specify how often to execute the command in the Sample Every 

field. 

9. Select the protocol to use to execute the command on the host 

machine. 

10. Specify the port to use to execute the command on the host 

machine. 






save these basic OneSight Virtual Agent monitor settings. You 

can now add this monitor to a monitor group. Refer to Adding 


Configuring State Machines 

The Configure State Machines page lists the state machines 

available for use in Virtual Agent Monitoring. State Machines are 

used when additional commands must be issued prior to gathering 

OneSight monitoring data. For example, an additional login may be 

required to tunnel in to another machine, or you may need to run a 

script on a system where a shell script or batch file cannot be 

installed. 

State machines appear within the Virtual Agent monitoring UI as 

either a Login Procedure or Command Procedure drop down list. A 

state machine can be shared across multiple Virtual Agent monitors. 



To configure a state machine: 


2. Click Monitors. 

3. Select a Virtual Agent monitor or create a new one. 

4. Click Browse next to either the Login Procedure or Command 

Procedure field. 

Add – Displays the Add Virtual Agent State Machine dialog 

box for adding a new state machine. 

Modify – Displays the Modify Virtual Agent State Machine 

dialog box for changing the selected state machine. 

Clone – Creates a copy of the selected state machine. 

Remove – Removes the selected state machine. 

Used by – Displays a list of monitors using this state machine. 

Name – The Name column identifies the state machine. 

User Group – displays the user group to which this state 

machine belongs. 



5. Click Add. 

General Tab 

Name – Enter the name of the state machine. this name appears 

in the State Machine drop-down list, so it should be a brief (40 

characters or less) description of the state machine. 

Virtual Agent State Machine Content – This section is used for 

the state machine XML contents as described below. 

Access Control Tab 

User Group – Displays the user group names. 

Owner – The user group for this state machine. A state machine 

can be directly owned by a single user group. 

Global Read – Gives read access to this user group and all of its 

sub user groups. 

Read – Gives read permission to the user group. 

Write – Gives write permission to the user group. 

Delete – Gives delete permission to the user group. 



6. Enter the XML as described below. 

7. Click OK. 

The State Machine 

The state machine lets you define a set of control branch points, or 

states. These states are named by you. OneSight provides the 

following pre-defined states to which you can add transitions: 

START – This is the initial state for the virtual agent. It waits in 

this state until it receives its first input, generally a login prompt. 

END – This state has no outbound transitions. If another state 

transitions to the END state, then the state machine is ended, and 

the virtual agent sends commands and receives unprocessed 

responses. 

Transitions – Each state has a set of rules or transitions associated 

with it. These transitions define what the agent will do given a 

specific response or prompt from the remote system. A transition is 

defined by a triple . This 

means that if the data received from the remote system matches the 

specified input pattern, then send the output string, and proceed to 

the state specified by next state. If two transitions have overlapping 

regular expressions, then the state machine picks the first transition 

that matches the input data. 

Input pattern – The input pattern is a perl style regular expression. If 

the expression is matched, the transition is executed. If more than 

one transition’s input pattern matches the same input, the result is 

non-deterministic, that is only one transition will trigger, not both. 

Output string – The output string is a string send via the telnet/ssh 

channel to the remote system upon matching a transition. The 

%username% and %password% substitution variables can be used to 

fill in the user name and password fields. 



Next state – The next state is the name of the state that should be 

transitioned to once the output string has been transmitted. If the 

next state is END then the state machine terminates. 

Special Transition – Each state can have a single timeout transition 

associated with it. If the time specified by the timeout elapses 

before any acceptable data has been received, the state machine 

transitions to the timeout state. In most cases, the timeout state is 

END. A default timeout is used for any state that does not have a 

timeout transition. 

XML Format 

 

A state machine can contain any number of state objects. It can 

have the following attributes: 

Name = [string] – the name of the state. 

Timeout = [integer] – the time in msec for state timeout 

(optional). 

 

Indicates that a block of state transitions are to follow. There can be 

only one transitions tag per state. 

 

Specifies an individual transition. It can have the following 

attributes: 

PerlExpression = [String] – The Perl expression that defines 

the pattern match under which this transition will be active. 

NewState = [String] – The name of the next state to go to if 

this transition is satisfied. 



Example 

OutputString = [String] – The string to be sent to remote side 

before the transition to the next state. 

 

 

 

 

 

 

 

 

 

 

 

 

 

Configuring OneSight Voice Quality - Basic Profile Monitors 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Configuring OneSight Voice Quality - Basic 

Profile Monitors 

You can set up a OneSight Voice Quality - Basic Profile monitor to 

collect voice quality metrics. The originate and answer VQ Probes 

must be installed and connected to OneSight. Refer to the VQ Probe 

documentation for information about installing the VQ Probe, and 

“Chapter 16” of this guide for information on configuring the VQ 

Probe in OneSight. 



Note: If you modify a monitor when a call is in progress, the call in 

progress may be terminated when the modification is applied. This 

applies to all modifications, including changes to the sample 

frequency. 


Quality - Basic in the Monitor Types box, settings to configure a 

OneSight Voice Quality monitor appear on these dialog box tabs: 

General Tab – Contains the options that you can use to define the 

system identification and authentication settings for a OneSight 

Voice Quality - Basic Profile monitor for your monitor group. 











this monitor. 




of the host and the OneSight Voice Quality - Basic Profile metric. 

To change the default assigned name, type a unique monitor name 

that helps you to identify what this monitor does. 



To create a OneSight Voice Quality - Basic Profile monitor: 


dialog box. 



Quality - Basic. 

Use the options on this tab to configure the monitor. The dial 

numbers listed in the drop downs are those that were configured 

using the VQ Probe configuration page. The VQ Probe 

configuration page can be accessed by clicking the Edit Config 

buttons. 

Originate Probe – Select the VQ Probe that will place the call. 

Edit Config – Displays the VQ Probe configuration dialog box 

for editing the selected probe. 



Extension Usage – Displays the list of extensions assigned to 

this probe and indicates whether they are in use or not. If they 

are in use, the dialog box displays which monitor is using the 

extension and whether it is being used as an originate or answer 

extension. 

Originate Extension – Select the phone number corresponding to 

the VQ Probe channel that will place the call. Once an 

extension has been used as an originate extension, it cannot be 

used as an answer extension for any Voice Quality Basic 

monitors. It can; however, be used as an originate extension for 

other Voice Quality Basic monitors. Only extensions that are 

available for use as originate extensions are displayed in the 

list. 

Answer Probe – Select the VQ Probe that will answer the call. If 

you are using an alternative dial number, you can also select 

from the top of the list to let the answering number 

determine which probe answers the call. 

Edit Config – Displays the VQ Probe configuration dialog box 

for editing the selected probe. 

Extension Usage – Displays the list of extensions assigned to 

this probe and indicates whether they are in use or not. If they 

are in use, the dialog box displays which monitor is using the 

extension and whether it is being used as an originate or answer 

extension. 

Answer Extension – Select the phone number of the Answer 

Probe. If you are not using an alternative dial number, this is the 

number that the Originate Probe will dial. If you are using an 

alternative dial number, it is the number dialed by the Originate 

Probe. Only extensions that are available for use as answer 

extensions are displayed in the list. If you have selected 

in the Answer Probe field, no numbers will be available for 

selection. 



Once an extension has been used as an answer extension, it 

cannot be used as an originate extension for any Voice Quality 

Basic monitors. It can; however, be used as an answer 

extension for other Voice Quality Basic monitors. 

Alternate Dial Number – Select this check box if an alternative 

dial number is being used to call agents. When checked, 

is added to the top of the Answer Probe dropdown list. Refer to 

“Chapter 16” for a description of the possible configurations. 

– Select the dial number to use. 

Edit Dial Numbers – Displays the VQ Configuration For Dial 

Numbers dialog box and imports the list. 

Sample Every: Advanced– Specifies how often 

samples are taken for this monitor. Refer to, ―Sample Every 

Settings,‖ later in this chapter for a description of these settings. 

Note: The sample frequency for Voice Quality Basic monitors 

cannot be less than five minutes. 








Quality specifications you supply, or you can type in your own 


4. Select the originate VQ Probe and its extension. 

5. Select the Alter. Dial Number check box if you are using an 

alternative dial number and select the number to use. You can 

configure and import the list of dial numbers by clicking the 

Edit Dial Numbers button. 


Configuring OneSight Voice Quality - Advanced Profile Monitors 

6. Select the answer VQ Probe and its extension. 

7. Select the CallMaster script to use or click Import to import a 

script. 

8. Enter how often to sample this monitor. 





Note: System monitor output is not displayed when a G5 or 

FX/TDM system originates the call. 


save these basic OneSight Voice Quality - Basic Profile 

monitor settings. You can now add this monitor to a monitor 

group. Refer to Adding Monitors to a Monitor Group in 

Chapter 4. 

Configuring OneSight Voice Quality - Advanced 


The OneSight Voice Quality - Advanced Profile Monitor lets you 

collect script metrics, such as IVR Response Time steps, and 

combine them with Voice Quality metrics when a VQ Probe Icon is 

included in the CallMaster script. A VQ Probe icon can be added at 

the end of an existing OneSight Voice Transaction script or you can 

add additional telephony icons to the VQ Probe Originate Call 

sample project. 

If you are modifying the sample project and if you are navigating 

through an IVR, you can enter the IVR data in the Navigate IVR 

diagram. Refer to the Hammer CallMaster documentation for more 

information about creating scripts. 



If you have your own CallMaster server, you can create a OneSight 

Voice Quality - Advanced Profile monitor in OneSight to verify the 

performance of your telephony-based voice transaction systems. 

The originate and answer VQ Probes must be installed and 

connected to OneSight. Refer to the VQ Probe documentation for 

information about installing the VQ Probe, and “Chapter 16” of 

this guide for information on configuring the VQ Probe in 


Note: The Hammer CallMaster server and the proxy server must be 

version 5.4 or later. 

The OneSight Voice Quality - Advanced Profile monitor lets you 

select which steps you want to test in the script. 

The OneSight Voice Quality - Advanced Profile monitor retrieves 

data for the monitors you have configured within your OneSight 

Voice Engine. 


Quality - Advanced Profile in the Monitor Types box, settings to 

configure a OneSight Voice Quality - Advanced Profile monitor 



OneSight Voice Quality - Advanced Profile monitor for your call 

center. 




Voice Quality - Advanced Profile monitor. You can also configure 

how an alert will affect the monitor group’s health. It can result in a 



the CallMaster script will run. 













this monitor. 












this profile. 

Note: When you modify alerts for OneSight Voice Quality - 

Advanced Profile monitors, you must select Override profile in the 

Alert Editor to make the fields available. Any changes that you 

make will apply to this monitor only, not to the profile itself. 

To create a OneSight Voice Quality - Advanced Profile monitor: 




dialog box. 



Quality - Advanced to add a monitor that checks the availability 

and responsiveness of a selected monitor from the OneSight 

Voice Transaction service. You will use settings on the General 

tab to configure a OneSight Voice Quality - Advanced Profile 

monitor. 

Script – Displays the script being used. 

Import – Displays the Import CallMaster script dialog box for 

selecting the script you want to use. 

Note: If you are using the phonebook on a Hammer G5, and you 

update the phonebook, the new numbers will not take effect 



until you click OK on the VQ Probes configuration page in 




Parameters – Displays the Input Parameter dialog box for 

entering an input parameter. For example, if you have a script 

that needs to place a call, you can enter one or more numbers in 

the input parameter list. This button is only available when the 

script requires input parameters. 

Voice Resource – Displays the Voice Resource Editor dialog 

box for specifying the CallMaster servers and channels to use 

as voice resources. 

Scenario Name – Specifies the name of the scenario. 

Retries – Specifies the number of times to retry the script if the 

script fails. 











Transaction specifications you supply, or you can type in your 


4. Click the Import button to display the Import CallMaster script 

dialog box. 



Script – Enter the script path or click Browse. 

Browse – Displays the Choose File dialog box for selecting a 

script. 

5. Select the script and click OK. 

This dialog box lets you select the script steps you want to test 

and select the units to use to evaluate the script steps. 

Check All – Selects all of the script steps. 

Uncheck All – Deselects all of the script steps. 

– Click the check box in front of the steps that you 

want to test. 

– Select the units to use to evaluate the steps. 

6. Select the steps that you want to test and click OK. 



7. If the script requires input parameters, the number of 

parameters required is shown in the Parameters field. Click 

Input Parameter to display the Input Parameter Editor. 

This dialog box lets you configure parameters particular to this 

script. The columns displayed are based on the script’s 

requirements. 

Add – Displays the Input Parameter Editor for entering 

parameters that pertain to this script. 

Modify – Displays the Input Parameter Editor for modifying the 

selected parameter set. 

Remove – Deletes the selected parameter set. 

Add from CSV file – Displays the Upload Input Parameter dialog 

box for adding parameters from a Comma Separated Value file. 

The file must be set up so that the first line of the file contains 

the column names, the second line contains the type of data, 

and the third line contains the default values. The input 

parameter data should start on the fourth line and each line 

should only contain one set of input parameter data. Data 

should be surrounded by double quotes. 

Parameters – Displays the configured parameters. 

8. The Input Parameter Editor shows the input parameters that it 

needs. In the example above, the script needs a phone number 

and digit. Click Add to add a parameter. 



Or click Add from CSV file to upload the parameters from a 

Comma Separated Value file. The file must be set up so that the 

first line of the file contains the column names, the second line 

contains the type of data, and the third line contains the default 

values. The input parameter data should start on the fourth line 

and each line should only contain one set of input parameter 

data. Data should be surrounded by double quotes. 

9. Enter the parameters or select the file and click OK. 

10. You can add multiple parameter sets. When you are finished 

adding parameters, click OK. 



11. Click Voice Resource to display the Voice Resource Editor for 

selecting servers and channels to use as voice resources. 

Add – Displays the CallMaster System Editor for adding a 

CallMaster server and for configuring voice groups for the 

server. 

Modify – Displays the Edit CallMaster System dialog box for 

editing the selected system. 

Remove – Deletes the selected system. 

CallMaster Server Name – Displays the configured CallMaster 

system names. 

Port – Displays the CallMaster system port being used. 

Available Voice Group – Displays the voice groups that are 

available for the selected system. 

Selected Voice Group – Displays the voice groups selected for 

testing. 



12. Click Add. 

CallMaster Server Name – Enter the CallMaster server name. 

Port – Enter the port to use. 

About CallMaster – Displays the minimum required CallMaster 

version and the current version and build numbers. 

Add – Displays the Voice Resource Editor for configuring a voice 

group. 

Modify – Displays the Voice Resource Editor for modifying the 

selected voice group. 

Remove – Deletes the selected voice group. 

13. Enter the CallMaster server name and its port that you want to 

use. 



14. Click Add to add a voice group or click OK to return to the 

Voice Resource Editor. If you click Add the following dialog 

box is displayed. 

This dialog box lets you configure voice groups. 

Voice Group – Enter the name of the voice group. 

Channels – Select the channels that you want to include in the 

voice group. 

15. Select the channels you want to use and click OK. 

16. In the Voice Resource Editor select the system and voice 

groups that you want to use and click OK. 




Configuring WMI Monitors 




save these basic OneSight Voice Quality - Advanced Profile 

monitor settings. You can now add this monitor to a monitor 

group. Refer to Adding Monitors to a Monitor Group in 

Chapter 4. 


You can set up a Windows Management Instrumentation (WMI) 

monitor to provide in-depth information about the configuration, 

status, and operational aspects of a Windows operating system. 

WMI is similar to Perfmon, however, it offers more information 

about the machine being monitored. 

Note: The WMI monitor requires a Remote Agent or Network Data 

Collector that has access to the machine being monitored. 

In the Add Monitor dialog box, when you click WMI in the Monitor 

Types box, settings to configure a OneSight WMI monitor appear 


System Tab – Contains the options that you can use to define the 

system identification and authentication settings for a WMI monitor 

for your monitor group. 

Object Tab – Specifies the object configuration for a specific WMI 

Metric. 



WMI alert will affect the monitor group’s health. It can result in a 



the WMI monitor checks a specific metric. 















this monitor. 




of the host and the WMI metric. To change the default assigned 

name, type a unique monitor name that helps you to identify what 

this monitor does. 

To create a WMI monitor: 

1. On the Monitors Page, click Add to open the Add Monitor dialog 

box. 




can be applied to your monitor group. Click WMI to add a 

monitor that will measure the performance of a specific WMI 

metric on a single machine. 

Use the options on this tab to specify the Windows machine to 

be monitored. 





System Identification – Configure these settings to specify the 

Windows machine that will report the WMI metric. 

DNS Name – Specifies the DNS name of the computer. 

NetBIOS name – Specifies the NetBIOS name, or Windows 

computer name, for this machine. 



Authentication – Configure these settings when a OneSight Data 

Collector or Remote Agent is not running on the system being 

monitored. 

User Name – Specifies the logon name that will provide 

access to the monitored machine. The user name and 

password that you specify must have administrative 

privileges on the monitored machine. 

Password – Specifies the password associated with the user 

name you supply. The user name and password that you 

specify must have administrative privileges on the monitored 

machine. 

Domain – Specifies the domain or machine name of the user 

name account. 

Test – When you add or modify a monitor, you can test System 





let OneSight create a unique name using the WMI specifications 




4. On the System tab, type in the DNS name, NetBIOS name, user 





is not required. Click the Object tab. 

Use the options on this tab to specify the WMI metric to be 

monitored. 

Use these settings to designate which WMI metric you want to 

check. To complete this information, click Discover WMI Metrics 

to find available metrics. WMI discovery is iterative. The first 

time you click Discover WMI Metrics, the top-level properties 

and their child classes are discovered. Select what you want to 

monitor and click Discover WMI Metrics again. Repeat this 



process until you have discovered the metric you want to 

monitor. 

Namespace – Specifies the name space, for example: root\cimv2 

(the default). Data in the WMI repository is organized by 

schemas, which are loaded into ―namespaces.‖ A namespace 

provides a domain (or container) for a schema and for the 

instances of the classes in that schema. 

Select – Specifies the name of the metric, for example: 

FreeSpace. 

From – Specifies the class name, for example: 

Win32_LogicalDisk. 

Where – Specifies the key name and value, for example: 

Name=”C:\”. 

Perl Expression – Enter a Perl Expression for parsing the results 

when the results either contain non-numeric data or you only 

want part of a numeric result. Refer to “Using Regular 

Expressions for Pattern Matching,” later in this chapter for 



collected. 


metric measurement is expressed in kilobytes, setting Scale to 


expressed in milliseconds, setting Scale to .001 will translate it 

to seconds. 

Translation Type – Translation Type controls how a metric’s 

data is displayed on the Alerts page and in Reports. 

No Translation – OneSight will present the data as it is 




Rate (minutes) – OneSight will present the data as a number, 

per minute. For example, if the time interval between two 

samples was 10 minutes, and 50 errors were found, the Rate 

(minutes) would be five (5) errors per minute. 



does not return data this way, use No Translation. 

Unit Measure – To define a Unit Measure, click the arrow to 

select a unit measure (%, bytes, hours, minutes, seconds). You 

can also type in a unit measure such as messages/minute. This 

measure is a display string. It does not perform any data 

translation. 




Discover WMI Metrics – Finds the available metrics and 

populates the result tree. WMI discovery is iterative. The first 





monitor. 

Note: Discovery may take several minutes. 




data. If you are measuring a WMI object representing a String 

datatype, it can be converted to a number for use in OneSight 

by using the String Mappings field. Simply specify a 


example, ―false=0;true=1‖; will convert a ―false‖ reading to 

a 0 value in OneSight, and this will be displayed in OneSight 



Status as ―false=0‖. If you only want to display the string on 

the OneSight status page, use a colon, rather than a semicolon 









5. On the Object tab, use the settings to designate which WMI 

metric you want to check. To complete this information, click 

Discover WMI Metrics to discover the available metrics and 

populate the result tree. WMI discovery is iterative. The first 





monitor. 

6. Enter a Perl Expression if needed. Refer to “Using Regular 

Expressions for Pattern Matching,” later in this chapter for 


7. Modify the sampling parameter and string mappings as needed. 






save these basic WMI monitor settings. You can now add this 




Sample Every Settings 



taken for this monitor. Select the unit of time to use for the 

sampling interval: seconds, minutes, or hours. You can specify 

sample intervals to occur regularly, hourly, or daily. 

To Sample Interval Value Example 

Regularly integer 3 sample very three 

units 

Hourly 

Daily GMT 

@ 

@ 

@ 

@ 

60@24 sample every 

hour at minute 24 

3@ sample every 

three hours at any 

minute 

1@12:15:34 sample 

once a day at 

12:15:34 

@12:15:34 sample 

once a day at 

12:15:34 

To sample at regular intervals, specify a simple integer value 

and select the appropriate units. For example, to sample every 5 

minutes, enter 5 and select minutes. OneSight selects a random 

time to take the first sample that is shortly after configuration or 

startup, and from then on samples every 5 minutes. 

To sample at a specific time every hour, specify the value as 

@. For example, to sample every hour at 

quarter past the hour, enter 1@15. 



To sample at a specific time every day, specify the value as 

24@. For example, to sample once a day at 

quarter past eleven (local time on the server machine), enter 

24@23:15:00. The first sample occurs at the time specified. 

To allow the different states to specify longer times, the 

individual states can specify a specific minute within an hour 

and a specific time within a day by using the extended syntax of 

@. The general form is 

[@[(|]. The presence of 

the @ symbol in the state specification causes the units in the 

select dropdown to be ignored and the frequency number is 

assumed to be hours. 

For example: 

4@ – Sample every 4 hours (any minute) 

3@24 – Sample every 3 hours at minute 24 

72@12:15:34 – Sample every 72 hours(or 3 days) at 

12:15:34 

For a daily interval, you can use the format 24@hh;mm:ss. The 

interval is 24 hours and the hh specifies the number of hours 

after midnight Greenwich time. 

You can also specify different sampling intervals based on the 

sample’s state using the following syntax: 

or ; or 

;;. Separate each state interval 

by a semi-colon. Each state interval must share the same unites. 

For example, 30;20;15 minutes samples every 30 minutes when 

in a good state, every 20 minutes in a warning state, and every 

15 minutes in a critical state. If two states are the same one can 

be omitted. For example, 30;;15 minutes samples every 30 

minutes in good and warning states, and every 15 minutes in a 

critical state. The format 30;20 minutes samples every 30 



minutes in a good state, and every 20 minutes in the warning 

and critical states. A single interval value applies to all three 

states. 

Advanced Sample Frequency Settings 

Select the unit of time to use for the sampling interval; seconds, 

minutes, hours or days. To sample at regular intervals, specify a 

simple integer value in the Sample Every text field and select the 

appropriate units. For example, to sample every 5 minutes, enter 5 

and select minutes. 

Good State, Warning State, Critical State – The advanced dialog has 

three state options: Good State, Warning State, Critical State. Each 

of the three states have their own frequency. If one of the state 

specification is missing, then is uses the state frequency 

specification for the prior state: 

Warning State unchecked: use the Good State frequency for 

Warning State 

Warning State checked but Critical State unchecked: use the 

Warning State frequency for Critical State 

both Warning State and Critical State unchecked: use the Good 

State frequency for Warning State and Critical State 

No Specific Minute – Select hours as the unit. Sample every specific 

hours(any minute) for this monitor. For example, to sample every 5 

hours at any minute, enter 5 in the Sample Every text field, select 

hours as the units and check No Specify Minute radio. 

At Minute – Select hours as the unit. Sample every specific hours at 

specific minute for this monitor. For example, to sample every 5 

hours at quarter past the hours, enter 5 in the Sample Every text 

field and select hours as the units, check At Minute radio and enter 

15 in the text filed besides At Minute radio. 


Exporting and Importing Monitors 

No Specific Time – Select days as the unit. Sample every specific 

days(any time) for this monitor. For example, to sample every 5 

days at any time, enter 5 in the Sample Every text field, select days 

as the units and check No Specify Time radio. 

At Time – Select days as the unit. Sample every specific days at 

specific time(hh:mm:ss) for this monitor. For example, to sample 

every 2 days at 12:15:34, enter 2 in the Sample Every text field and 

select days as the units, check At Time radio and in turn enter 12, 

15, 34 in the text fields besides At Time radio. 


You can export and import data from the General tab for most 

dedicated monitors via a comma-separated value (.CSV) file. This 

lets you: 

Input monitor configurations in a CSV file and create the 

monitors by importing the file. 

Export monitor configurations to a CSV file and copy them to 

another system. 

The first row of the CSV file is used for the column names. These 

column names correspond to the field names on the General tab. 

They will vary based on the type of monitor. For example, the CSV 

file for a Ping monitor would look like the following picture when 

opened in Microsoft Excel: 

Only one type of monitor can be exported or imported at one time. 

To obtain the file names for a particular monitor type, export a 

monitor of that type. You can then edit the file in a text editor or in 



Exporting Monitors 

Microsoft Excel. If you are deleting a row in the file, delete the entire 

row. Make sure to save the file as CSV. 

The following monitor types can be imported or exported: Database, 

DNS, Event Log, FTP, JMX, Logfile, Directory, Mail, OneSight Probe, 

OneSight Virtual Agent, Perfmon, Ping, Port, Process, Service, SNMP, 

SNMP Trap, TCP/IP Socket, URl, and WMI. 

Note: If you have exported monitors with file names that begin with 

a dash (―-―), Microsoft Excel assumes that they are formulas and 

displays them in the format ―#NAME?‖. If you modify the CSV file 

and save it, the monitor names are saved as ―#NAME?‖ formatted 

as text. To avoid losing the original file names, format all of the 

monitor name cells as text before modifying and saving the file. 

To export monitors: 

1. Click the Import/Export button on the General tab of a The 

Import Export Monitors dialog box is displayed. 

The type of monitor that you are importing is displayed under 

the Choose action for this monitor type Prompt. This dialog box 

has the following options: 

Choose action for this monitor type – Select whether you want to 

import or export monitors. 



Importing Monitors 

Import from a File – Select this option to import monitors. 

Browse – Enter the file to import or click 

Browse to navigate to it. It must be a CSV file. 

Export to a File – Select this option to export all monitors of the 

displayed type. 

Import – Imports the selected file. 

Export – Exports the selected monitor types. 

2. Select Export to a File. 


4. Click Save. The File save dialog box is displayed when the 

export is finished. 

5. Enter the file name to use. 

To import monitors from a CSV file: 

1. Click the Import/Export button on the General tab of a monitor 

of the type that you are importing. The Import Export Monitors 

dialog box is displayed. 


Configuring a Profile Monitor 

The type of monitor that you are importing is displayed under 

the Choose action for this monitor type Prompt. This dialog box 

has the following options: 

Choose action for this monitor type – Select whether you want to 

import or export monitors. 

Import from a File – Select this option to import monitors. 

Browse – Enter the file to import or click 

Browse to navigate to it. It must be a CSV file. 

Export to a File – Select this option to export all monitors of the 

displayed type. 

Import – Imports the selected file. 

Export – Exports the selected monitor types. 

2. Select Import from a File. 

3. Enter the name of the file or click Browse to display the Choose 

file dialog box for selecting the file. 

4. Click Import. When importing is finished, the Import Export 

Monitors dialog box is displayed show the results of the import. 


When you want to monitor a web component such as an IIS server, 

an Oracle database, NT operating system, or UNIX operating 

system, OneSight provides a ―profile,‖ that is, a default set of 

performance criteria so you can monitor performance of various 

critical functions carried out by that component. The list of profile 

monitors can include default profiles shipped with OneSight as well 

as any other profiles you create yourself. 



To create a monitor for a web component such as an Oracle 

database, you choose the Oracle profile monitor and apply it to a 

specific system on which an Oracle database is maintained. When 

you configure a profile monitor, you direct OneSight to monitor the 

specified type of web component on the specified computer. 

When you create a profile monitor the Monitor Creation Wizard 

requests the required discovery information to successfully apply 

the profile. 

In addition to creating one monitor at a time, you can apply a 

profile to multiple systems to create several monitors at once. When 

you do this, discovery information is not requested. The profile is 

applied to the systems regardless of the configuration of the 

systems. For this reason, it is recommended that you apply a profile 

to multiple systems immediately following multiple system 

discovery. Refer to Chapter 7 for information on multiple system 

discovery. 

What You Need to Know About Your System 

To set up a profile monitor, system-specific information must be 

entered for each machine that uses the profile. As you create a 

profile monitor, you will need to identify the systems and describe 

their properties, including the following: 

Machine identification information. For example, to monitor an 

NT operating system on a specific machine, you will need to 

supply an IP address or network name. 

Identification of components on a machine. For example, you 

must identify each disk on a machine that has multiple disks if 

you want to monitor disk space on all of them. 

The appropriate access information for the monitored system. For 

example, Perfmon user name and password information must be 

provided to allow access to the monitored systems. 



For database monitoring, appropriate database configuration for 

the OneSight server. For example, to monitor an Oracle database 

using the JDBC-ODBC Bridge for Oracle, you must provide the 

connect string, the name of the database, and user name and 

password information. You must also install the Oracle client on 

the OneSight server if it is not already present. 

Note: OneSight provides system profile information for each profile 

monitor, but system-specific information must be entered for each 

machine. For example, if you are monitoring an Oracle database, it 

must be added to the system. As you create a system monitor, you 

will need to identify the systems and describe their properties. 

To create a profile monitor: 

1. In the Monitors Page, on the Monitors tab, click Add. 



2. In the Add Monitor dialog box, the Monitor Types box lists all 

of the types of monitors that can be applied to your monitor 

group. Click a profile monitor, such as Oracle or Microsoft 

Windows NT, 2000. (These are listed alphabetically in a group 

following the list of dedicated monitors and have a specific 

icon: .) 

Use options in the Add Monitor dialog box to view the metrics 

and data sources configured for this profile. The right side of 

the Add Monitor dialog box describes this profile, lists its 

metrics and the data sources used by these metrics. 

Profile Manager – Opens the Profile Manager, where you control 

which profiles are available for creating profile monitors. You 

can modify existing profiles, and you can create your own 



profiles, either from scratch or by cloning an existing profile 

and modifying it. 

Profile – Displays the type of profile selected. 

Description – Describes what the profile does. 

Data Sources – Lists the data sources used by the metrics in the 

metric list for this profile. 

Metrics – Lists the metrics in this profile. 

3. Select the profile you want to use and click Next to start the 

Monitor Creation Wizard for selecting a system that you want 

to monitor with this profile’s metrics. Refer to “Applying a 

Profile to Multiple Systems” if you are applying the profile to 

more than one system. 



New System – Select this option to add a system that is not in 

the Existing System list. 

Name – Enter the name or IP address of the system. 

Location – Select the location to use. 

Existing System – Select this option to use an existing system. 

Show Systems – Lets you filter the list of systems that are 

displayed. 

Systems – Lists the existing systems. 

IP Address – Displays the system’s IP address. 

Discovered – Indicates whether components have been 

discovered for this system. 

4. To add a profile monitor for a particular machine, the machine 

must appear in the Existing System list. For example, to create 

a monitor for a web component such as an Oracle database, 

select a specific machine on which an Oracle database is 

maintained. Click the system you want to monitor with that 

profile’s metrics 

If the system that you want to monitor is not in the Existing 

System list, you must add it: 

Click New System. 

Type the System Name that identifies this machine. This 

name must be in the DNS table for your network. 




If system components have previously been discovered, this 

dialog box lists all of the components relevant to this profile. 

Discover – Click this button to discover components on the 

selected system. 

Check All – Selects all components for monitoring. 

Uncheck All – Deselects all components for monitoring. 

6. If components have not been discovered for this system click 

Discover. 

If you click Discover, the Setup Discovery Dialog box may be 

displayed asking for information needed to access the system. 

The information requested depends on the type of data source 

being used. 



Setup Discovery for SNMP – SNMP finds interfaces by using RFC 

1213 (MIB II). To use SNMP to find processes and hardware, 

the system must support the Host Resources MIB. 

Community – Specify the SNMP community string used for 

the machine you want SNMP to examine. For many devices, 

the default community string is public. 

Timeout seconds – Specifies the amount of time (in seconds) 

to wait for an SNMP reply. If Timeout Retries is greater than 

0 and a reply is not received, a retry attempt is made. For 

each subsequent retry, the timeout value is doubled. For 

example, if Timeout Seconds is 5 and Timeout Retries is 2, 

the first request attempt will occur after 5 seconds, the 

second attempt will occur after 10 seconds, and the third 


timeout period equals 35 seconds. If there is no response 

after this time, a Sample Failure is triggered. 

If Timeout Retries is 0, a Sample Failure is triggered when a 

reply is not received in this amount of time. 

Timeout retries – Sets the upper limit for the number of times 

an SNMP request is retried. For example, if Timeout Retries 

is set to 3, the SNMP request will be sent up to four times (the 

initial try plus three retries). 



Version – Specifies the SNMP version. 

Setup Discovery for Virtual Agent 

Connection Method – Select the connection method to use for 

the Virtual Agent. 





OneSight will attempt to infer the prompt by parsing the 

screen output. 

Charset – Specifies the character set to use. Select a character 

set from the list. 


languages such as Basque, Catalan, Danish, Dutch, 

English, Faeroese, Finnish, French, German, Icelandic, 

Irish, Italian, Norwegian, Portuguese, Rhaeto-Romanic, 

Scottish, Spanish, Swedish, Albanian, Afrikaans, and 

Swahili. 



languages. 











languages, similar to ISO 8859-1 with the Icelandic 

letters replaced with Turkish letters. It is also used for 

Kurdish. 









Windows 1250 – Microsoft Windows Code Page for 

Central European Latin alphabet languages. 


Russian and other Cyrillic languages. 


Western European languages. 


Greek. 


Turkish. 


Baltic. 


Port – Specify the port to use for connecting. 

Operating System – Specify the type of operating system. 

User Name – Specify a user name to log into an account on 

the host system. 



Password – Specify the password required to log into the 

User Name account on the system. 

Login Timeout (ms) – Specify the number of milliseconds to 

wait before timing out when logging in. 

Discovery Timeout (ms) – Specify the number of milliseconds 

to wait before timing out when doing discovery. 

Debug Mode – Specify whether to use debug mode. 

Setup Discovery Windows NT 

User name – Enter the user name for a system account that 

has rights to read the NT Windows Registry. 

Domain – Specify the domain name of the Windows NT 

machine. 

Password – Specify the password required by the system 

when logging in with the user name specified in the User 

Name box. 

Setup Discovery for Database 

Driver – Select a driver type from the list: jTDS JDBC Driver 

for Microsoft SQL Server, Inet Sprinta JDBC driver for 

Microsoft SQL Server, Oracle Thin JDBC driver, Sun 

JDBC:ODBC Bridge, DataDirect JDBC Driver for Microsoft 

SQL Server, or Custom. You must have the appropriate driver 

installed on the OneSight Server to discover database 

components. 

Driver String – This information will vary depending on the 

type of database that you are monitoring. If you selected any 

option other than Custom, the appropriate string is 

automatically displayed. For example, this is the string for 

the Oracle Thin JDBC driver: 




If you selected a Custom driver type, you can type in the 

Driver String yourself. 

Instance – Specify the SQL server instance. 


selected. For example, the default port for an Oracle Thin 

JDBC driver is 1521. Modify the port number if necessary. 

This is not required for a JDBC:ODBC or Custom driver 

setting. 

User name – If a user name and password are required for 

access to the database, enter the user name here. The user 

must have system administrator privileges. 

Password – If a user name and password are required for 

access to the database, enter the password here. 

Enter the information and click OK. 

If no additional information is required, the Discovery Status 

dialog box is displayed. 

Click Close to exit the Discovery Status dialog box. 

7. Select the components you want to monitor and click Finish to 

create the monitor. 

8. If one or more of the profile metrics cannot be applied, the 

Monitor Editor opens to show you the profile metrics that are 

not configured. This icon indicates that the metric could not be 

applied to the system component it is meant to monitor: 

The Metrics list shows all of the metrics that this profile uses to 

monitor a system. When you select one of the profile metrics, 

the System Components list shows the system components that 

the metric will monitor. 



If you select an unapplied metric, the System Components list 

indicates that you have not configured this type of component 

as part of your system definition. 

9. To add the missing components to your system definition, click 

the System Editor button. 

In the Components box, click a missing component and then 

click Add, which opens the Add System Component dialog 

box. 

In the Add System Component dialog box in the Add New 

Component section, the Type list defaults to the kind of 

component you are adding. In the Component box, specify a 

meaningful name that allows you to identify the specific 

component you are adding. Then click OK to return to the 

Add Missing Components dialog box. 

The newly added component appears in the Components list. 

Select this component and click Add Data Source to configure 

the data sources that OneSight metrics can use to obtain 

information about this system component. 

For information about the Properties tabs used for each type of 

component, see Chapter 7. 

10. Repeat step 9 to add information about each of the system 

components that is missing. Then click OK to return to the 

Monitor Editor. 

11. You can now add this monitor to a monitor group. Refer to 

Adding Monitors to a Monitor Group in Chapter 4. 

Applying a Profile to Multiple Systems 

When applying a profile to multiple systems, discovery information 

is not requested as it is when you apply a profile to only one system. 



The profile is applied to the systems regardless of the system 

configurations. 

To apply a profile to multiple systems: 

1. In the Monitors Page, on the Monitors tab, click Add. 

2. In the Add Monitor dialog box, the Monitor Types box lists all 

of the types of monitors that can be applied to your monitor 

group. Click a profile monitor, such as Oracle or Microsoft 

Windows NT, 2000. (These are listed alphabetically in a group 

following the list of dedicated monitors and have a specific 

icon: .) 


Using Regular Expressions for Pattern Matching 

3. Select the profile you want to use and click Next. 

4. Using the shift key, Shift-Click on the systems to which you 

want to apply this profile and click Finish to create the 

monitors. 


You can use Perl-style regular expressions to match for content in the 

following areas of OneSight: 

When defining good string absence and bad string presence for 

the URL monitor. 

Database and Log File query pattern matching in the Alert Editor. 



When collecting metric performance data from a log file using 

the Log File Monitor. 

When collecting metric performance data from a command line 

program using the OneSight Virtual Agent Monitor. 

For example, you can use /mytext \d\d/ to match any appearance of the text 

―mytext‖ followed by two digits. Entries that start and end with a slash 

(―/‖), plus a few optional modifiers, are recognized as regular expressions. 

Modifiers after the ending slash affect the kind of matching performed. 

You can combine modifiers, for example, ―/pattern/ic‖. 

/my string/s – Treats input as a single line containing newline 

characters, and performs a match on this input. 

/my string/x – Enables the use of regular expression extensions 

in Perl. 

Defining Expressions for Good Strings and Bad Strings 

You can specify expressions for good string absence and bad string 

presence alerts for the URL monitor. Using expressions for these strings 

will give you more flexibility in defining the strings while producing 

meaningful information when an alert is displayed on the status page or in 

an e-mail notification. For example, add this bad string search for a URL 

monitor: 

/Server down:*\n/ 

The bad string search that locates ―Server down:‖ will include this string 

and all other text displayed before the newline: (*\n). The Alert that is 

displayed on the OneSight status page will include the entire line. 

Defining Expressions for Metric Performance Data 

Using the Log File Monitor 

Some applications publish performance data to a text log file. Using the 

Log File Monitor, you can specify Perl expressions to collect 



performance data from a log file entry. This data can then be used within 

OneSight, both for alerting, using threshold alerts, and reporting. When 

specifying a Perl Expression to gather performance data, parentheses are 

used within the expression to delimit the numeric data to return. 

Log File Entry Modifier Results 

There are 100 bytes free /([0-9]+) bytes free/ 100 

3/05/01 11:03 AM 5.21 seconds /M (.*) seconds/ 5.21 

Defining Expressions for Metric Performance Data 

using the OneSight Virtual Agent Monitor 

Perl expressions are used to parse the output of a command line program 

and return the desired metrics using the OneSight Virtual Agent 

Monitor. This data can then be used within OneSight, both for alerting, 

using threshold alerts, and reporting. When specifying a Perl Expression 

to gather performance data, parentheses are used within the expression to 

delimit the numeric data to return. 

Command Expression Results 

echo 5 ^\w+\W+([0-9]+) 5 

vmstat 1 2 / (?:\S+\s+){4,4}([0-9]+)/ Any value in the Free 

Memory column of the 

vmstat program output 

(e.g. 661552.0). Note that 

the OneSight Virtual 

Agent returns the value 

on the last line of the 

program output that 

matches the expression. 



df -k 

/^[^F](?:\S+\s+){4,4}([0- 

9]+)%\s+(\S+)/ 

Any percentage value in 

the Capacity column of 

the Filesystem data 

returned by the df 

program output (e.g. 

3.0%). 

The OneSight Virtual Agent monitor includes several pre-defined 

OS/Program/Perl expression definitions for common metrics accessible 

using command line programs available with several versions of UNIX. 

You can also define custom settings in the Virtual Agent. 

The perl expressions are evaluated as follows: 

Subpattern 

^ 

Description 

Beginning of the line. 

( ) The part of the expression to return. 

\S Match a non-whitespace character. 

\s Match a whitespace character. 

(?:\S+\s+) 

Represents a column in the program output. 

Matches one or more non-whitespace character and 

one or more whitespace character. 

{4,4} Match at least 4 times but not more than 4 times 

(min,max). 

[0-9]+ Match one or more occurrences of anything between 

0 and 9. 

More information about using Perl expressions is available at 

www.perl.com. 


Adding Alerts to a Monitor 


One or more alerts are configured for each OneSight monitor. An 

alert does three things: 

Defines a problem condition such as an exceeded threshold or a 





both. 

Ranks the seriousness of the problem. (Critical, Warning, or 

Informational). 

If you are configuring a: 

Dedicated monitor – the alert that triggers a response can be due 

to a crossed threshold or a sample failure, or it can be scriptbased 

(such as the presence of an undesirable text string on a web 

page). 

Profile metric – the alert that triggers a response can be a crossed 

threshold, a sample failure, or a pattern match. 

The exact options available to you in the Alert Editor depend on the 

type of dedicated monitor you are configuring or on the data source 

used by the profile metric you are configuring. 

Note: For profile metrics, the system action plan overrides the 

profile’s alert plan when a system action plan has been configured. 

Refer to Chapter 7. 

Configuring Monitors Alerts Tab 

Use the Alerts tab to define alerts and associate them with action plans. 

The Alerts tab shows the alerts that are currently in effect for the monitor 



and whether they are associated with an action plan. Options on this tab 

allow you to add, clone, modify, or remove alerts for the monitor. 

Note: For Transaction monitors such as Oracle Test for Web 

Application, Oracle OpenScript, and OneSight Voice Transaction 

monitors, alerts cannot be added, cloned, modified, or deleted until 

the monitor has been saved. 

You can also configure how a monitor alert will affect the monitor group’s 

health. It can result in a Warning state, a Critical state, or can have no 

impact on health. 



Note: DNS, Mail, and Service monitors only allow modification of 

the default alerts. New alerts cannot be added for these monitors. 

The default alert, Sample Failure, changes the status of the monitor on 

the OneSight Console to Critical, as indicated by the red diamond. It does 

not, however, trigger any other behavior (the default Respond By option 

is ). If you want to be notified when the status has 

changed, click Modify to associate the alert with an action plan such as 

sending you an e-mail. 

Status – Indicates how the monitor status on the OneSight Console will 

change when this alert occurs. 

Applies to Critical State 


Setting Up an Alert to Trigger an Action Plan 

Applies to Warning State 

Alert Description – Identifies the type of alert that can occur. The default 

alert is Sample Failure. You can also add performance threshold alerts. 

Respond by – Identifies the action plan that will go into effect whenever 

an alert occurs. By default, no action plan is configured. To associate an 

action plan with an alert, click Modify and select an action plan from (or 

add a new one to) the Respond By list. 

Add – Click Add to open the Alert Editor. You can add threshold-based 

alerts to the monitor and associate them with action plans. 

Modify – Click Modify to open the Alert Editor. You can add or select an 

action plan, or change the effect of the alert on a monitor’s health—for 

example, from Critical (red) to Warning (yellow). 

Remove – Select an alert and then click Remove to delete a defined alert 

for this monitor. The default alert, however, cannot be removed. 


The way you open the Alert Editor depends on the type of monitor 

that you are working with: dedicated or profile. 

To open the Alert Editor for a dedicated monitor: 


2. Click Monitor Groups. 


you want to work with and click Modify. 

4. On the Monitors tab, select a dedicated monitor and then click 

Modify. 



5. Click the Alerts tab. 

6. To modify an existing alert, select it and then click Modify. The 

Alert Editor opens. To add a new alert, click Add. The Alert 

Editor opens. 

To open the Alert Editor for a profile monitor: 




2. Click Monitor Groups. 


you want to work with and click Modify. 

4. On the Monitors tab, select a profile monitor and then click 

Modify. 

5. In the Monitor Editor, click the Profile Editor button. 



6. In the Profile Editor, select the metric you want to create an 

alert for under Metrics and click the Add button on the right, in 

the Alerts group box. If you are modifying a metric’s existing 

alert, highlight the metric, then the alert, and click Modify. The 

Alert Editor opens. 

The Alert Editor 

Use the Alert Editor to configure alerts for a OneSight dedicated 

monitor or for a profile metric. Alerts define problem conditions the 

monitor or metric should detect and specify what OneSight should 

do if a problem occurs. The options available to you in the Alert 

Editor depend on the type of dedicated monitor you are configuring 

or on the data source used by the profile metric you are configuring. 

General Tab Main Settings 

Override profile – This field is displayed for OneSight Voice 

Transaction Profile monitors, OneSight Voice Watch Profile 

monitors, OneSight Voice Quality – Advanced monitors, and 

Empirix e-TEST Transaction monitors. Select this option to change 

alerts for this monitor. The profile itself will not be affected. 



Description – Enter a unique description for this alert. This text 

appears on the Status page and the Alerts page if an alert occurs. 

This description is also included in e-mail messages. 

Respond if – Specifies performance criteria 

for the monitored component. If the monitor detects the condition 

defined here, an alert occurs that can trigger a response. 

Notify Once – The response is triggered only once while the 

measured condition is true, regardless of how long the 

measurement stays above the threshold. When the measurement 

drops below the defined threshold (based on Threshold and Trigger 

Response if Samples Out of Samples Crossed Threshold 

settings) the alert is retired. Health is reset to good and any action 

plan that is in effect is terminated. 

Notify Repeatedly – The response is triggered when the measured 

condition is true. The response will continue to be triggered at 

every sample interval for as long as the condition is true. Use the 

Trigger Response if Samples Out of Samples Crossed 

Threshold settings to avoid triggering responses during acceptable 

spikes. 

The settings available in the Respond If list depend on the profile 

metric or dedicated monitor that you are configuring. Use the 

settings to choose under which condition OneSight should trigger a 

response: 

Greater Than Threshold – The response triggered by this setting 

can be an action plan (selected under Respond By), a health reset 

(selected under Apply To), or both. The following graphics show 

notify once followed by notify repeatedly. 



If an action plan is selected in the Respond By list, it is first 

triggered if the metric or monitor measurement is greater than the 

Threshold value. Use the Trigger Response if Samples Out of 

Samples Crossed Threshold settings to avoid triggering responses 

during acceptable spikes. 

If Warning State or Critical State is selected in the Apply To list, 

the monitor’s health will change to warning (yellow) or critical 

(red) when the measurement is greater than the Threshold value 

(based on Threshold and Trigger Response if Samples Out of 

Samples Crossed Threshold settings). 

Less Than Threshold – The response triggered by this setting can 

be an action plan (selected in the Respond By list), a health reset 

(selected in the Apply To list), or both. The following graphics 

show notify once followed by notify repeatedly. 




triggered if the metric or monitor measurement is less than the 

Threshold value. Use the Trigger Response if Samples Out of 

Samples Crossed Threshold settings to avoid triggering 

responses during ―acceptable spikes.‖ 

If Warning State or Error State is selected in the Apply To list, the 

monitor’s health will change to warning (yellow) or critical (red) 

the first time the measurement is less than the Threshold value. 

This value is based on settings for both Threshold and Trigger 

Response if Samples Out of Samples Crossed Threshold). 

Not Equal To – The response triggered by this setting can be an 

action plan (selected in the Respond By list), a health reset 

(selected in the Apply To list), or both. 


triggered if the metric or monitor measurement is not equal to the 






the first time the measurement is not equal to the Threshold 

value. This value is based on settings for both Threshold and 

Trigger Response if Samples Out of Samples Crossed 

Threshold). 



Equal Threshold – The response triggered by this setting can be 

an action plan (selected in the Respond By list), a health reset 

(selected in the Apply To list), or both. The following graphics 

show notify once followed by notify repeatedly. 


triggered if the metric or monitor measurement is equal to the 






the first time the measurement is equal to the Threshold value. 

This value is based on settings for both Threshold and Trigger 

Response if Samples Out of Samples Crossed Threshold). 



Threshold Range – This option lets you enter a range for the alert. 

This eliminates more than one alert being sent when both 

warning and critical thresholds are broken in the same sample 

period. 

Report Sample Failure – By default, every profile metric and 

dedicated monitor has an alert with this Respond If setting. The 

response triggered by this setting can be an action plan (selected 

in the Respond By list), a health reset (selected in the Apply To 

list), or both. You cannot create new Report Sample Failure 

alerts; you can only modify them. 

Acquisition Failure – By default, every profile metric and 

dedicated monitor has an alert with this Respond If setting. By 

default, these are considered warning states. The response 

triggered by this setting can be an action plan (selected in the 

Respond By list), a health reset (selected in the Apply To list), or 

both. You cannot create new Acquisition Failure alerts; you can 

only modify them. 

An acquisition failure is caused by problems that are not related 

to the target of the monitor and do not count against your 

Availability Report. Acquisition failures caused by the failure to 

find a framework will not generate a good state response plan. 

These failures are caused by an incorrectly configured monitor 

and are fixed by reconfiguring the monitor. Acquisition failures 

created by the agent will generate a good state response plan. 



Redirection – This setting only applies to the URL monitor. The 

response triggered by this setting can be an action plan (selected 

in the Respond By list), a health reset (selected in the Apply To 

list), or both. 

The response is triggered if the web server detects that a page 

redirection has occurred. 

Missing Image – This setting only applies to the URL monitor. 

The response is triggered is a web page has a link to an image 

that cannot be found. 

Pattern Match – This setting applies to profile metrics using Log 

File as their data source, and to the Log File, Event Log, and 

string-based Probe dedicated monitors. The response is triggered 

if the string entered under Search String is matched. When you 

select this response type, you can configure specific Pattern 

Match configuration options. 

The response triggered by this setting can be an action plan 

(selected in the Respond By list), a health reset (selected in the 

Apply To list), or both. 

NT Event Log Match – This setting only applies to profile metrics 

using NT Event Log as their data source. When you select this 

response type, you can configure specific NT Event Log Match 

configuration options. 



Apply To list), or both. 

The response is triggered if the NT Event Source, NT Event ID, 

and NT Event Type listed under NT Event Log Settings is found 

in the Windows NT Event Log. 

All of the Event Log criteria that you specify have to be matched 

for an alert to be triggered. For example, if you set up an NT 



Event Source and NT Event ID (and NT Event Type is All NT 

Events), then both NT Event Source and NT Event ID have to 

match. If you set up an NT Event Source, NT Event ID and NT 

Event Type other than All NT Events, then all specifications have 

to match. 

This alert also applies to Windows 2000 systems. 

SNMP Trap – This setting only applies to an SNMP Trap dedicated 

monitor. When you select this response type, you can configure 

specific SNMP Trap match configuration options. 



Apply To list), or both. The response is triggered if the SNMP Trap 

meets the basic Enterprise and Trap Type filter criteria in the 

General tab of the SNMP Trap monitor. 

All of the SNMP Trap criteria that you specify have to be 

matched for an alert to be triggered. For example, if you set up 

Enterprise and Trap Type filter criteria, then the trap message 

must meet both the Enterprise and the Type criteria. If you set up 

an SNMP Trap Search string, then the trap must meet the General 

filter criteria and the Search string criteria. 

e-TEST Transaction Failure – This setting applies to e-TEST 

Transaction monitors. An alert is triggered based on your entries 

and selections in the following fields: 

Test Name Filter – Specify a Perl-like expression that the test 

name must match for an alert to occur. For example, if the 

filter is /.*Succeeded.*/ then an alert fires for the test 

name ―LoginSucceeded‖ but not for test ―MyTM.‖ This test 

does not apply to unnamed tests such as navigation failure or 

timeout. These tests will trigger an alert even if a test name 

is specified. 



Note: If the Test Name Filters are left blank the alert occurs no 

matter on which test the underlying failure occurs. 

Failure Types – Select the type of failures for which you 

want to receive an alert. 

Influences Availability – Indicates if this alert condition 

affects whether the monitor is available. 

Voice Transaction Failure – This setting applies to Voice 

Transaction monitors, Voice Watch Transaction monitors, and the 

script steps in Voice Quality - Advanced profile monitors. This alert 

responds to failures that the OneSight Voice Engine receives from 

the CallMaster Server and that OneSight Voice Watch receives 

from the Voice Watch Server. This alert supports pattern matching 

using a Perl expression, allowing you to associate an action plan 

with a particular error message as described in the “Sample Failure 

and Crossed Threshold Settings” section below. 

Voice Transaction Warning – This setting applies to Voice 

Transaction monitors, Voice Watch Transaction monitors, and the 

script steps in Voice Quality - Advanced profile monitors. An alert 

is triggered if any step in the script returns a warning. 

Critical Voice Quality Score – This setting applies to the MOS and 

PESQ score metrics in the OneSight Voice Quality Basic and 

Advanced monitors. An alert is triggered when the score exceeds 

the threshold settings. 

Low Voice Quality Score – This setting applies to the MOS and 

PESQ score metrics in the OneSight Voice Quality Basic and 

Advanced monitors. An alert is triggered when the score exceeds 

the threshold settings. 

Respond by – Select how you want to respond if the alert condition 

occurs by selecting an action plan from the list box. Options 

displayed in this list box represent previously configured plans. To 

create a new plan for this alert, click . If you don’t 



want an action plan to be triggered in response to an alert, select 

. 

Apply to – Select what the monitor’s health should be when a 

sample cannot be gathered, when a threshold is crossed, when a 

web page is redirected, or when a string match occurs. For example, 

if you select Greater Than Threshold (Notify Once) in the Respond If 

list, Warning State in the Apply To list, and the threshold value is 

exceeded, a Warning state will result and the monitor health icon 

will turn yellow on the Console Status page. If the performance 

measurement drops back down below the threshold, the monitor’s 

state will be reset to good (green). 

Respond by (When Alert Is No Longer in Effect) – You can configure 

an action plan to notify you when an alert condition is no longer in 

effect. This option allows you to receive an e-mail, for example, if a 

previously reported problem has been corrected. Whenever an alert 

associated with a sample failure or an alert for a ―notify once‖ 

threshold returns to a good state after triggering an alert, any 

current alert is retired and a good state alert is triggered. 

Select how you want to respond if the alert condition occurs by 

selecting an Action Plan from the list box. Options displayed in this 

list box represent previously configured plans. To create a new plan 

for this alert, click . If you do not want an action 

plan to be triggered in response to an alert, select . 

If the alert is configured to avoid alerting on acceptable spikes 

(Trigger Response if of Samples...), this response regarding 

the return to a good condition occurs only after the of 

response has been triggered. 

Scope – These options are used to determine when an alert should 

occur when more than one location is being used. 

Alert when locations in alert state – One response plan will be 

triggered when the Nth location has this alert trigger. The 



response plan will be retired when N minus one or fewer 

locations have this alert triggered. Agents will alert. 

Alert when percent locations in alert state – One response plan 

will be triggered when the N percentage of locations has this alert 

trigger. The response plan will be retired when less than N 

percent of locations have this alert triggered. Agents will alert. 

Alert aggregate locations in alert state – One response plan 

will be fired when the aggregated value exceeds the specified 

threshold. This option can only be applied to a threshold alert. 

Agents will not alert. 

Respond by – You can configure an action plan to notify you when 

an alert condition is no longer in effect, that is, when the monitored 

component returns to a good state. Select an action plan or select 

add action plan to display the Action Plan Editor for adding a new 

action plan. 

Time Interval – Select the time interval for which alerts will be 

triggered. 

Sample Failure and Crossed Threshold settings 

Threshold – Enter the value over which OneSight should trigger a 

response. 

Note: Values over eight digits will be displayed in scientific 

notation if you exit the dialog box and re-enter it. For example, 

10,000,000 is displayed as 1.0E7. To make this not occur, change 

the UI.Alerts.FormatThreshold property in the 

OSServer.properties file to true. 

Trigger Response if Samples Out of Samples... 

You can avoid triggering alerts when a single ―spike‖ of poor 

performance occurs. Use of to bypass acceptable spikes for 

alerts configured to notify repeatedly or for sample failures. 



For threshold settings, use the Trigger Response if Samples Out of 

Samples Crossed Threshold. 

For a sample failure, use the Trigger Response if Samples Out of 

Samples Failed. 

For , enter the number of sample counts that must fail or cross a 

threshold before OneSight triggers a response. For , enter a total 

number (a count) of samples. The value of must be a number 

less than or equal to . 

The failures that contribute to this count can be interspersed with 

successful samples. For example, if 3 of 5 samples must fail to 

trigger an alert, a failure for the first, third, and fifth samples and 

successful measurements for the second and fourth samples will 

generate an alert. 

Sampling intervals, or the rates at which information is being 

gathered, are set in the Add Monitor dialog box for dedicated 

monitors, and in the Metric Editor (Agents tab) for profile metrics. 

Example 1 – The alert has the following settings: 

Respond If: Greater Than Threshold (Notify Once) 

Threshold: 25 

Trigger Response if 3 Samples 

Out of 4 Samples Crossed Threshold 



The following timeline shows how alerts are generated and retired 

as samples are taken: 

Sample Value Action Reason 

1st 20 none 3 samples > 25 

required to trigger alert 

2nd 30 none 3 samples > 25 


3rd 30 none 3 samples > 25 required 

to trigger alert 

4th 20 none 3 samples > 25 


5th 31 Alert: set health to 

Warning and/or 

start an action 

plan 3 of 4 are 

over 25 

6th 31 No new alert: 

health remains 

Warning; existing 

action plan 

continues 

processing if not 

completed already 

7th 21 Retire alert: set 

health to Good 

and retire the 

existing action 

plan 

Health already in 

Warning state, Action 

plan already in effect 

Only 2 of last 4 

samples are > 25 



Example 2 – The alert has the following settings: 

Respond If: Greater Than Threshold (Notify Repeatedly) 

Threshold: 25 

Trigger Response if 3 Samples 

Out of 4 Samples Crossed Threshold 

The following timeline shows how alerts are generated and retired 

as samples are taken: 

Sample Value Action Reason 

1st 20 none 3 samples > 25 


2nd 30 none 3 samples > 25 


3rd 30 none 3 samples > 25 


4th 20 none 3 samples > 25 


5th 31 Alert: may trigger 

an action plan 

6th 31 Alert: may trigger 

an action plan 

3 of 4 samples are >25 

3 of 4 sample are > 25, 

alert type is Notify 

Repeatedly 

7th 21 none Only 2 of 4 last 

samples are > 25 



Alert Message Filter – This setting applies to Voice Transaction 

Failure and e-TEST Transaction Failure alerts. It lets you use a Perl 

expression to associate an action plan with particular error 

messages. For example, if the filter is ―/.*Timed out.*/‖ then an 

alert fires for the alert message ―-14:Times out when waiting for 

energy,‖ but not for the message ―-10: Application under test is not 

responding to the seized line.‖ 

If this field is left blank, the alert fires regardless of the error 

message that is received. 

Notes Tab Settings 

The Notes tab lets you enter general information about this alert. 

Notes will be displayed on the Status and Alerts pages. In addition, 

they are used when running Intellisearch against monitors. Alerts 

with similar notes will be correlated. 

Notes for this alert – Enter any information relevant to this alert. 

Alert Editor Log Profile Metrics 

Use the Alert Editor to configure alerts for log file and NT Event Log 

metrics within a profile. 

Logfile Settings 

These options are available when you select Pattern Match in the Alert 

Editor. These apply to a profile that uses a log file as well as the Log File 

dedicated monitor. 

When you configure logfile settings for a profile monitor, the data source 

for this metric is Log File. These settings apply to events logged in the 

file specified in the Log File Data Source Configuration dialog box. 

Search String – Enter the string which, if found in the log file, will 

trigger a response. Enter the string value exactly as it would appear in the 

log file. 



Reset Sample Count – Determines how many sampling intervals need to 

occur after the above string is detected in the log file before an alert is 

retired. When the alert retires, the monitor or metric health is reset to 

Good (green) and any action plan associated with the alert is immediately 

terminated. If Reset Sample Count is set to 0, the Pattern Match alert will 

never trigger a response. 

NT Event Log Settings 

These options are available when you select NT Event Log Match in the 

Alert Editor Respond If group box. The data source for this metric is NT 

Event Log. 

NT Event Log Settings refer to events logged in the Windows NT Event 

Viewer (see Displaying the Windows NT Event Viewer for steps on 

how to access the Event Viewer). If the values you enter in the settings 

described below appear in the Windows NT Event Viewer, a response will 

be triggered. You can use the following three settings independently or 

together (recommended). 

Trigger Response if NT Source is – This setting refers to the Source 

column in the Windows NT Event Viewer. If, for example, you enter 

SNMP under Trigger Response if NT Source Is, a response will be 

triggered if SNMP event is logged in Event Viewer that has SNMP as its 

source (SNMP will be in the event’s Source column). Separate multiple 

sources with a comma. 

Trigger Response if NT Event ID is – This setting refers to the Event 


1001 under Trigger Response if NT Event ID Is, a response will be 

triggered if an event is logged in Event Viewer that has 1001 as its event 

ID (1001 will be listed in the event’s Event (ID) column). You can enter 

one ID, multiple IDs separated by commas, or a range of IDs. For 

example, “1” or “1,2” or “1,2,7-10” 

Trigger Response if Category is – This setting refers to the Category 


General under Trigger Response if Category Is, a response will be 

triggered if an event is logged in Event Viewer that has General as its 



Category (General will be listed in the event’s Category column). You can 

enter a list of strings or a list of number ranges separated by commas. 

Trigger Response if Username is – This setting refers to the Name 


Security under Trigger Response if Username Is, a response will be 

triggered if an event is logged in Event Viewer that has Security as its 

Category (Security will be listed in the event’s Name column). You can 

enter a list of strings separated by commas. 

NT Event Type – This setting refers to the symbols to the far left of events 

listed in the Windows NT Event Viewer. The symbols refer to event 

types. If you’re not sure which event type a symbol refers to, do the 

following in the Windows NT Event Viewer: highlight the event, click 

Detail on the View menu, and look under Type in the Event Detail dialog 

box. 

Reset Sample Count – Determines how many sampling intervals need to 

occur after the above conditions are met before an alert is retired. When 

the alert retires, the monitor or metric health is reset to Good (green) and 

any action plan associated with the alert is immediately terminated. If 

Reset Sample Count is set to 0, the NT Event Log Match alert will never 

trigger a response. 

Search String – Specifies a pattern that is validated against the 

description of the event. This string can be a full Perl regular expression 

(however, it does not return a result). See Using Regular Expressions 

for Pattern Matching in Chapter 5 for more information about 

specifying Perl expressions. 

Trigger Response for event that does NOT match the string – Triggers 

an alert for all errors except those that match the search string. 

SNMP Trap Settings 

These options are available when you select SNMP Trap in the Alert 

Editor Respond If group box. The data source for this metric is SNMP 

Trap. 



SNMP Trap Search – Specifies the text substring pattern to match before 

triggering an alert. This field is case-sensitive. If blank, all traps that meet 

the basic Enterprise and Trap Type filter criteria in the General tab of the 

SNMP Trap monitor trigger the alert. Enter any substring to further 

define the alert criteria. 

To alert on any trap originating from a particular IP address, enter the IP 

address. 

SNMP Trap Reset String – Specifies the string that indicates the alert 

condition no longer exists and the monitor can return to a Good state. 

Enter this field when the device sending the traps sends an ―all clear‖ type 

trap when the condition no longer exists. In this case, the Reset time 

should be set to its maximum value of 9999 (7 days) to ensure that the 

monitor does not return to a good state prematurely. 

If the device sends traps at a specified interval as long as the condition 

exists, and the absence of such traps indicates that the problem no longer 

exists, leave this field blank. 

Reset time (minutes) – Specifies how long to wait before returning to a 

Good state after an SNMP Trap message triggers an alert. If no additional 

SNMP Trap alerts occur for the length of the Reset time, OneSight 

returns the SNMP Trap monitor to a Good state. 

Setting the reset time to zero causes the trap to reset after zero minutes 

have passed, which means the trap alert will never be set. 

Note: If you specify both the SNMP Trap Reset String and the Reset 

time, whichever occurs first will reset the trap’s state. If you want to 

reset only by string, it is recommended that you set the reset time to 

9999. 

Example SNMP Trap Message 

Trap Received: 

Enterprise: oneSightTraps 

Trap Event Name: oneSightCritical 

Object ID: 

.iso.org.dod.internet.private.enterprises.empirix.oneSig 



ht.oneSightEventData.eventDescription.0 

GT 2 on http://www.empirix.com 

Object ID: 

.iso.org.dod.internet.private.enterprises.empirix.oneSig 

ht.oneSightEventData.extEventDescription.0 

GT 2: Value was 2.823 seconds, threshold is 2 seconds 

(10/15/01 3:24 PM) 

Event: GT 2 

... 

Triggering an E-mail Action Plan 

To set up an alert to trigger an e-mail action plan: 

1. If you have not already created your monitor, create one now. 

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

will let you know when your monitor has a problem. 

3. Click the Configure menu, click Monitor Groups, then click 

Modify. 

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

then click Modify. 

5. On the Alerts tab, you will see at least one preconfigured alert 

that notifies you if monitoring cannot be performed. By default, 

a failure to monitor changes the status of the monitor on the 

Status page to Red (Critical). However, if you want to be 

notified about this failure, you must associate the alert with an 

action plan. 

6. Select the default alert named for the state you associate with 

monitor failure (for example, URL Unavailable), and click 

Modify. 

7. In the Alert Editor, the Respond By option controls what action 

is triggered when an alert condition occurs. By default, there is 

no action plan associated with this alert condition, so you will 

see Respond by . 



Click the arrow next to the Respond By option and select an 

action plan you have configured with e-mail notification, then 

click OK. 

8. Click OK to update your monitor’s settings. 

Note: The amount of time it takes for the monitor to escalate the 

status to a Critical condition depends on factors such as how often 

the monitor tries to take a data sample. If you want to quickly 

confirm that your e-mail action plan is working, you may want to 

temporarily modify your monitor so that it will not sample 

successfully (for example, specify an incorrect URL or IP address) 

and then set it to sample at a very frequent rate. 

Creating a Threshold-based Alert 

If you want to know when web component performance either goes above 

or goes below an acceptable measurement, you can set up an alert that 

monitors a performance threshold. When the monitor detects that the 

threshold has been crossed, it triggers the alert. 

To create a threshold-based alert: 

1. If you have not already created your monitor, create one now. 

2. Click the Configure menu, click Monitor Groups, then click 

Modify. 

3. Click the monitor you want to configure, then click Modify. 

4. Click the Alerts tab, and then click Add to open the Alert Editor. 

5. In the Description box, type information that helps you to 

identify what this alert is measuring. For example, Slow Page 

Response Time. 

6. In the Respond If box, select the threshold condition that you 

want the monitor to respond to: 



Greater Than Threshold (Notify Once) – This alert will be 

produced the first time the measurement is greater than the 

Threshold value. The response is triggered only once while 

the measured condition is true. When the measurement drops 

below the defined thresholds the alert is retired. 

Less Than Threshold (Notify Once) – This alert will be 

produced the first time the measurement is less than the 

Threshold value. The response is triggered only once while 

the measured condition is true. When the measurement rises 

above the defined thresholds the alert is retired. 

Equal Threshold (Notify Once) – This alert will be produced 

the first time the measurement is equal to the Threshold 

value. The response is triggered only once while the 

measured condition is true. When the measurement rises 

above or drops below the defined threshold, the alert is 

retired. 

Greater Than Threshold (Notify Repeatedly) – The response is 

triggered if the measurement is greater than the Threshold 

value. The response will continue to be triggered at every 

sample interval for as long as the measurement stays above 

the threshold. 

Less Than Threshold (Notify Repeatedly) – The response is 

triggered if the measurement is less than the Threshold value. 

The response will continue to be triggered at every sample 

interval for as long as the measurement stays below the 

threshold. 

Equal Threshold (Notify Repeatedly) – This alert will be 

produced the first time the measurement is equal to the 

Threshold value. The response will continue to be triggered 

at every sample interval for as long as the measurement stays 

equal to the threshold. 



7. When you select a Threshold alert, the Alert Editor dialog box 

includes a Threshold Settings group box. Threshold settings 

affect when a response is triggered. 

Setting the Threshold – If you chose Greater Than Threshold, 

enter a value that represents the maximum measurement that 

you find acceptable. If you chose Less Than Threshold, enter a 

value that represents the minimum measurement that you find 

acceptable. For example, for a URL monitor, if you consider 

any response time that is 15 seconds or less to be acceptable, set 

Respond If to Greater Than Threshold and use 15 seconds as the 

threshold. 

Avoiding Alerts from “Spikes” – You can use the Trigger 


settings to avoid triggering responses during acceptable spikes. 

For , enter the number of samples that must be ―bad‖ before 

OneSight triggers a response. For , enter a total number (a 

count) of samples. The value of must be a number less than 

or equal to . 

8. If you want the alert to trigger an action plan when the 

threshold is crossed, click the arrow next to the Respond By 

option and select an action plan. Otherwise, accept the default: 

Respond by . 

9. If you want the alert to change the health status of the monitor 

when the threshold is crossed, click the arrow next to the Apply 

To option and select the health state you want the alert to 

trigger. Otherwise, accept the default: Apply to Nothing. 

10. Click OK to close the Alert Editor. Click OK again to save your 

changes to the monitor and return to the Monitor Group Editor. 

Then click OK to update the monitor group. 


Editing a Response to an Alert – Dedicated Monitor 

Editing a Response to an Alert – Dedicated 

Monitor 

By default, most of the dedicated monitors provided with OneSight 

are linked to at least one response. If you need to modify a response 

or create a new one, you will need to do two things in the Alert 

Editor: 

Define an alert: What must happen for the response to be 

triggered? 

Define a response: What should happen if a sample failure is 

received or a threshold is crossed? 

To define an alert for a dedicated monitor: 

1. In the Add Monitor dialog box or the Monitor Configuration 

dialog box, click the Alerts tab. 

2. If you are adding a new alert, click Add. If you are modifying an 

existing alert, select it and click Modify. 

3. The Alert Editor opens. Enter a description of the alert in the 

Description box. 

4. Select a Respond If setting. See the Respond If setting 

descriptions for information. 

5. Enter a value in the Threshold box. The value you enter should 

reflect what’s being measured and at what point you want 

OneSight to trigger a response. See Threshold Settings for more 

information. 

6. (Optional) Use the Trigger Response if Samples Out of 

Samples Crossed Threshold or Samples Failed settings to avoid 

triggering responses during acceptable spikes. 


Editing a Response to an Alert – Dedicated Monitor 

For , enter the number of sample counts that must be ―bad‖ 

before OneSight triggers a response. For , enter a total 

number (a count) of samples. The value of must be a 

number less than or equal to . 

7. Click OK to exit the Alert Editor and return to the Add Monitor 

dialog box. The alert you defined appears in the Alerts list. 

To define a response for a dedicated monitor: 

1. In the Add Monitor dialog box or the Monitor Configuration 

dialog box, click the Alerts tab. 

2. If you are adding a new alert, click Add, define the alert 

condition and then proceed with the steps listed below. If you 

are modifying an existing alert, select it and click Modify. 

3. In the Respond By list, select an action plan or click to create one. 

4. In the Apply To list, if available, select how the alert should 

affect the monitor’s health. For example, if the Sample Failure 

occurs, decide if the monitor should be set to a Warning state 

(the monitor will turn yellow on the Status page), a Critical 

state (the monitor status will turn red), or Nothing (no change in 

monitor status). 

Note: The Apply To setting is not available if Respond If is set to 

Greater Than Threshold (Notify Repeatedly) or Less Than 

Threshold (Notify Repeatedly). 


Editing a Response to an Alert – Profile Metric 


By default, most of the profile metrics provided with OneSight are 

linked to at least one response. If you need to modify a response or 

create a new one, you will need to do two things in the Alert Editor: 

Define an alert: What must occur for the response to be 

triggered? 

Define a response: What should happen if the alert condition 

occurs? 

To define an alert for a profile metric: 

1. In the Profile Editor, highlight the metric you want to create an 

alert for under Metrics and click the Add button on the right, in 

the Alerts group box. If you are modifying a metric’s existing 

alert, highlight the metric, then the alert, and click Modify. 

2. The Alert Editor opens. Enter a description of the alert in the 

Description box. 

3. Select a Respond if setting. See the Respond if setting 

descriptions for more information. 

4. The options available in the lower half of the Alert Editor 

change depending on the type of alert you are configuring. Do 

one of the following: 

Threshold Settings – enter a value in the Threshold box. The 

value you enter should reflect what’s being measured and at 

what point you want OneSight to trigger a response. See 

Threshold Settings for more information. 

Logfile Settings – enter the string that, if found in the log file, 

will trigger a response. 



NT Event Log Settings – enter values that, if they are found in 

the machine’s Windows NT Event Viewer, will trigger a 

response. See NT Event Log Settings for more information. 

5. (Optional) If defining a threshold-based alert, use the Trigger 


settings to avoid triggering responses during acceptable spikes. 

Trigger Response if Samples 

Out of Samples Cross Threshold 

For , enter the number of sample counts that must be ―bad‖ 

before OneSight triggers a response. For , enter a total 

number (a count) of samples. To find out how often a metric is 

sampling a web component, see the Sampling Interval setting in 

the Metric Editor (Data Sources tab). The value of must be 

a number less than or equal to . 

Note: If you do not enter values for these settings, OneSight will 

trigger the response (if any) based on the value entered in the 

Threshold box. 

6. Click OK to close the Alert Editor and return to the Profile 

Editor. To close the Profile Editor, click OK. 

To define a response for a profile metric: 

1. In the Profile Editor, highlight the metric you want to create a 

response for under Metrics. 

2. If you are adding a new alert, click the Add button on the right, 

in the Alerts group box, define the alert condition and then 

proceed with the steps listed below. If you are modifying an 

existing alert, select it in the Alerts group box and click Modify. 

3. In the Respond by list, select an action plan or click to create one. 


Displaying the Windows Event Viewer 

4. In the Apply to list, select what a crossed threshold or sample 

failure should mean in terms of the monitor’s health. For 

example, if the threshold is exceeded, decide if that should 

cause a Warning State (monitor will turn yellow on the Status 

page), Critical State (monitor will turn red), or Nothing. 

Note: The Apply to setting is not available if Respond if is set to 

Greater Than Threshold (Notify Repeatedly) or Less Than 

Threshold (Notify Repeatedly). 

Displaying the Windows Event Viewer 

To display the Windows Event Viewer: 

1. Click the Start button. 

2. Point to Programs, then Administrative Tools (Common). In 

Windows 2000 and 2003, point to Programs, then 

Administrative Tools. 

3. Click Event Viewer. The Windows Event Viewer opens. 


Configuring the Location From Which the Monitor Will Sample 

Configuring the Location From Which the 

Monitor Will Sample 

The Locations tab displays the Data Collector Locations from 

which the monitor checks your web site performance. One or more 

locations can be used. Refer to, ―Modifying the Location of 

Multiple Monitors,‖ later in this chapter for instructions on adding, 

changing, or deleting locations for several monitors at once. 

Note: Event Log and Perfmon monitors that do not have 

authentication configured will monitor using a local agent, if there 

is one, regardless of whether a location has been specified. 

Use all locations – Select this option to use all locations. 

Location – Specifies the Data Collector Locations from which the 

monitor checks performance. Locations that are available to the 

user group are listed. Select the locations for this monitor from the 

list. 


Adding a SmartLink to a Monitor 

Network – Specifies the network to which this location belongs. 

This information can be used for filtering reports. 

Region – Specifies the region to which this location belongs. This 

information can be used for filtering reports. 

Specify collection host – For Oracle Test for Web Applications 

Transaction monitors, specifies the name or IP address of the 

Remote Agent where the OATS Visual Script is running. 


The SmartLinks tab lets you associate URLs with a particular 

monitor or metric. The URLs are available on the popup menu on 

the Status Details Page. 

URL – Displays the URLs currently associated with this monitor. 



New Browser – Displays whether the URL should be displayed in a 

new browser window. 

Rollover Menu Text – Displays the text that will be displayed when 

you roll the mouse over the link on the Status Details page. 

Notes for this metric – Enter details about this metric in text or using 

HTML that can be found between the tags. These notes can 

be viewed by clicking on View notes for this metric on the popup 

menu on the Status Details page. 

Add – Displays the Smartlink Editor for adding a new URL. 

Modify – Displays the Smartlink Editor for modifying the selected 

URL. 

Remove – Deletes the selected URL. 

Click Add to add to display the Smartlink Editor dialog box. 

URL – Enter the URL that you want to associate with this monitor or 

metric. The URL can include specific substitution variables. 

Rollover Menu Text – Enter the text that you want to display when 

the mouse is rolled over the link on the Status Details page. 



Open in New Browser Window – Select this option to open a new 

browser window when the link is clicked in the Status Details page. 

Substitution Variables – The following substitution variables are 

supported: 

Note: Depending on the context in which the variables are used, 

they may not get resolved. For example, %systemname% may not 

resolve when at a monitor group level since there may be any 

number of system names. 

%DateShort% – The locale-specific date that the metric was last 

measured in the format mm/dd/yy. For example, 4/4/01. 

%DateLong% – The locale-specific date that the metric was last 

measured, in long format. For example, Wednesday, April 4, 

2001. 

%TimeShort% – The locale-specific time that the metric was last 

measured, in short format. For example, 1:52 PM. 

%TimeLong% – The locale-specific time that the metric was last 

measured, in long format including the time zone. For example, 

1:52:16 PM PDT. 

%Value% – the numeric value of the metric. For example, 11.701 

seconds. 

%MonitorGroup% – The name of the Monitor Group that contains 

the metric. For example, Business Partner Extranet. If multiple 

Monitor Groups use this metric, the result is a comma delimited 

list. 

%SystemName% – The name of the system that the metric is 

applied against. For example, JBK_P3. For URL monitors, the 

system name is the URL that you are monitoring. For example, 

http://www.empirix.com. This lets you use %SystemName% as 

your SmartLink for a URL monitor. 



%Monitor% – The name of the monitor that the metric is within. 

For example, URL (http://www.empirix.com). 

%Component% – The name of the component that the metric is 

applied against. For example, Disk C:. 

%Metric% – The name of the metric. For example, Disk: % Space 

Available. 

Note: For SNMP dedicated monitors, ―SNMP‖ is displayed. 

%Entity% – The monitored entity ID. 

%Item% – The metric item ID. 

%Location% – The location of the Data Collector. 

%_property% – Allows access to any monitor property. Substitute 

the word property for the actual property name. For example, 

some OneSight Voice Transaction and Voice Watch properties 

are: 

%_HIMServerName% – Returns the OneSight Voice 

Transaction server name. 

%_HIMPath% – Returns the path to the OneSight Admin and 

Detail .asp pages included with the OneSight Voice 

Transaction installation. 

%_HIMSID% – Returns the scenario ID. 

%_HIMSCID% – Returns the script ID. 

%_CPServerName% – Returns the Voice Watch server name. 

%_CPUserName% – Returns the User ID of the Voice Watch 



Configure Monitor Attributes Tab 

%_CPPassword% – Returns the password of the Voice 

Watch service account. 

%SmartSearch[:#OfEntries[CWG][:StringSizeLimit]]% – Generates 

a report listing monitors and their current alert state. #OfEntries 

is the maximum number of entries. CWG is an optional 

specification indicating whether to include monitors in critical, 

warning, or good states. StringSizeLimit is the maximum 

number of characters to return. For example, if you wanted to 

return a total of fifteen items that are in a critical or warning state 

with a string size less than 2500 use the following: 

%SmartSearch:15WC:2500%. 


The Attributes tab displays the attributes applied to the current 

monitor, monitor group, profile, or system and lets you change the 

attributes that are applied. To apply attributes to more than one 

monitor, monitor group, profile, or system, use the Assignment tab 

on the Attributes page. 



Attributes are used in OneSight to sort the monitors, monitor 

groups, profiles, and systems on the status page. You can assign 

custom attribute values to specific monitors and use the Group by 

selection on the status page to show only those monitors, monitor 

groups, profiles, or systems assigned to a specific attribute set. 

All Attributes – Shows the name of all of the configured attributes 

and their values. Click on the plus sign to expand the tree view. 

Selected Attributes – Shows the list of attribute values applied to 

this monitor, monitor group, profile, or system. Use the Add and 

Remove arrow buttons to customize the list of attribute values 

applied to the monitor, monitor group, profile, or system. 



Attribute Editor – Displays the Attribute dialog box for managing 

attributes. 

Attribute Sets – The Attribute Sets list shows the names of the 

custom attribute sets that have been defined in OneSight. The 

names added to this list will appear in the Group by select list on the 

OneSight status page. When you group the status page by an 

Attribute Set, the OneSight status lists only the monitors, monitor 

groups, systems, and profiles that are configured with an Attribute 

Value from that Attribute Set. 

In addition to custom Attribute Set names, the following names can 

also appear in the Group by list on the status page: 

 

Action Plan 

Location 

Monitor Type 

Profile 

System 



These Attribute Sets are added automatically by OneSight when 

monitors are configured and are not editable in the Attributes 

configuration. 

Add – Opens a dialog box for defining a new Attribute Set name. 

Modify – Opens a dialog box for changing the selected attribute set. 

Remove– Deletes the currently selected Attribute Set from the list. 

A dialog box appears asking to confirm the deletion. Removing an 

Attribute Set also deletes the associated Attribute values. The 

Attribute Set name is removed from the Group by list on the status 

page. The attribute values are also removed from the monitor group, 

monitor, system, and profile configurations. 

Used by – Displays a list of monitor groups, monitors, profiles, 

systems, and saved status groupings that are using this attribute set. 

Attribute Value Name – Shows the list of Attribute Value names for 

the currently selected Attribute Set. Attribute Values can be 

assigned to monitor groups, monitors, systems, and profiles. 

Add– Opens a dialog box for defining a new Attribute Value name. 

Remove– Deletes the currently selected Attribute Value name from 

the Attribute Set. A dialog box appears asking to confirm the 

deletion. Removing an Attribute Value also deletes the value from 

the monitor group, monitor, system, and profile configurations. 

Used by – Displays a list of monitor groups, monitors, profiles, and 

systems that are using this attribute value. 


Configure Monitor Groups Tab 

Configure Monitor Groups Tab 

The monitor groups tab lets you specify which monitor group(s) the 

monitor is used with. 

Available monitor groups – Lists all monitor groups configured in 

OneSight with the user group to which they belong in parenthesis. 

Select a monitor group in this list and click >> to add the monitor 

group to the Selected monitor groups list. Select a monitor group in 

the Selected monitor groups list and click



The Access Control tab lets you specify which user groups can 

read, write, or delete this monitor. 

This tab has the following options: 


Owner – The user group for this monitor. A monitor can be directly 

owned by a single user group. 

Global Read – Gives read access to this user group and all of its sub 

user groups. 




Applying Downtime to a Monitor 


Applying Downtime to a Monitor 

The Down Time tab lets you apply downtime to a monitor. 

Available Downtimes – Lists the downtimes that are available and 

that have not been applied to this monitor. 

Selected Downtimes – Lists the downtimes that have been applied to 


–Moves the selected downtime into the Selected 


– Moves the selected downtime into the Available 


Downtime Editor – Displays the Downtime Editor for creating and 

applying downtimes. Refer to ―Chapter 9‖ for more information on 

the Downtime Editor. 


Modifying Monitors 


Dedicated Monitors 


To modify a dedicated monitor: 

You can modify any monitor by clicking the Modify button on the 

Status Page or the Status details page. 

On the main Status page, click the Modify button to open the 

Configure Monitor Groups page. 

If you have opened the Status Details page by clicking a specific 

monitor group on the Status page, click the Modify button next to 

any monitor to open the Monitor Configuration dialog box. 

Use the options below to modify the behavior of a specific profile 

monitor. Your changes will apply only to the particular profile 

monitor that you choose to modify. If you want to make global 

changes to the characteristics of a profile, changes that will apply to 

every monitor group monitor that is based on that profile, use the 

Profile Editor. 

On the main Status page, click the Modify button to open the 

Configure Monitor Groups page. 

If you have opened the Status Details page by clicking a specific 

monitor group on the Status page, click the Modify button next to 

any monitor to open the Monitor Configuration dialog box. 

The Metrics list shows all of the metrics that the monitor can use to 

monitor your monitor group. 

This icon indicates that the metric is operational. 



When you select an operational metric, the System Components list 

identifies the names of the components that the metric is 

monitoring. Use the check box next to the component name to 

specify whether the profile metric applies or not to that system 

component. Clear the check box if you don’t want the profile metric 

to monitor this component. 

This icon indicates that the metric could not be applied to the 

system component it is meant to monitor. 

Click the System Editor button, then click one of the icons that 

indicates a component has not been adequately identified for 

monitoring purposes. Select the type of component that you want to 

monitor and add the missing information. 

In the Monitor Editor, you can make these types of modifications: 

You can specify whether an operational profile metric should 

apply or not to a specific system component. 

You can identify non-operational profile metrics and add the 

system component information required to make these metrics 

work properly. 

You can edit the profile used to create the monitor. Click the 

Profile Editor button to open the Profile Editor, where you can 

add or change metric definitions and configure alerts for the 

metrics. 

Note: Changes to a profile are global. The change affects all 

monitors that use that profile. 

Managing Non-operational Profile Metrics 

Use the procedure below to modify the behavior of a specific 

profile monitor. Your changes will apply only to the particular 

profile monitor that you choose to modify. If you want to make 

global changes to the characteristics of a profile, changes that will 



apply to every monitor group monitor that is based on that profile, 

use the Profile Editor. 



page. 


you want to work with and click Modify. The Monitor Group 

Editor opens. 

4. In the Name column on the Monitors tab, click the monitor that 

you want to modify and click Modify to open the Monitor 

Editor. 

5. In the Monitor Editor, the Metrics list shows all of the metrics 

that the monitor can use to monitor your monitor group. 

This icon indicates that the metric could not be applied to the 

system component it is meant to monitor because you have not 

added this type of component to your system definition. 

6. To add the missing components to your system definition, click 

the System Editor button. The Add Missing Components dialog 

box lists the system components that you need to add in order to 

apply all the profile’s metrics successfully. For details, see Add 

Missing Components. 

Enabling/Disabling Monitoring of a System Component 

Use the following procedure to modify the behavior of a specific profile 

monitor. Your changes will apply only to the particular profile monitor 

that you choose to modify. If you want to make global changes to the 

characteristics of a profile, changes that will apply to every monitor group 

monitor that is based on that profile, use the Profile Editor. 



Testing a Dedicated Monitor 


page. 


you want to work with and click Modify. The Monitor Group 

Editor opens. 

4. In the Name column, select the monitor that you want to modify 

and click Modify to open the Monitor Editor. 

5. In the Monitor Editor, the Metrics list shows all of the metrics 

that the profile monitor can use to monitor your monitor group. 

This icon indicates that the metric is operational. 

Select the operational metric that you want to enable or disable. 

6. The System Components list shows components that the metric 

is monitoring. 

Use the check box next to the component name to specify whether the 

profile metric should monitor that system component. 

For example, suppose the profile has a Disk metric for % Space Free. 

When you click that metric in the Metrics list, the System Components 

list will show each of the disks that the metric is monitoring. If you do not 

want to monitor one of the disks, clear the check box for that disk in the 

System Components list. 


When you add or modify a dedicated monitor, click the Test button 

to confirm that the settings you have configured are appropriate. 

When you click the Test button, OneSight confirms the validity of 

the initial settings required to initiate the monitoring process. The 

Test button does not exercise all settings for the monitor. The 

results of the test are not saved in the OneSight database, and do not 

change the status of the monitor on the OneSight status page. The 



following table indicates for each monitor, whether the monitor is 

sampled or if it is not sampled, what is tested when the Test button 

is clicked. 

Monitor Type 

DNS 

Event Log 

FTP 

Gomez GPN 

JMX 

LDAP 

Log File Perl Expression 

Log File Number of Matching 

Records 

Log File File/Directory 

Existence 

Log File File/Directory Size 

Log File Total Records Since 

Last Sample 

Log File time Since Last 

Modified 

Sampled or What is Tested 

Sampled 

Checks for connectivity and the 

ability to open the event log file. 

Sampled 

Returns the response time of the 

selected Gomez GPN monitor. 

Sampled 

Sampled 

Checks whether the file can be 

opened. 


opened. 

Sampled 

Sampled 


opened. 

Sampled 



Log File Directory 

Log File TCP 

Mail 

OneSight Compound Metric 

OneSight Probe 

OneSight Virtual Agent 

OneSight Voice Quality 


Profile 

OneSight Voice Watch 

Perfmon 

Ping 

Port 

Process 

Service 

Checks whether the directory 

can be opened. 

Checks connectivity. 

Sampled 

Sampled 

Sampled 

Sampled 

Sampled. Note that system 

monitor debug output is only 

displayed for G5 systems. It is 

not displayed for FX/TDM 

systems. 

Checks the availability of the 

URL. 

Checks the availability of the 

URL. 

Sampled 

Sampled 

Sampled 

Sampled 

Sampled 



SNMP 

SNMP Trap 

URL 

WMI 

Sampled 

Checks connectivity to the port. 

Sampled 

Sampled 

The status window provides a series of messages on the success or 

failure of each of the steps required to test the monitor. If the test 

does not complete, you can click Cancel to stop the test. 

For example, when you click Test for an FTP monitor, information 

similar to the following is displayed when the test is successful: 

Test Starting 

12:38:33 PDT Trying to connect to on port 

21 

12:38:33 PDT Connected. Logging in as 

12:38:33 PDT Logged in. Receiving file 

12:38:33 PDT Successfully received file from 

FTP server 

12:38:33 PDT Test complete 

Test complete 

When you click Test for an FTP monitor, information similar to the 

following is displayed when the test is unsuccessful because the file 

was not found: 

Test Starting 

12:38:33 PDT Trying to connect to on port 

21 

12:38:33 PDT Connected. Logging in as 

12:38:33 PDT Logged in. Receiving file 

12:38:33 PDT Error. 550 : The system cannot 

find the file specified. 

12:38:33 PDT Test complete 

Test complete 


Enabling/Disabling a Monitor 

To test a dedicated monitor: 

1. Open the Monitor Group Editor. 

2. Click the Monitors tab. 

3. In the Monitors list, select the monitor that you want test and 

click Modify. 

4. In the Monitor Editor, click the General tab. 





6. If the test fails, make changes to the monitor configuration 

based on the information in the Monitor Test window. 

Enabling/Disabling a Monitor 

To enable or disable a monitor: 


2. Click the Monitors tab. 

3. In the Monitors list, the check box that appears next to each 

monitor’s name determines whether or not that monitor is 

enabled. 

To disable a monitor, clear the check box adjacent to that 

monitor’s name. 

To re-enable a monitor, select the check box adjacent to that 

monitor’s name. 


Removing a Monitor 

Removing a Monitor 

To remove a monitor: 


2. On the Monitors tab, click the name of the monitor that you 

want to remove. 

3. Click the Remove button. 

Note: In the Monitors list, the check box that appears next to 

each monitor’s name determines whether or not that monitor is 

enabled. You can temporarily disable an existing monitor by 

clearing the check box adjacent to the monitor’s name. 

Modifying Alerts for Multiple Monitors 

You can add, change, and delete alerts for multiple monitors using 

the Bulk Modification option. These options apply to thresholdbased 

alerts and dedicated monitors only. You can add an alert to a 

maximum of 100 monitors at one time. You can modify or delete a 

maximum of 2000 alerts at one time. 

Adding Alerts to Multiple Monitors 

To add alerts to multiple monitors: 

1. Click the Configure page. 

2. Select Monitors. 

3. Select Bulk Modification. 



4. Select Alert Bulk Modification from the Available Options field. 

The Bulk Modification – Add Alerts dialog box lets you add a 

threshold-based alert to a maximum of 100 selected monitors. 

Specify the alert in the top half of the screen, then select the 

monitors to add the alert to in the bottom half of the screen. 

Click Show to display a list of all monitors or use the Show 

monitors where field to filter the list of monitors. 

When you click the Save Changes button the alert is added to 

the selected monitors. If an alert with the same name already 

exists, an error message is displayed and the alert is not saved. 

The top half of the screen displays the fields and options that 

apply to threshold-based alerts. These fields are described in 

detail in the “The Alert Editor” section of this chapter. 





example, you can search for all monitors with Ping in the name. 

In addition to plain text, you can enter a PERL expression in the 

contains field. 

Show – Displays the list of monitors based on the filtering 

selections. All monitors are listed if no filter has been specified. 

Note: Only the monitors explicitly owned by your user group 

are listed. To change monitors in a sub group of your user 

group you must activate the sub group by selecting it from the 

user group drop down list at the top of the screen. 

Check All – Checks all monitors in the list. 

Uncheck All – Unchecks all monitors in the list. 

Apply Changes – Saves the changes. This may take several 

minutes. 

Check box – Indicates which monitors are selected. Selected 

monitors will have the changes applied to them. 

Monitor Name – Displays the monitor name. Click in the column 

header to sort the list. An arrow is displayed showing the 

direction of the sort, ascending or descending. 

Threshold Alerts – Displays the threshold alerts for the monitor. 

Threshold Unit – Displays the threshold unit of measure. 

5. Configure the alert that you want to add. Refer to “The Alert 

Editor” section of this chapter for more information on 

configuring threshold-based alerts. 

6. Display the list of monitors that you want to choose from by 

entering filtering criteria in the Show monitors where field and 

then clicking Show. Clicking Show without entering filtering 

criteria displays all monitors. You can sort the list by clicking 

on a column header. 



7. Select the monitors to which you want to add the alert by 

clicking in the check box. You can add an alert to a maximum 

of 100 monitors. 

8. Click Apply Changes to apply the changes to the selected 

monitors. This may take several minutes. If the alert has the 

same name as an existing alert an error message is displayed 

and the alert is not saved. 


Changing Alert Thresholds for Multiple Alerts 

To change multiple alerts for multiple monitors: 







5. Click the Change Alerts tab. 

The Bulk Modification – Change Alerts dialog box lets you 

modify the threshold value of a maximum of 2000 alerts. This 

dialog box has the following options: 

New Threshold – This fields is displayed for all alert types 

except Threshold Range. Enter the new threshold to apply to 

the selected alerts. 

Upper Limit – This field is displayed when the alert type is 

Threshold Range. Enter the upper limit for the alert. 

Lower Limit – This field is displayed when the alert type is 

Threshold Range. Enter the lower limit for the alert. 








and alert type is – Select the type of alerts that you want to 

display. Select Any to display all types of alerts that meet the 

rest of the filtering criteria. 

and threshold is – Enter the current threshold of the alerts that 

you want to change. This field is displayed for all alert types 

except Threshold Range alerts. 

Upper Limit – Enter the upper limit of the alerts that you want to 

change. This field is displayed for the Threshold Range alert 

type. 

Lower Limit – Enter the lower limit of the alerts that you want to 


type. 

and state is – Select the state of the alerts that you want to 

change. 

and unit is – Select the unit of the threshold. 







Check All – Checks all monitors in the list that do not have a 

disabled check box. 


Save Changes – Saves the changes. This may take several 

minutes. 



Check box – Indicates which alerts are selected and which are 

available for selection. If you have selected Any in the and alert 

type is field, threshold range alerts will not be available for 

selection. They will be grayed out. You must select Threshold 

Range from the and alert type is field to change these alerts. 

Selected alerts will have the changes applied to them. You can 

select a maximum of 2000 alerts. 




Alert Name – Displays the alert name. 

Threshold – Displays the current value of the threshold. 

Unit – Displays the threshold unit of measure. 

6. Display the list of alerts from which you want to choose using 

the filtering criteria and clicking Show. Clicking Show without 

entering filtering criteria displays all alerts. You can sort the list 

by clicking on a column header. 

To change threshold range alerts you must select Threshold 

Range from the and alert type is field. Threshold Range alerts 

are not available for selection when you chose Any from the and 

alert type is field. 

7. Select the alerts you want to change by clicking in the check 

box. You can change a maximum of 2000 alerts. 

8. Click Apply Changes to apply the changes to the selected alerts. 

This may take several minutes. 




Deleting Alerts From Multiple Monitors 

To delete alerts from multiple monitors: 





5. Click the Remove Alerts tab. 

The Bulk Modification – Remove Alerts dialog box lets you 

remove a maximum of 2000 alerts. This dialog box has the 

following options: 








and alert type is – Select the type of alerts that you want to 

display. Select Any to display all types of alerts that meet the 

rest of the filtering criteria. 

and threshold is – Enter the current threshold of the alerts that 

you want to change. This field is displayed for all alert types 

except Threshold Range alerts. 

Upper Limit – Enter the upper limit of the alerts that you want to 


type. 

Lower Limit – Enter the lower limit of the alerts that you want to 


type. 

and state is – Select the state of the alerts that you want to 

change. 

and unit is – Select the unit of the threshold. 







Check All – Checks all monitors in the list. 



minutes. 


Modifying the Location of Multiple Monitors 

Check box – Indicates which alerts are selected. Selected alerts 

will be removed. You can select a maximum of 2000 alerts. 




Alert Name – Displays the alert name. 

Threshold – Displays the current value of the threshold. 

Unit – Displays the threshold unit of measure. 

6. Display the list of alerts from which you want to choose using 

the filtering criteria and clicking Show. Clicking Show without 

entering filtering criteria displays all alerts. You can sort the list 

by clicking on a column header. 

7. Select the alerts you want to change by clicking in the check 

box. You can delete a maximum of 2000 alerts. 

8. Click Apply Changes to delete the selected alerts. This may take 

several minutes. 



You can add, change, and delete locations for multiple monitors 

using the Bulk Modification option. You can modify a maximum of 

100 monitors or 2000 metrics at one time. 

To modify locations for multiple monitors: 






4. Select Location Bulk Modification from the Available Options 

field. 

The Bulk Location Modification dialog box has three tabs that 

have the same fields: 

Add Locations – Adds additional locations to the selected 

monitors. Adding a location increases the number of metrics 

associated with the monitor by the number of metrics 

collected by the monitor at any one location. For example, 

adding a second location to a monitor doubles the number of 

metrics associated with the monitor. 

Change Locations – Replaces the existing locations with the 

selected locations for the selected monitors. 

Remove Locations – Removes the selected locations from the 

selected monitors unless the removal will result in no 

locations being assigned to the monitor. 



Examples 

Assuming Monitor1 is assigned to Boston and New York 

Operation 

Selected Locations 

Existing Locations 

after Save Changes 

Add Detroit Boston, New York, 

and Detroit 

Change Detroit Detroit 

Delete Boston New York 

Available Locations – Lists the available locations. Select the 

locations that you want to add, change to, or remove from the 

selected monitors. Use the right arrow button to move them into 

the Selected Locations field. 

Selected Locations – Lists the locations that have been selected. 

Use the left arrow button to remove them from this list. 

– Moves selections either into or out of the 

Selected Locations field. 












On the Remove Locations tab, monitors not using the selected 



location(s) have a disabled checkbox since the location cannot 

be removed from a monitor that is not using the location. 

Check All – Checks all monitors in the list that do not have a 

disabled check box.. 



minutes. 

Check box – Indicates which monitors are available for 

selection and which monitors are selected. Selected monitors 

will have the changes applied to them. The monitors that are 

available for selection are determined by which tab you are in: 

Add Locations – Monitors that already use all of the selected 

locations will have a disabled check box. Monitors that do 

not support using more than one location will have a disabled 

check box. 

Change Locations – Monitors that already use all of the 

selected locations will have a disabled check box. Monitors 

that do not support using more than one location will have a 

disabled check box if more than one location has been 

selected in the Selected Locations field. 

Remove Locations – Monitors not using the selected 

location(s) will have a disabled check box. In addition, 

monitors that will result in zero locations after the removal, 

that is, the only location assigned to the monitor is the 

selected location, will have a disabled check box. 

Note: Monitors that do not allow a location to be selected 

when the monitor is created will have a disabled check box. 






Existing Locations – Displays the locations that are currently 

used by the monitor. Click in the column header to sort the list. 

An arrow is displayed showing the direction of the sort, 

ascending or descending. 

5. Select the tab that corresponds to the action you want to 

perform: 

Add Locations – Adds additional locations to the selected 

monitors. Adding a location increases the number of metrics 

associated with the monitor by the number of metrics 

collected by the monitor at any one location. For example, 

adding a second location to a monitor doubles the number of 

metrics associated with the monitor. 

Change Locations – Replaces the existing locations with the 

selected locations for the selected monitors. 

Remove Locations – Removes the selected locations from the 

selected monitors unless the removal will result in no 

locations being assigned to the monitor. 

6. Select the locations that you want to add, change to, or remove 

by selecting them in the Available Locations list and clicking the 

right arrow button to move them to the Selected Locations list. 

7. Display the list of monitors that you want to choose from by 

entering filtering criteria in the Show monitors where field and 

then clicking Show. Clicking Show without entering filtering 

criteria displays all monitors. You can sort the list by clicking 

on a column header. 

8. Select the monitors to which you want to apply changes by 

clicking in the check box. The monitors that are available for 

selection are determined by which tab you are in. 

Add Locations – Monitors that already use all of the selected 

locations will have a disabled check box. Monitors that do 


Adding Multiple Dedicated Monitors 

not support using more than one location will have a disabled 

check box. 

Change Locations – Monitors that already use all of the 

selected locations will have a disabled check box. Monitors 

that do not support using more than one location will have a 

disabled check box if more than one location has been 

selected in the Selected Locations field. 

Remove Locations – Monitors not using the selected 

location(s) will have a disabled check box. In addition, 

monitors that will result in zero locations after the removal, 

that is, the only location assigned to the monitor is the 

selected location, will have a disabled check box. 

Note: Monitors that do not allow a location to be selected 

when the monitor is created will have a disabled check box. 

Note: You can modify a maximum of 100 monitors or 2000 

metrics at one time. 

9. Click Save Changes to apply the changes to the monitors. This 

may take several minutes. 


Adding Multiple Dedicated Monitors 

You can add several dedicated monitors with a similar 

configuration in a single operation. This is done by placing the 

%filename% variable in the host field. This variable points to an 

XML file that is located in the imports directory. 

This file will contain one or more host values, and any 

individualized property settings for a specific monitor instance. 

Alert properties cannot be overridden. 


Globally Changing Proxy Settings 

When you accept the configuration, a monitor is added for each 

host in the file, using the settings specified in OneSight, unless 

individual properties are specified in the file. If a monitor by the 

same name already exists, it will be overwritten. In this way, group 

modifications can be made. For example, you could modify the 

sample rate for a group of monitors. 

A sample file, monitors.xml, is provided in the imports directory. 

The format of the variable is %filename%, where filename is the 

name of the XML file in the imports directory. Because this 

implementation is a form of variable substitution, the actual host 

value in the XML file can be the entire value for the Host field or it 

can be a substring within the field. For example, 

http://www.%filename%.com?myarg=val. 

To add multiple monitors: 

1. Setup the monitors file in the imports directory using the 

monitors.xml file as a template. 

2. On the Monitors Page, click Add New to open the Add Monitor 

dialog box. 

3. Select the type of monitor you are adding. 

4. Make any necessary configuration changes on the tabs. 

5. Enter %filename% in the Host field. 

6. Click OK. 


You can change the proxy server settings for all monitors of the 

same type at the same time rather than changing each monitor 

individually. To change proxy server settings for all monitors of the 

same type: 




2. Select Proxy. 

Monitor Type – Select the type of monitor for which you want to 

change proxy settings. Proxy settings for all monitors of this 

type will be changed. 

Use a proxy server – Select this check box and enter changes. 

Proxy Server – The IP address of the proxy server. 

Proxy Port – The port of the proxy server. 

Proxy User – The username for the proxy server. 

Proxy Password – The password for the proxy server. 

Confirm Password – Re-enter the password for the proxy server. 

3. Select the Use a proxy server check box. 

4. Enter the new settings. 

5. Click OK. 



Using Profiles 

A profile provides a set of performance criteria, in the form of 

metrics, to help you monitor the behavior of a particular type of 

back-end web component. You create a profile monitor by applying 

a profile to a specific machine. You can also create dedicated 

monitors for specific web components. Profiles differ from 

dedicated monitors in these ways: 

You can apply a profile to more than one web component of the 

same type. For example, you can apply the Windows profile to 

one PC running Windows 2000 or Windows 2003 or to multiple 

PCs running Windows 2000 or Windows 2003. 

Applying a profile to a web component requires specification of 

system information for each machine. As you create a profile 

monitor, you will need to identify the systems and describe their 

properties. See Adding Profiles for details. 

The Add Monitor dialog box is where you apply profiles to web 

components to create profile monitors. The Profile Manager is 

where you control which profiles are available to be applied. 

Default Profiles 

OneSight provides default profiles, listed in the Profiles list in the 

Profile Manager, that have been optimized to monitor web servers, 

database applications, operating systems, application servers, mail 

servers and other SNMP-enabled devices (see What OneSight 

Monitors in Chapter 1 for the full list of supported components): 

489

The Profile Manager 

Web Servers 

Apache Web Server, version 1.3x on UNIX machines 

HTTP server (generic) 

Microsoft IIS, version 4.0 and 5.0 on Windows machines 

Netscape Enterprise Server, version 3.6 

iPlanet 4.0 on UNIX machines 

(To monitor an iPlanet 4.0 web server, use the Netscape Enterprise 

Server profile.) 

Database Applications 

Oracle, versions 8.0, 8i, and 10g 

Microsoft SQL Server, versions 6.5, 7.0, 2000 

DB2 

Operating Systems 

Microsoft Windows NT, version 4.0 with Service Pack 4 or 

higher 

Microsoft Windows 2000 

Microsoft Windows Vista 

Sun Solaris, versions 2.6, 7.0, 8.0, and 10 

Linux 

RedHat 10 

AIX 5.3 



HP-UX 11i 

Application Server 

Allaire ColdFusion 

BEA WebLogic 

Mail Servers 

Microsoft Exchange version 5.5 

Switches and Controllers 

Cisco Catalyst 4000 Service Switch 



F5's BIG-IP 

Uninterruptible Power Supplies 

APC Symmetra 

Firewalls 

Netscreen Firewall 

If you are monitoring web components running the software listed 

above, the default profiles should meet your needs. To monitor 

back-end customer service technology components for which there 

are no default profiles, you can create your own either from scratch 

or by cloning an existing profile and modifying it. See adding, 

cloning, or modifying a profile for more information. 

Chapter 6: Using Profiles 491


Which Profile Should I use? 

In some cases, you have more than one profile option available for 

monitoring a web component. In particular, the RFC 1213 Network 

Device can provide network statistics for a wide variety of 

machines. 

For example, you can monitor a Linux machine using the Linux 

profile or using the RFC 1213 Network Device profile. If you want 

to monitor the overall health of the Linux machine, the Linux 

profile is more appropriate. The Linux profile has a focus on system 

statistics, while the RFC 1213 profile has a focus on network 

statistics. If you have a specific network statistic within RFC 1213 

that you want to use, you can also set up an SNMP dedicated 

monitor. 

If you have an Apache web server on a UNIX machine or an IIS web 

server on a Windows 2000 or 2003 machine, there are specific 

profiles for these purposes. In addition, the HTTP web server profile 

is a more generic web server profile that can be used on a wider 

variety of systems because it contains no metric for monitoring the 

web server’s log file. 

Profile Symbols 

In the Profiles list in the Profile Manager, you will see these 

symbols next to the profile names and descriptions. 

Profile is defined and applied to a component. 

Profile is defined but not applied to a component. 


Use the Profile Manager to control which profiles are available for 

creating monitors. 

To open the Profile Manager: 




2. Select Profiles. 

Adding, Cloning, and Modifying Profiles 

There are up to four main steps to add, clone, or modify a profile: 

1. Enter the main settings of a profile. 

2. Add metrics to or remove metrics from a profile. 

3. Edit metrics (optional). 

4. Edit a response to an alert (optional). Refer to Chapter 8. 



Entering a Profile’s Main Settings 

To enter a profile’s main settings: 

1. In the Profile Manager click one of the following buttons to 

display the Profile Editor: 

Add – to create a new profile from scratch. 

Clone – to create a new profile based on an existing one. 

Modify – to modify how an existing profile is configured. 

Main Settings 

Name – Type a name that identifies this profile. 

Description – Type a description that helps you differentiate 

this profile from the other profiles you are using to monitor 

your web components. 



Metrics Tab Settings 

Metrics – The Metrics group box displays the metrics in the 

profile you are configuring. A metric provides OneSight with 

detailed information about a specific aspect of a monitored 

web component, such as how many disk reads an Oracle 

database performs every 10 minutes. Each profile you create 

can contain one or more metrics. The profiles provided by 

default with OneSight each have a metric called Monitor: 

Monitor is Operational. The purpose of this 

metric is to determine whether the monitored web component 

can be sampled. 

Add – Adds a metric to a profile. 

Remove – Removes a metric from a profile. Clicking Remove 

does not delete the metric altogether; it just removes it from 

the profile you are creating or configuring. 

Global Metric Manager – Displays the Global Metric Manager 

to reconfigure a metric or to create a new metric from 

scratch. Because multiple profiles can use the same metric, 

keep in mind that metric configuration changes are global, 

not unique to the profile through which you accessed the 

metric. For example, if you change a metric’s Sample Every 

value from 30 to 60 seconds, every profile containing that 

metric will use 60 seconds as the metric’s new sampling 

interval. 

Alerts Tab Settings – The Alerts group box appears when you 

highlight a metric in the Metrics list. An alert draws your 

attention to monitored web component performance, such as an 

overloaded disk drive, that you want to know about. In response 

to an alert, OneSight can trigger an action plan, change a 

monitor’s health, or, in some cases, do both. Use the Alert 

Editor, which appears when you highlight a metric and click 

either Add or Modify, to link an alert to a response. Each metric 

in the Metrics group box can be linked to one or more alerts. 



Add – Click this button to link a metric alert to a OneSight 

response using the Alert Editor. 

Clone – Duplicates the selected alert. 

Modify – Click this button to change how a metric alert is 

configured using the Alert Editor. 

Remove – Click this button to remove a metric alert. 

SmartLink Tab Settings 

URL – Enter the URL that you want to associate with this 

monitor or metric. The URL can include specific substitution 

variables. 

New Browser – Select this option to open a new browser 

window when the link is clicked in the Status Details page. 

Rollover Menu Text – Enter the text that you want to display 

when the mouse is rolled over the link on the Status Details 

page. 

Notes for this metric – Enter details about this metric in text 

or using HTML that can be found between the tags. 

These notes can be viewed by clicking on View notes for this 

metric on the popup menu on the Status Details page. 

Update – saves or updates the notes for this metric. 

Attributes Tab Settings – Attributes are used in OneSight to sort 

the monitors, monitor groups, profiles, and systems on the 

status page. You can assign custom attribute values to specific 

monitors and use the Group by selection on the status page to 

show only those monitors, monitor groups, profiles, or systems 

assigned to a specific attribute set. 

To apply attributes to more than one profile at a time, use the 

Assignment tab on the Attributes page. 



All Attributes – Lists all configured Attributes and their 

associated values in a tree view. 

Selected Attributes – Shows the list of attribute values applied 

to this monitor, monitor group, profile, or system. Use the 

right and left arrows to customize the list of attribute values 

applied to the monitor, monitor group, profile, or system. 

Right Arrows – Adds the selected attribute value to the 

monitor, monitor group, profile, or system. 

Left Arrows – Removes the selected attribute value from the 

current monitor, monitor group, profile, or system. The 

attribute value is no longer applied to the current monitor, 

monitor group, profile, or system, but remains in the 

attributes configuration. 

Access Control Tab Settings 


Owner – The user group for this profile. A profile can be 

directly owned by a single user group. 

Global Read – Gives read access to this user group and all of 

its sub user groups. 




2. Type or edit the profile’s Name and Description. 



Adding/Removing Metrics From a Profile 

To add metrics to or remove metrics from a profile: 

1. If you are: 

Adding a profile – the profile you are adding contains no 

metrics. In the Profile Editor, click the Add button below the 

empty Metrics list, then follow the steps below. 

Cloning or modifying a profile – the Metrics list in the Profile 

Editor displays the profile’s metrics. To remove a metric 

from the profile, highlight the metric and click Remove. To 

add a metric, click Add, then follow the steps below. 

Use the Add Metrics dialog box to add metrics to or remove 

metrics from a profile. A metric provides detailed information 

about a specific aspect of a monitored web component. Each 

profile can contain one or more metrics. 

The Add Metrics dialog box has the following options: 



Available Metrics – These are the metrics you can choose from 

as you create or modify a profile. 

Selected Metrics – These are the metrics in the profile you are 

creating or modifying. If you are creating a new profile, this list 

will be empty. 

Global Metric Manager – Click this button to use the Global 

Metric Manager to reconfigure a metric in the Available 

Metrics list or to create a new metric. Because multiple profiles 

can use the same metric, it is important to keep in mind that 

metric configuration changes are global. For example, if you 

change a metric’s Sampling Interval from 30 to 60 seconds, 

every profile containing that metric will use 60 seconds as the 

metric’s new sampling interval. 

– Click this button to add a metric from the 

Available Metrics list to the Selected Metrics list. Clicking Add 

does not remove metrics from the Available Metrics list. 

– Click this button to remove a metric from the 

Selected Metrics list. Clicking Remove will not delete the 

metric all together, just from the profile you are creating or 

modifying. 

2. Add a metric to your profile by highlighting a metric under 

Available Metrics and clicking the right arrow button (>>). The 

metric’s name appears in the Selected Metrics list. To remove a 

metric from the profile, highlight the metric name under 

Selected Metrics and click the left arrow button (


Removing Profiles 

return to the Profile Editor. The metrics you selected appear in 

the Metrics list. 

4. To exit the Profile Editor, click OK. The profile you created is 

added to the Profiles list in the Profile Manager. 

Note: If you have metrics that are getting floating values outside 

the range of 10 3 to 10 7 , such as phone numbers, reporting may 

not be accurate. 

1. Select a profile in the Profile Manager. 


Importing Profiles 

3. A warning dialog box opens, confirming that you want to 

remove the profile. Click OK. 

The profile is removed from the Profile Manager, but not deleted 

altogether. To recover the profile, click Import, highlight the profile’s 

name in the Import Profiles dialog box, and click Import. If you are 

trying to recover a profile that you created, it can only be recovered if it 

was exported. 

Use the Import Profile dialog box to import profiles from the 

OneSight server’s Imports folder (\Empirix\OneSight\Imports) to 

the Profiles list in the Profile Manager. 



1. In the Profile Manager, click Import. The Import Profile dialog 

box opens. 



2. Under Available Files, the profiles in the OneSight server’s 

Imports folder (the default location is 

\Empirix\OneSight\imports) are listed. To import a profile, 

highlight it and click Import. The Confirm dialog box may be 

displayed. Following is a sample message: 

Use this dialog box to confirm that you want to perform the 

action you specified. 

Importing Metrics and Profiles 

If you are importing a profile and the metrics included in that 

profile, this dialog box appears when existing settings will be 

overwritten by the import request. 

Importing a metric 

OneSight profiles consist of a set of metrics as well as some 

alert and threshold settings. When you import a profile that 

already exists on your server, OneSight confirms that you are 



willing to replace the existing profile and the associated 

selected metrics. 

When you import a metric, the existing settings for the metric 

(for example, sample frequency) will be overwritten. You can 

change a metric’s settings in the OneSight Metric Editor. 

If you have not made any changes to the existing metric and 

profile, they may be the same as the metrics and profile you are 

importing. In this case, you can click OK to complete the profile 

import procedure. 

Importing a profile 

After being prompted about overwriting individual metrics 

within the existing profile, you will also be asked if you are 

willing to replace the existing version of the profile. Profile 

settings (as opposed to metric settings) include alerts and 

threshold settings. You can change a profile’s settings in the 

Profile Editor. 

If you have not made any changes to the existing metric and 

profile, they may be the same as the metrics and profile you are 

importing. In this case, you can click OK complete the profile 

import procedure. 

Importing a profile without importing metrics 

If you choose not to replace the existing metrics but you do 

choose to replace the profile, the imported profile will use the 

existing metrics but will use the imported profile’s alerts and 

threshold settings. 

3. Select the metrics that you want to import. 

4. Click OK. 

5. After the file is added to the OneSight server’s Imports folder 

(you may need to click Refresh to see it), it will be available for 


Global Metric Manager 

Exporting Profiles 

import into the Profile Manager by highlighting it and clicking 

Import. 

1. In the Profile Manager, highlight the profile you want to export 

to the OneSight Server’s Imports folder 

(\Empirix\OneSight\imports), for example, MyProfile. 

2. Click Export. A message box notifies you that the export is 

complete. 

The profile you highlighted in the Profile Manager is exported 

to the \Empirix\OneSight\imports folder and given an .imp 

extension. For example, 

\Empirix\OneSight\imports\MyProfile.imp. 

Note: When you export a profile using the same name as the 

original profile, a zero is appended to the original file name. For 

example if you exported a profile with the same name, the file 

names would be as follows: 

MyProfile0 – the original profile 


MyProfile – the exported custom profile 

Profiles are composed of metrics. Metrics provide OneSight with 

detailed information about specific aspects of monitored web 

components. For example, among the metrics in the Windows 

profile is one called Disk: % Space Free. Applying the Windows 

profile to a machine running Windows 2000 or to a Windows 2003 

machine creates a profile monitor that supplies OneSight with 

information about how much disk space is available on that 

machine, among many other types of information. 



What to remember about metrics: 

Metrics rely on data sources – Data sources gather information for 

metrics and dedicated monitors. You can review, create, or 

modify data source information in the Data Source Configuration 

tab. 

One metric can sample multiple instances of a component – Using 

the Disk: % Space Free example above, when the Disk: % Space 

Free metric is applied as part of the Windows profile to a 

Windows machine that has four logical disks, each of those 

logical disks will be sampled by the same Disk: % Space Free 

metric. The Sample for Each setting, set in the Metric Editor 

(General tab), controls this behavior. 

Metric changes are global – When you modify a metric, such as 

changing its Sample Every measurement from 60 to 

120 seconds, that modification applies to every instance of that 

metric, whether it is shared by another profile or sampled for 

each instance, as described above. If you want to avoid making a 

global change, try cloning the metric you are interested in (in the 

Global Metric Manager) and modifying it to suit your purposes. 

Keep it simple – If you create a metric from scratch, keep it 

simple. For example, do not build in special Translation Type or 

Scale settings on your first pass. 

Use the Global Metric Manager to control which metrics are 

available for use in profiles and how those metrics are configured. 

Adding/Cloning/Modifying Metrics 

Empirix OneSight provides predefined metrics for the web 

components it can monitor. If you are creating or modifying a 

profile, try to use those predefined metrics rather than create your 

own. 



To create or modify metrics: 

1. In the Profile Editor, click the Global Metric Manager button. 

The Global Metric Manager opens. 

Global Metric Manager settings – When you use the Global 

Metric Manager, keep in mind that multiple profiles can contain 

the same metric and any changes you make to a metric affect all 

those profiles. For example, if you delete a metric, you delete it 

from every profile that contains that metric. Or, if you change a 

metric’s Sample Every from 30 to 60 seconds (in the 

Metric Editor), every profile containing that metric will use 60 

seconds as the metric’s new sampling interval. 

Add – Creates a new metric using the Metric Editor. 

Clone – To use an existing metric as the base for creating a new 

one, select a metric in the Global Metrics list and click Clone. 

The Metric Editor opens and you can modify the cloned metric 

there. 

Modify – To modify an existing metric using the Metric Editor, 

select a metric in the Global Metrics list and click Modify. 



Remove – To permanently remove a metric from Empirix 

OneSight, select the metric and click Remove. 

Used By – Displays the profiles and monitors that use this 

metric. 

Name – The Name column lists the names of existing metrics. 

User Group – Displays the user group to which this metric 

belongs. 

Data Source – Displays the data source used by this metric. 

Group – The Group column lists the Group to which each metric 

belongs. The Group can be either general or specific. For 

example, if a metric measures something that is unique to 

Apache web servers, Web Server, Apache will be its Group. If a 

metric measures something that is common to all of OneSight’s 

supported web servers, Apache, Microsoft IIS, and Netscape 

Enterprise, Web Server, Any will be its Group. 

Type – Displays the type of metric. When applied to a system, 

the type determines the type of license used. Refer to Chapter 

2. 

Basic – metrics that measure basic operating system 

performance such as CPU, Disk, etc. 

Premium – metrics defined by the contact center. 

Advanced – metrics that are not basic or premium. 

Description – Displays a description of the selected metric. 



2. If you are: 

Modifying or cloning a metric – highlight the metric name in 

the Global Metrics list and click Modify or Clone. 

Creating a new metric – click Add in the Global Metric 

Manager. 

3. In the Metric Editor, type or edit the metric name in the Metric 

Name box. 

4. Do the following on the General tab. Refer to General Tab 

Settings for a description of this dialog box. 

Type or edit the metric description in the Description box. 

Select a setting under Sample for Each. 

Select Group, Report Category, and Translation Type settings. 

If you are creating a new metric, select a measurement from 

the Unit Measure list or type the unit of measure you want to 

use. If you are modifying or cloning an existing metric, this 

field will be filled in for you. 



Enter or edit the Sample Every: value. This is how 

often the metric will attempt to gather information from the 

web component. 

5. Refer to Data Sources Tab Settings for a description of this 

dialog box. On the Data Sources tab, if you are: 

Modifying or cloning a metric – the data source(s) listed will 

probably meet your needs. To change how that data source is 

configured, change the settings and click OK. 

Creating a metric – the metric you are creating will not work 

unless there is a data source to collect information for it. 

Select the data source you want to use. See Adding a Data 

Source for information on how to fill out these fields. 



6. Click the Attributes tab if you want to assign attribute values to 

this metric. Assigning attribute values lets you filter data by 

attribute on metric-based reports. Refer to Attribute Tab 

Settings for information on how to fill out these fields. 

7. Click OK to exit the Metric Editor. The metric you just 

modified or added appears under Global Metrics in the Global 

Metric Manager. 

8. In the Global Metric Manager, click Close. 

9. In the Profile Editor, if you: 

Modified or cloned a metric in a profile, you are now ready 

to Create or modify a response to an alert for that metric. 

Created a metric and want to add it to a profile, click the Add 

button. In the Add Metric dialog box, highlight the metric 

you created under Available Metrics and add it to the 

Selected Metrics list. Click OK. The metric you created is in 

the profile. Now you’re ready to Create or modify a response 

to an alert. 

10. Create or modify a response to an alert. Refer to Chapter 8. 



General Tab Settings 

Use the Metric Editor to define or modify general and data sourcespecific 

information about a metric. The general tab displays basic 

metric settings, such as the metric’s name and the type of web 

component it is measuring. Use the options on the General tab of 

the Metric Editor to define basic aspects of a metric, such as its 

name, description, report setting, and unit of measurement. 

Metric Name – Type a name for this metric. The name you enter also 

appears in the Name column of the Profile Editor and the Global 

Metric Manager. 

Description – Type a description for the metric. The description you 

enter also appears in the Description area of the Global Metric 

Manager. 

Sample for Each – Sample for Each settings correspond with the 

items under Components in the System Editor. Use the Sample for 

Each settings to make the metric sample each component of that 

type that it finds on the monitored web component. Take, for 

example, a metric that measures Queue Length that has Disk as its 

Sample for Each setting (Disk: Queue Length). When Disk: Queue 

Length is applied as part of a profile to an NT machine that has four 

logical disks, four instances of the Disk: Queue Length metric will 

be created, one metric instance for each logical disk. 

The Sample for Each setting called System does not replicate metrics. 

Use System to measure ―one of a kind‖ items on a machine. 

Group – Specify the group to which this metric belongs. The Group 

designation can be either general or specific. For example, if the 

metric measures something that is unique to Apache web servers, 

you could type Web Server, Apache as the Group setting. If the metric 

measures something that is common to all of OneSight’s supported 

web servers, Apache, Microsoft IIS, and Netscape Enterprise, you 

could type Web Server, Any as the Group setting. 



The purpose of the Group specification is to provide information 

about how this metric should be used. When defining profiles, you 

can use the group information to determine which metrics can be 

part of the profile. 

The following table lists examples of Groups used in OneSight 

default profiles. 

General Group setting 

AppServer ColdFusion 

ATG Dynamo 

DB Server Oracle 

Other group settings 

Allaire ColdFusion Application 

Server (see also WebLogic for 

SNMP) 

ATG Dynamo 

Oracle, versions 8.0 and 8i 

SQL 6.5: Microsoft SQL Server 

version 6.5 

SQL 7, 2000: Microsoft SQL Server 

version 7 or 2000 

Mail Server Exchange 5.5 

Microsoft Transaction 

Server 

RealSystem Server 

(Windows) 

SNMP 

Machines running Microsoft 

Exchange 5.5 Mail Server software 

Microsoft Transaction Server 

RealSystem Server version 8.0 

CheckPoint-MIB: Hosts and devices 

supporting the CheckPoint MIB. 

Cisco-Process-MIB: Machines 

running Cisco Catalyst 4000 or 

5000. 



Cisco-Stack-MIB: Machines running 

Cisco Catalyst 4000 or 5000. 

Cisco-Switch-Engine-MIB: 

Machines running Cisco Catalyst 

4000 or 5000. 

CPQHOST-MIB: Hosts and devices 

supporting the Compaq PC Server 

CPQHOST MIB. 

CPQHLTH-MIB: Hosts and devices 

supporting the Compaq PC Server 

CPQHLTH MIB. 

DELLHOST-MIB: Hosts and devices 

supporting the Dell PC Server 

DELLHOST MIB. 

DELLHLTH-MIB: Hosts and devices 

supporting the Dell PC Server 

DELLHLTH MIB. 

HOST-RESOURCES-MIB: Any 

machine with Agents that support 

the Host Resources MIB, including 

Linux and IBM AS/400. 

HP-UX: Hosts and devices 

supporting the Hewlett-Packard 

Unix MIB. 

LOAD-BAL-SYSTEM-MIB: Hosts 

and devices supporting the F5 BIG- 

IP Load Balancer MIB. 

SNMP 

RFC1213-MIB: Hosts and devices 

supporting SNMP MIB-II (RFC 

1213), covering a wide variety of 

TCP/IP devices. 

TUBS-MIB: Hosts and devices 



supporting the TUBS MIB. 

UCD-SNMP-MIB: Hosts and devices 

supporting the UCD SNMP MIB, 

including many Linux systems. 

WebLogic-MIB: Machines running 

BEA Web Logic Application Server. 

System 

Windows NT 4.0 with Service Pack 

4 or higher, Windows 2000, or 

Solaris version 2.6, 7.0, or 8.0. 

Windows NT: Windows NT 4.0 with 

Service Pack 4 or higher or 

Windows 2000. 

Solaris: Solaris, version 2.6, 7.0, or 

8.0. 

Web Server 

Any: Apache Web Server, version 

1.3x; Microsoft IIS, version 4.0 or 

5.0; or Netscape Enterprise Server, 

version 3.6, iPlanet 4.0 on UNIX 

machines, HTTP server (generic). 

Apache: Apache Web Server, 

version 1.3x on UNIX machines. 

IIS: Microsoft IIS, version 4.0 or 

5.0. 

IPlanet: IPlanet Web Server 4.0 on 

UNIX machines. 

Netscape: Netscape Enterprise 

Server, version 3.6 



Report Category – Choose which type of report should incorporate 

the data from this metric. The Report Category 

setting should work for most metrics. If you are modifying a metric 

that is provided as part of a profile, try to use the existing Report 

Category setting. The following list shows the reports that each 

category lets you run: 

– The most general reports. 

Throughput – Reports that describe the volume of data that can be 

transferred per unit of time 

Response Time – Reports that provide response-related data, such 

as how quickly a remote web site responds. 

Monitor Is Operational – Reports that provide information on 

monitor availability. 

Translation Type – Translation Type settings control how OneSight 

translates a metric’s data when displayed on the OneSight Alerts 

page and in Reports. If you are modifying a metric that is provided 

as part of a profile, use the existing Translation Type setting: 

No Translation – OneSight presents the metric’s data as it is 


Rate (minutes) – OneSight presents the metric’s data as a delta, 

per minute. If the time interval between two samples was 10 

minutes, and 50 errors were found, the Rate (minutes) would be 

five (5) errors per minute. 

Note: Rate (minutes) translates data sources that return their values 

as an endlessly increasing counter. If the data source does not return 

data this way, use No Translation. For example, some network 

metrics from the UNIX System data source are returned as the 

number of errors since the machine was rebooted. To get the error 

rate per minute, use Rate (minutes). 



Unit Measure – Select which unit of measurement should be 

associated with this metric and displayed in places like the OneSight 

Alerts page and Reports. You can also use this field to enter your own 

unit of measurement setting. If you are modifying a metric that is 

provided as part of a profile, try to use the existing Unit Measure 

setting: 

% (percent) – the metric’s data is expressed as a percentage. 

bytes – the metric’s data is expressed in bytes. 

hours – the metric’s data is expressed in hours. 

minutes – the metric’s data is expressed in minutes. 

seconds – the metric’s data is expressed in seconds. 

– the metric’s data is expressed with no unit of 

measurement. 

Sample Every – Specifies how often samples are taken 

for this metric. Select the unit of time to use for the sampling 

interval: seconds, minutes, or hours. You can specify sample 

intervals to occur regularly, hourly, or daily. 

To Sample Interval Value Example 

Regularly integer 5 minutes 

Hourly @ 60@15 minutes 

Daily @ @23:15 minutes 

Daily GMT 24@hh 24@01 hours 

To sample at regular intervals, specify a simple integer value and 

select the appropriate units. For example, to sample every 5 

minutes, enter 5 and select minutes. OneSight selects a random time 



to take the first sample that is shortly after configuration or startup, 

and from then on samples every 5 minutes. 

To sample at a specific time every hour, specify the value as 

@. For example, to sample every hour at 

quarter past the hour, enter 60@15 and select minutes as the units. 

The first sample is taken shortly after configuration or startup so 

that the status gumball will go out of waiting. Subsequent samples 

are then taken as specified. 

To sample at a specific time every day, specify the value as @. For example, to sample once a day at quarter past eleven 

(local time on the server machine), enter @23:15. The first sample 

occurs at the time specified. 

You can specify in seconds, minutes, or hours 

using the following formats: 

Seconds: hh:mm:ss 

Minutes: hh:mm 

Hours: hh 

When specifying midnight, use the format @0. 

For a daily interval, you can also use the format 24@hh. The 

interval is 24 hours and the hh specifies the number of hours after 

midnight Greenwich time. You must select hours as the units. The 

first sample is taken shortly after configuration or startup so that the 

status gumball will go out of waiting. Subsequent samples are taken 

as specified. 

You can also specify different sampling intervals based on the 

sample’s state using the following syntax: 

or ; or 

;;. Separate each state interval by a 

semi-colon. Each state interval must share the same unites. For 

example, 30;20;15 minutes samples every 30 minutes when in a 

good state, every 20 minutes in a warning state, and every 15 



minutes in a critical state. If two states are the same one can be 

omitted. For example, 30;;15 minutes samples every 30 minutes in 

good and warning states, and every 15 minutes in a critical state. 

The format 30;20 minutes samples every 30 minutes in a good state, 

and every 20 minutes in the warning and critical states. A single 

interval value applies to all three states. 

Data Sources Tab Settings 

Use the options on the Data Sources tab of the Metric Editor to 

determine which data sources gather information for a metric, how 

often the information is gathered, whether that information should 

be stored in the OneSight database, and, if so, how often it should 

be stored. The settings on this tab vary depending on which data 

source is selected. 

Attributes Tab Settings 

The Attributes tab displays the attributes applied to the current 

metric and lets you change the attributes that are applied. To apply 

attributes to more than one metric, use the Assignment tab on the 

Attributes page. 

Attributes are used in OneSight to sort the monitors, monitor 

groups, profiles, and systems on the status page. You can assign 

custom attribute values to specific monitors and use the Group by 

selection on the status page to show only those monitors, monitor 

groups, profiles, or systems assigned to a specific attribute set. 

Attributes are also used to filter reports that support attribute 

filtering. 

All Attributes – Shows the name of all of the configured attributes 

and their values. Click on the plus sign to expand the tree view. 


this metric. Use the Add and Remove arrow buttons to customize the 

list of attribute values applied to the metric. 



Attribute Editor – Displays the Attribute dialog box for managing 

attributes. 



names added to this list will appear in the Group by select list on the 

OneSight status page. When you group the status page by an 

Attribute Set, the OneSight status lists only the monitors, monitor 

groups, systems, and profiles that are configured with an Attribute 

Value from that Attribute Set. 

In addition to custom Attribute Set names, the following names can 

also appear in the Group by list on the status page: 

 

Action Plan 

Location 

Monitor Type 

Profile 

System 






Add – Opens a dialog box for defining a new Attribute Set name. 

Modify – Opens a dialog box for changing the selected attribute set. 

Remove– Deletes the currently selected Attribute Set from the list. 

A dialog box appears asking to confirm the deletion. Removing an 

Attribute Set also deletes the associated Attribute values. The 

Attribute Set name is removed from the Group by list on the status 

page. The attribute values are also removed from the monitor group, 

monitor, system, and profile configurations. 


systems, and saved status groupings that are using this attribute set. 

Attribute Value Name – Shows the list of Attribute Value names for 

the currently selected Attribute Set. Attribute Values can be 


Add– Opens a dialog box for defining a new Attribute Value name. 

Remove– Deletes the currently selected Attribute Value name from 

the Attribute Set. A dialog box appears asking to confirm the 

deletion. Removing an Attribute Value also deletes the value from 

the monitor group, monitor, system, and profile configurations. 


systems , and metrics that are using this attribute value. 



Access Control Tab Settings 


read, write, or delete this metric. 

This tab has the following options: 


Owner – The user group for this metric. a metric an be directly 



user groups. 






Adding a Data Source 

Data sources act as information gatherers for profile metrics or 

dedicated monitors. You can view the metrics used for OneSight’s 

default profiles in the Data Source Configuration dialog box. You 

supply additional information in the System Editor when you apply 

the profile. 

OneSight also makes use of third-party data sources that reside on 

the machines that OneSight is monitoring. Some OneSight data 

sources (SNMP and Perfmon) require that a corresponding thirdparty 

data source be running to operate successfully. 

If you are using 

this data source… 

JDBC 

On the monitored machine you may need to... 

n/a 

Log File 

NT Event Log 

Perfmon 

Ping 

Service 

SNMP 

Install the OneSight Data Collector or Remote 

Agent for NT or the OneSight Remote Agent 

for Solaris or Linux. 

n/a 

If the Data Collector or Remote Agent (for 

NT) is not installed on the monitored machine, 

make sure that the OneSight server can access 

the machine’s Perfmon data. For metrics that 

sample disk performance, you may also need 

to execute the Diskperf command. 

Ping is not available from UNIX machines. 

n/a 

Enable SNMP. Also, be sure that the schema 

(MIBs) on the monitored machine supports 

the data you plan to collect. 



SNMP Trap 

UNIX 

URL 

Enable SNMP. Make sure the OneSight 

Service is running. 

System Install the OneSight Remote Agent for 

Solaris or Linux. 

n/a 

To add a data source to a metric: 

1. In the Metric Editor, click the Data Sources tab. 

2. Select a data source from the Available Data Sources box. The 

data sources listed do not represent the data sources available 

on the machine the metric will monitor, but rather all possible 

data sources that OneSight can use. 

Fill in the fields on the right side of the dialog box. The fields 

displayed are different for each data source. See the dialog box 

descriptions that follow. 



3. Click OK. The data source you added appears under Data 

Sources in the Metric Editor. 

JDBC Dialog Box 

Use this dialog box to add or modify a data source to a metric that 

relies on JDBC information being configured. 

Query – Enter a query appropriate for the database application this 

metric is monitoring. 

Report On – Select Query Time or Query Result as the value to be 

measured. 

Query time – Lets you run response time-related reports using this 

metric’s data. 

Good Content String – Enter the string that should be returned for 

the query you specified. If the string is not matched, an error is 

returned. 



Query result – Lets you run reports using the numeric or string 

result of the query. 

Perl Expression – Enter the numeric value that should be returned 

for the query you specified. If this metric returns a string that 

contains more than just numerical information, then a regular 

expression can be used in Match string to extract the numerical 

result that OneSight requires. For more information, see Using 

Regular Expressions for Pattern Matching in Chapter 5. 





measuring a JDBC result representing a string datatype, it can be 




reading to a zero value in OneSight. String mappings can also be 

used to translate a number to a string for display in OneSight. 

Note: When the output of a database query is a result set the query 

retrieves all rows of the result set. It processes for good content 

match, perl expression match, or advanced string mapping, treating 

the entire result set as a whole data block. Matching is successful 

when there is at least one match in the whole data block. If the 

result needs to be returned, the first matched value is returned. 

Return the first column of the first row – Select this option to return 

the first column of the first row if there are multiple results. 

Loop on result items, returning the first match – Select this option to 

loop on each result and return the first result that matches. 

Concatenate result items (space delimited) – Select this option to 

concatenate all results and return the first result that matches. 

Results are space delimited. 



Scale – Type the multiplier you want applied to the data that is 

collected. 





Timeout (sec) – Enter the length of time after which the query will 

time out. 

JMX Dialog Box 

Use this dialog box to add the JMX data source to a metric. 

Attribute Name – The Mbean’s attribute name. 

Attribute Property – The Mbean’s attribute property. 


collected. 







String Mappings – If you are measuring an object representing a 

string data type, it can be converted to a number for use in OneSight 

using this field. Specify a semicolon delimited mapping of strings to 

integers. For example, ―false=0;true=1‖ will convert a false reading 

to a zero value in OneSight. String mappings can also be used to 

translate a number to a string for display in OneSight. 

Log File, Directory Dialog Box 

Use this dialog box to add or modify the Log File data source to a 

metric. The Log File data source monitors text log files produced by 

applications such as web servers, database servers, or application 

servers. For the Log File data source to function correctly, the 

OneSight Data Collector or Remote Agent must be installed on the 

monitored machine. 

You can monitor directory existence, size, or the number of files or 

folders in a directory. For metrics that apply to folders, you can 

select whether to return values on the directory and all 

subdirectories or only the topmost directory. 



Monitor Type – Specifies the type of monitor you want to create: 

Log File – Select this monitor type to monitor a log file. 

Directory – Select this monitor type to monitor a directory. 

File/Directory Name – Specifies the path to the log file or directory 

that you want to monitor. For example, c:\temp\mlog.txt. 

Metric Type – Select the type of metric. The metric types that are 

available depend on the type of monitor you are using: 

Log File Monitor 

Perl Expression – select this option when you want to use a Perl 

expression to collect numerical performance data from a log file 

entry. 

Number of Matching Records – this metric returns the number of 

records that match the entered Perl expression. 



File/Directory Existence – this metric returns a one when the file 

or directory exists, otherwise, it returns a sample failure. 

File/Directory Size – this metric returns the size of the file or 

directory. 


returns the number of records written to the log file since the last 

sample. 

Time Since Last Modified – this metric returns the length of time 

since the log file was changed. 

Directory Monitor 

File/Directory Existence – this metric returns whether the file or 

directory exists. 

File/Directory Size – this metric returns the file or directory size. 

Number of Folders – this metric returns the number of folders in 

the directory. 

Number of Files – this metric returns the number of files in the 

directory. 


since the directory was last modified. 



time operating mode. In this mode each line read from the file is 

treated as a single log file entry and is processed individually. 


arbitrary record-based mode. In this mode a Perl expression is 

used to determine where each record in the file starts and ends. 

The expression is applied to the data as it is read, and records are 







Max Record Length – Enter the maximum record length. Entries 

that exceed this length are ignored. 

Record Format (PERL) – Enter the Perl expression defining the 

record, including the delimiter character. 

Inactivity Sample Count – If the Log File data source detects that the 

monitored log file does not log any new information for the number 

of sample counts you enter here, a sample failure will result. A 

value of 0 (the default) disables this setting. 

Perl Expression – Specifies a Perl Expression used to collect 


checks the last entry whenever the log file changes. This returned 

data can then be used within OneSight, both for alerting, using 

threshold alerts, and reporting. 

To check if the file exists, use the File/directory exists metric type 

and leave this field blank. 




you are measuring a log file response that is a string, it can be 


Mappings field. Simply specify a semicolon delimited mapping 

of Strings to Integers. For example, ―false=0;true=1‖; will 

convert a ―false‖ reading to a 0 value in OneSight, and this will 

be displayed in OneSight Status as ―false=0‖. If you only want to 

display the string on the OneSight status page, use a colon, rather 

than a semi-colon to delimit the values. 










Sample Continuously – Select to sample continuously. This field is 

only available when Metric Type is Perl Expression value. 

File/Directory Must Exist – Select to check that the file/directory 

exists. 

Directory Range – Specify whether to monitor all directories 

including sub directories or to monitor only the top directory. This 

field applies to all metric types except File/Directory Existence 

monitors. 

Alert Collection Mode – Select how you want alerts to be processed. 

Report Alerts as they Occur – If multiple alerts occur on the same 

trigger they are all sent. Alerts with the same timestamp as a 

previous alert will not be sent. 

Report First Alert Encountered for a Trigger – The first alert that 

occurs during a sample run for a specific trigger is the only one 

sent. Subsequent alerts for the same trigger are ignored. 

Report Last Alert Encountered for a Trigger – The last alert that 


sent. Previous alerts for the same trigger are ignored. 



message. 



NT Event Log Dialog Box 

Use this dialog box to add or modify the NT Event Log data source 

to a metric. The NT Event Log data source monitors events logged 

in the Event Viewer. 

Note: This data source applies to both Windows 2000 metrics and 

Windows 2003 metrics. 

Event log – Select whether the Windows event log that is being 

monitored is an Application, System, or Security event log. You can 

also specify a different type of log by typing its name here. 

Inactivity sample count – If the Event Log data source detects that 

the monitored log file does not log any new events for the number 

















message. 


None – Checks to see if the monitor is operational. 



Number of Matching Records – Returns the number of records that 

match the specified criteria. 

Number of Records in Log – Returns the total number of records 

in the log. 



Time Since Last Modified – Returns the time since the log was last 

modified. 

The following fields are available when you select a metric type of 

Perl Expression or Number of Matching Records. 




results. 

Match if NT Even Source is – Filter based on NT event source. 

Match if NT Event ID is – Filter based on NT event ID. 

Match if Category is – Filter based on category. 

Match if Username is – Filter based on Username. 

NT Event Type – Select the type of NT event you want to monitor. If 

no type is selected, all event types are monitored. 



Perfmon Dialog Box 

Use the Perfmon Data Source Configuration dialog box to add or 

modify how the Perfmon data source is configured. As you work in 

this dialog box, you may find it helpful to view the Windows 

Performance Monitor as a reference. If you do use Windows 

Performance Monitor to obtain object and counter names, enter the 

names exactly as they appear in Windows Performance Monitor 

(use the same spacing, capitalization, and the like). 

Object – Enter an object, for example: LogicalDisk. In the Windows 

operating system, an object is a standard mechanism for identifying 

a system resource. 

Counter – Enter a counter, for example: Free Megabytes. The counter 

defines what is being measured in the object. Every object has at 

least one counter. 

Instance – Enter an instance, if any, for the object you entered 

above, for example: D: 



An object can have one, several, or no instances. For example, for a 

system with multiple processors, the Processor object type has 

multiple instances, each processor being a different instance. Using 

this example, you would enter one of those instances under Instance. 

Some object types, such as Memory and Server, do not have 

instances, in which case you do not need to enter anything under 

Instance. For disk drive instances, use upper case letters—for 

example, D: instead of d:. 

Leave the Instance box empty if Sample for Each is set to something 

other than System. 


collected. 

If the metric measurement is expressed in kilobytes, setting Scale to 


expressed in milliseconds, setting Scale to .001 will translate it to 

seconds. 

Note: for Perfmon data sources, setting Scale to 0 will use a default 

value provided by Windows. 

To display the Windows Performance Monitor: 

In both Windows 2000 and Windows 2003, select the Run option 

from the Start button, then type perfmon or use the following 

procedure. 

1. Click the Start button. 

2. Point to Programs, then Administrative Tools. 

3. Click Performance Monitor. The Performance Monitor opens. 

4. If you are using the Performance Monitor to display the Object, 

Counter, and Instance fields, click the Add counter toolbar button 

(+ symbol). 



Ping Dialog Box 

Use the Ping Data Source Configuration dialog box to add or 

modify how the Ping data source is configured. 

Metric – Specifies the metric to use for the data source: Average 

Round Trip Time or Percentage of Success. 

Length – Enter the number of bytes that should be included in each 

echo request packet. 

Time to Live – Specify the maximum number of router hops 

permitted. If the echo request takes more than the maximum number 

of hops, it is thrown away and the Ping attempt is treated as a 

failure. 

Time Out Seconds – Enter the amount of time (in seconds) to 

wait for an echo reply. If an echo reply is not received in this 

amount of time, the Ping echo request is retried. 

# of Packets – Specify the number of packets to send for the Ping 

echo request. 




collected. 





Port Dialog Box 

Use this dialog box to add the Port data source to a metric or 

modify how a Port data source is configured. 

Port – Specifies the port you want to monitor. Click the arrow to 

select from a variety of common ports. If the port you want to 

monitor is not listed, select Other and type in the port number. 

Time Out Seconds – Specifies the number of seconds to wait for 

a reply. 

Retries – Specify the upper limit for the number of times a connect 

request is retried. For example, if Retries is set to 2, the connect 



request will be sent up to 3 times. After the third try, if no response 

is received, the connect attempt is treated as a failure. 

Send String – Specifies the query to be sent to the port. By default, a 

linefeed character is appended to the string you specify. If you want 

to use an alternate control character, simply append the character 

you prefer. If you don’t want any control character appended, add 

the null character (\0x00) to the end of the string. 

Match String – Specifies the string that should be returned. If you 

specify this string, you can trigger an alert and an action plan when 

the string is not returned. String matching is case sensitive. 

Maximum Read Length – Specifies maximum length of the string to 

be read from the port when searching for the text specified in the 

Match String box. 

Process Dialog Box 

Use this dialog box to add the Process data source to a metric or 

modify how a Process data source is configured. 



Process – Specify the name of the process you want to monitor. To 

monitor all processes on a system, leave this field blank and set the 

Sample for Each field in the Metric Editor to Process. You can then 

select Process Discovery on the Find Components dialog box to find 

all processes on the system. 

Measurement – Specifies the process measurement you want to 

monitor. Click the arrow to select either count (number of 

instances), memory (in MB), or CPU (in percent). 

Method of Aggregation – Specifies the method of aggregation to use 

for monitoring memory or CPU usage. Click the arrow to select a 

method, either Total, Min, or Max. 

It is common for an application to run multiple processes with the 

same name or even the same commandline. Method of Aggregation 

indicates how to aggregate data about multiple processes. ―Total‖ 

specifies that the monitor should add the measurements from all 

such processes, for example, returning the total memory used by 

processes named ―httpd‖. ―Min‖ specifies the smallest measurement 

for all such processes, returning, for example, the least CPU usage 

for all such processes. ―Max‖ specifies the largest measurement for 

all such processes, which would help determine, for example, if a 

single httpd process is using most of the CPU. 

Send sample failure if zero processes found – Sends a sample failure 

if no processes are found. 

Service Dialog Box 

Use this dialog box to add the Service data source to a metric for a 

profile monitoring a Windows 2000 or Windows 2003 machine or 

to modify the way a Service data source is configured. 



Note: OneSight also offers a dedicated Service monitor that allows 

you to monitor a service metric on an individual system. 

Service Display name – Specify the 2000 or Windows 2003 service 

you want to monitor with this metric. This is the display name as it 

appears in the Control Panel. 

To see details about the Windows services that you want to monitor 

in Windows 2000 or 2003, open the Control Panel, then click 

Services in Administrative Tools. 



SNMP Dialog Box 

Use this dialog box to add the SNMP data source to a metric or 

modify how an SNMP data source is configured. SNMP (Simple 

Network Management Protocol) is a widely used protocol that 

governs network management and the monitoring of network hosts 

and devices and their functions. OneSight’s SNMP data source 

allows you to monitor hosts and devices that have SNMP enabled 

(see Adding a Data Source for more information). 

Object ID Settings 

Object ID – Specify an Object ID (OID). OneSight only uses objects 

that return numeric values. If the Object ID you enter does not begin 

with a ―.‖, OneSight assumes the OID is within the MIB-II 

(.1.3.6.1.2.1) hierarchy. Enter the following information in the 

Object ID box. 

Get – Enter the OID and append the instance identifier to it. For 

scalar objects, the instance is always 0. For example, if you want 

to retrieve the MIB-2 sysUpTime (.1.3.6.1.2.1.1.3) object, enter 

.1.3.6.1.2.1.1.3.0 in the Object ID box, since there is only one 



instance of this object, and scalar SNMP objects require the ―.0‖ 

instance identifier. 

Table Get – Enter the OID. Do not append the instance identifier 

(―.0‖) to it since, for columnar (table) objects, the instance is 

non-zero and determined by OneSight’s search of the Search for 

String parameter within the Table Get OID parameter’s column. 

Translation Type – This setting is available only if you select the 

Enable check box under the Divide by Object ID setting. The Delta 

translation type means that a metric used in a Divide by 

calculation is computed as the difference between its current and 

previous samples. This allows the Object ID to reflect a complex 

calculation such as the difference between the current collision 

count and the previous collision count divided by the difference 

between the current output packets and the previous output 

packets. 

General Settings 

Action – Select an action: 

Get – Allows you to perform a traditional SNMP get operation. If 

you select Get, you must also specify a valid Object ID, and 

append the instance identifier to it. 

Table Get – Allows you to search an SNMP table for numeric data 

associated with a particular instance, or row, of the table. If you 

select Table Get, you must also specify a valid Object ID (no 

instance identifier), Search for String, and column to look in. 

Search for string – This setting only applies if Table Get is selected 

in the Action box. Enter the string or regular expression that 

OneSight will search for in the Table Get OID column that you 

specify. Because this string search identifies the instance, or row, of 

the table, you do not need to append an instance identifier under 

Object ID. 



In the case of a web server, this is the port number of the web 

server. 

Refer to Using Regular Expressions for Pattern Matching in 

Chapter 5 for more information on using regular expressions. 

in OID column – This setting only applies if Table Get is selected in 

the Action box. Enter the column where OneSight will search for 

the Table Get string you specified above. 


collected. 





MIB Browser – Displays the MIB browser in a separate window. You 

can view objects in the MIB browser and copy and paste the 

appropriate OID into the Object ID field on the Add Data Source 

screen. 

Divide by Object ID settings 

Use the settings under Divide by Object ID in conjunction with Object 

ID settings (above) to gather information that’s best expressed as a 

ratio. If you do this, the value retrieved by Object ID (above) is the 

dividend and the value retrieved by Divide by Object ID (below) is the 

divisor (Object ID/Divide by Object ID). 

Enable – Select the Enable check box to divide the value of the 

Object ID above by the value of the Object ID you specify below. 

Object ID – Enter an object ID. For example, in the HOST- 

RESOURCES MIB, disk size (hrStorageSize) and disk in use 

(hrStorageUsed) are two different OIDs which, when divided, 

give you the ratio, or portion, of the disk that is in use. Using this 



example, you could enter 25.2.3.1.6 as the Object ID and 

25.2.3.1.5 as the Divide By Object ID. 


Enable check box under the Divide by Object ID settings. The Delta 



previous samples. This allows the Object ID to reflect a complex 




packets. 











reading to a zero value in OneSight. 

SNMP Trap Dialog Box 

Use this dialog box to add the SNMP Trap data source to a metric or 

modify an SNMP Trap data source. 

MIB File – Optionally specifies the name and location of the 

Management Information Base (MIB) file for the SNMP device. The 

MIB file is provided by the SNMP device manufacturer. The MIB 

file allows OneSight to import the OIDs by name rather than 

number. When you specify a MIB file, the Enterprise and Trap Type 

lists will be populated with the OID names defined in the MIB file. 



You can select the names in the Enterprise and/or Trap Type lists to 

define which SNMP Trap to monitor. 

The OneSight Server Administrator must copy other SNMP device 

manufacturer MIB files to the MIB file directory of the OneSight 

Server before a filename can be specified in this field (OneSight 

includes a onesight.mib file). If you get an error when specifying a 

MIB file, contact your OneSight Server Administrator to verify the 

SNMP device MIB file is available on the OneSight server. 

List Mibs – Lists the MIB files in the C:\Empirix\OneSight\mibs\ 

directory on the OneSight server. Use to enter a MIB that is 

not listed. 

Get Values – Gets the values for Enterprise and Trap type from the 

MIB file entered in the Mib File field. 

Upload MIB – Lets you upload a MIB file to the 

C:\Empirix\OneSight\mibs\ directory on the OneSight server. 

MIB Browser – Displays the MIB Browser in a separate window. 

You can view objects and copy and paste them into the Add 

Monitor dialog box. 

Note: When using SNMP Trap metrics with translation, the mib file 

must be copied to the following two locations. If it is not, OneSight 

will still receive and process the trap, however, it will not translate 

the OIDs to text. 

c:\Empirix\Onesight\mibs\ 

c:\Empirix\DataCollector\mibs\ 

Enterprise – Specifies the Enterprise criteria to define which SNMP 

Trap to monitor. Enter a specific Enterprise OID. 

Trap Type – Specifies the Trap Type criteria to further define which 

SNMP Trap to monitor. Enter a specific trap type OID. 



Reset Trap – Specifies the Trap Type criteria that will reset any 

existing alerts for this monitor. 

Socket Dialog Box 

Use this dialog box to set up a TCP/IP socket to collect data on a 

TCP/IP port on a remote system. The data source connects to the 

host and port specified and treats the data it receives in the same 

way as it would treat the data in a log file. This is useful, for 

example, for monitoring a serial port via a serial to TCP converter 

or for monitoring a system that has a logging port. 

TCP/IP Port – Specify the TCP/IP port that you want OneSight to 

connect to. Data must be being sent down this port. 


Perl Expression – select this option when you want to use a Perl 

expression to collect data. 



Number of Matching Records – this metric returns the number of 

records that matched the entered Perl expression. 

Total Records Encountered Since Last Sample – this metric returns 

the number of records written since the last sample. 


since data was sent to the channel. 



time operating mode. In this mode each line read from the file is 

treated as a single log file entry and is processed individually. 


arbitrary record-based mode. In this mode a Perl expression is 

used to determine where each record in the file starts and ends. 

The expression is applied to the data as it is read, and records are 





Max Record Length – Enter the maximum record length. Entries 

that exceed this length are ignored. 

Record Format (PERL) – Enter the Perl expression defining the 

record, including the delimiter character. 

Inactivity Sample Count – If the Log File data source detects that the 

monitored log file does not log any new information for the number 



Perl Expression – Specifies a Perl Expression used to collect 




checks the last entry whenever the log file changes. This returned 

data can then be used within OneSight, both for alerting, using 

threshold alerts, and reporting. 

To check if the file exists, use the File/directory exists metric type 

and leave this field blank. 




you are measuring a log file response that is a string, it can be 


Mappings field. Simply specify a semicolon delimited mapping 

of Strings to Integers. For example, ―false=0;true=1‖; will 

convert a ―false‖ reading to a 0 value in OneSight, and this will 

be displayed in OneSight Status as ―false=0‖. If you only want to 

display the string on the OneSight status page, use a colon, rather 

than a semi-colon to delimit the values. 








Sample Continuously – Select to sample continuously. This field is 

only available when Metric Type is Perl Expression value. 















message. 

UNIX System Dialog Box 

Use this dialog box to add the UNIX System data source to a metric 

or modify a UNIX System data source. For the UNIX System data 

source to function correctly, the OneSight Remote Agent must be 

installed on the monitored machine. 



The metrics this data source can gather depend on the data sources 

(described below) that collect the data. For example, for Solaris 

metrics, the data source will use the kstat (3K) facility to collect 

CPU, disk, and memory data; the proc (/proc) file system to collect 

process data; and the Streams mechanism to collect network data. 

Metric Settings 

Data Source 

kstat – Provides kernel statistics. 

proc – Retrieves process data. 

streams – Provides network-related data. 

iostat – Reports disk and I/O activity metrics similar to those 

provided by the iostat -x command. 

vmstat – Reports statistics regarding process, virtual memory, 

trap, and CPU activity similar to those provided by the vmstat 

and vmstat -S commands. 



df – Retrieves the amount of disk space occupied by mounted or 

unmounted file systems, the amount of used available space, and 

how much of the file system’s total capacity has been used. 

For more information about how to collect statistics using UNIX 

system data sources, check the OneSight Support area of the 

Empirix.com web site. 

Object – Enter an object for the data source you selected. 

Metric – Enter a metric. 

Scale - Type the multiplier you want applied to the data that is 

collected. 





Translation Type – This setting is available if you select the Enable 

check box the Divide by Metric option described below. The Delta 

translation type means that a metric used in a Divide by calculation 

is computed as the difference between its current and previous 

samples. This allows the metric to reflect a complex calculation 

such as the difference between the current collision count and the 

previous collision count divided by the difference between the 

current output packets and the previous output packets. 

Divide by Metric Settings 

Use the settings under Divide by metric in conjunction with Metric 

settings (above) to gather information that is best expressed as a 

ratio. If you do this, the value retrieved by Metric (above) is the 

dividend and value retrieved by Divide by metric (below) is the 

divisor (Metric/Divide by metric). 



Enable – Select the Enable check box to divide the value of the 

metric above by the value of the metric you specify below. 

Object – Enter an object. The data source specified in the Data 

Source list, under Metric, is the data source that will be used. 

Metric – Enter a metric. 


Enable check box under the Divide by Metric settings. The Delta 



previous samples. This allows the metric to reflect a complex 




packets. 

URL Dialog Box 

Use the URL Data Source Configuration dialog box to add or modify 

how the URL data source is configured. 



Report on – Lets you check the amount of time it takes to download the 

file/content or the size of the file. Once you know the file size you can 

create an alert to check whether the size is greater than expected. 

Download Time – Returns the download time. 

Download File Size – Returns the size of the file. 

Perl Expression – Specifies a Perl Expression used to retrieve the 

file size. 









reading to a zero value in OneSight. 

Measurement Details 

Retrieve Images – If you want to calculate URL availability and 

access time with retrieval of embedded images (such as .gif and 

.jpeg files and references within tags) included, select this 

check box. 

Retrieve Objects – If you want to calculate URL availability and 

access time with retrieval of embedded objects (such as ActiveX 

objects and Java applets) included, select this check box. 

OneSight measures the time taken to retrieve data used by 

objects, but does not include the time needed to retrieve any 

executable file required in order to interpret the data. Content 

types other than HTML and images are also classified as objects. 

Save object download details – When selected, collects data for the 

object timer report. 



Authentication Settings – Fill in User Name and Password information 

to monitor URLs with HTTP Basic Authentication restrictions. 

User Name – If the URL specified requires a name and password 

for access, enter the name in this field. 

Password – If the URL specified requires a name and password 

for access, enter the password in this field. 




If you find that a OneSight URL monitor fails to reach a URL when your 

browser successfully connects to the same URL, check your proxy server 

settings in your browser. For example, in Internet Explorer, select 

Internet Options from the Tools menu and then click LAN settings on 

the Connections tab. If proxy server settings are configured for your 

browser, they may also need to be configured for the URL monitor. 



Proxy Host – The name or IP address of the proxy server. 


Proxy User Name – The proxy server login user name. 




Virtual Agent Dialog Box 

Use this dialog box to add the Virtual Agent data source to a metric. 

Operating System – Select the operating system being used on the 

host machine. If you select Custom Setting, enter the Command, Perl 

Expression, and Key Index manually. 

Metric Name – Specifies the metric to measure. If you select a 

predefined metric for one of the operating systems, the Command, 

Perl Expression, and Key Index are automatically entered. If you select 

Custom Setting, enter the Command, Perl Expression, and Key Index 

manually. 

Command – Specifies the command to execute on the host machine. 

Perl Expression – Specifies a Perl expression to use to report the 

data returned from the executable program. See Using Regular 

Expressions for Pattern Matching in Chapter 5 for more 

information about specifying Perl expressions. 



Process remote server response as a single block – When selected, 

all output is treated as a single block of data. The default is to treat 

output as one line at a time. 

String Mapping – OneSight collects numeric performance data. If 

you are measuring a response from a Virtual Agent that is 

represented a string, it can be converted to a number for use in 

OneSight by using the String Mappings field. Simply specify a 

semicolon delimited mapping of Strings to Integers. For example, 

"false=0;true=1" will convert a "false" reading to a 0 value in 

OneSight, and this will be displayed in OneSight Status as 

"false=0". If you wish to just display the string in OneSight Status, 

use a colon, rather than a semicolon, to delimit your values. 

If you neglect to provide a mapping for a specific string, OneSight 

will consider this a Sample Failure, and report the String that was 

returned. 

String Mappings can also be used to translate a number to a String 

for display in OneSight Status. This is helpful when numbers 

represent an objects state. 

Note that string matching is case-insensitive. 

Key Index – Specifies which value within the Perl expression that 

represents the instance of the data returned from the executable 

program. If the metric can be an instance, then the key defines 

which value should be checked for that particular instance. 

-1 – there is no key to match. The Virtual Agent returns the first 

value it matches. 

0 – the Virtual Agent uses the first value it matches to compare 

against the configured component. If a match is found, the second 

match is returned as the metric to OneSight. 



1 – the Virtual Agent uses the second value it matches to 

compare against the configured component. If a match is found, 

the first match is returned as the metric to OneSight. 

Refer to the examples at the end of this section for information on 

how the perl expression and the key index should be configured to 

correctly extract a value. 

Command Procedure – Select the state machine containing the XML 

for running a complex command. This is useful, for example, when 

you want to run a different command depending on the output of a 

previous command. Refer to “Configuring State Machines,” in 

Chapter 5 for more information. 

Configuration Example 1 

The user has a Linux system with the following components (―/‖ 

and ―.sys‖) defined for the file system. The command that is to run 

is df –a and the output is as follows: 

File 

System 

1Kblocks 

Used Available Use% Mounted On 

tmpfs 498792 213176 285616 43% / 

proc 0 0 0 - /proc 

sysfs 0 0 0 - /sys 

devpts 0 0 0 - /dev/pts 

usbfs 0 0 0 - /proc/bus/usb 

The following are defined in the Metric Editor: 

Command: /bin/df –a 

Perl Expression: /\S+\s+([0-9]+)\s+[0-9]+.*\S+\s+(\S+)/ 

Key Index: 1 



In this example, the perl expression checks each line of output and 

extracts the following values: 

498792 / 

0 /proc 

0 /sys 

0 /dev/pts 

0 /proc/bus/usb 

The Virtual Agent then checks each line of the output and uses the 

key index to identify a matching row and returns the appropriate 

value. 

Note: The Virtual Agent only uses the first two matches it finds. For 

example, it uses the first two values in parenthesis, not including 

the column delimiters such as (?:\S+\s+). 

Configuration Example 2 

Using the example above, what happens if the components are 

defined as tmpfs and sysfs. the Metric Editor configuration would 

be as follows: 

Command: /bin/df –a 

Perl Expression: /(\S+)\s+([0-9]+)\s+[0-9]+.*\S+\s+(\S+)/ 

Key Index: 0 

The matching output would be: 

tmpfs 498792 

proc 0 

sysfs 0 

devpts 0 

usbfs 0 

Even if the final (\S+) remains in the pattern, it will not be included 

in the matches that the Virtual Agent evaluates. In addition, the key 

index had to be changed to match the newly defined components. 



WMI System Dialog Box 

Use this dialog box to add the WMI data source to a metric or 

modify a WMI data source. 

Namespace – Specifies the name space, for example: root\cimv2 (the 

default). Data in the WMI repository is organized by schemas, 

which are loaded into ―namespaces.‖ A namespace provides a 

domain (or container) for a schema and for the instances of the 

classes in that schema. 

Select – Specifies the name of the metric, for example: FreeSpace. 

From – Specifies the class name, for example: Win32_LogicalDisk. 

Where – Specifies the key name and value, for example: Name=”C:\”. 


collected. 






you are measuring a WMI object representing a String datatype, it 

can be converted to a number for use in OneSight by using the 

String Mappings field. Simply specify a semicolon delimited 

mapping of Strings to Integers. For example, ―false=0;true=1‖; 

will convert a ―false‖ reading to a 0 value in OneSight, and this 

will be displayed in OneSight Status as ―false=0‖. If you only 

want to display the string on the OneSight status page, use a 

colon, rather than a semi-colon to delimit the values. 








Setting a Metric’s Sampling Interval 

To set a metric’s sampling interval: 

1. In the Metric Editor, click the General tab. 

2. In the Sample Every: box, enter how often you would 

like the web component sampled. 



Removing Metrics 

3. From the list to the right of Sample Every , select 

whether the Sample Every value should be measured in 

Seconds, Minutes, or Hours. 

To delete a metric: 

1. In the Profile Editor, click the Global Metric Manager button. 

The Global Metric Manager opens. 

2. Highlight the metric’s name under Global Metrics and click 

Remove. 

3. A warning dialog box appears, confirming that you intend to 

permanently delete the metric. Click OK. 

The metric is removed from the profile, and from any other 

profiles to which it belonged. 


Modifying a Metric’s Data Source 

Modifying a Metric’s Data Source 

To modify a metric’s data source: 

1. In the Metric Editor, click the Data Sources tab. 

2. Modify the configuration information (see the descriptions of 

the settings in the Data Source Configuration dialog boxes for 

more information). 

3. Click OK. 



Configuring Systems 

Adding Systems 

Systems, and information about the components on each system, 

must be identified so that OneSight profiles can be used to create 

profile monitors for the web components running on those 

machines. 

You can add systems one at a time or you can add multiple systems. 

Multiple systems are imported from a .csv or .xml file, after which 

you can perform multiple system discovery to discover the 

components to monitor. 

To add a system definition: 


565


2. Click Systems to open the Systems page. 

Show Systems Where contains – Select the 


example, you could search for all systems at the location 

Boston. In addition to plain text, you can enter a PERL 

expression in the contains field. 

Add – To manually set up a new system definition for a 

specified machine, click Add to open the Add System dialog 

box. After specifying the machine’s computer name or IP 

address, click OK. Optionally, you can direct OneSight to find 

system components (such as disk drives, processes, and web 

servers) on the system that you are adding. However, this is not 

necessary because when you apply a profile to the system to 

create a monitor, OneSight prompts you to add any missing 

system components that are tracked by that monitor. 

In the System Editor, on the System tab, specify the Operating 

System that is running on the machine. Click OK in the System 

Editor to save the machine information and return to the Add 

Monitor dialog box. 



Modify – To change the name or system properties of an existing 

system, select the system name in the Systems list and click 

Modify. In the System Editor, make the desired changes, and 

then click OK to update the system information and return to the 

Add Monitor dialog box. 

Remove – To remove a system from the list, select the system 

name in the Systems list and click Remove. 

Import – Displays the Add System dialog box for adding 

multiple systems from a .csv or .xml file that specifies the 

systems to add and optionally, some additional properties. After 

importing the systems, you can use Multiple System Discover to 

find the components to monitor. 

Used By – Opens a list of the profile names that currently use 

the selected system. 

Multiple System Discovery – Displays the discover components 

dialog box for selecting the discovery methods that you want to 

use to discover the components to monitor. 

Note: the systems being discovered must have the same type of 

operating system. For example, they must be all Windows 

machines or all Linux machines. 

Bulk Location Modification – Displays the Bulk Location 

Modification dialog box for changing the location of multiple 

systems. 

3. Click Add to open the Add System dialog box. 

Chapter 7: Configuring Systems 567


Use settings in the Add System dialog box to add a new system 

to the list of systems that are recognized by OneSight for 

monitoring purposes. The Add System dialog box has the 

following settings 

System Name – Type the computer name or IP address that 

identifies the machine. 

Device Type – Specify the type of device. This specification 

affects licensing and which profiles and metrics can be applied 

to the system. Metrics are categorized into three types. Basic 

metrics measure basic operating system performance such as 

CPU, Disk, etc. and cannot be modified. Premium metrics are 

metrics defined by the contact center and cannot be modified. 

All other metrics are advanced metrics. The options are: 

Advanced Server – All profiles can be applied to this system. 

If you are using premium metrics, you must define the system 

as an advanced server. Each profile applied to this system 

consumes one advanced server license. In addition, each 

premium profile applied to this system consumes both an 

advanced server license and a premium profile license. 

Basic Server – Only basic profiles such as Windows, Linux, 

Solaris, Unix, etc., can be applied to this system. The license 

consumed is per system, not per profile. 



Network Device – Only profiles with Ping or SNMP metrics 

can be applied to this system, otherwise a licensing error will 

occur. The license consumed is per system regardless of the 

number of profiles applied. 

4. In the System Name box, type the computer name or IP address 

that identifies the machine you want to add and select the 

device type. When you click OK, the System Editor opens. 

Use settings in the System Editor to supply information about 

the components on the current system. The System Editor lists 

all the types of system components that you can monitor on the 

specified machine. 

Display Name – Identifies the system that you are currently 

defining. 

Components – Shows the types of objects that profiles are used 

to monitor: System, CPU, Database, Database log file, Disk, 

File System, Interface, Port, Process, and Web server. When 

you add a system component, the Components list expands to 

show the name of the added components under the appropriate 

category. For example, if you add a disk drive, the name of the 



drive you added appears in the Disk section of the Components 

list. 

Add – Opens the Add System Component dialog box so that 

you can add a system component or a global component type. 

Remove – Removes the currently selected system component 

from the system definition. 

Add Data Source – When you select a component in the 

Components list, and click Add Data Source, the Add Data 

Source dialog box is displayed listing the data sources 

applicable to this component. When you click OK, the Property 

tabs are displayed with the settings for configuring the data 

sources that OneSight profile metrics use to obtain information 

about this type of system component. 

For information about the Properties tabs used for each type of 

component, refer to the following sections. 

Remove Data Source – Removes the selected data source. 

Discover Components – Directs OneSight to find system 

components on the current system. The Find Components 

Configuration dialog box opens so that you can specify what 

methods should be used to find components. When you click 

OK, the discovery process runs and reports on its progress. 

When the process completes click Done to return to the System 

Editor. 

5. You can use the System Editor to identify all of the components 

on this system that you want OneSight to monitor. See Adding 

System Components Manually for more information. 

6. Click OK to save the system definition you have added and 

return to the Add Monitor dialog box. 


Adding Multiple Systems 


You can import multiple systems into OneSight using a .csv or .xml 

file that contains the system names and some optional additional 

properties. This file must be located in the OneSight imports 

directory. A sample file, systems.xml, is located in the imports 

directory. 

The following optional properties can be included in addition to the 

system names: 

Settings on the System’s System tab: Device Type, IP Address, 

NetBIOS Name, Operating System, Location, and On Failure. 

SNMP Discovery settings: Community, Timeout, Retries, Port, 

and Version. 

Windows NT authentication information: User, Password, and 

Domain. 

Virtual Agent discovery settings: Connection Method, Port, 

Prompt, Charset, Operating System, User, Password, Private Key 

file, Login Timeout, and Discovery Timeout. 

User group cannot be specified. Imports must be done by specific 

user group. 

Property names in the import file must match those expected by 

OneSight. If they do not, an error message is displayed. The 

following example .xml files show the property names that should 

be used. Following is a list of valid values for certain properties: 

DeviceType – NetworkDevice, BasicServer, AdvancedServer 

OperationSystemType – NT_OS, OTHER_UNIX_OS, 

SUN_SOLARIS_OS 

Location – Default Location, 



OnFailure – Send ping, Run Traceroute, Do Nothing 

SnmpVersion – Snmp_Version1, Snmp_Version2c 

ConnectionMethod – Local Machine, SSH, Telnet 

Charset – Big5, Big5-HKSCS, EUC-JP, etc., UTF-16, etc., UTF-8, 

etc. 

OperatingSystem – HPUX-v11_0, Linux-RH-v7_1, HPUX, 

AIX-v4_3, Solaris-v5_8, Windows 

Following is an example that includes only the system name. 

 

 

 

 

 

Following is an example that includes the system name and 

discovery properties for SNMP. 

 

 

 

 

 

 

 

 

 

 


discovery properties for Windows. 

 

 

 

 

 

 



 

 


discovery properties for the System tab. 

 

 

 

 

 

 

 

 

 

 

 


discovery properties for Virtual Agent. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

To add multiple systems: 


2. Click Systems to open the Systems page. 

3. Click Import to display the Add systems dialog box. 



Import File Name – Enter the name of the .csv or .xml file that 

contains the systems that you want to import and any optional 

properties. This file must be located in the OneSight imports 

directory. 

4. Enter the name of the import file. This file must be located in 

the OneSight imports directory. 

5. Click OK. The systems are imported. You can now discover the 

components to monitor by clicking Multiple System Discover. 

Refer to “Discovering Multiple Systems” later in this chapter. 


Adding a New Component Type 


Use options in the Add System Component dialog box to add a new 

global component type. 

Information about the components on each system must be 


for the web components running on those machines. The Add New 

Component Type dialog box allows you to manually add new 

global components types in addition to those defined automatically 

by OneSight. You can also use this dialog box to add a new 

component manually. 

After adding a new component type, you need to configure the data 

sources that gather information for the profile metrics that apply to 



this component type. In the System Editor, select the component 

type that you added and fill in the discovery settings on the 

Properties tabs. See the Find Components Configuration dialog box 

help for information on running the Find Components discovery 

procedure. 

Add type – Select the type of component you are adding to display 

the fields associated with the selected type. 

Component Type – Select this option to add a new component 

type. This is the only option available from the system node. 

Component – Select this option to add components for the 

selected component type. 

Component Type Definition 

Name – Specify a meaningful name that allows you to identify 

the specific component type you are adding. 

Description – Type a description that helps you differentiate this 

component type from the other component types you are defining 

to monitor your web components. 

Component Definition 

Component type – The type list defaults to the kind of component 

that was selected when you clicked the Add button to open the 

Add System Component dialog box. Select the type of 

component you want to add and configure. 

Component – Specify a meaningful name that allows you to 

identify the specific component you are adding. You can add 

multiple instances of a component using the following syntax: 

name[[[numbers..numbers]]] 

For example, e[[[8..10]]] creates the following components: 

e8, e9, and e10. 


Modifying System Definitions 

Data Sources to Add – The data sources applicable to the type of 

component you are adding are listed. Select the data sources that 

you want to use. When you click OK the associated tabs are 

displayed so that you can configure the selected data sources. 


To modify a system definition: 


2. Click Systems. 

3. Select the system in the Systems list and click Modify. The 

System Editor opens. Use settings in the System Editor to 

update information about the components on the current 

system. 

CPU System Information 

When you add a new CPU component, you must add information to 

the Properties tabs to configure the data sources that OneSight 

metrics use to obtain information about the CPU. 

Component Tab – The Component Tab shows the name of the CPU 

you are configuring. Changing this name will affect the CPU entry 

on the left side of the System Editor dialog box. 

Name – In the Name box, specify a meaningful name that allows 

you to identify the specific CPU you are adding. 

Perfmon Tab – The Windows Performance Monitor (Perfmon) can 

be used with OneSight to gather resource information for specific 

components and program processes throughout your system. To 

enable OneSight to use this information, you must first start and 

configure Performance Monitor for your system. For more 

information, see Chapter 5. 



Instance – Typically, this value is zero for single-processor 

machines. If you have a multiprocessor machine, then look up the 

Instance value in the NT Performance Monitor. 

SNMP Tab – Adding information to the Simple Network 

Management Protocol (SNMP) tab enables OneSight to provide 

specific performance and configuration information on network 

devices, such as routers, or on hosts, such as workstations or 

mainframes. 

To use SNMP with OneSight, you must enable SNMP on the 

machines you intend to monitor. For more information, see the 

SNMP System Requirements. The OneSight Solaris profile queries 

the Sun SNMP agent for Sun’s MIB and the RFC-1213 (MIB-2). 

The following options are available on the SNMP tab for the 

component type. 

Object ID (to override default discovery) – Enter the object ID of 

the object you want to discover if it is different than the default 

discovery. Click Browse to display the MIB browser for 

searching for the object. 

Perl Expression – Enter a Perl expression if you want to further 

qualify the results returned by the discovery request. Refer to 

Using Regular Expressions for Pattern Matching in Chapter 5 

for more information about regular expressions. 

The following option is available on the SNMP tab for individual 

components. 

Search for string – This field is automatically filled in as a result 

of discovery based on the Object ID and Perl expression that 

were entered. 

UNIX System Tab – Currently, the CPU component does not use 

UNIX System information as a data source. Settings on this tab can 

be ignored. 



Virtual Agent Tab – This tab is necessary when you are using a 

virtual agent metric and you apply a profile that makes use of the 

component. 

Instance – Enter the component that you want to monitor. 

WMI Tab – Windows Management Instrumentation (WMI) can be 

used to provide OneSight with in-depth information about the 

configuration, status, and operational aspects of your Windows 

operating system. 


Database System Information 

After OneSight has discovered a database on a system (or you have 

added a database to the system list yourself), you must add the 

following information for OneSight to monitor the database. 

Oracle Database System Information 




Note: The strings in the examples below are case-sensitive: use the 

same case as displayed. 

Component Tab – The Component tab shows the name of the 

database you are configuring. Changing this name will affect the 

database entry on the left side of the System Editor dialog box. 

OneSight uses JDBC to connect to your Oracle database. 

JDBC Tab – OneSight uses a JDBC driver to connect to your 

database. Two examples of such a JDBC driver are: 

JDBC-ODBC Bridge (installed as part of OneSight). Before 

configuring the JDBC-ODBC bridge for Oracle, you must first 



install the Oracle Client on the OneSight server and set up an 

ODBC DSN. 

Oracle Thin JDBC driver. You will need to install the Oracle Thin 

JDBC driver on the machine that runs OneSight. Download the 

JDK 2.0 version from 

http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.htm 

l. Unzip the driver classes into a Classes folder beneath your 

OneSight folder. 

For monitoring enterprise level databases, the Oracle Thin JDBC 

driver is recommended. 

Driver – Select a driver type from the list: Oracle Thin JDBC driver, 

Inet Sprinta JDBC driver for Microsoft SQL Server, Sun 

JDBC:ODBC Bridge, or Custom. You must have the appropriate 

driver installed on the OneSight Server in order to set up a Database 

monitor. 

Driver String – This information will vary depending on the type of 

database that you are monitoring. If you selected any option other 

than Custom, the appropriate string is automatically displayed. For 

example, this is the string for the Oracle Thin JDBC driver: 




Connect String – For most drivers, this string is constructed from 

the information you supply in the following fields. The structure of 

the Connect String is different for each driver type, but OneSight 

builds this string for all driver types except a Custom driver type. 

For a Custom driver setting, type in the Connect String. 





database. This is not required for a JDBC:ODBC or Custom driver 

setting. 

Instance – Specify the database instance. 


selected. For example, the default port for an Oracle Thin JDBC 

driver is 1521. Modify the port number if necessary. This is not 

required for a JDBC:ODBC or Custom driver setting. 

Database Name or Database SID – For the Inet Sprinta driver for 

SQL Server, provide the database name. For the Oracle Thin 

JDBC driver, provide the database or server ID. 

System DSN – This field applies to the JDBC:ODBC Bridge driver 

type only. In the Windows Control Panel, locate the System DSN 

in the ODBC Data Sources field to confirm the name of the 

database. The connect string will have the following format: 


jdbc:odbc: 

User name – If a user name and password are required for access 

to the database, enter the user name here. The user must have 

system administrator privileges. 

Password – If a user name and password are required for access 

to the database, enter the password here. 

Perfmon Tab – This tab applies to profiles for Microsoft SQL 

Server. This tab does not apply to Oracle databases. 

Instance – Instance refers to the Perfmon counter instance and is 

not used for monitoring Oracle databases. Leave this field blank. 

UNIX System Tab – The UNIX System tab is used when configuring 

monitors to collect data on UNIX workstations. If the machine you 



are configuring as a monitored system is not a UNIX machine, this 

tab is unnecessary. 

If you are monitoring a UNIX machine, make sure the proper 

OneSight UNIX Remote Agent is installed. For help installing the 

UNIX Remote Agent, see Installing the UNIX Remote Agent in 

Chapter 2. 

Instance – Enter the name of the database to be monitored. 






Sample JDBC settings for Oracle 

Driver – oracle.jdbc.driver.OracleDriver 

Connect String – jdbc:oracle:thin:@DBserver:1521:orcl 

User name – sys 

Password – change-on-install 

SQL Database System Information 




Note: The strings in the examples below are case-sensitive: use the 

same case as displayed. 






OneSight uses JDBC and Perfmon to connect to your SQL Server 

database. 

JDBC Tab – OneSight uses a JDBC driver to connect to your 

database. Two examples of such a JDBC driver are: 

JDBC-ODBC Bridge (installed as part of OneSight) 

Note: The SQL Server ODBC driver is installed with MSDE and 

Microsoft SQL Server. If you do not have either of these on the 

Empirix OneSight server and you are using a remotely installed 

SQL database for OneSight, you need to install the SQL Server 

ODBC driver on the OneSight machine and set up an ODBC DSN. 

The ODBC driver is included with the SQL Server Client utilities. 

Inet Sprinta JDBC driver for SQL Server (installed as part of 

OneSight) 

The information you provide here depends on which of these 

drivers you are using. For monitoring enterprise level databases, the 

Inet Sprinta JDBC driver is recommended. 

Driver – Select a driver type from the list: Oracle Thin JDBC driver, 

Inet Sprinta JDBC driver for Microsoft SQL Server, Sun 

JDBC:ODBC Bridge, or Custom. You must have the appropriate 

driver installed on the OneSight Server in order to set up a Database 

monitor. 

Driver String – This information will vary depending on the type of 

database that you are monitoring. If you selected any option other 

than Custom, the appropriate string is automatically displayed. For 

example, this is the string for the Oracle Thin JDBC driver: 






Connect String – For most drivers, this string is constructed from 

the information you supply in the following fields. The structure of 

the Connect String is different for each driver type, but OneSight 

builds this string for all driver types except a Custom driver type. 

For a Custom driver setting, type in the Connect String. 



database. This is not required for a JDBC:ODBC or Custom driver 

setting. 

Instance – Specify the database instance. 


selected. For example, the default port for an Oracle Thin JDBC 

driver is 1521. Modify the port number if necessary. This is not 

required for a JDBC:ODBC or Custom driver setting. 

Database Name or Database SID – For the Inet Sprinta driver for 

SQL Server, provide the database name. For the Oracle Thin 

JDBC driver, provide the database or server ID. 

System DSN – This field applies to the JDBC:ODBC Bridge driver 

type only. In the Windows Control Panel, locate the System DSN 

in the ODBC Data Sources field to confirm the name of the 

database. The connect string will have the following format: 


jdbc:odbc: 

User name – If a user name and password are required for access 

to the database, enter the user name here. The user must have 

system administrator privileges. 

Password – If a user name and password are required for access 

to the database, enter the password here. 



Sample JDBC settings for SQL Server 

Driver – com.inet.tds.TdsDriver 

Connect String – 

jdbc:inetdae::1433?database=OneSight 

User name – sa 

Password – 

Perfmon Tab – If you use the profiles for Microsoft SQL Server, 

version 6.5 or 7.0 to monitor a database server running either of 

those database applications, the OneSight Server must be able to 

access the server’s Perfmon, and the monitored database server’s 

Perfmon must have SQL object counters. 

Instance – Type the name of the database to be monitored. To 

confirm the database name, use Perfmon on the machine you 

want to monitor and select the object type SQL Server to see the 

database name instance. 








Chapter 2. 

Instance – Enter the name of the database to be monitored. 








Database Instance System Information 

Enter the following information for discovering named instances of 

SQL databases. 




Perfmon Tab – The Windows NT Performance Monitor (Perfmon) 

can be used with OneSight to discovery multiple named instances 

of SQL databases. To enable OneSight to use this information, you 

must first start and configure Performance Monitor for your system. 

For more information, see Perfmon. 

Instance – Enter the instance names separated by a semi-colon. 

For example, ABC;DEF. 

Database Log File System Information 

Currently, the Database log file component type is not used by any 

existing profile metric. This component type will be used for 

database log files when implemented in future database profiles. 

Disk System Information 

When you add a new disk component, you must add information to 


metrics use to obtain information about the disk. 

Note: If you are using Windows 2003/2008 with a firewall, you 

must open the SNMP agent port configured on the SNMP tab (the 

default is port 161), otherwise discovery may fail. 



Component Tab – The Component Tab shows the name of the disk 

you are configuring. Changing this name will affect the Disk entry 



you to identify the specific Disk you are adding. For example: 

“C:”. 

Perfmon Tab – The Windows Performance Monitor (Perfmon) can 

be used with OneSight to gather resource information for specific 

components and program processes throughout your system. To 

enable OneSight to use this information, you must first start and 

configure Performance Monitor for your system. For more 

information, see Perfmon. 

Instance – Typically, this value is the drive letter plus a colon (:). 

For example: “C:”. OneSight will not allow you to enter a 

lowercase value in this box. 





mainframes. 


















components. 



were entered. 





For help installing the UNIX Remote Agent, see Installing the UNIX 

Remote Agent in Chapter 2. 

Instance – When configuring a UNIX profile, enter the system 

disk information using the module.machine.name format. This 

information can be gathered using a UNIX kernel statistics utility 

(for example, kstat). For example: sd.0.sd0 

To configure multiple disk instances, highlight the Disk type and 

click Add. 

For more information about how to collect statistics using UNIX 

system utilities, see the Knowledgebase section on the OneSight 

Support web page. 



component. 









File System Information 

When you add a new File System component, you must add 

information to the Properties tabs to configure the data sources that 

OneSight metrics use to obtain information about the file system. 

Component Tab – The Component Tab shows the name of the file 

system you are configuring. Changing this name will affect the File 

System entry on the left side of the System Editor dialog box. 


you to identify the specific file system you are adding. 








Chapter 2. 

Instance – When configuring a profile for a UNIX machine, enter 

the file system information for the machine you are monitoring. 

For example: /dev 

Information regarding specific mounted file systems for a UNIX 

system can be accessed using the df utility on the UNIX shell. 



To configure multiple file system instances, highlight the File 

System type and click Add. 



component. 


Interface System Information 

When you add a new interface component, you must add 


OneSight metrics use to obtain information about the interface. 

Note: If you are using Windows 2003/2008 with a firewall, you must 

open the SNMP agent port configured on the SNMP tab (the default 

is port 161), otherwise discovery may fail. 

Component Tab – The Component Tab shows the name of the 

interface you are configuring. Changing this name will affect the 

Interface entry on the left side of the System Editor dialog box. 


you to identify the specific interface you are adding. 

Perfmon Tab – Currently, the Interface component does not use 

Perfmon as a data source. Settings on this tab can be ignored. 

Ping Tab – When configuring a profile to monitor a UNIX machine, 

the Ping tab must be configured to specify the IP address. 

IP Address – Enter the IP address for the interface you are 

monitoring. 







mainframes. 
















components. 



were entered. 








Chapter 2. 



Instance – When configuring a profile to monitor a UNIX 

machine, enter the network device information using the 

module.machine.name format. This information is used to identify 

a specific device driver on your UNIX system. For example, 

device drivers are entered using the following format: 

hme.0.hme0 

To configure multiple UNIX devices, highlight the Interface type 

and click Add. 






Load Balancer System Information 

When you add a new load balancer component, you must add 


OneSight metrics use to obtain information about the load balancer. 

Component Tab – The Component Tab shows the name of the load 

balancer you are configuring. Changing this name will affect the 

Load Balancer entry on the left side of the System Editor dialog 

box. 


you to identify the specific load balancer you are adding. 





mainframes. 







The following option is available on the SNMP tab for the 


Object ID – Enter the object ID of the object you want to discover. 


components. 



were entered. 

Service System Information 

When you add a new service component, you must add information 

to the Properties tabs to configure the data sources that OneSight 

metrics use to obtain information about the service. 


service you are configuring. Changing this name will affect the 

Service entry on the left side of the System Editor dialog box. 


you to identify the specific service you are adding. 

Service Tab – The Service tab shows the name of the service you 

want to monitor. 

Service Name – Enter the name of the service you want to 

monitor. 



System Properties Information 

When you add a new system, you must add information to the 

Properties tabs to configure the data sources that OneSight metrics 

use to obtain information about the system. 




System Tab – The System Tab specifies the IP address and 

operating system of the machine you are configuring. 

Device Type – Specify the type of device. This specification affects 

licensing and which profiles and metrics can be applied to the system. 

Metrics are categorized into three types. Basic metrics measure basic 

operating system performance such as CPU, Disk, etc. and cannot be 

modified. Premium metrics are metrics defined by the contact center 

and cannot be modified. All other metrics are advanced metrics. The 

options are: 

Advanced Server – All profiles can be applied to this system. If 

you are using premium metrics, you must define the system as an 

advanced server. Each profile applied to this system consumes one 

advanced server license. In addition, each premium profile 

applied to this system consumes both an advanced server 

license and a premium profile license. 

Basic Server – Only basic profiles such as Windows, Linux, 

Solaris, Unix, etc., can be applied to this system. The license 

consumed is per system, not per profile. 

Network Device – Only profiles with Ping or SNMP metrics can 

be applied to this system, otherwise a licensing error will occur. 

The license consumed is per system regardless of the number of 

profiles applied. 



DNS Name – Specify the DNS name of the system. By default, this 

information is replicated as the NetBIOS Name, described below. 

IP Address – Specify the IP address of the system. 

NetBIOS Name – In most cases, the NetBIOS name and the DNS 

name are the same. OneSight assumes the setting for the DNS 

name should also be used for the NetBIOS name. If there is a 

difference, systems that use Perfmon as the data source cannot be 

monitored. Check the NetBIOS name on the machine you want to 

monitor (in the Network properties Identification tab, this is the 

Computer Name) to determine if the DNS name and the NetBIOS 

name are different. 

Operating System – Specify the type of operating system that is 

running on the machine. 

Location – Specifies the Data Collector Location from which to 

check the profile monitor. Select the location for this monitor 

from the list. 


in an alert when the system fails. 




the alert. 


the alert. 

System Response Plan – The following fields define a response plan 

associated with this system. The system plan applies to profile 

metrics only and overrides the profile alert’s plan. If the alert has an 

action plan of , the system plan is ignored. 



When in Warning State Respond by – Specify how you want to 

respond when the profile metric enters a Warning state by 

selecting an action plan from the list. Options displayed in this 

list represent previously configured plans. To create a new plan 


When in Critical State Respond by – Specify how you want to 

respond when the profile metric enters a Critical state by 

selecting an action plan from the list. Options displayed in this 



When Returning to Good State Respond by – Specify how you 

want to respond when the profile metric returns to a Good state 

by selecting an action plan from the list. Options displayed in this 







mainframes. 


machines you intend to monitor. The OneSight Solaris profile 

queries the Sun SNMP agent for Sun’s MIB and the RFC-1213 (MIB- 

2). For the Netscape Enterprise Server profile, OneSight uses the 

Netscape HTTP Server MIB in addition to the Sun MIB. 

For more information on how to configure the Netscape SNMP 

agent to coexist with the Sun SNMP agent, refer to Netscape 

documentation. 

Community – Specifies the SNMP password of the system. 

Timeout Seconds – Specifies the amount of time (in seconds) to 

wait for an SNMP reply. If Timeout Retries is greater than 0 and a 



reply is not received, a retry attempt is made. For each 

subsequent retry, the timeout value is doubled. For example, if 

Timeout Seconds is 5 and Timeout Retries is 2, the first request 

attempt will occur after 5 seconds, the second attempt will occur 

after 10 seconds, and the third attempt will occur after 20 

seconds. In this example, the total timeout period equals 35 

seconds. If there is no response after this time, a Sample Failure 

is triggered. 



Timeout Retries – Sets the upper limit for the number of times an 

SNMP request is retried. For example, if Timeout Retries is set to 

3, the SNMP request will be sent up to four times (the initial try 

plus three retries). 




SNMP Trap Tab 

Community - Specifies the community string for filtering traps. 

The default is public. 

Virtual Agent Tab – Adding information to the Virtual Agent tab 

enables OneSight to provide specific metrics and configuration 

information for the operating system (specified on the System tab) 

on the machine. The Virtual Agent settings in the System editor 

also provide the default values for the system when adding Virtual 

Agent data sources to a Profile monitor. 

Connection Method – Select the connection method to use for the 

Virtual Agent. 

Port – Specify the port to use to for the Virtual Agent connection. 



Prompt – Specify the command line prompt for the host machine. 

If you do not specify a command line prompt, OneSight will 

attempt to infer the prompt by parsing the screen output. 

Charset – Specifies the character set to use. Select a character set 

from the list. 

Operating System – Select the operating system of the host 

system. 

User Name – Specify a user name to log into an account on the 

host system. 

Password – Specify the password required to log into the User 

Name account on the system. 

Private key file – Specify the private key file to use for 

authentication when the connection method is SSH. This method 

is used in place of user name and password and requires that the 

equivalent public key file be installed on the remote system that 

you are logging in to. 

Login Timeout (ms) – Specify the length of time to wait before 

timing out when logging in. 

Discovery Timeout (ms) – Specify the length of time to wait 

before timing out when performing discovery. 

JMX Tab – Adding information to the JMX tab enables OneSight to 

provide specific performance and configuration information on JMX 

MBeans. 

JMX App name – The name of the JMX application. Valid entries 

are those listed or a user-created name in the Data Collector’s 

OSDC.properties file. 




Authorization Required – Select true to enter authentication 

information. 

User Name – The username for accessing the JNDI server. 


Trust Store Filename – Enter the client-side trust store path and 

file name. This file should be in the datacollector directory. 


Key Store Filename – Enter the client-side key store path and file 

name. This file should be in the datacollector directory. 


Windows NT Tab – Adding information to the Windows NT tab 

enables OneSight to provide specific performance and 

configuration information on Windows NT machines. 

User Name – Enter the user name for a system account that has 

rights to read the NT Windows Registry. 

Password – Specify the password required by the system when 

logging in with the user name specified in the User Name box. 

Domain – Specify the domain name of the Windows NT machine. 

Attributes Tab Settings – Attributes are used in OneSight to sort the 

monitors, monitor groups, profiles, and systems on the status page. 

You can assign custom attribute values to specific monitors and use 

the Group by selection on the status page to show only those 

monitors, monitor groups, profiles, or systems assigned to a specific 

attribute set. 

To apply attributes to more than one system at a time, use the 

Assignment tab on the Attributes page. 



All Attributes – Shows the name of the attribute set and its 

attribute values. 


this system. Use the Add and Remove arrow buttons to customize 

the list of attribute values applied to the monitor, monitor group, 

profile, or system. 

Attribute Editor – Opens the Attribute Editor for adding and 

deleting attributes and attribute values. 

Access Control Tab – The Access Control tab lets you specify which 

user groups can read, write, or delete this system. 


Owner – The user group for this system. A system can be directly 

owned by a user group. 






Port System Information 

When you add a new Port component, you must add information to 


metrics use to obtain information about the Port. 


must open the ports in the port list, otherwise discovery may fail. 



Component Tab – The Component Tab shows the name of the Port 

you are configuring. Changing this name will affect the Port entry 



you to identify the specific Port you are adding. 

Port Tab – A Port monitor checks on the availability of a specified 

network port. While checking network port availability, the port 

monitor can also check the value returned from a query to ensure 

that an application is available and running correctly. If a port does 

not reply, or if the reply is incorrect (as determined by a text 

match), an alert is triggered. The Port monitor can be used to 

monitor network applications that are not available as part of other 

OneSight monitors. 

The monitor must have appropriate privileges to access the 

specified port on the monitored machine. 

Port – Specifies the port you want to monitor. 

Process System Information 

Currently, the Process component type is not used by any existing 

profile metric. If you performed a OneSight Find System 

Components operation, process information is added to the list of 

components present on the system. At this time, this is simply for 

informational purposes. 





process you are configuring. Changing this name will affect the 

Process entry on the left side of the System Editor dialog box. 




you to identify the specific process you are adding. 

Perfmon Tab – The Windows NT Performance Monitor (Perfmon) 

can be used with OneSight to gather resource information for 

specific components and program processes throughout your 

system. To enable OneSight to use this information, you must first 

start and configure Performance Monitor for your system. 

Instance – Specify the process name. To find the name, see the 

NT Performance Monitor. 

Process Tab 

Instance – Specify the process name. 





mainframes. 


















components. 



were entered. 








Chapter 2. 

Instance – Specify the process to monitor. This value can be 

anything running as a process on the UNIX operating system. For 

example, the process ID for a Netscape web server is ns-httpd. 

The process ID for an Apache web server is httpd. Use the UNIX 

process status (ps) command to determine what processes are 

currently running. 



component. 









VM System Information 

When you add a new VMWare component, you must add 


OneSight metrics use to obtain information about VMWare. 

Component Tab – The Component Tab shows the name of the VM 

you are configuring. Changing this name will affect the Process 

entry on the left side of the System Editor dialog box. 


you to identify the specific VM you are adding. 





mainframes. 


















components. 



were entered. 

VMProcess System Information 

When you add a new VMProcess component, you must add 


OneSight metrics use to obtain information about the VM 

processes. 


VMWare process you are configuring. Changing this name will 

affect the VMProcess entry on the left side of the System Editor 

dialog box. 


you to identify the specific VMWare process you are adding. 





mainframes. 


















components. 



were entered. 

Web Server System Information 

When you add a new web server component, you must add 


OneSight metrics use to obtain information about the web server. 




Component Tab – The Component Tab shows the name of the web 

server you are configuring. Changing this name will affect the Web 

Server entry on the left side of the System Editor dialog box. 


you to identify the specific web server you are adding. 

Home Page Tab – The Home Page tab must be configured to specify 

the IP address of the machine hosting the web server and the port 

used by the web server. 

IP Address – Enter the IP address of the machine hosting the web 

server you are monitoring. 



Port – Enter the port number used by the web server you are 

monitoring. 

Secure – Select True if the server you are adding is a secure 

server. 

Specify an HTTP Host Header – Select True if you want to define 

an HTTP Host Header. When selected, the monitor uses the IP 

Address specified in the URL Address and the header specified in 

the HTTP Host Header field. When cleared, the monitor uses the 

host specified in the URL Address field. Use this option if you 

have a single IP that hosts multiple web sites. 

HTTP Host Header – Specify the value to look for in the Host: 

field in the HTTP Get Request. For example, if you host web sites 

www.mywebsite.com and www.myotherwebsite.com using IP 

address 255.255.001.001, specify http://255.255.001.001 as the 

URL Address and www.mywebsite.com or 

www.myotherwebsite.com as the HTTP Host Header value. 

Perfmon Tab – Information on the Web Server Perfmon tab is used 

by the IIS profiles only. 

The Windows NT Performance Monitor (Perfmon) can be used with 

OneSight to gather resource information for specific components 

and program processes throughout your system. To enable 

OneSight to use this information, you must first start and configure 

Performance Monitor for your system. 

Instance – This value is typically “Default Web Server”. 

SNMP Tab – Information on the Web Server SNMP tab is used by 

the Netscape profile only. 

Adding information to the Simple Network Management Protocol 

(SNMP) tab enables OneSight to provide specific performance and 

configuration information on network devices, such as routers, or 

on hosts, such as workstations or mainframes. 


Adding System Components 


machines you intend to monitor. The OneSight Solaris profile 

queries the Sun SNMP agent for Sun’s MIB and the RFC-1213 (MIB- 

2). For the Netscape Enterprise Server profile, OneSight uses the 

Netscape HTTP Server MIB in addition to the Sun MIB. 

For more information on how to configure the Netscape SNMP 

agent to coexist with the Sun SNMP agent, refer to Netscape 

documentation. 

Search for string – Enter the port number for the web server you 

are monitoring or a regular expression. Refer to Using Regular 

Expressions for Pattern Matching in Chapter 5 for more 

information about regular expressions. 





For help installing the UNIX Remote Agent, see Installing the UNIX 

Remote Agent in Chapter 2. 

Instance – Enter the server instance. 







Information about the components on each system must be 


for the web components running on those machines. The Add 



System Component dialog box allows you to manually define the 

system components that you want to monitor. 

After adding a system component, you need to configure the data 

sources that gather information for the profile metrics that monitor 

that component. In the System Editor, select the component that you 

added and fill in the settings on the Properties tabs. 

Adding Components Manually 

Profile monitors need information about the components present on 

each system that they monitor. Use this method to manually add a 

system component to an existing system definition. 

To add system components manually: 

1. Open the System Editor. 



2. In the Components box, click a component and then click Add, 

which opens the Add System Component dialog box. 

Add type – Select the type of component you are adding to 

display the fields associated with the selected type. 

Component Type – Select this option to add a new component 

type. This is the only option available from the system node. 

Component – Select this option to add components for the 

selected component type. 

Component Type Definition 

Name – Specify a meaningful name that allows you to 

identify the specific component type you are adding. 

Description – Type a description that helps you differentiate 

this component type from the other component types you are 

defining to monitor your web components. 

Component Definition 



Component type – The type list defaults to the kind of 

component that was selected when you clicked the Add 

button to open the Add System Component dialog box. Select 

the type of component you want to add and configure. 

Component – Specify a meaningful name that allows you to 

identify the specific component you are adding. You can add 

multiple instances of a component using the following 

syntax: 

name[[[numbers…numbers]]] 

For example, e[[[8..10]]] creates the following 

components: e8, e9, and e10. 

Data Sources to Add – The data sources applicable to the type of 

component you are adding are listed. Select the data sources 

that you want to use. When you click OK the associated tabs are 

displayed so that you can configure the selected data sources. 

3. The Type list defaults to the kind of component you are adding. 

In the Name box, specify a meaningful name that allows you to 

identify the specific component you are adding. Then click OK 

to return to the System Editor. 

4. The newly added component appears in the Components list 

(for example, if you add a disk component named “C:”, it is 

added under Disk). Select this component in the Components 

list and click Add Data Source to display the options you need to 

fill out in order to configure the data sources that OneSight 

metrics use to obtain information about this system component. 

5. After supplying information about the new system component, 

click OK to update the system. 



Adding Components Automatically 

Profile monitors need information about the components present on 

each system that they are configured to watch. You can direct 

OneSight to find system components (such as disk drives, 

processes, and web servers) and add them to the system definition. 

For this to work correctly, you must first enable the data sources 

used by the auto-find process. 

Note: It is preferable to define system components while adding a 

profile monitor. When you add a profile monitor to a machine, 

OneSight prompts you to add any missing system components that 

are tracked by that monitor. 

The process that automatically finds system components can use 

SNMP, Process monitor, Perfmon (remote or local) and the UNIX 

Remote Agent to identify processes and devices. Refer to Adding a 

Data Source in Chapter 6. 



To automatically add system components to an existing system 

definition: 




2. Click Discover Components. The Discover Components 

Configuration dialog box opens where you specify what 

methods should be used to find out about the components 

present on the selected computer system. 

Check All – Selects all discovery methods. 

Uncheck All – Deselects all discovery methods. 

Discover Components Using – Select the discovery methods that 

you want to use to discover components. 

Advanced – Displays the Advanced Discovery Editor for 

selecting the component types to find. This may be necessary 

when you have a component type that only works for Solaris 

and a Windows system is doing discovery. 



3. Click Advanced if you want to select which components to 

discovery. 

4. Select the components that you do not want to discover and 

click the right arrows to add them to the Ignore component types 

list. 

5. Click OK when you are done. 

6. Select one or more methods to use to find out about the 

components present on the selected computer system. The 

Setup Discovery dialog box is displayed. 



Note: When discovery is performed, OneSight notes the type of 

system. The next time you discover, only those methods 

appropriate for the type of system are available in the Discover 

Components dialog box. For example, if the system is a 

Windows system, UNIX or Virtual Agent will not be listed. To 

reset the dialog box to show all methods, set the Operating 

System field to Unknown. 

Use options in the Find Components Configuration dialog box 

to configure the data sources to be used to find out about the 

components on the selected computer systems. 

SNMP – SNMP finds interfaces by using RFC 1213 (MIB II). To 

use SNMP to find processes and hardware, the system must 

support the Host Resources MIB. 

Community – Specify the SNMP community string used for 

the machine you want SNMP to examine. For many devices, 

the default community string is public. 

Timeout seconds – Specifies the amount of time (in seconds) 

to wait for an SNMP reply. If Timeout Retries is greater than 

0 and a reply is not received, a retry attempt is made. For 



each subsequent retry, the timeout value is doubled. For 

example, if Timeout Seconds is 5 and Timeout Retries is 2, 

the first request attempt will occur after 5 seconds, the 

second attempt will occur after 10 seconds, and the third 


timeout period equals 35 seconds. If there is no response 

after this time, a Sample Failure is triggered. 



Timeout retries – Sets the upper limit for the number of times 

an SNMP request is retried. For example, if Timeout Retries 

is set to 3, the SNMP request will be sent up to four times (the 

initial try plus three retries). 




Virtual Agent Connection Settings 

Connection Method – Select the connection method to use for 

the Virtual Agent. 

Port – Specify the port to use for connecting. 



OneSight will attempt to infer the prompt by parsing the 

screen output. 

Charset – Specifies the character set to use. Select a character 

set from the list. 


languages such as Basque, Catalan, Danish, Dutch, 



English, Faeroese, Finnish, French, German, Icelandic, 

Irish, Italian, Norwegian, Portuguese, Rhaeto-Romanic, 

Scottish, Spanish, Swedish, Albanian, Afrikaans, and 

Swahili. 



languages. 











languages, similar to ISO 8859-1 with the Icelandic 

letters replaced with Turkish letters. It is also used for 

Kurdish. 










Central European Latin alphabet languages. 


Russian and other Cyrillic languages. 


Western European languages. 


Greek. 


Turkish. 


Baltic. 


Operating System – Specify the type of operating system. 


User Name – Specify a user name to log into an account on 

the host system. 

Password – Specify the password required to log into the 

User Name account on the system. 

Private Key File – Enter the name of the private key file. 

Advanced 

Login Timeout (ms) – Specify the number of milliseconds to 

wait before timing out when logging in. 

Discovery Timeout (ms) – Specify the number of milliseconds 

to wait before timing out when doing discovery. 



Login Procedure – Select the state machine containing the 

XML for logging in. This is useful, for example, when you 

are logging into one machine and then logging in to another 

machine. Refer to “Configuring State Machines,” in Chapter 

5 for more information. 

Windows NT 

User name – Enter the user name for a system account that 

has rights to read the NT Windows Registry. 

Password – Specify the password required by the system 

when logging in with the user name specified in the User 

Name box. 

Domain – Specify the domain name of the Windows NT 

machine. 

JMX 

JMX App name – The name of the JMX application. Valid 

entries are those listed or a user-created name in the Data 

Collector’s OSDC.properties file. 


Authorization Required – Select true to enter authentication 

information. 

User Name – The username for accessing the JNDI server. 


Trust Store Filename – Enter the client-side trust store path 

and file name. This file should be in the datacollector 

directory. 




Key Store Filename – Enter the client-side key store path and 

file name. This file should be in the datacollector directory. 


7. Enter the discovery configuration information and click OK. 

8. When the process completes, click OK. 

To automatically find system components when 

you add a new system: 


2. Select Systems. 



3. Click Add to open the Add System dialog box. 

4. Specify the machine name or IP address of the system to be 

added and click OK. 

5. Click Discover Components to open the Discover Components 

Configuration dialog box where you specify what methods 

should be used to find out about the components present on the 

selected computer system. 




components present on the selected computer system. The 

Setup Discovery dialog box is displayed. 

7. Enter the discovery configuration information and click OK. 

8. When the process completes, click OK. 

Discovering Multiple Systems 

You can discover the components to monitor on multiple systems at 

one time. This is useful after you have imported multiple systems 

into OneSight. Existing components that are not detected by 

discovery are not removed during this process. 

Note: the systems being discovered must have the same type of 

operating system. For example, they must be all Windows machines 

or all Linux machines. 

To discover multiple systems: 





3. Click Multiple System Discover. 


components present on the systems and click OK. The Setup 

Discovery dialog box is displayed. 



5. Enter the properties for discovery. These properties will be used 

for each system and saved for each system. Click OK. 

6. Click OK when discovery is finished. 

Modifying the Location of Multiple Systems 

You can change the location of multiple systems at one time. You 

can change a maximum of 100 systems, 100 monitors, and 2000 

metrics. 

To change the location of multiple systems: 



3. Select Bulk Location Modification. 

This dialog box displays a list of configured systems and their 

locations. The list can optionally be filtered. Systems that are 

grayed out are in the selected location. This dialog box has the 

following options: 

Choose a Location To Apply To Multiple Systems – Select the 

location that you want to apply to the selected systems. 



Show Systems Where contains – Select the 


example, you could search for all systems at the location 

Boston. In addition to plain text, you can enter a PERL 

expression in the contains field. 

– Displays the list of systems based on the filter 

selections. 

Note: Only the systems explicitly owned by your user group are 

listed. To change systems in a sub group of your user group you 

must log on as a user in the sub group. 

Check All – Checks all systems in the system list. 

Uncheck All – Unchecks all systems in the system list. 

Save Changes – Saves changes and redisplays the dialog box. 

4. Filter the list of displayed systems, if necessary. 

5. Select the location that you want to apply to the selected 

systems. Grayed out systems are already assigned to the 

selected location. 

6. Select or deselect systems using the check box in front of the 

system name or using the Check All and Uncheck All buttons. 

7. Click Save Changes to apply the location to the selected 

systems. 

8. Repeat these steps as necessary. 

9. Click Close when you are done. 



Modifying System Components 

To modify a system component: 

Use this method to update information about a system component in 

an existing system definition. 


2. In the Components box, click the name of the component that 

you want to modify. 

3. Use settings on the Properties tabs to configure the OneSight 

profile metric data sources for the selected system component. 

4. Click OK to update the system definition and return to the 

System Editor. Click the Cancel button to close the System 

Editor. 

Removing System Components 

Use this method to remove a system component from an existing 

system definition. To remove system components: 


2. In the Components box, click the name of the component that 

you want to remove. 

3. Click Remove and confirm that you want to delete this 

component definition. 


Changing Passwords 


System Passwords 

When you configure System monitors in OneSight, you can specify 

User Name, Domain, and Password information for each system by 

selecting Password from the Configure tab. If passwords for the 

systems being monitored change periodically, the password 

information in the OneSight System monitor configurations need to 

be updated to have the current passwords. 

You can use the Configure Password options to change the 

passwords defined in OneSight System configuration settings rather 

than opening each System configuration individually. 

In addition, you can copy passwords from one Windows system to a 

another. 

Domain/User Name – Select the domain name/user name from the 

list. The list contains the domain names and user names specified in 

OneSight System configurations. The System List displays the 

OneSight System configurations that use the selected Domain/User 

Name. 



System List – Shows the OneSight System configurations that use 

the selected Domain/User Name. 

User Name – The System configuration User name. 

New Password – Enter the new Password to use in the System 

configurations. The Password characters appear as asterisks for 

security. 

Confirm Password – Enter the Password again to confirm it. 

Domain – The System configuration Domain. 

Copy Password – Displays the Change Password dialog box for 

copying a password from one Windows system to another. 

Visual Script Passwords 

When you configure Oracle Test for Web Applications Transaction 

monitors in OneSight, you can specify Realm, Username, and 

Password information for visual scripts. If passwords for the scripts 

change periodically, the password information in the Oracle Test 

for Web Applications Transaction monitor configurations need to 

be updated to have the current passwords. 



You can use the Configure Password options to change the 

passwords defined in Oracle Test for Web Applications Transaction 

monitor configuration settings rather than opening each monitor 

configuration individually. 

Domain/User Name – Select the domain name/user name from the 

list. The list contains the domain names and user names specified in 

Oracle Test for Web Applications Transaction monitor 


Realm – Displays the full Uniform Resource Locator (URL) for the 

Web application that requires a user name and password. 

New Password – Enter the new Password. The Password characters 

appear as asterisks for security. 

Confirm Password – Enter the Password again to confirm it. 



URL Script Passwords 

When you configure URL monitors in OneSight, you can specify 

user name and password information for URLs that require 

authentication. Use this dialog box to change the password for all 

URL monitors that are configured with the same user name. 

User Name – Select the user whose password you want to change. 

New Password – Enter the new password for this user. 

Confirm Password – Re-enter the new password for this user. 

Virtual Agent Passwords 

You can change the password for all virtual agents using the same 

connection method and user name. 



Connection Method – Select the protocol used to connect. 

User Name – Select the user name whose password you want to 

change. 

System List – Shows the OneSight System configurations that use 

the selected connection method and user name. 

New Password – Enter the new password to use. The password 

characters appear as asterisks for security. 

Confirm Password – Enter the password again to confirm it. 



Creating Action Plans 

An action plan consists of a sequence of actions that are triggered 

when an alert occurs. These actions tell OneSight how to respond 

should a problem arise with the health of your e-business system. 

For example, you can create an action plan that sends an e-mail 

notification to a member of your team when a specified threshold is 

crossed. The recipient of the mail has the opportunity to retire the 

alert, given what is known about the problem. If the recipient of the 

e-mail action does not respond before the escalation timeout period 

has expired, the action plan automatically performs the next action 

in the plan. Once an action is configured, it can be used by any 

monitor group or profile. 

633

Creating a New Action Plan 

The Action Plans page displays a list of all currently defined action 

plans. To access an existing plan, select a name from the list and 

click Modify. To create a new action plan click Add. 

To determine whether an action plan is in use by a monitored 

component or whether the plan has been scheduled, check the 

Action Plan Symbols: 

Action plan is configured but not in use by a monitor group or 

monitored component. 

Action plan is scheduled but not in use by a monitored 

component. 

Action plan is in use by one or more monitored components. An 

action plan in this state can be modified; however, it cannot be 

renamed or removed. 

Action plan is scheduled and in use by one or more monitored 

components. An action plan in this state can be modified; 

however, it cannot be renamed or removed. 

OneSight provides default action plans for use when configuring 

monitors and profiles. These action plans are named to allow you to 

quickly associate your monitors with action plan of the same name 

and type. While these action plans are provided for you, they are 

not preconfigured with any specific actions. To use these action 

plans, or any new action plans you configure, you must add the 

necessary actions to each plan you intend to use and configure them 

accordingly. 

Each action in an action plan is associated with a time interval. For 

example, you can have an action plan that has two time intervals, 

one for work hours and one for after hours and weekends. The 

actions that will occur if the action plan is triggered can be different 

for each time interval. A default time interval of 24x7 is 

automatically added to new action plans but can be deleted. 




To create a new action plan: 

1. Click the Configure menu, then click Action Plans. 

Chapter 8: Creating Action Plans 635


2. On the Action Plans page, click Add. 

The Action Plan Manager opens when you click Add or Modify 

on the Action Plans page. The Action Plan Manager enables 

you to configure action plans for specific alerts. An action plan 

consists of a sequence of responses that are triggered when an 

alert occurs. 

Name – Displays the action plan name. 

Schedules for this Action Plan – Displays the time intervals used 

by this action plan. Time intervals are created by selecting Time 

Intervals on the Configure tab. Refer to Chapter 14 for more 

information. 

Actions for this Schedule – Displays the sequence of actions to 

be taken when this action plan is triggered by an alert during the 

selected time interval. 



3. In the Action Plan - Add dialog box, enter a name for the new 

plan in the Name box. 

4. Click Add in the Schedules for this Action Plan section to add 

more time intervals. 

This dialog box lists all time intervals that have been 

configured that are not being used in the plan. 

5. Select the time interval you want to add and click OK. 


Adding Actions to the Plan 

6. Select the time interval to which you want to add actions, and 

click Add in the Actions for this Schedule section. 


To add actions to an action plan: 

1. In the Global Action Manager, select an action to be added to 

the new plan and click OK. 



To create a new action for this plan, click Add in the Global 

Action Manager, then create a new action. 

You can add or modify actions at any time; additions made to 

the list of actions affect all action plans, except those plans 

currently displayed as in use on the OneSight Console. The 

following parameters must be configured for each action: 

Name – Displays the common name for this action. This name 

is used to identify this action throughout the OneSight system. 

Note: Actions cannot be duplicated using the same name. To 

create a duplicate action, add a new action to the list using a 

different name. 

Action Type – Displays the current action type. 

Message Template – Displays the list of message templates. By 

default, OneSight selects the message template most 

appropriate for the specified action type. You can also create 

your own custom message templates. See Adding Message 

Templates for details. 

Note: The %DescriptionByOID% substitution variable can be 

used in the SNMP Trap message template to generate an OID 



for each valid message template variable. For example, 

%Monitor%, %Metric%, etc. Specific mappings are in the 

OneSight.MIB file. In the default template, a maximum length of 

1100 has been specified for the %DescriptionBy OID% value. 

In some circumstances the trap message may be discarded due 

to excessive length. Refer to 

http://support.microsoft.com/kb/233401/en-us for details. 

Modify – Displays the Modify Alert Message Template dialog 

box for modifying the selected message template. 

Escalation Timeout – Amount of time (in minutes) for this 

action to wait after executing before performing the next action 

in the Action Plan. 

Escalation time out for good state – when checked, use the 

escalation timeout for alerts associated with a return to good 

state. 

Reminder Interval – Amount of time (in minutes) to wait before 

repeating the action if the alert is still valid. 

Repeat for good state – when checked, applies to alerts 

associated with a return to good state. 

Total Counts – The total number of times to repeat this action. 

For example, if you have set up a 24x7 action plan to send 

email actions with the following actions and settings: 

Action 1: Escalation = 5, Reminder = 1, Total Counts = 20 




The entire action plan will first execute the actions serially, that 

is, action 1 completes the first iteration, and subsequent actions 

occur as the escalation timeout expires for each action. Then 



the remaining iterations for each action are executed according 

to the total counts and reminder intervals. 

For example: 

In Minute . . . 

the Following Actions Occur 

1 Action 1 

2 Action 1 

3 Action 1 

4 Action 1 

5 Action 1, Action 2 

6 Action 1 

7 Action 1 

8 Action 1 

9 Action 1 

10 Action 1, Action 2, Action 3, Action 4 

11 Action 1 

12 Action 1 

13 Action 1 

14 Action 1 


16 Action 1 



17 Action 1 

18 Action 1 

19 Action 1 


21 

22 

23 

24 

25 

26 

27 

28 

29 

30 Action 3 


box for editing the selected message template. 

Escalation time out for good state – Enables escalation when this 

action is used in a return to good state action plan. 

Repeat for good state – Enables repeat when this action is used 

in a return to good state action plan. 

2. When the fields for this action are completed, click Test to 

confirm the success of this action. 



3. When the last action has been added to the action plan, click the 

Access Control tab to configure which user groups have access 

to this action plan. 

Owner – The user group for this action. An action can be 








4. Configure permissions and click OK in the Global Action 

Manager. 

Note: You must enable each action type in the Global Action 

Options dialog box before the action plan will perform 

properly. 


Configuring Global Action Options 

5. Click OK. The new plan appears in the Action Plans list. 


Use this dialog box to configure actions for the Global Actions 

list. Configured actions can be added to an Action Plan, which 

become alerts when problems occur with a component of your 

system. 

1. On the Action Plans page, click Global Actions. 

2. In the Global Action Manager, click Global Options. 

Before an action type is available for use in an action plan, it 

must be enabled in the Global Action Options dialog box. The 

exception is e-mail actions, which are enabled by default. To 

enable actions and notification types, click the Enable check 

box for the specified type and complete any configuration 

information for that action type. 

Action Types 

E-Mail – Displays configuration options for e-mail 

notifications. 



Incoming E-Mail – Displays configuration options for 

specifying the account that will be monitored for replies to e- 

mail replies to e-mail actions. 

Scripting – Displays configuration options for scripting 

actions. This panel also enables you to define environment 

variables and parameters for individual scripts. 

3. Select the enable check box for each of the action types you 

have configured. 

4. Complete the configuration for each action type and click OK to 

preserve your settings. 

Triggering An Email Action 

E-mail notification is one of the most direct methods for receiving 

up-to-date information regarding the health status of your e- 

business system. When you specify e-mail as a notification method, 

the recipient you define receives an e-mail message, including a 

subject and message, detailing the nature of the alert. 

Note: A mail server must be configured for the email action to 

work. For more information, see Configuring the Mail Server. 

In the Action Manager, when you click E-Mail in the Action Types 

list, the bottom portion of the dialog box displays options for 

configuring an e-mail action. 



To create a new action plan with an e-mail action: 

1. Click the Configure menu, then click Action Plans. 



2. On the Action Plans page, click Add to add a new action plan or 

select one of the default action plans and click Modify. If you 

choose to add a new action plan, enter a name for the new plan 

in the Name box in the Action Plan dialog box. 

3. Select the time interval to which you want to add actions. By 

default, the Actions List is empty. Click Add to begin adding 

actions to the plan. 



4. In the Global Action Manager, click Add to add a new action to 

this action plan. 

5. In the Action Manager - Add dialog box, enter a name for this 

action, for example, E-mail Fred. 

6. Select E-mail as the Action Type. 

Use the following options to specify how the E-Mail 

Notification action is configured: 

General Tab 


is used to identify this action throughout the Empirix OneSight 

system. 











Escalation Timeout – Time (in minutes) before this action 

performs the next action in the list. 

Note: This box is required for creating actions. Enter the 

amount of time appropriate to the type of action you are 

configuring. Entering zero (0) in this box causes this action and 

the action following to execute simultaneously. 



state. 






Test – Performs a test of this action as configured. You must 

enable this action type in Global Options before a test of this 

action will succeed. If your test produces a 501 (syntax) error, 

you may have a problem with your OneSight server name. 

E-Mail Configuration 

Address – Check this option to enter the e-mail address for the 

recipient of this notification. The address must be a complete e- 

mail address (for example, name@domain.com). Specify multiple 

e-mail addresses, separating the addresses by a comma or a 

space. 

System User – Check this option to select the email recipient 

from the list of OneSight users. 



An example e-mail notification is as follows: 

Subject: CPU overloaded, long run queue (user_nt) 

OneSight Warning Alert. 

CPU overloaded, long run queue: Value was 16 

processes, threshold is 4 

processes (4/4/00 6:17 PM) 

Component: user_nt 

Event: CPU overloaded, long run queue 

Metric: Processes: Run Queue Length 

Monitor: Windows NT 4 (user_nt) 

Monitor Group: User Monitor Group 

Description: Number of processes in the run queue 



read, write, or delete this action. 









7. From the Message Template list, select a message template for 

the action. By default, OneSight selects the message template 

most appropriate for the specified action type. You can also 

create your own custom message templates. See Adding 

Message Templates later in this chapter for details. 

8. Enter an Escalation Timeout. This is the amount of time you 

want OneSight to wait before performing the next action in the 



action plan. Since this action plan has only one step, you can 

type in 0. 

9. Enter a reminder interval. This is the amount of time you want 

OneSight to wait before repeating this action. 

10. Enter the total counts. This is the number of times to repeat this 

action. 

11. Under E-Mail Configuration, either select Address to enter the 

e-mail address of the person(s) to notify when the action is 

executed, separating email addresses with a space,. Or select 

System User to choose the user from the list of OneSight users. 

12. Click Test to confirm that the information you entered will 

create a successful action. 

Note: The settings in the Global Options for this action type 

must be defined before a test of this action will succeed. 

13. Click OK to close the next two dialog boxes. You will now be 

able to pick this action plan when you want to associate an alert 

with an action plan. 

Replying to an E-mail Alert 

You can configure OneSight to accept incoming e-mail responses to 

e-mail alert notifications. The responses will go to an email account 

that is enabled and configured by creating an Incoming E-Mail 

Global Action Option as described later in this chapter. 

This allows you to acknowledge an alert, suspend or retire an action 

plan, and include a note about what you are doing. If subsequent 

email alerts happen later in the Action Plan’s escalation, these notes 

can be included. They can also be seen in the console. The Admin 

Email Template includes the %AlertNotes% variable to make this 

happen. 



%AlertNotes% is filled in for escalations after the 

acknowledgement. If you are not escalating, the variable will be 

blank. For example, if you had the following action plan: 

Email Eric. Wait 5 minutes. Email Stan. 

If Eric acknowledges the alert before it is emailed to Stan, 

%AlertNotes% contains the acknowledgement. 

Email actions that allow incoming email are tracked using an 

identifier in the subject of the e-mail. For example, Action ID: 412. 

When you reply to an e-mail alert, the following reply commands 

can be used and must begin the body of the email. Reply commands 

are case-sensitive. 

ACK – Acknowledge the alert 

ESC – Escalates the action to the first non-delay action that follows 

the e-mail action that was replied to. If the escalation has occurred, 

no action is taken. 

RET – Retire the action plan 

SUS – Suspend the action plan 

For example: ACK “I’ll take a look at it now. Mbrown” 

The list of reply commands is determined the possible options for 

that action plan. For example, you cannot escalate if there is no 

follow-up action to escalate to in the action plan. You cannot 

resume an action plan from an e-mail reply. 

Acknowledging an alert that is no longer outstanding has no effect. 

Suspending or retiring an action plan does nothing when the alert is 

already retired. 

All inbound actions will be included in the Audit reports of the 

type, ―E-Mail Reply.‖ The activities will be: alert acknowledged, 

retire action plan, suspend action plan, and escalate action. 



Valid incoming replies are deleted after they are processed. Invalid 

replies are left on the server. If an incoming reply is no longer valid 

by the time it is received, it is written to the Audit log with the 

message, ―E-Mail reply ignored – request no longer valid at the 

time of receipt for E-Mail reply (0).‖ 

Validating Email Connections 

E-mail servers that check the host name using RFC 810 will not 

accept connections to machines with a name containing an 

underscore. If the machine name of the OneSight server includes an 

underscore, you may have problems associated with e-mail servers 

under the following conditions: 

If you change the mail server specification in the Global Action 

Options dialog box. 

If you configure a Mail monitor for an e-mail server that enforces 

RFC 810. 

Most e-mail servers do not enforce this RFC. To check for this 

problem on OneSight servers with names that include an 

underscore: 

Test your Mail monitor when you create it. 

Test your e-mail action when you create it. 

SMTP daemons that do not accept this host name return a 501 

(syntax error) message when a connection is attempted. If you see 

an error of this type, you can reconfigure the monitored component 

or the e-mail server or you can install OneSight on a machine that 

has a name without an underscore. 

RFC 810 – RFC 810 states that the host name must be ―text string up 

to 24 characters drawn from the alphabet (A-Z), digits (0-9), and the 

minus sign (-) and period (.). No blank or space characters are 

permitted as part of a name. No distinction is made between upper 



and lower case. The first character must be a letter. The last 

character must not be a minus sign or period.‖ 

Adding/Modifying Message Templates 

The message content for Empirix OneSight alerts is configured 

using text template files. Empirix OneSight is shipped with default 

message template files for the various Alert types (e.g., e-mail, 

pager, SNMP trap), but you can add your own message templates in 

OneSight to further customize your alert notifications. This can be 

useful for the following reasons: 

You can customize alert content to generate messages containing 

only the information that is meaningful to the alert notification 

recipient. Alert messages can be customized for each configured 

action, so a single alert condition can now be configured to 

trigger, for instance, different e-mail text for each recipient of the 

alert notification. 

You can customize alert content so that it is formatted optimally 

for the intended alert devices (e.g., email, pager, phones, etc). 

You can customize e-mail alerts to include direct links to the 

Empirix OneSight Status and Reports pages. This can be useful 

for OneSight Administrators and Operators. 

OneSight selects an appropriate default template based on the type 

of action you are configuring. 

Customization of alert message text is accomplished using 

OneSight defined substitution variables. These same substitution 

variables can also be passed to Scripting Actions in both the 

Parameters and Environment Settings fields. 



Adding a New Alert Message Template 

To create a new Message Template: 


2. Select Alert Message Template. 

This dialog box lists existing alert message templates and lets 

you add, modify, and remove them. 

Add – Displays the Add Alert Message Template dialog box for 

adding a new alert message template. 


box for modifying the selected alert message template. 

Remove – Deletes the selected alert message template. 

Used By – Displays a list of the actions that are using the 

selected alert message template. 

Name – Displays the name of the alert message template. 



Description – Displays the description of the alert message 

template. 

3. Click Add. 

Name – Enter the name of the Message Template. This name 

appears in the Message Template drop-down list, so it should 

be a brief (40 character) description of the template. 

Description – Enter a description of the Message Template. The 

description is currently ignored by OneSight, but it is useful for 

documenting the purpose of your template. 

Subject – This section is used for the subject content in e-mail 

actions. This section can be a mixture of text and substitution 

variables. For example, %DescriptionShort%, displays a short 

description of the alert condition. Refer to the “Message 



Template Variables” section later in this chapter for a list of 

available substitution variables. 

Body – This is the actual content of your actions. This section 

can be a mixture of text and substitution variables. For example 

to display the alert priority, a long description, and links to the 

status details page, you would enter the following: 

OneSight %Priority% Alert 

%DescriptionLong% 

Current status: %statuslink% 

Refer to the “Message Template Variables” section later in this 

chapter for a list of available substitution variables. 

Note: To send HTML-based emails, include either an or 

tag in the body of the message, preferably in the 

body section. OneSight will then set the headers so that email 

recipients using an HTML capable email client, will be able to 

view alerts in that format. 

4. Enter the content of the alert message template and click OK. 

Modifying an Alert Message Template 

Warning: If you modify an existing template that was provided by 

Empirix, Inc., the changes will be lost following an upgrade to a 

future version of OneSight. Your custom Message Templates will 

always be preserved following an upgrade. 

To modify a Message Template: 


2. Select Alert Message Template. 



3. Select the alert message template that you want to change and 

click Modify. 

4. Make any changes and click OK. 

Message Template Variables 

The Message Template substitution variables are defined below. 

These variables are recognized in the Message Template Files 

because they are surrounded by the percent (―%‖) character. 

Additionally, you can specify a maximum length for each variable 

by appending a colon (―:‖) character and maximum length value to 

the end of the variable name. For example, 

%DescriptionLong:48% will limit the extended description of the 

alert to 48 characters. 

Note: Depending on the context in which the variables are used, 

they may not get resolved. For example, %systemname% may not 



resolve when at a monitor group level since there may be any 

number of system names. 

%AlertName% – The name of the alert condition. Example: ―Slow 

URL‖. 

%AlertNotes% – Contains runtime acknowledged notes. After an 

alert is acknowledged, escalated email actions can optionally 

include %AlertNotes%. 

%AlertSummary% – The summary of the alert condition, as 

generated by OneSight. Example: ―Slow URL: Value was 11.701 

seconds, threshold is 8.0 seconds (4/4/01 1:52 PM)‖. 

%AlertText% – The text of the alert as received from the agent. 

%AlertThreshold% – The numeric threshold value that triggered the 

alert. Example: ―8.0 seconds‖. 

%AlertType% – The type of the alert, as defined by OneSight. 

Example: ―Greater Than Threshold (Notify Once)‖ 

%AlertValue% – The numeric value of the alert, or ―N/A‖ for non 

threshold alerts. Example: ―11.701 seconds‖. 

%Attribute->attribute% – Attribute is the name of the attribute whose 

value you want to interrogate. For example, if you have an attribute 

named Application with a value of Card Services, then 

%Attribute->Application% resolves to Card Services if the 

alerting Monitor contains this Attribute. 

%ChartLink% – A http link to the OneSight Metric Performance 

Report for the metric that generated the alert. This variable can be 

useful for e-mail actions sent to OneSight Administrators and 

Operators. 

%Component% – The name of the component that generated the 

alert. Example: ―Disk C:‖. 



%ConfigAlertNotes% – Contains the configuration notes for the alert 

as specified in the Notes tab of the Alert Editor. 

%ConfigLink% – A http link to the OneSight Metric Configuration 

Report for the metric that generated the alert. This variable can be 

useful for e-mail actions sent to OneSight Administrators and 

Operators. 

%CurrentClip% – For OneSight Voice Engine scripts, attaches the 

voice clip of the current run to an email. 

%DateLong% – The locale-specific date the alert occurred, in long 

format. Example: ―Wednesday, April 4, 2001‖. 

%DateShort% – The locale-specific date the alert occurred, in short 

format (mm/dd/yy). Example: ―4/4/01‖. 

%DescriptionLong% – An extended description of the alert 

condition, as generated by OneSight. 

%DescriptionShort% – A short description of the alert condition, as 

generated by OneSight. This variable is useful for the Subject line 

of an e-mail action. 

%InsertFile:filename% – Filename is the path and name of the file to 

be inserted into the message. For example, you could use this 

variable to include the output results of a prior action. A script 

action could write to an output file and a subsequent email action 

could include the contents of the file. 

%IntelliSearch% – Including this variable in your template will 

invoke the IntelliSearch algorithm against the alerting Monitor. The 

format is as follows: 

IntelliSearch[:numberOfEntries[CWG][:StringSizeLimit]] 



where: 

numberOfEntries specifies how many monitors are potentially 

returned 

C specifies Monitors in Critical State 

W specifies Monitors in Warning State 

G specifies Monitors in Good State 

StringSizeLimit is the maximum length of this variable's result 

For example, %IntelliSearch:5WC:2500% will allow 5 items that 

are in critical or warning state and will (in total) be less than 2500 

characters in length. 

%Location% – The location of the Data Collector that sends out the 

alerts. 

%Metric% – The name of the metric that generated the alert. 

Example: ―Disk: % Space Available‖ 

Note: For SNMP dedicated monitors, ―SNMP‖ is displayed. 

%MetricDescription% – The description of the metric that generated 

the alert. 

%Monitor% – The name of the monitor that generated the alert. 

Example: ―URL (http://www.empirix.com)‖. 

%Network% – The network of the Data Collector that sends out the 

alerts. 

%PlanName% – The name of the OneSight Action Plan that 

generated the alert. Example: ―Email KenD‖. 

%Priority% – The priority of the alert. Example: ―Warning‖. 



%_property% – Allows access to any monitor property. Substitute 

the word property for the actual property name. For example, some 

OneSight Voice Engine and Voice Watch properties are: 

%_HIMServerName% – Returns the CallMaster server name. 

%_HIMPath% – Returns the path to the OneSight Admin and 

Detail .asp pages included with the CallMaster installation. 

%_HIMSID% – Returns the scenario ID. 

%_HIMSCID% – Returns the script ID. 

%_CPServerName% – Returns the Voice Watch server name. 

%_CPUserName% – Returns the User ID of the Voice Watch 


%_CPPassword% – Returns the password of the Voice Watch 


%Region% – The region of the Data Collector that sends out the 

alerts. 

%StatusLink% – A http link to the OneSight Status Details Page for 

the metric that generated the alert. This variable can be useful for e- 

mail actions sent to OneSight Administrators and Operators. 

%SystemName% – The name of the system that generated the alert. 

Example: ―JBK_P3‖. 

%TimeLong% – The locale-specific time the alert occurred, in long 

format, including the time zone. Example: ―1:52:16 PM PDT‖. 

%TimeShort% – The locale-specific time the alert occurred, in short 

format. Example: ―1:52 PM‖. 

%UserGroup% – The name of the user group. 



%WebApplication% – The name of the Monitor Group that generated 

the alert. Example: ―Business Partner Extranet‖. If multiple 

Monitor Groups use this metric, the result is a comma delimited list. 

Triggering a Scripting Action 

In the Action Manager dialog box, when you click Scripting in the 

Action Types list, the bottom portion of the dialog box displays 

options for configuring a Scripting action. 

Note: If you are running a script on a remote machine, that machine 

must have either a Data Collector or Remote Agent installed. 

To add a scripting action: 


2. In the Global Action List Manager, click New. 

3. In the Action Manager - Add dialog box, enter a name for the 

action in the Name box. 



4. From the Action Type list, select Scripting. 

Use the following options to specify how the Scripting action is 

configured: 








state. 














action will succeed. 

Path – Enter a path, including the script name, for this script. 

The path can either be absolute or relative to the machine on 

which the script is executed. For example: 

F:\scripts\script.bat 

If you specifically call the command engine, for example: 

C:\winnt\system32\cmd.exe, you must add ―/c‖ at the 

beginning of the parameters value as shown in the second 

example below. 

Note: If you are using the %Monitor% variable and you have 

created monitors with spaces in the name, run the batch file 

using the command engine as described above, and place quotes 

around each parameter. If you do not, parameters may not be 

passed correctly. 

For UNIX systems, enter the shell path. For example: /bin/sh 

Parameters – Parameters entered into this field are appended to 

the script command. For example, entering ―-edaf‖ is equivalent 

to a command line entry such as: F:\scripts\script.bat – 

edaf 

If you specifically call the command engine, ―/c‖ must be added 

to the beginning of the parameter value. For example: /c 

F:\scripts\script.bat -edaf 



For UNIX systems, specify the location of the Shell script. For 

example: /user/myname/script.sh 

OneSight Message Template Variables can also be included as 

script parameters. 

Environment Settings – This field is used to pass an 

environment setting to your host system. To use this box, set 

the environment variables the same way that you set them on 

the respective systems. If more than one environment variable 

needs to be set, separate them using an ampersand (&). 

For example: 

UNIX – PATH=/bin:/usr/bin&LIBPATH=/lib:/usr/lib 

NT – 

PATH=c:\winnt\system32;c:\winnt&LIBPATH=c:\winnt\lib 

Notes: For best results, do not include a space before or after 

the ampersand (&) when entering multiple settings. 

If the script continues to fail, try adding 

COMSPEC=c:\winnt\system32\cmd.exe to the NT Environment 

settings. 

OneSight Message Template Variables can also be included as 

values for environment variables. 

Machine Name – Enter the name of the machine on which the 

script will execute. The machine name can either be qualified 

(sunsolaris.company.com) or unqualified (sunsolaris). A 

Remote Agent or Data Collector must be running on this 

machine. 

You can specify the %SystemName% message template variable 

for the machine name. The c variable will resolve to the system 

associated with the alert that triggered the script action. 














5. Enter an escalation timeout value. 


OneSight to wait before repeating the action. 

7. Enter the total counts. This is the number of times to repeat the 

action. 

8. In the Scripting Configuration section, enter the correct path for 

this script. 

9. In the Parameters box, enter any parameters necessary for this 

script. You can also include Message Template Variables as 

script parameters. 

10. In the Environment Settings box, enter any NT or UNIX 

environment variables exactly as you would enter them on a 

command line. You can also include Message Template 

Variables as values for environment variables. 



11. Enter the Machine Name on which the script will be executed. 





13. Click OK. 

Triggering an SNMP Action 

The Simple Network Management Protocol (SNMP) action type 

exists to integrate the Empirix OneSight Console with other systems 

or frameworks that can receive SNMP traps. The SNMP type enables 

you to configure an SNMP trap so that OneSight alerts and profiles 

can be sent by other systems. 

To ensure proper communication, a MIB (Management Information 

Base) file is provided to describe the SNMP objects used by 

OneSight. This file can be copied and loaded on remote systems. 

The MIB serves two important purposes: 

To allows traps to be configured before they are received. 

To allow you to view additional information regarding each trap 

type, including a description of the alert that triggers the trap and 

the priority level of the trap. 

In the Action Manager, when you click SNMP in the Action Types 


configuring an SNMP action. 



To add an SNMP action: 







4. From the Action Type list box, choose the SNMP action type. 

Use the following options to specify how the SNMP action is 

configured: 



Action Type – Displays the current notification type. 


















state. 









Destination Host – Displays the destination host name or IP 

address to which the trap is sent. 

Trap Source – Displays the host name or IP address from which 

the trap was sent. By default, the server on which OneSight is 

running is displayed. 

Community – The community string is the SNMP community 

string authorized by the destination trap listener. The default 

SNMP community string for OneSight is public. 

Port – The standard port for SNMP traps is 162. Change the 

default port number in this box. 

Charset – This field is used for internationalization. If 

necessary, select the appropriate character set. 



ISO-8859-1 – Latin alphabet for Western European languages 

such as Basque, Catalan, Danish, Dutch, English, Faeroese, 

Finnish, French, German, Icelandic, Irish, Italian, Norwegian, 

Portuguese, Rhaeto-Romanic, Scottish, Spanish, Swedish, 

Albanian, Afrikaans, and Swahili. 



languages. 










ISO-8859-9 – Latin alphabet for Western European languages, 

similar to ISO 8859-1 with the Icelandic letters replaced with 

Turkish letters. It is also used for Kurdish. 









Windows 1250 – Microsoft Windows Code Page for Central 

European Latin alphabet languages. 

Windows 1251 – Microsoft Windows Code Page for Russian 

and other Cyrillic languages. 

Windows 1252 – Microsoft Windows Code Page for Western 

European languages. 

Windows 1253 – Microsoft Windows Code Page for Greek. 

Windows 1254 – Microsoft Windows Code Page for Turkish. 

Windows 1257 – Microsoft Windows Code Page for Baltic. 


Specific Type – Displays a priority level for SNMP traps. These 

types (with the exception of Automatic and OneSight User) are 

named to correspond with industry-accepted priority levels for 

SNMP traps. 

Note: An Empirix MIB can be imported into applications that 

process traps (such as your network management system) from 

the OneSight installation directory 

(empirix/onesight/mibs/onesight.mib). This MIB contains the 

appropriate information for OneSight trap types. Importing this 

MIB allows you to configure these types in your network 

management system. 

The following list describes the items in the Specific Type list: 

Automatic – This option associates the trap level specified 

with corresponding OneSight warning levels. 

OneSight – Critical – Defines this SNMP action as OneSight 

Critical. 



OneSight – Major – Defines this SNMP action as OneSight 

Major. 

OneSight – Minor – Defines this SNMP action as OneSight 

Minor. 

OneSight – Warning – Defines this SNMP action as OneSight 

Warning. 

OneSight – Normal – Defines this SNMP action as OneSight 

Normal. 

OneSight – User – This option is reserved for a user-defined 

mapping of SNMP trap priority levels. User-defined 

information is added using the User Text box. 

User Text – Displays user-defined text when the Specific Type 

is OneSight User. 


















Message Templates for details. 

6. In the Escalation Timeout field, enter the amount of time (in 

minutes) for this action to exist before escalating to the next 

action in the action plan. 




action. 

9. In the SNMP Configuration section, enter the destination host 

and trap source for this action. 

10. From the Specific Type list, select the appropriate type for this 

action. 

11. If the Specific Type is OneSight User, enter a message for the 

user in the User Text box. 





13. Click OK. 

Triggering an SNMP Set Action 

The Simple Network Management Protocol (SNMP) Set action type 

lets you perform an SNMP set operation, setting a particular MIB 

Object ID (OID) to a specified value. For this action to work, 



change the SNMP community string rights to Read-Write in the 

SNMP Services Panel and restart the service. 

In the Action Manager, when you click SNMP Set in the Action 

Types list, the bottom portion of the dialog box displays options for 

configuring an SNMP Set action. 

To add an SNMP Set action: 







4. From the Action Type list box, choose the SNMP Set action 

type. 

Use the following options to specify how the SNMP action is 

configured: 












state. 











SNMP Set Configuration 

Host – The system where the specified SNMP Object ID’s 

value will be set. You can use the %SystemName% message 

template variable to specify the host. 

Port – The port on the specified host. 

Community – The community string is the SNMP community 

string authorized by the destination trap listener. The default 

SNMP community string for OneSight is public. 

OID – The OID that you want to set. 

Value – The value to set the SNMP Object ID’s value to. You 

can also use message template variables to specify the value. 

Data Type – The type of data. 




















action. 

8. In the SNMP Set Configuration section, enter the host. 

9. Enter or click Browse to select the OID. 

10. Enter the value to which you want to set the OID. 

11. Select the type of data. 




must be defined before a test of this action will succeed. In 

addition, the SNMP community string rights in the SNMP 

Services Panel must be changed to Read-Write and the service 

must be restarted. 

13. Click OK. 



Triggering a Delay Action 

The Delay action type lets you make the wait between actions more 

explicit. This action adds a delay period where nothing is done. 

To add a Delay action: 







4. From the Action Type list box, choose the Delay action type. 

Use the following options to specify how the Delay action is 

configured: 












state. 








Test – Performs a test of this action as configured. 


















action. 





9. Click OK. 

Triggering a Monitor Action 

The Monitor action lets you enable or disable a monitor based on an 

event. For example, you could start a monitor that does additional 

checks when a problem occurs, or you could disable a monitor that 

should not be running under certain conditions. 

In the Action Manager, when you click Monitor in the Action 

Types list, the bottom portion of the dialog box displays options for 

configuring a Monitor action. 

To add Monitor action: 







4. From the Action Type list box, choose the Monitor action type. 

Use the following options to specify how the Monitor action is 

configured: 














state. 









Monitor Configuration 

– Select the monitor or monitor group that 

you want to enable or disable. 

Enable – Select this option to start the selected monitors 

when this action occurs. Deselect this option to stop the 

selected monitors when this action occurs. 




















action. 

8. In the Monitor Configuration section select the monitor or 

monitor group that you want to start or stop as a result of this 

action. 

9. Select enable to start the monitor or monitor group. Deselect 

enable to stop the monitor or monitor group as a result of this 

action. 



11. Click OK. 

Triggering a Socket Connection Action 

The Socket Connection action lets you open a socket and send a 

message. 

In the Action Manager, when you click Socket Connection in the 


options for configuring a Socket Connection action. 



To add a Socket Connection action: 







4. From the Action Type list box, choose the Socket Connection 

action type. 

Use the following options to specify how the Socket 

Connection action is configured: 












state. 











Socket Connection Configuration 

Remote Host – Enter the remote host to which you want to 

send a message. 

Port – Enter the port. 

Text to Send – Enter the text to send. 




















action. 

8. In the Socket Connection Configuration section enter the 

remote host. 

9. Enter the port to use. 

10. Enter the text to send. 



12. Click OK. 

Triggering a HTTP Post/Get Action 

The HTTP Post/Get action lets do a Get or Post using HTTP 

Protocol. 

In the Action Manager, when you click HTTP Post/Get in the 


options for configuring an HTTP Post/Get action. 



To add an HTTP Post/Get action: 







4. From the Action Type list box, choose the HTTP Post/Get action 

type. 

Use the following options to specify how the HTTP Post/Get 

action is configured: 












state. 











HTTP Post/Get Configuration 

Web URL – Enter the URL of the web site. 

Type of request – Select whether you want to do a get or post. 

Message to Post – This field is available when the type of 

request is Post. Enter the message to post. 

Note: name/value pairs can be defined by name=value, 

separated by an ampersand (&). For example, 

param_from=onesight&param_msg=timeout. The 

name/value pairs posted can be processed by the remote 

server which receives the post. 




















action. 

8. In the HTTP Post/Get Configuration section enter the URL to do 

a post or get against. 

9. Select the type of request. 

10. For a post action, enter the message to post. 



param_from=onesight&param_msg=timeout. The name/value 

pairs posted can be processed by the remote server which 

receives the post. 



12. Click OK. 

Triggering a Syslog Action 

The Syslog action lets you log a message to a Syslog deamon. 

Note that the syslog on a Unix/Linux machine does not accept 

remote syslogs by default. You must change the configuration to 



enable it. Different Unix/Linux implementations may require 

different steps to enable remote syslogs. Following is an example: 

Vi /etc/syslog-ng/syslog-ng.conf 

Uncomment the following line to make it listen on port 514: 

#udp(ip(“10.12.34.110”) port(514)); 

Restart the syslog-ng service: 

Syslog-ng –f /etc/syslog-ng/syslog-ng.conf 

In the Action Manager, when you click Syslog in the Action Types 


configuring a Syslog action. 

To add a Syslog action: 







4. From the Action Type list box, choose the Syslog action type. 

Use the following options to specify how the Syslog action is 

configured: 












state. 











Syslog Configuration 

Syslog Host – Enter the name or IP address of the machine 

where the syslog deamon is running. 

Message to Send – Enter the message to log. Note that 

substitution variables cannot be used here. 




















action. 

8. In the Syslog Configuration section enter the name or IP 

address of the machine where the syslog deamon is running. 

9. Enter the message to log. 



11. Click OK. 


The Global Action Manager displays currently configured actions. 

Use this dialog box to configure individual actions or responses for 

use within your e-business system. The actions you configure are 

used to perform specific tasks—such as e-mail alerts, or scripting 

actions—when associated with action plans, profiles, and monitor 

group health. 



Note: When you change a global action, this affects all action plans 

that use it. 

Clicking New or Modify from the Global Action Manager displays 

the Action Manager for that action type. From the Action Manager, 

actions can be created or modified to accomplish specific results. 

You can make modifications to actions at any time; changes made 

to the configuration of actions affect all action plans, except the 

plans currently in use by the OneSight Console. 



Use this dialog box to configure properties that affect all actions. 

The Global Action Options dialog box includes tabs for global 

options such as e-mail and scripting. 

Before an action type is available for use in an action plan, it must 

be enabled in the Global Action Options dialog box. The exception 

is e-mail actions, which are enabled by default. To enable actions 

and notification types, click the Enable check box for the specified 

type and complete any configuration information for that action 

type. 

Configuring Global Email Actions 

To configure global e-mail options: 


2. On the Global Action Manager page, click Global Options. 

3. In the Global Actions Options dialog box, click the E-Mail tab. 

Configure properties for all e-mail actions. From this tab you 

can define the primary and backup e-mail servers, identify the 

sender address for e-mail notifications, enable message 



consolidation for e-mail notifications, and disable e-mail 

messaging, if necessary (e-mail notifications are enabled by 

default). 

Enable E-mail Notification – E-mail actions are enabled by 

default. To disable e-mail actions, clear this check box. 

Require User Authentication – SMTP authentication will be 

required. 

Servers Settings 

E-Mail Server – Displays the machine name of the primary host 

server for e-mail. For example: mailhost.company.com. For more 

information, see Configuring the Mail Server. 

Backup E-Mail Server – Displays the machine name of the 

backup host server for e-mail. For example: 

backup.company.com. For more information, see Configuring the 

Mail Server. 

Identification Settings 

Sender’s Address – Defines the address to be displayed when 

an e-mail notification arrives at the destination address. For 

instance, defining the Sender’s Address as 

OneSight_team@company.com quickly alerts the recipient that 

the message is about the health of the system. 

Account Name – Type the name of the user account to which 

the message will be sent (for example, mailtest). This should 

be the account name for the e-mail address that you specified 

in the Sender’s Address box. This field is only available 

when Require User Authentication is selected. 

Password – Enter the password for SMTP authentication. 

This field is only available when Require User 

Authentication is selected. 



This server requires a secure connection (SSL) – Select this 

checkbox if the server requires an encrypted connection. The 

target email server must be using SSL and you must place the 

mail server trust certificate into the .keystore file in the 

OneSight installation directory. This field is only available 

when Require User Authentication is selected. 

Message Consolidation Settings 

Enable Consolidation – Consolidates e-mail actions that are 

configured to use the same e-mail address (for example, any e- 

mail action type addressed to: it_manager@company.com). 

Multiple actions may be triggered due to a cascading system 

failure or a recurring problem. Select this option to reduce the 

number of e-mail notifications delivered during a critical 

period. Since a single action can be used by multiple action 

plans, the frequency of notifications is potentially high. 

When the Enable Consolidation check box is cleared, the 

recipient receives a notification each time an action is triggered 

by the system. When Enable Consolidation check box is 

selected, the recipient receives the first notification, then 

OneSight consolidates all notifications for the interval time 

specified in the Consolidation Interval box, and notifies the 

recipient each time the interval time has expired. The body of 

the message includes the highest priority notification received 

during this interval. 

An example consolidation message is: 

Subject: CPU overloaded, long run queue (user_nt) 

OneSight Warning Alert. 

CPU overloaded, long run queue: Value was 16 

processes, threshold is 4 

processes (4/4/00 6:17 PM) 

Component: user_nt 

Event: CPU overloaded, long run queue 

Metric: Processes: Run Queue Length 

Monitor: Windows NT 4 (user_nt) 



Monitor Group: User Monitor Group 

Description: Number of processes in the run queue 

Note: Selecting this check box sets message consolidation for 

all e-mail notifications. If a cascading system failure occurs, e- 

mail notifications will still be sent; however, they will be 

consolidated for the interval specified. To disable e-mail 

notifications entirely during a critical period, clear the Enable 

E-Mail Notification check box. 

Consolidation Interval (minutes) – Displays the amount of time 

(in minutes) that messages are consolidated before being sent to 

the recipient. The first notification is delivered prior to the 

consolidation time period. When the time period expires, a 

single (consolidated) notification is delivered, and the 

consolidation interval is reset. 

Note: To ensure that the most important notifications are 

delivered, even with message consolidation turned on, OneSight 

will interrupt the consolidation interval if a higher priority alert 

is encountered during the consolidation period. 

4. To enable e-mail notifications, select the Enable E-mail 

Notification check box. 

5. Under Servers, enter the machine names of the primary and 

backup e-mail servers. 

6. Under Identification, enter the return address in the Sender’s 

Address field. This e-mail address may be used for reply mail, 

as well as to alert the recipient of either the nature of the 

message or the source of the message generation (for example, 

OneSight_mgr@company.com). 

7. Under Message Consolidation, select the Enable Consolidation 

check box to activate this feature. Selecting this check box 

enables the OneSight system to manage the number of potential 

messages a recipient receives as a result of a given alert. Set the 

consolidation interval as appropriate. 



8. Click OK to preserve these settings. 

Configuring the Mail Server 

A mail server must be configured for email notification to work. 

Note: If you configure the mail server specification on a OneSight 

server with a name that that includes an underscore (for example, 

onesight_server), you should confirm that that e-mail alerts 

continue to function after making this change. If your server 

validates host names according to RFC 810 (most servers do not), a 

OneSight server name containing an underscore may be rejected. 

To configure the mail server, complete the following steps: 

1. On the Configure Action Plans page, click Global Actions. 

2. One the Global Action Manager page, click Global Options. 

3. In the Global Action Options dialog box, click the E-Mail tab. 

4. Under Servers, enter the domain names of the primary and 

backup SMTP mail servers to use when sending e-mail. 

Note: When specifying the primary or backup mail servers, use 

the SMTP port designated by your company. If you do not 

specify a port number, the default SMTP port number (port 25) 

is used. If you are unsure of your company’s mail server 

domain names or SMTP port number, contact your System 

Administrator. 


To use an SMTP port other than the standard port used for mail, 

complete the following steps: 

1. In the Global Action Options dialog box, click the E-Mail tab. 



2. Under Servers, specify the port number following the server 

name (separated by a colon), where is the nonstandard 

port. For example: mailhost.company.com: 

3. If you are using the default SMTP port 25, you do not need to 

specify it in this box. 


Configuring Global Incoming E-Mail Options 

Use the Incoming E-Mail tab to configure the e-mail account that 

will be monitored for replies to e-mail actions. OneSight will not 

monitor the e-mail server if there are no outstanding action plans. 

If OneSight cannot connect to the email server, it will write a 

message to the OneSight log. 

Note: If you are using Microsoft Outlook, line breaks may be 

removed, resulting in poorly formatted alert text. To make Outlook 

stop removing extra line breaks: 

1. Select Options from the Tools menu in Outlook. 

2. Click the E-mail Options button on the Preferences tab. 

3. Uncheck Remove extra line breaks in plain text messages. 



4. Click OK. 

Accept e-mail responses – Select this check box to enable incoming 

e-mail actions. 

E-Mail Server (POP) – Enter the e-mail server. For example, 

server.empirix.com. To specify an alternate port for the server, 

append the port number to the server name. For example, 

server.empirix.com:995. 

Account Name – Enter the user name of the account. 

Password – Enter the password for the account. 

This server requires a secure connections (SSL) – Select this check 

box if the server requires a secure connection. 

Configuring Global Scripting Options 

Use the Scripting tab to configure properties that affect all scripting 

actions. 


Modifying An Action Plan 

Enable Scripting Actions – Select this check box to enable scripting 

actions for the OneSight system. 


An action plan specifies a sequence of actions that you want 

OneSight to perform if a monitor detects a problem that triggers an 

alert. To modify an existing action plan, complete the following 

steps: 

1. On the Action Plans page, highlight an existing plan, and then 

click Modify. 



2. In the Action Plans - Modify dialog box, change the name for 

the plan, if necessary. 

Note: If an action plan is in use by a monitored web component, 

the value in the Name box cannot be edited. 

3. Click Add in the Schedules for this Action Plan section to add 

more time intervals to the plan, or select a time interval and 

click Remove to delete the time interval from the plan. 

4. Select a time interval and click Add in the Actions for this 

Schedule section to include additional actions in the plan or 

click Modify to edit an existing action. 

Caution: When you edit an existing action, this change applies 

to every action plan with which it is associated. 

5. Click Remove to delete an action from the list. 

6. When you are finished modifying the action plan, click OK in 

the Global Action List Manager. 

7. In the Action Plan - Modify dialog box, use the arrow buttons to 

reorder the actions in the plan, if necessary. 

8. Click OK. The modified plan appears in the Action Plans list. 

Modifying an Email Action 

To modify an email action: 




2. In the Global Action List Manager, select an e-mail action and 

click Modify. 

3. In the Action Manager - Modify dialog box, change the name 

for the action in the Name box if appropriate. 







6. Enter a reminder interval and total count. 

7. Under E-Mail Configuration, either select Address to enter the 

e-mail address of the person(s) to notify when the action is 

executed, separating email addresses with a space,. Or select 

System User to choose the user from the list of OneSight users. 







9. Click OK. 

Modifying a Scripting Action 

Note: If you are running a script on a remote machine, that machine 

must have either a Data Collector or Remote Agent installed. 

To modify a scripting action: 


2. In the Global Actions List Manager, select an existing scripting 

action and click Modify. 

3. In the Action Manager - Modify dialog box, modify the name 

for the action in the Name box, if necessary. 

4. Enter a value in the Escalation Timeout box. 

5. Enter reminder interval and total count. 

6. In the Scripting Configuration section, modify the path field if 

necessary. 



7. In the Parameters field, modify any parameters necessary for 

this script. You can also include Message Template Variables 

as script parameters. 

8. In the Environment Settings field, modify the environment 

variables as necessary. You can also include Message 

Template Variables as values for environment variables. 





10. Click OK. 

Modifying an SNMP Action 

To modify an SNMP action: 




2. In the Global Actions List Manager, select an existing SNMP 









5. In the Escalation Timeout box, enter the amount of time (in 


action in the Action Plan. 


7. In the SNMP Configuration section, enter the new destination 

host and trap source for this action, as required. 

8. In the Specific Type box, select the action type for this action. 



9. If the Specific Type is OneSight User, enter a message for the 

user in the User Text box. 





11. Click OK. 

Modifying an SNMP Set Action 

To modify an SNMP set action: 


2. In the Global Actions List Manager, select an existing SNMP set 






4. In the Escalation Timeout box, enter the amount of time (in 


action in the Action Plan. 


6. In the SNMP Set Configuration section, enter the host and port, 

as required. 

7. Enter or select the new OID, value and data type. 




must be defined before a test of this action will succeed. In 

addition, the SNMP community string rights in the SNMP 

Services Panel must be changed to Read-Write and the service 

must be restarted. 

9. Click OK. 

Modifying a Delay Action 

To modify a delay action: 




2. In the Global Action List Manager, select an delay action and 

click Modify. 







7. Click OK. 

Modifying a Monitor Action 

To modify a monitor action: 




2. In the Global Action List Manager, select an e-mail action and 

click Modify. 










7. Under Monitor Configuration section, select or deselect a 

monitor or monitor group. 





9. Click OK. 

Modifying a Socket Connection Action 

To modify a socket connection action: 


2. In the Global Action List Manager, select a socket connection 






6. Under Socket Connection Configuration section, enter the name 

or IP address of the remote host. 

7. Enter the port. 

8. Enter the text to send. 





10. Click OK. 

Modifying an HTTP Post/Get Action 

To modify an HTTP Post/Get action: 


2. In the Global Action List Manager, select an HTTP Post/Get 






6. Under HTTP Post/Get Configuration section, enter the URL. 

7. Select the type of request. 



8. For post requests, enter the message to post. 



param_from=onesight&param_msg=timeout. The name/value 

pairs posted can be processed by the remote server which 

receives the post. 



10. Click OK. 

Modifying a Syslog Action 

To modify a syslog action: 


2. In the Global Action List Manager, select a syslog action and 

click Modify. 





Retiring an Action Plan 


6. Under Syslog Configuration section, enter the name or IP 

address of the host. 

7. Enter the message to send. 



9. Click OK. 

Retiring an Action Plan 

When you manually terminate the action plan and click Retire, you 

can add a note as part of the retirement process. This feature allows 

you to add your own information to the action plan’s historical 

record. You can review this text in the Action Plan History report. 

Action Plans Not Associated With an Alert 

You can schedule action plans for specific actions that are not 

associated with an alert. For example, if you want to launch a script 

to reboot a server on a regularly scheduled basis, or if you want a 

schedule so that you receive a page confirming that the OneSight 

server is running, you can set up an action plan and then schedule it. 



To schedule an action plan click the Schedule button on the Action 

Plan page. 

Use this dialog box to disable a scheduled action plan, run an action 

plan only once, or schedule a repeated action. 

Begin at – The list of options for beginning action plans consists of 

a 24-hour range in fifteen minute increments. 

Do once – To configure a single action plan occurrence, click this 

button and specify a date. 

Repeat – To configure a regularly scheduled action plan, click this 

button and configure the time that the action plan should be 

scheduled. You can schedule an action plan that occurs every day, 

every week, or every month. 

Every Hour – select a minute of the hour for the hourly action 

plan. 

Every Day – no additional detail is required. 

Every Week on day – select a day (Sunday through Saturday) for 

the weekly action plan. 

Every Month on day – select a day (1 through 31) for the monthly 

action plan. 






Configuring Downtime 

After you set up monitors and action plans, configuring downtime 

prevents the generation of unnecessary alerts. Setting up your 

downtime information also provides more accurate reporting and 

status information. 

Configuring scheduled downtime results in the following: 

No alerts will be triggered if the component is unavailable. 

Action plans in progress for a component when a downtime 

begins will be retired. 

OneSight Console Status page information will indicate that a 

component is currently in a scheduled downtime. 

Reports that measure availability and performance over time 

include a separate category, Scheduled Downtime, to distinguish 

downtime from those periods that the system was unavailable due 

to an unexpected problem. 

Downtime schedules cannot be modified or deleted for systems that 

are currently in a scheduled downtime. Only downtime schedules 

that have not started or have expired can be modified or deleted. 

Running downtimes can be cancelled. Downtimes that have not 

started or have expired cannot be cancelled. 

Items Available for Downtime Scheduling 

The items available for downtime scheduling include any 

configured web component, arranged in the hierarchy reflected in 

723


your monitor groups. You can schedule downtime for an individual 

monitor or an individual component using a profile monitor. You 

can also schedule downtime for all monitors belonging to the same 

monitor group, or for all monitor groups. 

If you have multiple monitors with the same host name or IP 

address on a specific machine, it is easier to schedule downtime for 

a system. This way, all of the monitors associated with this system 

will have the same scheduled downtime. 

You can schedule downtime in three ways: 

By Monitor – Use this tab to apply downtime schedules to a 

monitor group or individual monitors. 

By System – Use this tab to apply systems to downtime schedules. 

By Downtime – Use this tab to apply monitors to downtime 

schedules. 

On the By Monitor tab, the list of currently scheduled downtimes can 

differ for any item selected in the upper portion of this dialog box. 

A specific monitor may have a several downtime schedules. For 

example, there may be a system-wide downtime scheduled monthly, a 

monitor group downtime scheduled weekly, and a monitor downtime 

scheduled daily. However, you must modify a downtime at the same 

monitor group level that you configured it. 

A global downtime cannot be modified for a specific monitor. A 

global downtime can be modified only when the All Monitor 

Groups option is selected. 

A downtime associated with an entire monitor group cannot be 

modified for a specific monitor. A monitor group downtime can 

be modified only when the monitor group is selected. 



On the By System tab, the list of currently scheduled downtimes can 

differ for any item selected in the upper portion of this dialog box. 

The downtime list shows the status of the downtimes: 

Not run 

Active 

Expired 

A specific system or all systems may have a several downtime 

schedules with different start and end times. For example, there may 

be a system-wide downtime scheduled monthly, a system downtime 

scheduled weekly, and a system downtime scheduled daily. However, 

you must modify a downtime at the same system level that you 

configured it. 

An all systems downtime cannot be modified for a specific 

monitor or system. An all systems downtime can be modified 

only when the All Systems option is selected. 

A downtime associated with a system cannot be modified for a 

specific monitor. A system downtime can be modified only when 

the system is selected. 

Scheduling Downtime by Monitor 

To schedule downtime by monitor: 


Chapter 9: Configuring Downtime 725


2. Select Downtime. 

3. Select an item and click Add or Modify to edit downtime 

information for the selected monitor groups or monitors. 



Note: You cannot modify the downtime configuration of a 

system that is in a currently scheduled downtime. However, you 

can cancel the current running downtime. 

Name – Enter a name for the downtime schedule or keep the 

default name. 

Sample during downtime – When selected, sampling will 

continue during downtime. When not selected, sampling will 

stop during downtime. 

Do once – To configure a single downtime event, select this 

option. 

Start Date – Specify the start date on which you want 

downtime to begin or click the calendar to select a date. 

Downtime cannot be configured in the past. 

Start Time (hh:mm) – Enter the start time. 



End Date – Specify the end date on which you want 

downtime to end or click the calendar to select a date. 

End Time (hh:mm) – Enter the end time. 

Repeat – To configure a regularly scheduled downtime, click 

this button and configure the time that the downtime will occur. 

You can schedule a downtime event that occurs every hour, 

day, week, bi-weekly, monthly, or on the last day of the month. 

Every – Select the frequency with which you want to 

schedule downtime. 

Start Time (hh:mm) – Enter the time to start downtime for all 

frequencies except hourly. 

End Time (hh:mm) – Select this option to enter the time to 

stop downtime. This is for downtimes that need to stop at a 

particular time, not after a specified duration. 

Duration – Select this option to enter the length of the 

downtime in hours and minutes. This is for downtimes that 

do not need to stop at a particular time. 

on day – Select a day (Sunday through Saturday) for the 

weekly, and bi-weekly downtime. For the bi-weekly 

downtime, the schedule starts on the next selected day. For 

example, if you create the schedule on Monday and select 

Tuesday as the downtime day, the downtime starts tomorrow. 

on day – Select a day for the monthly downtime. The options 

are 1 through 31 and first, second, third, fourth, or last 

Monday, Tuesday, Thursday, Friday, Saturday, or Sunday. 

on minute - Select a minute of the hour for the hourly 

downtime. 



Notes for this downtime – Enter relevant information for this 

downtime, such as the reason for the downtime. 

4. Enter the downtime information and click OK. 

Scheduling Downtime by System 

To schedule downtime by system: 





3. Click the By System tab. 

4. Select All systems or the system to which you want to add a 

downtime schedule. 

5. Click Add or Modify to display the Downtime Schedule dialog 

box to add a new downtime schedule or modify and existing 

schedule. 

6. Enter the downtime schedule information and click OK. 

Scheduling Downtime by Downtime 

To schedule downtime by downtime: 





3. Click the By Downtime tab. 

4. In the upper portion of the dialog box select the downtime 

schedule to which you want to apply monitors. 



5. Click Add in the Monitors using this downtime section. 

6. Select the monitors you want to view using the monitors where 

and contains fields and click Show. 

7. Select the monitors that you want to apply to this downtime and 

click OK. 

8. Click Add or Modify in the Downtimes schedules portion of the 

dialog box to add a new downtime schedule or modify an 

existing schedule. If you modify an existing schedule the 

changes apply to all monitors using the schedule. 


Putting a Monitor Immediately Into Downtime 


You can put a monitor into downtime for a specified period of time 

starting immediately. Select Start Downtime from the popup menu 

on the Status Detail page or the Alert page. 

Pre-Defined – Select this button to pick downtime from a predefined 

list: 5, 10, or 30 minutes. 

Other – Select this button to enter the number of minutes for the 

downtime. 

Sample during downtime – When selected, sampling will continue 

during downtime. When not selected, sampling will stop during 

downtime. 

Notes for this downtime – Enter relevant information for this 

downtime, such as the reason for the downtime. 






Configuring Attributes and Views 

The Attributes tab of the Attribute editor lists the custom Attribute 

Sets and Attribute Values that are defined in OneSight. You can 

add or remove Attribute Sets or Attribute Values that can be used to 

sort the monitors on the status page. 

The Assignment tab of the Attribute editor lets you add and remove 

attributes across multiple monitors, monitor groups, systems, and 

profiles. 

The Saved Status Groupings tab lists all of the configured status 

groupings that are defined in OneSight. These status groupings can 

be used on the status page to group monitors. They can also be 

configured as the default status grouping for the user. 

Attributes can also be used to create Attribute Matrix Views for 

viewing on the reports tab. An Attribute Matrix View is a high-level 

business view of your application using two attribute sets to create a 

table. 

In addition, you can create image-based custom status views that 

can reflect the geographical location of distributed applications. 

Configuring Attributes 

Adding Attributes Sets and Values 

To add attributes sets and values: 


735


2. Select Attributes to open the Attribute dialog box. 

Use these options to define and manage OneSight attribute sets 

and attribute values. 



names added to this list will appear in the Group by select list 

on the OneSight status page. When you group the status page 

by an Attribute Set, the OneSight status lists only the monitors, 

monitor groups, systems, and profiles that are configured with 

an Attribute Value from that Attribute Set. 

In addition to custom Attribute Set names, the following names 

can also appear in the “Group by” list on the status page: 

 

Action Plan 

Location 



Monitor Type 

Profile 

System 




Add – Opens a dialog box for defining a new Attribute Set 

name. 

Modify – Opens a dialog box for changing the selected attribute 

set. 

Remove– Deletes the currently selected Attribute Set from the 

list. A dialog box appears asking to confirm the deletion. 

Removing an Attribute Set also deletes the associated Attribute 

values. The Attribute Set name is removed from the Group by 

list on the status page. The attribute values are also removed 

from the monitor group, monitor, system, and profile 



systems, and saved status groupings that are using this attribute 

set. 

Attribute Value Name – Shows the list of Attribute Value names 

for the currently selected Attribute Set. Attribute Values can be 


Add– Opens a dialog box for defining a new Attribute Value 

name. 

Modify – Opens a dialog box for changing the selected attribute 

value. 

Chapter 10: Configuring Attributes and Views 737


Remove– Deletes the currently selected Attribute Value name 

from the Attribute Set. A dialog box appears asking to confirm 

the deletion. Removing an Attribute Value also deletes the 

value from the monitor group, monitor, system, and profile 



and systems that are using this attribute value. 

3. Click Add above the Attribute Sets list. 

Use the Add Attribute Set dialog box to add a new Attribute Set 

Name to the list of attributes that are defined in OneSight. Set 

names appear in the Group by option list on the OneSight status 

page. 

Attribute Set Name – Specify a name for the attribute set. 



Access Control Tab – Use this tab to specify which user groups 

have access to this attribute set. 

Owner – The user group for this attribute set. An attribute set can 

be directly owned by a single user group. 







4. Define a name for the set. 

5. Specify access control permissions and click OK. 

6. Make sure the attribute set is selected and click Add above the 

attribute values list. 

Use the Add Attribute Value dialog box to add a new Attribute 

Value Name to the list of attributes values in the selected 

Attribute Set. Attribute Values can be added to monitor groups, 

monitors, systems, and profiles and are used to group items on 

the OneSight status page. 



Attribute Set Name – Displays the Attribute Set to which the 

attribute value will be added. 

Attribute Value Name – Specify the name of the Attribute Value 

to add to the Attribute Set. 

7. Define a name for the value and click OK. 

8. In one or more monitor, monitor group, profile, or system 

configurations, click the Attributes tab. 

9. Click Add. 

10. Select the Attribute value to apply to the monitor, monitor 

group, profile, or system configuration. 

11. Click the Status tab. 

12. On the Status page, select an Attribute Set name from the Group 

by list. Only those monitors, monitor groups, profiles, or 

systems that have an attribute value from that set will appear on 

the status page. 

Removing Attributes Sets and Values 

To remove attributes sets and values: 


2. Click Attributes to open the Attribute Editor. 

3. Select an attribute set or value. 

4. Click Remove above the selected item. 

5. Click Yes to confirm. 


Assigning Attributes to Objects 

Assigning Attributes to Objects 

To assign attributes to multiple monitors, monitor groups, systems, 

and profiles: 


2. Select Attributes to open the Attribute Editor. 

3. Click the Assignment tab. 

Attribute Set – Select the attribute set containing the attributes 

value that you want to assign. 

Attribute Value – Select the attribute value that you want to 

assign. 

Show – Lists the objects of the type that you selected. 

– Select the type of objects that you want to assign 

this attribute value to and click Show. For monitor object types 

you can filter the list so that not all monitors are listed. 


Configuring Saved Status Groupings 

Check All – Selects all of the objects that are listed. 

Uncheck All – Deselects all of the objects that are listed. 

Check box – Select or deselect objects. 

Name – Displays the object name. 

4. Select the type of object that you want to assign this attribute 

value to. For monitor object types, you can also select the 

criteria of the monitors you want to list. 

5. Click Show. 

6. Select the objects that you want to assign this attribute value to. 

Click Check All to select all of the objects in the list. Click 

Uncheck All to deselect all of the objects in the list. 

Note: If, at this point, you change the selected attribute set, 

attribute value, or filtering criteria, you will be asked if you 

want to save the previous changes if those changes have not 

been saved. 



Adding a Saved Status Grouping 

To add a status grouping: 





3. Click the Saved Status Groupings tab. 

Add – Opens a dialog box for adding a new status grouping. 

Modify – Opens a dialog box for modifying the selected status 

grouping. 

Remove – Deletes the selected status grouping. 

Used by – Displays a list of users that are using this status 

grouping. 

Name – Lists the status groupings that are currently configured. 

User Group – Lists the user group. 



4. Click the Add button. 

Status Grouping Name – Enter a name for the status grouping. 

Primary Attribute Set – Select the first attributes set to group by. 

Second Attribute Set – Select the second attribute set to group 

by. 

Third Attribute Set – Select the third attribute set to group by. 

Fourth Attribute Set –Select the fourth attribute set to group by. 

5. Enter a name for the status grouping. 

6. Select the attributes by which you want to group. 



7. Click the Access Control tab to control which user groups have 

access to this status grouping. 

Use this tab to specify which user groups have access to this 

status grouping. 


Owner – The user group for this status grouping. A status 

grouping can be directly owned by a user group. 








8. Configure permissions and click OK. 

9. Click Close to exit the Attribute Editor. 

10. On the Status page, select an Status Grouping from the Group by 

list. 

Modifying a Saved Status Grouping 

To modify a status grouping: 



3. Click the Saved Status Grouping tab. 

4. Select the status grouping you want to change and click Modify. 



Deleting a Saved Status Grouping 

To delete a saved status grouping: 



3. Click the Saved Status Grouping tab. 

4. Select the status grouping that you want to delete and click 

Remove. 

5. Click Close to exit the Attribute Editor. 


Configuring Attribute Matrix Views 


Attribute Matrix Views let you create a customized status page by 

using two sets of attributes to create a table. Attribute Matrix Views 

are also available in the Add Report menu on the Reports tab. 

The example below uses two attribute sets, application and 

communication. Application has three values: billing, shopping, and 

service. Communication has four attribute values: agent, kiosk, 

voice, and web. Custom icons have been assigned to each of the 

communication attributes. 

Each icon represents one or more monitors that have both the 

application and communication attributes. The unspecified column 

contains monitors that do not have a communication attribute, but 

do have an application attribute. Monitors that do not have either 

attribute set are not displayed. 

Clicking a row or column header displays detailed monitor status 

for that respective row or column. Clicking any icon shows detailed 

monitor status for the included monitors. 



Adding Attribute Matrix Views 

To add an Attribute Matrix View: 


2. Click Attribute Matrix Views. 

Add – Displays the Attribute Matrix View – Add dialog box for 

adding an Attribute Matrix View. 

Modify – Displays the Attribute Matrix View – Modify dialog 

box for changing the selected Attribute Matrix View. 

Remove – Deletes the selected Attribute Matrix View. 



Name – Displays the Attribute Matrix View name. 

Description – Displays the Attribute Matrix View’s description. 

3. Click Add. 

Name – Enter a name for the Attribute Matrix View. This name 

will be listed in the Attribute Matrix Views menu item in the Add 

Report menu on the Reports tab. 

Title – Enter the title of the report. 

Description – Enter a description of the report. The description 

is displayed under the report title. 



Select Tab – Use this tab to select the attributes to use for the x 

and y axis and to configure custom icons to display in the 

Attribute Matrix View report. 

Row Attribute Group – Select the attribute group to use for the 

row. 

Column Attribute Group – Select the attribute group to use for 

the column. 

Modify – Displays the Status Icon – Modify dialog box for 

changing the default status icons. 

Set All To Default – Sets all status icons to the default icons. 

Name – Displays the name of the attribute value. 

Icon – Displays the icons assigned to the attribute value. 

Access Control Tab – Use this tab to specify which user groups 

have access to this Attribute Matrix View. 


Owner – The user group for this Attribute Matrix View. An 

Attribute Matrix View can be directly owned by a user 

group. 






4. Select the attribute to use for the rows. 



5. Select the attribute to use for the columns. 

6. Change the icons, if necessary, by clicking Modify. 

This dialog box lets you change the icons that are displayed in 

the report so that they are meaningful in the context of your 

report. 

Icon Set – Select the icon set that you want to use for the status 

icons. Select Default to reset the icon set. 

URL – Enter the location of the icon file that you want to use for 

each state. The files must be located in the 

\Empirix\OneSight\webapps\ROOT\images directory on the 

OneSight installation drive. File names are case sensitive. 

7. Click OK. 

8. Click OK. You can view this Attribute Matrix View by selecting 

it from the Attribute Matrix Views menu option in the Add Report 

menu on the Reports tab. 

Modifying Attribute Matrix Views 

To modify an Attribute Matrix View: 





3. Select the Attribute Matrix View that you want to change, and 

click Modify. 

4. Make any changes. 

5. Click OK. 


Configuring Custom Status Views 

Deleting Attribute Matrix Views 

To delete an Attribute Matrix View: 



3. Select the Attribute Matrix View that you want to delete, and 

click Remove. 

4. Click OK when asked to confirm. 


Custom Status Views allow you to create a customized view 

representing status however you want to visualize it.. For example: 

Geographically – you can overlay status icons on a map image. 

NOC View – you can overlay status icons on a network diagram 

image. 

Hybrid – you can include OneSight pages such as status and 

reports onto a status map, along with URL links. 

Custom Reports – you can overlay metric values onto a 

background images such as a spreadsheet. 

To build a Custom Status View, you create items that you position 

on a canvas using drag and drop. The following types of items can 

be added to a Custom Status View: 

monitors and monitor groups – displays a status icon of the monitor 

or monitor group. 



text – text can be used to label information on the Custom Status 

View or can be used as a link to another location, such as another 

Custom Status View. Text can be formatted using a .css file. 

images – any browser supported image can be used including .gif, 

.jpg, .bmp, and .png. 

area – areas are typically used to provide a clickable area. For 

example, on a map of the United States you could create an area 

in each state that linked to state-specific information. 

frame – frames are used to include a URL, RSS feed, or other 

OneSight content such as an Attribute Matrix View. 

Custom Status Views are available from the main Status menu and 

in the Reports menu, where they can be included in Dashboard 

reports. 

Refer to the example at the end of this section for a step-by-step 

walkthrough of creating a Custom Status View. 

Adding a Custom Status View 

To add a Custom Status View: 




2. Select Custom Status Views. 

Add – Displays the Custom Status View – Add dialog box for 

adding a new Custom Status View. 

Modify – Displays the Custom Status View – Modify dialog box 

for changing the selected Custom Status View. 

Remove – Deletes the selected Custom Status View. 



3. Click Add. 

Name – Enter a name for the Custom Status View. 

Description – Enter a description of the Custom Status View. 

Width – Enter the width of the status map in pixels. 

Height – Enter the height of the status map in pixels. 

Adjusting the width or height resizes the canvas area. 

Map Definition Pane 

Add – Displays the Custom Status View Item – Add dialog 

box for adding a new item. 

Modify – Displays the Custom Status View Item – Modify 

dialog box for modifying the selected item. 



Remove – Removes the selected item. 

Select All – Selects all items in the item list. This is useful 

when you want to reposition a group of items simultaneously. 

Select None – Deselects all items in the item list. 

– Lists all items. The order that the items are 

listed determines the Z-order, that is which items can be 

placed on top of other items. Items can be placed on items 

that are below them on the list. Note that frame items cannot 

have items placed on top of them regardless of where they 

are in the list. You can select more than one item to move 

items simultaneously. 

Canvas Pane – The canvas is where you compose the Custom 

Status View. Click on the item you want to move in the item list 

then drag it to the desired location. 

If you need fine grained control when positioning items, you 

can use the arrow keys on the keyboard to move items one pixel 

at a time. These keys function differently depending on the 

browser you are using: 

Internet Explorer – click the item you want to move using the 

mouse, then use the arrow keys to adjust the item’s position. 

Firefox – first, click a blank area on the canvas, then click the 

item you want to move. Use the arrow keys to adjust the 

item’s position. 



4. Click on an item in the item list that you want to add to 

highlight it on the canvas. Click and drag it to the desired 

location. Continue this procedure until you are done. Refer to 

“Creating custom Status View Items” for information on 

creating new items. The following example shows monitors on 

a map of the United States. 

5. Click OK. 

6. Click OK to exit the Custom Status Views dialog box. You can 

view the Custom Status View by selecting it from the Status 

menu or you can add it to a Dashboard report. 

Creating Custom Status View Items 

Before you can create a Custom Status View, you must create the 

items that you are going to use in it. The following sections explain 

how to create the various types of items. 

Creating a Report Item 

You can add a Gauge report or Metric Performance report to your 

Custom Status View. 

When you select gauge as the item type, a mini-gauge is added to 

the Custom Status View. The gauge has a white rectangle around it. 



To eliminate the white rectangle when place the report behind an 

image that has been made semi-transparent using the Opacity 

setting for the image. 

1. Click Add on the Map Definition tab. 

2. Select Report as the item type. 

Item Type – Select the type of item you want to add. 

Name – Enter a name for the item. If you do not enter a name, 

OneSight will automatically create a name, when possible. 

CSS Style – Enter any valid CSS attribute pair, separated by 

semicolons. For example, font-size : 24px; fontfamily:Rockwell; 

This field is automatically generated for 

Frame and Area items when you enter the height and width. If 

you are adding a gauge report, the width must be less than 

365px or the graph will get truncated. The height must be no 

less than 220 px. 

Note: CSS is not validated. 



Show – Lets you filter the list of monitor groups or monitors 

that are displayed on this page. 

Name – Lists the names of the monitor groups or monitors 

based on the filtering criteria. Select the monitor group or 

monitor for which you want to create an item. 

Report for Metric – Displays the selected metric. This is the 

metric that will be reported on. 

Report Type – Select the type of report you want to add, Gauge 

or Metric Performance. 

Note: If you are adding a gauge report, the width in the CSS 

Style field must be less than 365px or the graph will get 

truncated. The height must be no less than 220px. 

Text – Enter the text that you want to display next to the 

gumball or click Show Metric Value to select a metric whose 

value you want to display. The Text field is automatically filled 

in when you select a metric value. Use the monlight_blank.gif 

icon to only display the value. 

Preview – Displays the item in a separate window. 

3. Enter a name for the item or let OneSight create a name. 

4. Select how you want to filter the monitor list and click Show. 

5. Select the metric that you want to report on. 

6. Select the type of report you want to add. 

7. Click Preview to view the item and click OK when you are done. 

Creating a Monitor Group or Monitor Item 

The Monitor Group and Monitor items show a rolled-up view of 

their status. 




2. Select Monitor Group or Monitor as the item type. 



OneSight will automatically create a name, when possible. 

Hover Text – Enter the text you want displayed when you 

mouse-over the item. For monitors only, you can also enter the 

%hover% variable. It displays the same hover text that is 

supplied on the top-level status page for monitors. It is 

automatically entered into this field for monitors that are 

automatically named. 

Drill Down URL – Enter the URL of the page you want to display 

when you click on the item. For monitor groups and monitors 

only, you can also enter the %drilldown% variable. For monitor 

groups, the variable resolves to the selected monitor group’s 

detailed status page. For monitors, it resolves to the selected 



monitor’s Intellisearch page. It is automatically entered into this 

field for monitor groups and monitors. 

For monitors, the %drilldown_monitorgroup% variable drills 

into the first monitor group of the monitor. 

Note: To link to another Custom Status View, use the URL that 

is displayed when you view the Custom Status Map from the 

main View menu. 




Frame and Area items when you enter the height and width. 


Show – Lets you filter the list of monitor groups or monitors 

that are displayed on this page. 

Name – Lists the names of the monitor groups or monitors 

based on the filtering criteria. Select the monitor group or 

monitor for which you want to create an item. 

Icon Set – Select the icon set that you want to use for the status 

icons. Select Default to reset the icon set. 

New Icon Set – Displays the Add Icon Set dialog box for 

creating a custom set of icons to use for the status display. 

Remove Icon Set – Deletes the selected custom icon set. Default 

icon sets cannot be deleted. 

URL of Good State Icon – Enter the location of the icon you 

want to use when the monitor group or monitor is in a good 

state or click Browse to navigate to the image. 

URL of Warning State Icon – Enter the location of the icon you 

want to use when the monitor group or monitor is in a warning 




URL of Critical State Icon – Enter the location of the icon you 

want to use when the monitor group or monitor is in a critical 


URL of Other States Icon – Enter the location of the icon you 

want to use when the monitor group or monitor is in a state 

other than good, warning, or critical, or click Browse to 

navigate to the image. 

Status Icon Tips – Following are some tips for using status 

icons. 

To create conditional “special effect,” such as a popup, 

specify alternative images for the status icons. 

To make your status icons stand out on a colored background 

images, set the opacity of the background images to between 

20-50%. 

Use the pin_.png status icon images when adding a 

monitor or monitor group status of a map for pushpin look. 

Use the monlight_blank.gif status icon images to show nothing 

when appropriate. 

Show Metric Value – This option is only available for monitor 

items. A dialog box is displayed that lets you select the metric 

value that you want to display. The text field is automatically 

filled in with the appropriate values in the 

%value:componentID:metricID% variable. 

Text – Enter the text that you want to display next to the 

gumball or click Show Metric Value to select a metric whose 

value you want to display. The Text field is automatically filled 

in when you select a metric value. Use the monlight_blank.gif 

icon to only display the value. 





4. Enter text you want displayed when you mouse-over the item. 

5. Enter the URL that you want displayed when you click on the 

item. If you leave this field blank and have let OneSight 

generate the item name, OneSight defaults to the Monitor 

Group’s detailed status page or the Monitor’s IntelliSearch 

page. 

6. Optionally enter the CSS style that you want to use. 

7. Select the monitor group or monitor that you want to use. To 

change the default list of monitor groups, select the filtering 

criteria and click Show. 

8. Change the default icons or create a new icon set, if necessary. 

To create a new icon set: 

1. Click New Icon Set to display the Add Icon Set dialog 

box. 

Name – Enter the name of the new icon set. The name 

will be displayed in the Icon Set drop down on the 

Custom Status View Item – Add dialog box. 

URL of Good State Icon – Enter the path and name of the 

image to use for the good state icon or click Browse to 

select it from the Browse Status Images Directory 

dialog box. This field is optional. 

URL of Warning State Icon – Enter the path and name of 

the image to use for the warning state icon or click 



Browse to select it from the Browse Status Images 

Directory dialog box. This field is optional. 

URL of Critical State Icon – Enter the path and name of 

the image to use for the critical state icon or click 


Directory dialog box. This field is optional. 

URL of Other States Icon – Enter the path and name of 

the image to use for the other states icon or click 


Directory dialog box. This field is required. 

2. Click Browse beside each state icon line to display the 

Browse Status Images Directory dialog box. 

3. Select the image that you want to use and click OK. 

4. Repeat for each status type. Note that you must select 

an image for the URL of Other States Icon field; all other 

status icon fields can be left blank. 

5. Click OK. 

9. Enter the text you want to display next to the icon. For monitor 

items you can also click Show Metric Value to select a metric 

whose value you want to display in place of text. The Text field 

is automatically filled in with the 

%value:componentID:metricID% variable. 


Creating a Text Item 

Text items are useful for both labels and links. 

1. Click Add on the Map Definitions tab. 



2. Select Text as the item type. 



OneSight will automatically create a name. 


mouse-over the item 


when you click on the item. 









Text – Enter the text. 





4. Enter the text you want to display when you mouse-over the 

item. 

5. Enter the URL you want displayed when you click on the item. 

6. Enter the CSS style to apply to the text. 

7. Enter the text. 


Creating an Image Item 

An image item can be any valid browser image file that you want to 

display in the Custom Status view. OneSight provides a library of 

images that you can use including over 300 geographical maps, 

gumballs, pins, flags, etc. In addition, you can import any browser 

supported images into OneSight. 

Images cannot be larger than the overall Custom Status View. 


2. Select Image as the item type. 







mouse-over the item. 











Image URL – Enter the name and location of the image you want 

to use. 

Image Opacity – Select the percentage of opacity for the image. 

The image will soften with a lower opacity value. This is useful 

when placing images on top of one another. For example, 

pushpins will be easier to see on a color background image with 

a lower opacity. It can also be useful for making an item 

transparent. 

Browse – Displays the Browse Status Images Directory for 

selecting the image you want to use. 



4. Enter the text you want to display when you mouse-over the 

item. 

5. Enter the URL that you want to display when you click on the 

item. 



6. Enter the CSS style to use. 

7. Images must be located in the statusImages directory. Click 

Browse to select an image. 

Import – Displays the Import Status Image File dialog box for 

importing an image into OneSight. The file is imported into the 

statusImages/imports directory. 

Select the image you want to use. If it is not listed here, you can 

import it. 



8. Expand the tree and select the image you want to use and click 

OK or click Import to select and import an image into OneSight. 

Image URL – Enter the name and location of the image you want 

to import or click Browse to navigate to it. 

9. Enter the name and location of the image you want to import or 

click Browse to navigate to it and click OK. 

10. Click Preview to view the item and click OK. 

Creating a Area Item 

An area item is typically used to create a hot spot on the status 

view. For example, you could create hot spots on a map that link to 

information specific to those locations. 




2. Select Area as the item type. 












semicolons. This field is automatically generated for Frame and 

Area items when you enter the height and width. 


Width – Enter the width of the area in pixels. 

Height – Enter the height of the area in pixels. 





4. Enter the height and width of the area. The CSS Style field is 

automatically generated. 


Creating a Frame Item 

A frame item is a URL page, with a set width and height., that is 

displayed in the Custom Status view. Following is a list of some of 

the things that you can put in a frame that contributes to the Status 

View in a meaningful way: 

OneSight At-A-Glance display 

OneSight Attribute Matrix View 

Custom Report 

Mini-Gauge Report 

RSS Feeds 

Weather widgets, etc. 


2. Select Frame as the item type. 















Frame URL – Enter the URL of the content you want to display. 

To use an Attribute Matrix View, display the view from the 

Status Menu, change status_view to status_attr in the URL 

and use this value. Doing this removes extraneous menu 

content. To use a OneSight report, display the report, refresh 

the UI to get the URL, change report.jsp to 

report_window.jsp in the URL and use this value. To include 

a mini-gauge report, change 1062 to 1061. 

The Attribute Matrix URL is “/status_attr.jsp” and the 

At=A=Glance URL is “/status_console.jsp.” 

Width – Enter the width of the frame in pixels. 

Height – Enter the height of the frame in pixels. 



4. Enter the width and height of the item. The CSS Style field is 

automatically generated. 




Modifying Items 

To modify an item: 



3. Select the Custom Status View containing the item you want to 

modify and click Modify. 

4. Select the item and click Modify to display the Custom Status 

View – Modify dialog box. 


Deleting Items 

To delete an item. 



3. Select the Custom Status View containing the item you want to 

delete and click Modify. 

4. Select the item and click Remove. 

5. Click Yes when asked to confirm the deletion. 

Modifying a Custom Status View 

To modify a Custom Status View: 





3. Select the Custom Status View that you want to change and 

click Modify. 


Deleting a Custom Status View 

To delete a Custom Status View: 



3. Select the Custom Status View that you want to delete and click 

Remove. 

4. Click Yes when asked to confirm the deletion. 

Custom Status View Example 

This example shows call queue monitors overlaid onto a map of the 

United States, their status indicated by the color or the push pin. 

One location displays a gauge report. An Attribute Matrix view is 

included showing the status of each location. The Current Average 

Queue value for all locations is displayed via a Compound Monitor. 

A link to a Custom Status View of Europe is also included. 

This example assumes that the following items have already been 

configured in OneSight: 

Four monitors, one for each call center 

A compound monitor for displaying the current average queue 

value 

Application and site attributes 

An Attribute Matrix View showing the status of each location 



The outer glow image has been imported into OneSight 

1. Click Custom Status Views from the Configure page. 



2. Click Add. 

3. Enter “Call Queues” in the Name field. 

4. Click Add to begin adding items. First we will add the 

background map image. Select Image in the Item Type field. 



5. Click Browse to select the image from the image library. 

Expand the tree and select the USA6c.gif file. 

6. Click OK. The Name and Image URL fields are automatically 

populated. Select 30 in the Image Opacity field. This will soften 

the background so that the monitor icons can be seen. The CSS 

Style field is automatically populated. 



7. Click OK. Select USA6c.gif in the list to highlight it on the 

canvas, then click and drag it to position it. 

8. Next we will add the monitor groups. Click Add. 

9. Select Monitor Group or Monitor in the Item Type field. Select the 

Green River Call Queue monitor. The Hover Text and Drill Down 

URL fields are automatically populated. 



10. Next we will change the icons from the default icons to push 

pins. In the URL of Good State Icon line, click Browse. Select the 

pin_green.png file. 



11. Click OK. Repeat this process for the remaining three state 

icons, selecting, pin_yellow.png, pin_red.png, and pin_grey.png. 



12. Click OK. The image is displayed in the top left-hand corner of 

the canvas. Select Green River Call Queue from the list and click 

and drag the pin to it’s appropriate location. 



13. Repeat steps 8-12 for the remaining three monitors: Pittsburgh 

Call Queue, LA Call Queue, and Atlanta Call Queue. 



14. Next we will add the bubble that will contain the gauge report. 

Click Add. Select Image in the Item Type field. Click Browse. 

Select the Outer Glow – Grey .png file from the imports directory. 

This example assumes that you have imported this image. All 

imported images reside in the imports directory. 

15. Click OK. 



16. Click OK. Select the Outer Glow – Grey .png file from the list and 

move it to the desired location. 

17. Next we will add the Gauge report. Before we add the item, we 

need to get the report’s URL. 

18. Click OK to save the Custom Status View. Click Close to exit 

the Custom Status View dialog box. 

19. Click the Reports tab. Display the Gauge report for the 

Pittsburgh Call Queue monitor. Click Refresh to display the 

correct URL. 



20. Change reports.jsp to report_window.jsp. 

21. Change 1060 in the URL to 1061 and click Refresh. Copy this 

URL from the slash in front of report_window.jsp. 

22. Return to the Custom Status View configuration. Select Call 

Queues and click Modify. 

23. Click Add to add the gauge report item. 

24. Paste the URL into the Frame URL field. The Name field is 

automatically populated. 



25. Enter 155 in the Width field and 120 in the Height field. The CSS 

Style field is automatically populated. 

26. Click OK. Click on report_window.jsp and use the arrows to 

move the item to the top of the list, then place the item in the 

bubble. 

27. Next we will add the Attribute Matrix View showing the status 

of the call queues. First we need to get the ID. 



28. Click OK. Click Close to exit the Custom Status View 


29. Display the Attribute Matrix View from the Status menu. Copy 

the ID portion of the URL. 

30. Return to the Custom Status View configuration. Click Add to 

add a new item. 

31. Select Frame in the Item Type field. Enter 

/Status_attr.jsp?id= and paste the ID that you just copied. 

The Name field is automatically populated. Enter 700 in the 

Width field and 100 in the Height field. The CSS Style field is 

automatically populated. 



32. Click OK. The item is displayed at the top of the canvas. 

33. Next we will add a title for the Custom Status View. Click Add. 

34. Select Text from the Item Type field. Enter font-size: 48px; 

font-family: garamond; font-style: italic in the CSS 

Style field. Enter Call Queues in the Text field. The Name field 

is automatically populated. 



35. Click OK. Select Call Queues from the list and move it to the 

appropriate location. 

36. Next we will add a monitor that displays the value of the 

Current Average Queue. Click Add. 

37. Enter a name for the monitor. Select the monitor. Click Show 

Metric Value. 

38. Click OK. Enter Current Average Queue in front of the variable 

in the Text field to add a label. 

39. Click Browse next to the URL of Good State Icon field. Select the 

moonlight_blank.gif file since we do not want to display a status 



icon. We only want to display the value. Repeat this step for the 

remaining three icons. 



40. Click OK. Select the item from the list and move it to the 

appropriate location. 

41. Next we will add a link to a Custom Status View of Europe that 

has already been created. First we need to get the URL. Click 

OK. Click Close to exit the Custom Status View configuration. 

42. Display the Custom Status View of Europe from the Status 

menu. Copy the URL from /Status-view.jsp to the end. 

43. Return to the Custom Status View configuration. Click Add to 

add the item. 



44. Select Text from the Item Type field. Enter Jump to Europe in the 

Name field. Copy the URL into the Drill Down URL field. Enter 

font-size:14px; font-style: italic; in the CSS Style 

field. Enter Europe >> in the Text field. 

45. Click OK. Select the item from the list and move it to the 

bottom right of the screen. 

46. Click OK. Click Close. You can now view the Custom Status 

Map. 



47. Select Custom Status Views from the Status menu and select 

Call Queues. 



Configuring Database Storage and 

Locations 

To configure database storage, click the Configure menu, then click 

Database. 

Use the Database Storage settings to specify the number of days to 

keep records in the OneSight database. 

Specifying When to Delete Database Records 

Use the settings on the Database Storage tab to specify when 

various records should be deleted from the OneSight database. 

Deleting records from the database affects the types of reports that 

you will be able run. 

Alerts – Select the number of days that data about monitored web 

component alerts should remain in the OneSight database. This 

795


includes alerts that have action plans associated with them as well 

as those that have no response configured. 

Action Plans (Resolved) – Select the number of days that data about 

resolved action plans should remain in the OneSight database. 

Historical Data Settings – The Historical Data settings refer to the 

types of data stored in the OneSight database for every item within 

every web component that OneSight measures or tests. 

Historical Data Detail – Type in the number of days that the 

OneSight database should store information about every 

measurement and alert that transpires for everything that OneSight 

is measuring. From a resource perspective, this is “expensive” 

information to store, so a lower number is best if you are concerned 

about capacity. 

Historical Data Hourly Summary – The OneSight database also 

stores, for every hour that OneSight is monitoring an item, a value 

that summarizes the measurements returned by that item. Select the 

number of days you want the OneSight database to store that type 

of information. 

Audit Data – Specifies the number of days of data to store for the 

Audit report. The Audit report provides an audit trail of OneSight 

configuration activity. Specify the number of days you want the 

OneSight database to store that type of information. 

Log Files – Specifies the number of days to keep log files. 

Auxiliary data – Specifies how long to store auxiliary data. This data 

includes the saved HTML source from successful Oracle Test for 

Web Applications Transaction monitor runs if the Save HTML from 

successful runs check box on the General tab of the Oracle Test for 

Web Applications Transaction monitor configuration is checked, 

the saved HTML source from failing Oracle Test for Web 

Applications Transaction monitor runs if the Save HTML from 

failing runs check box on the General tab of the Oracle Test for 



Web Applications Transaction monitor configuration is checked, 

the detail data from successful runs of VoiceWatch, and the detail 

data from failed runs of VoiceWatch. 

UC Data – Specifies how long to store unified communication data 

collected from monitors such as Avaya Call Manager, Cisco, 

Microsoft, etc. 

Enable Automatic Scheduled Database Backup – When selected, 

database backup occurs automatically based upon the defined 

schedule. 

These options let you specify the frequency of the automatic 

database backup. 

Begin at – Enter the time that you want to begin database backup in 

24-hour time in hh:mm format. 

every –Select how often you want to schedule a database backup. 

Hour on minute – select a minute of the hour for the hourly 

backup. 

Day – no additional detail is required. 

Week on day – select a day (Sunday through Saturday) for the 

weekly backup. 

Bi-Weekly on day – select a day for the bi-weekly backup. The 

schedule starts on the next selected day. For example, if you 

create the schedule on Monday and select Tuesday as the backup 

day, the backup schedule starts tomorrow. 

Every Month on day – select a day (1 through 31) for the monthly 

backup. 

Last day of month – no additional detail is required. 

Chapter 11: Configuring Database Storage and Locations 797

Configuring Locations 

OK – Click OK to save changes you have made to the above fields. 

Once you save your changes, you cannot return to OneSight’s 

default settings. 


The Locations tab displays a list of the Data Collectors and Remote 

Agents that have been installed. Once installed you can configure 

how the Data Collector or Remote Agent should respond when it 

disconnects or reconnects. The Location Group tab lets you 

organize locations into groups by creating a location group and 

selecting the locations to include in the group. 

Use the Configure Locations settings to specify the Location and 

Location Group options. 

Locations Tab – Use the settings on the Locations tab to specify 

how to respond when a Data Collector location disconnects or 

reconnects. 



Locations Group Tab – Use the settings on the Locations Group tab 

to add or remove location groups and specify which location(s) 

belong to which group(s). 

Locations – The list of remote Data Collector Locations. Data 

Collectors are a separately installable service that registers with the 

OneSight server to provide data collection services for specified 

agents. Data Collector locations can be identified by any userdefined 

name. 

Network – The network to which this location belongs. This field 

can be used when filtering reports. 

Region – The region to which this location belongs. This field can 

be used when filtering reports. 

When this Data Collector Location disconnects Respond by – Shows 

the action plan to use if the currently selected Data Collector 

Location disconnects. 

When this Data Collector Location reconnects Respond by – Shows 

the action plan to use if the currently selected Data Collector 

Location reconnects. 

Modify – Click Modify to change the selected locations’ responses. 

Remove – Click Remove to remove the selected location. 



Used By – Opens a dialog box that shows which data collectors(s) 

are connected to the location and which monitor groups and 

monitors are using the collector(s). 



Modifying Locations 

Specify the action plan to use if the selected Data Collector 

Location disconnects or reconnects. 

Name – Displays the name of the data collector. 

When this Data Collector Location disconnects Respond by – Select 

the action plan to use to respond to a Data Collector Location 

disconnecting. 

When this Data Collector Location reconnects Respond by – Select 

the action plan to use to respond to a Data Collector Location 

reconnecting. 

You can select one of the existing action plans or configure Action 

Plans to use to respond to Data Collectors disconnecting or 

reconnecting. 

Network this Data Collector Location belongs to – Enter or select the 

network to which this location belongs. This information can be 

used when filtering reports. 



Region this Data Collector Location belongs to – Enter or select the 

region to which this location belongs. This information can be used 

when filtering reports. 

Adding Location Groups 

To add Location Groups: 


2. Select Locations to open the Configure Locations page. 

3. Click the Location Groups tab. 

Location Groups – The list of Location Groups defined in 

OneSight. Location groups that are not being used by a user 

group will be shown as not in use. Use Add and Remove to 

customize the list. 

Add – Opens a dialog box for specifying a new location group 

name. 



Remove – Click Remove to remove the selected location group. 

Used by – Displays a list of user groups that are using this 

location. This button is not available if there are no user groups 

using this location. 

Locations – The list of remote Data Collector Locations. Select 

a location group name and then select Add to display a list of 

locations to select from. 

Add – Opens a dialog box for selecting a location to add to the 

group. 

Remove – Click Remove to remove the selected location from 

the group. 

4. Click Add. 

Location Group Name – Specify a name for the Location Group. 

5. Define a name for the group and click OK. 

6. Click Add to select a location to add to the group and click OK. 

Removing Location Groups 

To remove location groups: 


2. Select Locations to open the Configure Locations page. 



3. Click the Location Groups tab. 

4. Select the location group you want to remove. 


6. Click Yes to confirm the removal. 




Configuring Users 

Configuring Roles 

A user must log in and be authenticated to use the OneSight 

Console. Each user is assigned to a user group and within that user 

group, is assigned a role. A user group is a hierarchical structure 

representing the user’s organization. The user group determines 

which objects, such as monitors, profiles, etc., that the users in the 

user group can access. For example, engineering will have different 

access requirements than marketing. 

The user’s role determines individual permissions, such as view 

access, reporting access, and configuration access to the objects 

available to the user group. For example, an administrator will have 

different access requirements than an operator. 

In addition, individual objects (such as profiles, monitors, etc.) can 

control which user groups have read, write, and delete access to 

them. This is done using the Access Control tab for that object. 

The user’s role determines individual permissions, such as view 

access, reporting access, and configuration access to the objects 

available to the user group. OneSight comes with four default roles: 

Administrator, Analyst, Business, and Operator. These roles cannot 

be modified or deleted. Use the Role editor to add, clone, modify, 

and remove roles. 

To add roles: 


805


2. Select Roles to display the Roles dialog box. 


Add – Displays the Role Editor for adding a new role. 

Clone – Copies the selected role making it easy to create similar 

roles. Click Modify to edit the new role. 

View – Displays the Role Editor for viewing the selected user’s 

settings. 

Modify – Displays the Role Editor for modifying the selected 

role. 

Remove – Deletes the selected role. Roles that are in use cannot 

be deleted. 

Used by – Displays a dialog box that lists the users that have 

been assigned to the selected role. 

Name – Lists all of the configured roles. 



3. Click Add to display the Role Editor. 

4. Enter a name for the role. 

5. Assign permissions by selecting a tab and selecting or 

deselecting privileges. 

6. Click OK. 

Chapter 12: Configuring Users 807


Configuration Rights Tab 

The Configuration Rights tab lets you assign permissions to 

configuration tasks. 

Note: It is possible for users with permission to configure roles to 

either assign their own role all permissions or no permissions, 

potentially giving themselves more permissions than necessary or 

locking themselves out of all configuration tasks. 

View Configuration – Select this check box to access the 

configuration permissions. 

Configure User Groups – Lets the user configure user groups. 

Configure Users – Lets the user configure users. This options is only 

available for Administrator users. 

Change User Password – Lets the user change user passwords in the 

User Editor. 



Configure Roles – Lets the user configure roles. 

Configure Monitors – Lets the user configure monitors. 

Configure Monitor Groups – Lets the user configure monitor groups. 

Configure Profiles – Lets the user configure profiles. 

Configure Metrics – Lets the user configure metrics. 

Configure Systems – Lets the user configure systems. 

Configure Attributes – Lets the user configure attributes. 

Configure Support Page – Lets the user configure the support page. 

Configure SLAs – Lets the user configure service level agreements. 

Configure Actions – Lets the user configure actions. 

Configure System Passwords – Lets the user configure system 

passwords. 

Configure Proxy Settings – Lets the user configure proxy settings for 

monitors. 

Schedule Downtimes – Lets the user schedule downtimes. 

Configure Alert Message Templates – Lets the user configure alert 

message templates. 

Configure Action Plans – Lets the user configure action plans. 

Configure Time Intervals – Lets the user configure time intervals. 

Configure Database Options – Lets the user configure database 

storage options. 

Configure Location – Lets the user configure locations. 



Alerts Rights 

Use Server Utilities – Lets the user access the Trace Route, Regex, 

and MIB Browser utilities. 

View Support Page – Lets the user view the support page. 

Configure Views – Lets the user configure attribute matrix views and 

custom status views. 

Note: Only users in the default user group can access the support 

page, alert templates, location configuration, and database storage 

options. 

The Alerts Rights tab lets you set alert privileges. 

View Alerts – Select this check box to access alert rights. 

Retire Alerts – Lets the user retire alerts. 



Reporting Rights 

The Reporting Rights tab lets you set report permissions. 

View Reports – Select this check box to access reporting 

permissions. 

View SLA Reports – Lets the user view service level agreement 

reports. 

Email Reports – Lets the user email reports. 

Save Reports – Lets the user save reports. 

Schedule Reports – Lets the user schedule reports if Save Reports is 

selected. 



Status Rights 

The Status Rights tab lets you set status permissions. 

Request updated sample value – Lets the user request an updated 

sample value from the Smartlink icon menu on the Status and User 

Experience pages. 

View Status Page – Lets the user view the monitor status page. 

View User Experience Page – Lets the user view the user experience 

page. 

View Attribute Matrix Page – Lets the user view the attribute matrix 

page. 

View Custom Status Page – Lets the user view the custom status 

page. 

View UC Voice Quality Page – Lets the user view the UC Voice 

Quality page. 



Access Control 

Use this tab to configure which user groups have access to this 

object. 

Deleting Roles 


Owner – The user group for this role. A role can be directly owned 

by a single user group. 


user groups. 




The default roles and roles that are in use cannot be deleted. To 

delete a role: 


2. Select Roles 


Configuring User Groups 

3. Select the role you want to delete. 



A user group is a logical grouping of users that own monitor 

groups. All objects that are needed to create a monitor group 

(monitors, system, profiles, etc) can be created for a user group and 

these objects will be accessible only to users that are members of 

the user group (and any super user). 

User groups can be hierarchical to match the structure of your 

organization. 

Each user may belong to only one user group and every object in 

the system that is owned by a user group may not be seen or used by 

any other user group’s users. 

There is a special user group, called Default, that serves as a place 

where global objects such as profiles, metrics, and attributes can 

reside. Global objects can be used and viewed by all other user 

groups. 

To add User Groups: 




2. Click Groups to open the User Groups page. 

Use the Configure User Groups options to add, modify, and 

remove user groups in the OneSight configuration. 

User Groups – Lists the currently defined user groups in the 

OneSight configuration. Select the check box to enable the User 

Group in the OneSight configuration. Clear the check box to 

disable the User Group in the configuration. If a user group is 

disabled then login for all users belonging to that user group 

will be disabled (except for super users which may always 

login) and all monitors and monitor groups within that user 

group will not sample. 

Add – Opens the User Group Editor for specifying the License 

and Location Group information for a new User Group. 

Modify – Opens the User Group Editor for modifying the 

License and Location Group information for an existing User 

Group. 

Remove – Deletes the currently selected User Group from the 

OneSight configuration. If a user group is deleted, then all 

users, monitors, monitor groups, systems, profiles, attributes 



and other objects owned by that user group will be deleted. 

Super users may delete users groups. 

3. Click Add. 

Use the Licenses tab to allocate specific licenses to User 

Groups in the OneSight configuration. 

Name – Enter the user group name. 

E-mail – Enter the e-mail address of the primary contact for this 

user group. 

Parent User Group – Select the user group to which this user 

group belongs. 

Do not restrict licenses – When selected, User Group has access 

to all available licenses. The License Type, Avail/In Use, and 

Allocation options are dimmed. When cleared, you can allocate a 

specific number of each type of license to the User Group. The 



Avail/In Use column shows the number of available licenses and 

the number currently in use. Specify the number of each type of 

license to allocate to the User Group in the Allocation column. 

Refer to How OneSight Determines the License Type in 

Chapter 2 for information on determining which licenses to use. 

License Type – Lists each type of OneSight license. 

Avail/In Use – Shows the number of available OneSight licenses 

and the number currently in use. 

Allocation – Specifies the number of each type of license to 

allocate to the User Group. The Do not restrict licenses check 

box must be cleared to allocate a specific number of licenses to 

the User Group. 

Note: If you have monitors that are in a disabled state because 

there are not enough licenses, and you increase the number of 

licenses, the disabled monitors are not automatically enabled. 

You must enable the individual monitors by deselecting and 

selecting the Enable button for the monitors you want to enable 

on the Status Detail page. Checking and unchecking the Enable 

button for the monitor group will have no effect. Check and 

uncheck the Enable button at the monitor level. 

4. Enter a User Group Name. 

5. Specify the email address for the User Group. 

6. Select the parent user group to which this user group belongs. 

7. To allocate licenses for the User Group, clear the Do not restrict 

licenses check box, and then specify the number of each type of 

license to allocate to the User Group in the Allocation column. 

Note: If you have monitors that are in a disabled state because 

there are not enough licenses, and you increase the number of 

licenses, the disabled monitors are not automatically enabled. 

You must enable the individual monitors by deselecting and 



selecting the Enable button for the monitors you want to enable 

on the Status Detail page. Checking and unchecking the Enable 

button for the monitor group will have no effect. Check and 

uncheck the Enable button at the monitor level. 

8. To provide unrestricted licenses for the User Group, select the 

Do not restrict licenses check box. 

9. To specify locations associated with the User Group, click the 

Location Group tab. 

Use the Location Groups tab to associate a User group with a 

specific Location Group in the OneSight configuration. 

Location Group – Provides a list of the currently available 

Location Groups. Select a Location Group to associate with the 

User Group or add a new Location Group. 

10. Select the Location Group to associate with the user group. 

Removing User Groups 

To remove User Groups: 


2. Select Groups to open the User Groups page. 


Adding New Users 

3. Select the User Group Name to remove. 


5. Click Yes to confirm. 


The User Editor allows you to add new users or change the name, 

password, or privilege level of existing users. 

The Configure Users page lists all of the users that are currently 

allowed access to the OneSight Console. This is where you specify 

who can log on and what level of access each user has. You can add 

new users, modify the name, password, default view, or access level 

of any selected user, and remove an existing user. 

Use these options to manage access to Empirix OneSight: 

Check Box – The check box adjacent to each user controls whether 

or not the user is enabled. When selected, the user is enabled. When 

cleared, the user is disabled. Disabled users cannot log in to 




Locked out users are unchecked and have the locked out icon beside 

the check box. 

Name – Shows a list of all identified OneSight users. A check in the 

first column indicates that the user is enabled. 

To modify the name or access rights of an existing user, select 

the user name in the list and click Modify. 

To delete a user from the list, select the user name in the list and 

click Remove. 

User Group – shows the user group to which the user belongs. 

Add – To set up a new OneSight user, click Add to open the User 

Editor. After entering information to specify the user’s password 

and how the user may interact with the OneSight Console, click OK 

to save the user information and return to the Configure Users page. 

Modify – To change the name, password, default view, or access 

rights of an existing user, double-click the user name in the list. Or, 

select the user name in the list and click Modify. In the User Editor, 

make the desired changes and click OK to update the user 

information and return to the Configure Users page. 

Remove – To remove a user from the list and prevent access to the 

OneSight Console, select the user name in the list and click 

Remove. 

Global Options – Displays the User Global Options dialog box for 

configuring when passwords expire, how many times the user can 

try to log in before being locked out, and what characters the 

password must contain. 


Modifying User Settings 


A user must log in and be authenticated to use the OneSight 

Console, and there are different privilege levels for users. The User 

Editor allows you to add new users or change the name, password, 

or privilege level of existing users. 

Use these options to configure a OneSight user definition: 

Do not reenable this user after timeout – This option is only 

displayed when the user has been disabled based on security 

constraints. For example, when the user has failed to log in for the 

number of retries set in User Global Options. When selected, the 

user is disabled and cannot log in to OneSight until this check box 

is cleared by the Administrator 

User Name – Type the name that the user must provide to log in to 

the Empirix OneSight Console. This value is not case sensitive. 

Password – Type a string that the user must provide to log in to the 

Console. This value is case sensitive. 



Confirm Password – Retype the password you entered in the 

Password box. This value is case sensitive. 

Force password change on next login – Forces the user to change 

his/her password at the next login. This field is only displayed when 

the password has been set to expire on the User Global Options 

dialog box. 

E-mail – Enter the user’s email address. 

Time Zone – Select the user’s time zone. 

User group – Select the user group to which this user belongs. 

Role – Select the user’s role. The role determines the user’s access 

privileges. 

Status Grouping – Select the status grouping that OneSight will use 

to display monitors on the Status page. 

Start Page – Select the view that you want displayed when you log 

in to OneSight. 

Overview – Displays the Overview page. 

Default Status – Displays the General Status page. 

User Experience – Displays the User Experience page. 

Service Level Agreement – Displays the SLA Status page. 

Attribute Matrix View –Displays the selected Attribute Matrix 

View. 

Custom Status View –Displays the selected Custom Status View. 

Alerts – Displays the Alerts page. 

Reports – Displays the selected dashboard report. 



Editing User Rights 

Configuration – Displays the Configuration page. 

Attribute Matrix – Select the Attribute Matrix View that you want 

displayed when the Attribute Matrix View is the selected view. 

Custom Status – Select the Custom Status View that you want 

displayed when the Custom Status View is the selected view. 

Dashboard – Select the Dashboard report you want displayed when 

the Reports page is the selected view. 

You can configure the rights that each user has by clicking the 

Rights tab. 

Note: You cannot configure your own rights. 

Change password in My Settings – If checked, the user can change 

his/her password. If not checked, the user can only change his/her 

email address and time zone. 

Allow Windows Login – When selected, allows the user to use 

windows login for OneSight authentication. 


Configuring Global Options 


Use the User Global Options dialog box for configuring when 

passwords expire, how many times the user can try to log in before 

being locked out, and what characters the password must contain. 

Password Expiration Policy – Use these settings to configure when 

passwords will expire. 

Expires after days– Enter the number of days after which the 

user will have to enter a new password. When this field is 

selected, the Force password change on next login is displayed in 

the User Editor. 

Never expires – When selected, passwords will not expire. 



Expires after the user has not logged in for days – This option 

is available when Expire after user reset the password for is 

selected. Enter the number of days after which the user account 

will expire if the user has not logged in during this time. 

Logout user when idle for minutes – Enter the number of 

minutes after which the user will be logged out if no action has 

been taken in OneSight. 

Password Lockout Policy – Use these options to configure the 

number of attempts users will have to log in and how long they will 

be locked out if they fail to login. 

Disable accounts after unsuccessful login attempts – 

Enter the number of attempts the user will have to log in. 

Disable account for hours – Enter the number of hours 

to lock out users after an unsuccessful attempt to log in. 

Disable account until administrator reset – When selected, users 

are locked out until the administrator resets the password. 

Password Content Policy – Use these options to configure the 

characters that must be included in the password. 

Passwords must contain alpha characters (a-z) – When selected, 

passwords must contain alphabetic characters. 

Passwords must contain number characters (0-9) – When selected, 

passwords must contain numeric characters. 

Passwords must contain upper and lower case alpha characters (az 

and A-Z) – When selected, passwords must contain both upper 

and lower case alphabetic characters. 

Passwords must contain special characters (~!@#$%^&*()+-,.) – 

When selected, passwords must contain special characters. 



Passwords must be different from former times –When 

selected, the password must be different from the previous 

number of passwords. 

Passwords must contain at least characters – When 

selected, passwords must contain the indicated number of total 

characters. 

Passwords must match regular expression – When selected, 

passwords must match the indicated regular expression. The 

regular expression can be used to design a custom password 

requirement that forces any combination of characters in any 

particular order and pattern, to keep a password to a minimum or 

maximum length, or to fit a particular style or format. 



Configuring Service Level 

Agreements 

The Service Level Manager (SLM) handles the continuous process 

of managing, measuring, reporting, and improving the quality of 

services provided by IT and service providers. This module is 

licensed separately and the options associated with it are only 

displayed if a license has been purchased. 

Service Level Agreements (SLA) describe the expected level of 

service and what happens when the levels or targets are not met. 

Targets define the expected level of service or threshold in a 

Service Level Objective. Service Level Objectives (SLO) are the 

specific targets of performance or availability for monitored 

elements. For example, the transaction response time cannot exceed 

ten seconds. An SLA is comprised of multiple SLOs. 

SLOs can only be created for monitors that collect quantifiable 

performance data for metrics other than availability metrics. 

An SLA belongs to a user group and can be configured by 

administrators or super users. Administrators can configure SLAs in 

their own user group. Super users can configure SLAs in any user 

group. 

SLOs can be measured during time intervals defined by you. The 

time interval defines the hours of operation that a service is in 

effect. They can be monitored on availability or by component 

dependent metrics such as response time or CPU usage. 

827

Creating SLAs 

When configuring the SLA you can set up a schedule for receiving 

notification of any SLOs in the SLA that are below a specified 

warning level. The warning level is a “target” that allows you to 

proactively respond before service levels are missed. An email 

containing a report is sent if at least one SLO is in a warning state. 

This report can also be viewed from the reports menu. It is the third 

view of the SLA. 

SLA status can be viewed by selecting SLA Status on the Console 

main menu. Reports can be viewed by selecting the Reports tab. 

The ongoing process of service level management includes the 

following steps: 

Benchmarking – The process of measuring and understanding 

what you are already providing. Prior to setting targets for your 

Service Level Objective you should understand the level of 

performance that you are currently delivering. You should 

understand how each transaction or monitored element has 

performed historically because for example, you would not want 

to commit to a five second SLO for response time when the 

transaction has never performed under seven seconds. 

The things that you benchmark depend on your services and 

requirements. For example, you may benchmark the response 

time perceived by users, the accuracy of content and data, the 

ability to complete end-user transactions, or operational 

efficiency such as mean time to repair or mean time between 

failures. 

Defining – The process of defining Service Level Agreements and 

setting realistic Service Level Objectives. Each end-user service 

can be managed separately based on the business needs. Targets 

and warning thresholds should be based on the benchmark 

results. 

In addition, the objectives can be managed according to business 


Creating SLAs 

Creating SLAs 

operations by defining time intervals. For example, some 

requirements may only need monitoring during peak hours. 

Managing – The process of measuring and managing from the 

end-user perspective. OneSight provides real-time alerting so that 

you can be proactive when service levels are in jeopardy, that is, 

when they reach the defined warning level. In addition, OneSight 

provides real-time and historical reports for availability and 

performance. 

You can also use the SLA status page to immediately understand 

which SLAs are in violation and to prioritize response activities 

for restoring impacted services. 

Improving – The process of continuously understanding where 

and what improvements can be made. 

The overall tasks for configuring an SLA are as follows: 

1. Configure time intervals. Time intervals are used when creating 

SLOs to indicate the time period for which the objective applies. 

Refer to Chapter 14. 

2. Create the SLA. 

3. Create the SLOs. 

To create an SLA: 


Chapter 13: Configuring Service Level Agreements 829

Creating SLAs 

2. Click Service Level Agreements to open the Configuring Service 

Level Agreements page. 


Service Level Agreements – lists existing SLAs. 

Add – displays the New Service Level Agreement dialog box 

for adding a new SLA. 

Modify – displays the Update Service Level Agreement dialog 

box for modifying the selected SLA. 

Remove – deletes the selected SLA. 

Service Level Objectives – displays the existing SLOs for the 

selected SLA. 

Add – displays the New Service Level Objective dialog box 

for adding a new SLO. 


Creating SLAs 

Modify – displays the Update Service Level Objective dialog 

box for changing the selected SLO. 

Remove – deletes the selected SLO. 

3. Click Add under the Service Level Agreements section. 


General Tab 

Name – enter the name of the SLA. 

Description – enter a description of the SLA. 

Automatic warning schedule – sends an email at the configured 

time if an SLO in the SLA is in a warning state. The email 

contains the Service Level Warning report that can also be 

viewed from the Reports menu. 

Begin at – select the time at which to begin. 


Creating SLAs 

Note: When using Repeat every hour on minute, this field is 

ignored. The value in the on minute field is used as the Begin at 

time. 

Do once on Date – sends email on the selected date. 

Repeat every – select the interval for sending the email. The 

options are: 

Hour on minute – sends email every hour on the selected 

minute. 

Day – sends email once a day at the selected time. 

Week on day – sends email once a week on the selected day 

and time. 

Month on day – sends email once a month on the selected date 

and time. 

To – enter the email addresses to send the report to separated by 

a comma or space. 



read, write, or delete this SLA. 

Owner – The user group for this SLA. an SLA can be directly 








Creating SLOs 


4. Enter the name and description of the SLA. 

5. Select the notification information. 

6. Click OK. 

Creating SLOs 

An SLO can be based on either availability or performance. For 

each, you can specify a target percentage and a warning percentage. 

The target percentage is either the percentage of time that the metric 

must be available or must be performing at the specified level. The 

warning level is the percentage below which you want to be notified 

so that you can do something before the percentage goes below the 

target causing you to pay a penalty to your customers. For example, 

if your target is 95% and the warning level is 97% and the SLO 

goes to 96%, you will get a notification. The warning level should 

be higher than the target and both percentages must be less than 

100%. OneSight supports targets up to 99.999%. 

You can also select how to aggregate the data. This affects 

reporting. For example, if you have a performance objective with a 

threshold of less than 3 seconds, a target of 99%, and daily 

aggregation, this means that you want 99% of the samples to be 

under 3 seconds. For reporting purposes, OneSight counts the 

number of samples under three seconds for the day because 

aggregation is daily. If the number of failures divided by the 

number of samples is less than 99%, the SLO fails for the day. 

For reporting, the compounding period is the report period. For 

example, monthly or weekly. The average is never reset. 

For an availability objective, the samples are computed, not the 

time. This means that if you increase the sampling rate on the 

fifteenth of the month and get better results for the last half of the 


Creating SLOs 

month, the SLO will be better than if a time-based calculation had 

been used. 

To create an SLO: 


2. Click Service Level Agreements to open the Configure Service 


3. Select the SLA for which you want to create an SLO. 


Creating SLOs 

4. Click Add in the Service Level objectives section. 


Service Level Agreement – lists the SLAs to which you have 

access. 

Monitor Group – select the monitor group containing the 

monitor that is required for this SLO. 

Monitor – select the monitor or monitors. Monitors can be used 

in more than one SLO. 

Note: Some monitors can be configured only for availability. 

These are monitors for which a location cannot be specified and 

monitors that monitor availability instead of performance. For 

example, SNMP Trap, Service, etc. 

Location – select the location of the monitor. This field is 

displayed only if more than one location is defined. 


Creating SLOs 

Include page level targets – for transaction type monitors lets 

you select steps for use in an SLO. Each step in a transaction 

can be an SLO; however, only those you select will be used. 

Note: If you are interested in only one step in a transaction, it is 

recommended than you use a URL monitor. 

Compound availability – lets you combine metrics to determine 

if the objective is being met. For example, you may have three 

ping monitors and the objective is that the average availability 

should not be less than 95%. 

5. Click Next. If you selected Compound availability the next dialog 

box is displayed. If you did not select this option, go to the next 

dialog box. 


Metrics/Components – Lists the monitors that you selected on 

the New Service Level Objective dialog box. 

Name – enter the name of the SLO. 

Compounding – select the type of compounding. 


Creating SLOs 

Average – averages the results of the selected metrics. For 

example, if you have three ping monitors and the first is 

available 100% of the time, the second 95% of the time, and 

the third is 90% of the time, the average is 95%. 

Minimum – takes the lowest value of all of the monitors in the 

group. In the above example, the minimum availability is 

90%. 

Add – adds the SLO. 

Remove – deletes the selected SLO. 

6. Select the metrics to use in the SLO. 

7. Enter a name, select the type of compounding, and click Create 

SLOs. 

This dialog box lets you set up availability and metric 

performance SLOs for individual monitors. You can set up one 

or both of these SLOs . Each SLO will be displayed separately in 

the Configure Service Level Agreements dialog box. They will 

be labeled as Avail or Metric Perf. 


Name – the name of the SLO. 


Creating SLOs 

Availability – lets you configure an availability SLO. For 

example, the target may be that the monitor must be available 

95% of the time. 

Time Interval – select the time interval during which the target 

must be met. These intervals are configured by selecting Time 

Intervals from the Configure menu. 

Target – enter the percentage of time that the monitor must be 

available, up to 99.999%. 

Send Availability Warning – lets you configure when the monitor 

is considered to be in a warning state. If you set up a schedule 

when you created the SLA, this configuration determines when 

an email is sent. 

Aggregation – select how to aggregate the results, daily, 

weekly, monthly, or user-configured date interval. 

Warning Level – enter the percentage at which the monitor is 

considered to be in a warning state. This percentage must be 

higher than the target percentage. When the SLO goes below 

this percentage, a notification is sent. 

Grace Period – enter the length of time, in minutes, to wait 

before considering availability to be a problem. For example, if 

you enter fifteen minutes, the sample failure must occur for 

fifteen minutes before being considered a problem. The 

availability report will ignore the failure samples within this 

outage. 

Metric Performance – lets you configure a metric performance 

SLO. For example, 95% of the samples should be less than 5 

seconds. 

Time Interval – select the time interval during which the target 

must be met. These intervals are configured by selecting Time 

Intervals from the Configure menu. 


Creating SLOs 

Target – enter the percentage of time that the monitor must 

meet the threshold, up to 99.999%. 

Threshold – select the type of threshold and enter the amount. 

In the above example, you would select less than and enter 5. 

Send Metric Perf. Warning – lets you configure when the monitor 

is considered to be in the warning state. If you set up a schedule 

when you created the SLA, this configuration determines when 

an email is sent. 

Aggregation – select how to aggregate the results, daily, 

weekly, or monthly. 

Warming Level – enter the percentage at which the monitor is 

considered to be in a warning state. This percentage must be 

higher than the target percentage. When the SLO goes below 

this percentage, a notification is sent. 

If you have any compound SLOs they are listed at the bottom of 

the dialog box. 

8. Enter the SLOs. 

9. Click Finish. 


Updating SLAs 

Updating SLAs 

To change an SLA: 





Updating SLAs 

3. Select the SLA that you want to update and click Modify. 

Deleting SLAs 

4. Make changes and click OK. 

When you delete a Service Level Agreement all of its associated 

Service Level Objectives are also deleted. To delete a Service Level 

Agreement: 




3. Select the SLA that you want to delete and click Remove. 

4. Click OK. 


Updating SLOs 

Updating SLOs 

To change an SLO: 




3. Select the SLO that you want to update and click Modify. 

This dialog box has the following options. 

Name – the name of the SLO. 


Updating SLOs 

Service Level Indicator – indicates the type of indicator, average 

availability, availability, or metric performance. 

Service Level Agreement – indicates the name of the SLA. 

Time Interval – the time interval that is being monitored. These 

intervals are configured by selecting Time Intervals from the 

Configure menu. 

Threshold – the threshold of the SLO. 

Target – the target percentage. 

Set Warning – enables the warning level fields. 

Warning Level – enter the percentage at which the SLO is 

considered to be in a warning state. 

Warning Aggregate – select how to aggregate the results, daily, 

weekly, monthly, or user-configured date interval. 

Set Grace Period – check this box if you want to specify a grace 

period for this SLO. 

Grace Period – enter the length of time, in minutes, to wait 

before considering availability to be a problem. For example, if 

you enter fifteen minutes, the sample failure must occur for 

fifteen minutes before being considered a problem. The 

availability report will ignore the failure samples within this 

outage. 

Modify Composition – displays the SLO screen for selecting the 

monitors to include. This button is only displayed when the 

indicator type is compound availability. 

4. Make changes and click OK. 


Configuring Date Intervals 

Deleting SLOs 

To delete a Service Level Objective: 




3. Select the SLA containing the SLO that you want to delete 

4. Select the SLO that you want to delete and click Remove. 

5. Click OK. 


You can configure a date interval that can be used for the warning 

aggregate period or for the SLA Status display. Date Intervals will 

be listed for selection in the following fields: 

Adding Date Intervals 

Aggregation field on the Create Service Level Objectives dialog 

box 

Warning Aggregate field in the Update Service Level Objectives 

dialog box 

Time Interval field on the SLA Status page 

To add a date interval: 




2. Click Date Intervals under Service Level Agreements. 

Add – Displays the Date Interval Editor for adding a new date 

interval. 

Clone – Makes a copy of the selected Date Interval. 

Modify – – Displays the Date Interval Editor for modifying the 

selected date interval. 

Remove – Deletes the selected date interval. 

Used By – Displays a list of SLOs that are using this date 

interval. 

Name – Displays the name of the date interval. 

User Group – Displays the user group to which the date interval 

belongs. 



3. Click Add. 

Date Interval Name – Enter a name for the date interval. 

Server Time Zone – Displays the server’s time zone. 

User Time Zone – Displays the user’s time zone. 

General Tab 

Select the type of date interval: 

Days – Select the number of days in this time interval, up to six 

days. 

Weeks – Select the number of weeks in this time interval, up to 

four weeks. 

Months – Select the number of months in this time interval, up 

to twelve months. 



read, write, or delete this date interval. 




Owner – The user group for this date interval. A date interval 

can be directly owned by a user group. 






4. Enter a name for the date interval. 

5. Select the interval in days, weeks, or months. 

6. Click OK. 

Modifying Date Intervals 

To modify a date interval: 



3. Select the Date Interval you want to modify and click Modify. 

4. Make any changes. 

5. Click OK. 

Deleting Date Intervals 

Date Intervals that are being used cannot be deleted. Click Used by 

to display a list of SLOs that are using the selected date interval. To 

delete a date interval: 





3. Select the date interval you want to delete and click Remove. 

4. Click OK when asked to confirm the deletion. 



Configuring Custom Reports 

Report templates allow you to easily extend OneSight reporting to 

include your own customized reports. The features include: 

Ease of use – It is very simple to add a report to OneSight 

without knowledge of OneSight reporting or the Corda PopChart 

rendering engine. 

Flexible data acquisition – You can report on OneSight data or 

any available SQL database. In addition, report templates will 

accept properly formatted CSV, XML, or HTML files as input. 

Flexible rendering options – Any report can be displayed either as 

a chart (line, bar, pie, stacked bar, etc), or as an HTML table. 

Gauge “dials” are also supported. 

Extensibility – You can post-process SQL data prior to rendering, 

allowing more advanced data manipulation that might be difficult 

within the SQL query. This is done by implementing a simple 

java interface. 

PDF support – In addition to Flash output, any chart can be 

generated as a PDF. 

Creating Reports Using Report Templates 

To create a report using OneSight report templates you need to add 

your report to the report templates properties file. After editing, it is 

not necessary to restart OneSight; any changes to the properties file 

will be recognized. 

849

Running a Report Templates Report 

Running a Report Templates Report 

After you have setup a report by editing the OneSight Report 

Templates properties file, you can decide how you would like users 

to access and view the report. The options include: 

Invoke the report URL manually in the browser. OneSight 

provides the reportTemplate.jsp file that loads a report by ID. You 

can invoke the report by manually entering the URL. For 

example, http://localhost:8080/reportTemplate.jsp?id=Report4 would 

load the report “Report4”. 

Include the report as a menu item on the main reports page. If you 

set the visible property to true in the Report Templates 

properties file, the report will show up as a link in the Report 

Templates Section under the Saved Reports section. The menu 

item name is based on the .title property. Note that these 

reports are global and will show up for all users. 

Include the report in a saved view. Any URL can be displayed on 

the reports page and therefore it can be included in a saved report 

layout. This gives you more control over the visibility of the 

report and allows you to integrate the report with other related 

reports. 

Include the report as a SmartLink (e.g., 

reportTemplate.jsp?id=Report1) 

Custom. You could create a customized page that includes an 

invocation of the report within a frame of that page. 


Report Templates Properties File 

OneSight Report Templates Example Report 


You define a report by editing the report templates properties file. 

The file is called reportTemplates_en.properties, and resides in the 

OneSight properties directory (OneSight\properties). This file 

contains a list of all custom reports. Each custom report entry 

includes the following parameters. Refer to the example file at the 

end of this chapter for a more comprehensive list: 

.title – This is the report title that is displayed in the report. It is 

also the menu item name if the .visible property is set to true. 

.visible – Indicates whether to include the report in the list of 

custom reports shown on the main reporting page. 

.datasourceName – The report‟s data source. Supported data 

sources include: sql, csv, html, xml. 

datasourceValue. – The parameters required for the data source. 

These are datasource specific. 

Chapter 14: Configuring Custom Reports 851


.template – The appearance type, which corresponds to a 

PopChart appearance file. Default appearance files for common 

types (bar, line) are provided within OneSight, or you can use a 

custom appearance file. This requires assistance from the 

OneSight Services Team or a Corda builder license. 

.outputType – The output type. Valid output types include FLASH 

(the default), PDF, and TABLE (an HTML table). 

Editing the Report Templates Properties File 

The reportTemplates_en.properties file can be edited manually within 

the OneSight properties directory, or it can be edited within the 

OneSight console using the 

http://hostname:8080/support/ReportTemplateEdit.jsp file. When you 

invoke http://hostname:8080/support/ReportTemplateEdit.jsp, it loads in 

the properties file. After you make the necessary edits, click the 

Save button. Saved changes are effective immediately. 

About Custom Report Data Sources 

A report data source can be an SQL query, a CSV or XML file, or an 

HTML table within an html page. Corda makes it very easy to 

import data from csv, html, and xml files. The files must follow the 

prototypical table format. Examples are provided within the 

PopChart\chart_root\reportTemplates\data subdirectory. In this 

scenario, you need to update the file using an external means such 

as a scheduled OneSight action). 

For an SQL query, you also need to provide the connection 

parameters. The samples in the report templates include a report 

that connects to the OneSight database and reads alerts. Any 

accessible DB cab be used. In fact, the SQL datasource is database 

agnostic, so you need to be aware of security issues surrounding 

custom reports. 


Creating a Gauge Report 

Passing Arguments to a SQL Query 

If you are using an SQL query, you can pass any number of 

arguments to the query. This is a two-step process. 

1. When specifying the query in the OneSight report templates 

properties file, include a „?‟ character where the argument 

substitutions will occur. For example: 

Report5.sql=SELECT PropName, AgentPropertySeq FROM 

EmpirixAdmin.tbl_AgentProperty WHERE 

(AgentPropertyListID = ?) 

2. When invoking the report, specify the appropriate number of 

„arg‟ parameters in the URL that will map to the „?‟. For 

example: 

id=MyReport&arg=16&arg=18, would substitute 16 and 

18 for two ? within the query. 

Creating a Gauge Report 

OneSight report templates support gauge reports. Gauges are unique 

in that you specify a single value to graph, such as a tachometer as 

shown below. 

To specify a gauge report, you must first specify the 

.datasourceName as SQL. Only SQL results can be represented in a 

gauge (this is a Corda limitation). You then specify a 


Post-Processing of SQL results using Java 

.datasourceValue of “gauge”. Finally, you specify the ranges in 

the gauge, and their respective colors. For example: 

GaugeExample.datasourceName=sql 

GaugeExample.datasourceValue=gauge 

GaugeExample.gaugeRanges=Normal,00b200,0,750;Warn 

ing,b2b200,750,900;Critical,b20000,900,1000 


When the datasourceName property value is SQL, the OneSight 

report templates renders the query results verbatim. The 

datasourceValue property can optionally specify a java class file 

to load to process the results data and subsequently return your 

modified data. This is useful when the SQL query would not 

otherwise be able to perform the data processing your report 

requires. 

The java class file is an interface implementation of the 

IReportTemplate interface. This interface is trivial, and it‟s 

complete definition follows: 

package com.wrq.wam.reports.reportTemplates; 

// report template classes must implement this 

interface 

public interface IReportTemplate 

{ 

} 

public String processResults(String xmlStr); 

As you can see, you only need to implement a single method, 

processResults, which takes a string and returns a string. The data 

is a string containing an XML representation of the query result 

data. For example: 



package reportTemplateExamples; 

import 

com.wrq.wam.reports.reportTemplates.IReportTemplate; 

/* Add the following to reportTemplate_en.properties 

to provide. 

..datasourceValue=reportTemplateExamples 

.ReportTemplateExample 

*/ 

public class ReportTemplateExample implements 

IReportTemplate 

{ 

public ReportTemplateExample() 

{ 

} 

} 

public String processResults(String xmlStr) 

{ 

} 

return xmlStr.replace('L', 'Z'); 

This implementation replaces any “L” characters with “Z‟ 

characters. A more typical use case would be actual processing of 

the XML input, and mathematical manipulation of the results data. 

Alternately, your java program could defer to an XLST process. 


Implementation Notes/Caveats 

To build the class file, you need to temporarily copy the OneSight 

jar to your build directory and invoke the javac compiler: For 

example: 

"c:\ jdk1.5.0_06\bin\javac.exe" -cp onesight.jar 

ReportTemplateExample.java 

Implementation Notes/Caveats 

Because this feature is not within the OneSight framework and is 

loosely coupled with the existing OneSight reporting, the 

following advanced features are not available: 

OneSight filtering. You can customize the jsp to provide 

your own filtering mechanism if you need to. In addition, 

filtering exists outside of OneSight, since OneSight‟s data 

structures (UserGroups, etc) are only available by directly 

querying the OneSight database. 

Reporting Drill-down. 

No time slider. 

The difficulties inherent in querying data from the OneSight 

database, particularly time series data, has not been addressed. 

Since OneSight can provide CSV data for many of its reports, and 

since this feature allows for CSV as a data source, one way to 

report on prefiltered OneSight data is to use the OneSight CSV 

reports as input into a report templates report. An example of this 

is provided in the sample properties file that shows OneSight 

alert distribution within a pie chart. 

The appearance files and sample data files are located in the 

OneSight popchart\chart_root\reportTemplates subdirectory. 


Report Templates Configuration File 


Edit the reportTemplates_en.properties file to add a report. It must 

exist in the properties directory. For example: 

# -------------------------------------- 

# 

# This is the Report Templates Configuration file. 

# Individual Reports are added within this file. 

# 

# -------------------------------------- 

# -------------------------------------- 

# 

# Individual reports are appended the this comma 

# separated list of reports. This name here used as the 

# report ID when invoking the report using the 

# reportTemplate.jsp. # E.G., 

# http://localhost:8080/reportTemplate.jsp?id=Report1 

# -------------------------------------- 

reportList = Report1, Report2, Report3, Report4, 

Report5, GaugeExample, VoiceWatch, Oroboros 

# -------------------------------------- 

# Each Report in above list shall be listed below with 

# its properties. 

# The following properties are supported: 

# .title - This is the title of the report that appears 

# within the report frame. This property is required. 



# .visible - The visible property determines whether the 

# report appears on the main reports page, available to 

# all OneSight users. 

# .template - This is the Corda PopChart appearance file 

# that determines the type of chart (E.G., bar, stacked 

# bar, line, pie, etc). This property is required. These 

# files are within the directory: 

# popchart\chart_root\reportTemplates\apfiles\en. 

# .datasourceName - The source of the data. Valid types 

# include: CSV, XML, HTML (a table within an HTML page), 

# SQL. This property is required. A Gauge (see 

# datasourceValue, below) only supports SQL. 

# .datasourceValue - For the file type data sources 

# (CSV, XML, HTML), this is the location of the file. 

# This property is required for file type data sources. 

# For a gauge "chart", set this to 'gauge'. 

# If you wish to post process the data, this is the 

# filespec to your java class. 

# .gaugeRanges - The ranges when datasourceValue is 

# 'gauge'. List as 

# title,color,min,max;title,color,min,max; etc. 

# .disabledColumns - For the file type data sources, 

# these are the columns to leave out of the report, 

# delimited by commas. The format 1-4 is also supported 

# when a range can be specified. 

# .htmlTable - For the HTML data source, the value of 

# this property is the name of the table, as specified 

# by the attribute in the html file 

# specified by the .dataSourceValue. 

# .width - Optional height of chart. Note that this 

# property can also be provided as a runtime argument to 

# reportTemplate.jsp. 

# .height - Optional height of chart. Note that this 

# property can also be provided as a runtime argument to 

# reportTemplate.jsp. 

# .outputType - Determines the format of the output. 

# Valid types include FLASH (the default), PDF, TABLE. A 

# value of TABLE will output an HTML table, rather than 

# a chart. Note that this property can also be provided 



# as a runtime argument to reportTemplate.jsp. E.G., 

# 

http://localhost:8080/reportTemplate.jsp?id=Report4&outp 

utType=TABLE 

# Also note the following JDBC connection parameters for 

# the SQL dataSourceValue, which are all required for a 

# SQL data source. 

# .jdbcDriver - The JDBC driver. E.G., 

# "com.inet.tds.TdsDriver" 

# .jdbcConnectionUrl - The JDBC connection string. 

# E.G., jdbc:inetdae:frs0671:1433?database=Trunk 

# .user - The user name. 

# .password - The password. 

# .sql - The SQL query. Must be on a single line. Note 

# the query can have the ? mark character. This allows 

# the parameter substitution in the URL. 

# E.G., 

# 

http://localhost:8080/reportTemplate.jsp?id=Report4&arg= 

57&arg=foo 

# -------------------------------------- 

# Sample report using bar graph and CSV file as data 

# source 

Report1.title = My CSV Report 

Report1.visible=true 

Report1.template = stackedbarcolumn.pcxml 

Report1.datasourceName=csv 

Report1.datasourceValue=reportTemplates/data/medals.csv 

# Sample report using stacked bar graph and XML file as 

# data source 

Report2.title = My XML Report 

Report2.visible=false 

Report2.template = stackedbar.pcxml 

Report2.datasourceName=xml 

Report2.datasourceValue=reportTemplates/data/bball.xml 

Report2.width = 1024 

Report2.height = 768 



# Sample report using line graph and table in HTML file 

# as data source 

Report3.title = My HTML Report 


Report3.template = line.pcxml 

Report3.datasourceName=html 

Report3.datasourceValue=reportTemplates/data/data1.html 

Report3.htmlTable=CordaData 

# Sample report using pie graph and SQL query as data 

# source 

Report4.title = OneSight Alert Distribution 


Report4.template = pie.pcxml 

Report4.datasourceName=sql 

# 

Report4.datasourceValue=com.wrq.wam.reports.reportTempla 

teExamples.ReportTemplateExample 

Report4.datasourceValue=reportTemplateExamples.ReportTem 

plateExample 

Report4.jdbcDriver=com.inet.tds.TdsDriver 

Report4.jdbcConnectionUrl=jdbc:inetdae:frs0671:1433?data 

base=OneSightTrunk 

Report4.user=sa 

Report4.password= 

Report4.sql=select 

EmpirixAdmin.tbl_AlertDetail.AlertName, 

COUNT(EmpirixAdmin.tbl_AlertDetail.AlertName) AS 

Alert_Count FROM EmpirixAdmin.tbl_AlertDetail GROUP BY 

EmpirixAdmin.tbl_AlertDetail.AlertName 

# Sample report using pie graph and SQL query as data 

# source with example of using Arguments. 

Report5.title = My SQL with Arg 


Report5.template = pie.pcxml 



Report5.datasourceName=sql 

Report5.jdbcDriver=com.inet.tds.TdsDriver 

Report5.jdbcConnectionUrl=jdbc:inetdae:frs0671:1433?data 

base=Trunk 

Report5.user=sa 

Report5.password= 

Report5.sql=SELECT PropName, AgentPropertySeq FROM 

EmpirixAdmin.tbl_AgentProperty WHERE 

(AgentPropertyListID = ?) 

# Sample Gauge 

GaugeExample.title = Some Load Measurement 

GaugeExample.visible=false 

GaugeExample.template=dialgauge.pcxml 

GaugeExample.datasourceName=sql 

GaugeExample.datasourceValue=gauge 

GaugeExample.gaugeRanges=Normal,00b200,0,750;Warning,b2b 

200,750,900;Critical,b20000,900,1000 

GaugeExample.jdbcDriver=com.inet.tds.TdsDriver 

GaugeExample.jdbcConnectionUrl=jdbc:inetdae:frs0671:1433 

?database=OneSightTrunk 

GaugeExample.user=sa 

GaugeExample.password= 

GaugeExample.sql=select 

COUNT(EmpirixAdmin.tbl_AppliedMonitor.MonitorID) FROM 

EmpirixAdmin.tbl_AppliedMonitor 

VoiceWatch.title = VoiceWatch Report 

VoiceWatch.visible=false 

VoiceWatch.template = stackedbarcolumn.pcxml 

VoiceWatch.datasourceName=csv 

VoiceWatch.datasourceValue=reportTemplates/data/andrew.c 

sv 

VoiceWatch.disabledColumns=1-4,6-8,23 

Oroboros.title=My Alert Distribution 

Oroboros.visible=false 

Oroboros.template=stackedbar.pcxml 

Oroboros.datasourceName=csv 

Oroboros.datasourceValue=http://localhost:8080/support/R 

eportsCSV.jsp?csv=1&report=1039&1=01d&uid=admin


n


Configuring Time Intervals 

Time intervals belong to user groups and are used: 

when creating SLOs to indicate the time period for which the 

objective applies 

in action plans to determine the actions to take when an alert 

occurs during the time interval 

Creating New Time Intervals 

To create a time interval: 


863


2. Click Time Intervals to open the Configure Time Intervals page. 


Time Intervals – lists the existing time intervals. 

Add – displays the New Time Interval dialog box for adding a 

new time interval. 

Clone – makes a copy of the selected time interval that can then 

be edited. 

Modify – displays the Update Time Interval dialog box for 

changing the selected time interval. 

Remove – deletes the selected time interval. 

Used By – displays a list of actions plans and SLOs that are 

using the selected time interval. 



3. Click Add. 


General Tab Settings 

Time Interval Name – enter the name of the time interval. 

Server Time Zone – displays the OneSight server’s time zone. 

User Time Zone – displays the user’s time zone. 

Block select – lets you select a group of blocks by indicating 

the first and last block on a row or column. When not 

selected, you must select each block individually. Selected 

blocks have a green circle in them. 

Clear all – resets the dialog box so that no times are selected. 

Access Control Settings 


Owner – The user group for this time interval. A time interval 

can be directly owned by a user group. 



Chapter 15: Configuring Time Intervals 865

Changing Time Intervals 




4. Enter the name of the new time interval. 

5. Select the times that you want included in the time interval. 


Changing Time Intervals 

To change a time interval: 




Deleting Time Intervals 

3. Click Modify. 

4. Make any changes and click Save. 


You can delete all time intervals except the last one. To delete a 

time interval: 



3. Select the time interval that you want to delete and click 

Remove. 

4. Click OK. 

Chapter 15: Configuring Time Intervals 867





Configuring VQ Probes 

Voice Quality (VQ) Probes calculate the voice quality score of calls 

using the following systems: 

The VQ Probe System 

OneSight System 

OneSight is used to configure and schedule CallMaster voice 

quality scripts. The calling side, known as the A side, plays a 

prompt and the receiving side, known as the B side, listens to the 

prompt and calculates its VQ score. The B side then plays the same 

prompt and the A side listens to it and calculates its VQ score. The 

bi-directional scores are sent back to OneSight where they can be 

monitored and viewed. 

Voice Quality Basic monitors can make calls directly from the VQ 

Probe Core to a remote VQ Probe, through the customer PBX 

directly to the remote VQ Probe, and remote VQ Probes can call one 

another. 

Voice Quality Advanced monitors combine Voice Quality scores 

with script metrics. In addition the Voice Quality Advanced 

monitor can make calls through the customer PBX through an IVR 

to the remote VQ Probe. 

869

Editing VQ Probes 

The following diagram shows the possible calling configurations. 

Note that calls through an IVR can only be made using the Voice 

Quality Advanced monitor. 

The general tasks for setting up a VQ Probe are as follows: 

Install the VQ Probe as described in “Chapter 2” of the VQ 

Probe User’s Guide. 

Configure the VQ Probe in OneSight as described in this chapter. 

Set up the OneSight monitor as described in “Chapter 5” of this 

manual. 

VQ Probe Self Monitors 

When OneSight starts up, it automatically checks to see if there are 

any connected VQ Probes. If there are, OneSight creates selfmonitors 

for them and places them in the VQ Probe Self Monitoring 



monitor group. These monitors collect the following metrics on the 

VQ Probe: 

CPU 

Memory 

Disk space 

HTServer 

Sigserver 

DataManager 

This monitor group is displayed on the Status page if any VQ Probe 

goes into a warning or critical state. To always display this monitor 

group, Select Logging and Debugging Controls from the Support 

page and check the Show VQ Probe Self Monitor Group check box. 


When you install a VQ Probe, you enter the OneSight Server to 

which the probe will connect. The VQ Probe configuration page 

lists all of the VQ Probes that have connected to this OneSight 

Server. You can configure and schedule the VQ Probe from this 

page. 

Configuring a VQ Probe 

VQ Probes can be configured on Hammer systems or non-Hammer 

systems. The configuration screens are not the same. This section 

describes how to configure a VQ Probe on a non-Hammer system. 

Refer to “Configuring a VQ Probe on a G5 or FX/TDM System,” 

later in this chapter for information on configuring VQ Probes on a 

Hammer system. 

Chapter 16: Configuring VQ Probes 871


Note: The VQ Probe should use static IPs per channel. If the IP 

address should change, reopen the configuration for the probe and 

save it. 

To configure a VQ Probe: 


2. Click VQ Probes. 

This dialog box shows a list of connected VQ Probes. OneSight 

automatically adds VQ Probes to the list and remembers them 

even if they disconnect. 

Modify – Displays the VQ Probe Editor for modifying the 

configuration package associated with this probe. 

Remove – Removes the selected VQ Probe from the list. Probes 

can only be removed if they are not connected to OneSight and 

if they are not being used by any monitors, including disabled 

monitors. If the probe is still connected to OneSight, OneSight 

will add the probe back to the list. 



Used By – Displays the data collector by which the probe is 

connected and the monitor groups and monitors that are using 

the selected probe. 

Edit Alternate Dial Numbers – Displays the VQ Configuration 

For Dial Numbers dialog box for managing dial numbers. 

Name – Displays the name of the VQ Probe. 

Version – Displays the VQ Probe version. 

State – Displays whether or not the probe is connected. 

3. Select the VQ Probe that you want to modify and click Modify. 

This dialog box lets you create and configure channel groups. A 

channel group is a group of channels that has the same settings 

and whose phone extensions will be incremented by one 

starting with the first configured extension. 



Note: The channels configured here are for use with the 

OneSight Voice Quality Basic and Advanced monitors. These 

channels cannot be used for anything else. 

The following options are available when VQ Probe Settings is 

selected in the tree. 

Channel Groups 

Add Group – Adds a new channel group to the list. 

Remove Group – Removes the selected channel group. 

Number of channels – Enter the number of channels in the 

selected group. 

Update – Updates the number of channels in the selected 

channel group. 

4. Select the length of the prompt to use. 

5. Add additional channel groups, if necessary. 



6. In the tree, select the channel group that you want to configure. 

General 

Protocol – Select the protocol to use. The type of protocol 

determines which fields are displayed in the Configuration 

section of this dialog box. 

Note: UNIStim is only supported for probe to probe calling. It 

is not supported for Hammer to probe calling. 

IP Address – Enter the local IP address that the VQ Probe will 

use to originate calls, and listen on for incoming messages 

and connections. 

Select the starting IP address for each channel group. Each 

channel in the group will use the next incremental IP address. 

A unique IP address must be associated with each station 

extension. You must manually add your IP addresses to the 



VQ Probe using the network interface properties page on the 

probe itself. To do this, you must use static IP addresses, not 

DHCP. If you use DHCP, you will not be able to add multiple 

IP addresses to the interface. To add IP addresses: 

1. Select Settings from the Start menu, then select Network 

Connections. 

2. Double-click on the network interface you are 

configuring. 

3. Click the Properties button on the General tab. 

4. Double click Internet Protocol (TCP/IP). 

5. Select Use the following IP address. 

6. Enter the IP address, subnet mask, default gateway, 

preferred DNS server, and the alternate DNS server. 

7. Click Advanced. 

8. Click Add. 

9. Enter the other IP addresses you wish to add using the 

same subnet mask entered previously. 

10. Click OK when done. 

11. Click OK. 

Extension – Enter the first channel’s extension. Subsequent 

extensions will be incremented by one. 

Media 

Codec – Select the codec that the media will be transmitted 

in. 



Note: The Codec used directly effects the maximum MOS 

score that can be returned. This, in turn, effects how you 

configure thresholds for alerting on your monitors. Refer to 

the Codec comparison chart at the end of this section for a list 

of Codecs and their expected maximum MOS scores. 

Interpacket Delay (ms) – Select the interpacket delay. The 

values in the dropdown are based on the type of codec being 

used. The higher the interpacket delay, the larger the RTP 

packets. 

DTMF Type – Select the type of DTMF digits that the channel 

sends. The following options are available: 

In Band (Audio) – DTMF digits are sent via standard RTP 

encoding. 

Out of Band (RFC2833) – DTMF digits are sent in the RTP 

stream as defined in RFC 2833. If you select this option, 

and the receiving endpoint does not support Out of Band 

DTMF, the call fails. 

Note: If the receiving endpoint does not recognize the Out 

of Band DTMF sent by hammer, set DTMF to In Band. 

Both – The channel sends both standard RTP-encoded 

audio and RFC 2833. When sending both Out of Band 

and In Band, only Out of Band digits (2833) are verified. 

If the receiving endpoint does not support Out of Band 

DTMF, the call can still connect normally; however, any DTMF 

transmission sends both In Band and Out of Band even 

though the receiving endpoint has not declared that it can 

receive Out of Band DTMF. 

Signaling – DTMF digits are sent in signaling messages. 



SIP Configuration 

PBX – Enter either the IP Address or the name of the Call 

Manager with which the extension registers. 

Register with PBX – Enter whether or not it is necessary to 

register with the PBX. 

Username – Enter the user name that all probes will use to 

authenticate to the PBX. This field is displayed when Register 

with PBX is set to Yes. 

Password – Enter the password that all probes will use to 

authenticate to the PBX. This field is displayed when Register 

with PBX is set to Yes. 

Skinny 

Skinny Type – Select the Skinny type. 

Station MAC Address – Enter the MAC address of the phone 

configured on the Call Manager. 



Register with PBX –Enter whether or not it is necessary to 

register with the PBX. 

Local Terminal Type – Select the local terminal type. 

H.323 

H.323 Type – Select the type of H323 that you want to use. 





Register with PBX – This field is displayed when the H.323 

Type is H323 H245 Phone. Enter whether or not it is 

necessary to register with the PBX. 

Gatekeeper IP – This field is displayed when the H.323 Type 

is H323 FS RAS Phone or H323 H245 RAS Phone. Enter the 

IP address of the gatekeeper. 

Register with Gatekeeper – This field is displayed when the 

H.323 Type is H323 FS RAS Phone or H323 H245 RAS 

Phone. Enter whether or not it is necessary to register with 

the Gatekeeper. 

Avaya H.323 

Avaya_H.323 Type – Select the Avaya H.323 type. Note that 

Avaya 96xx – 46xx Station and Avaya H323 Trunk are the 

only types supported. 



Register with PBX – This field is displayed when the Avaya 

H.323 type is Avaya 96xx-46xx Station. Enter whether or not 

it is necessary to register with the PBX. 

Security Code – This field is required if Register with PBX is 

set to Yes. Enter the four digit security code for these stations 

on the Avaya. 

UNIStim Configuration 

Mac Address – Enter the Mac address. 





Username – Enter the user name that all probes will use to 

authenticate to the PBX. Leave this field blank if 

authentication is not required. 

Password – Enter the password that all probes will use to 

authenticate to the PBX. Leave this field blank if 

authentication is not required. 

Unique network ID – Enter the four digit network ID of the 

endpoint. This field is used to respond to the server when the 

server queries the endpoint’s location information. 

Manufacturer ID – Enter the two digit unique manufacturer ID 

of the endpoint. 

Firmware Version – Enter the firmware version code of the 

endpoint. 

7. Enter the configuration information for this probe and click 

Save. 

Configuring a VQ Probe on a G5 or FX/TDM System 

VQ Probes can be configured on Hammer systems or non-Hammer 

systems. The configuration screens are not the same. This section 

describes how to configure a VQ Probe on a Hammer system. Refer 

to “Configuring a VQ Probe,” earlier in this chapter for 

information on configuring VQ Probes on a non-Hammer system. 

To configure a VQ Probe on a G5 or FX/TDM System: 





This dialog box shows a list of connected VQ Probes. OneSight 

automatically adds VQ Probes to the list and remembers them 

even if they disconnect. 

Modify – Displays the VQ Probe Editor for modifying the 

configuration package associated with this probe. 

Remove – Removes the selected VQ Probe from the list; 

however, if the probe is still connected, OneSight will add the 

probe back to the list within minutes. Use remove to clear out 

Probes that are no longer expected to connect. 

Used By – Displays the data collector by which the probe is 

connected and the monitor groups and monitors that are using 

the selected probe. 

Edit Dial Numbers – Displays the VQ Configuration For Dial 

Numbers dialog box for managing dial numbers. 

Name – Displays the name of the VQ Probe. 

Version – Displays the VQ Probe version. 

State – Displays whether or not the probe is connected. 



3. Select the VQ Probe that you want to modify and click Modify. 

This dialog box lets you configure the channels to use for VQ 

monitoring and the extensions associated with them. When you 

click the Add new mapping button, fields are displayed to enter 

groups of consecutive channels and extensions that can be used 

for VQ monitoring. You can enter the first channel number, the 

first extension number, and the number of consecutive 

channels. The configured extensions will be displayed in the 

Dial Number field on the Configure OneSight Voice Quality 

Monitor page. 

Note: The configured channels should be dedicated for use only 

for Voice Quality – Basic monitors in OneSight and should not 

be used for any other functions. In addition, these channels 

cannot be used as A sides with the Voice Quality – Advanced 

monitors. 

Add new mapping – Displays the next group of fields for 

configuring consecutive channels and their extensions. 

Start Channel – Enter the first channel to use for VQ 

monitoring. 

Start Extension – Enter the first extension to use. 

Length – Enter the number of consecutive channels. 



Note: If you need to use a non-numeric extension, create a 

channel group with a length of one. Any value can then be 

entered in the Start Extension field. 

Delete mapping – Deletes the associated mapping group. 

4. Click Add new mapping to display the next group of fields for 

configuring consecutive channels and their extensions. 

Note: The configured channels should be dedicated for use only 

for VQ monitoring from OneSight and should not be used for 

any other functions. 

5. Enter the first channel. 

6. Enter the first extension. The configured extensions will be 

displayed in the Dial Number field on the Configure OneSight 

Voice Quality Monitor page. 

7. Enter the number of consecutive channels. 

8. Repeat steps 4-7 for additional channel groups. 

9. Click OK when you are finished. 

Changing or Adding IP Addresses 

If your VQ Probe is using only one IP address and one channel, and 

you need to change the IP address, you must stop the VQ Probe 

Data Collector and change the IP address. In addition, before 

restarting the Data Collector, update the Comm.ConnectFrom field 

with the IP address to use to connect to Empirix OneSight and 

update the PackageAgentName in the OSDC.properties file. If you 

do not, the VQ Probe may fail to connect to Empirix OneSight. 

If your VQ Probe is using one IP address and one channel group 

with unique IP addresses for each channel, and you want to increase 

the number of channels, you must update the OSDC.properties file 


Deleting VQ Probes 

in addition to restarting the Data Collector. Before restarting the 

Data Collector, update the Comm.ConnectFrom field with the IP 

address to use to connect to Empirix OneSight and update the 

PackageAgentName. 

Codec Comparison Chart 

The following chart shows some commonly used Codecs and their 

maximum expected MOS scores from best to worst. 

Codec Data rate (kb/s) MOS 

G.711 64 4.5 

G.723 6.3 3.9 

G.726 24 3.8 

G.729a 8 3.7 

G.723 5.3 3.65 

Deleting VQ Probes 

You can remove a VQ Probe from the VQ Probes dialog box. Probes 

can only be removed if they are not connected to OneSight and if 

they are not being used by any monitors, including disabled 

monitors. If the probe is still connected, OneSight will add the 

probe back to the list. To delete a VQ Probe: 



3. Select the VQ Probe that you want to delete and click Remove. 


Editing Dial Numbers 


You can add and modify the list of dial numbers. The dial numbers 

will be displayed in the dial numbers list on the General Tab when 

you create a OneSight Voice Quality monitor. To edit a dial 

number: 

1. Click the Configure tab. 

2. Select VQ Probes. 

3. Click Edit Alternate Dial Number. 

Add – Displays the Add Dial Number dialog box for adding a 

dial number. 

Modify – Displays the Edit Dial Number dialog box for adding a 

dial number. 

Remove – Deletes the selected dial number. 

Alias – Displays the Dial Number’s alias. 

Dial Number – Displays the number to dial. 



4. Click Add to add a new dial number or click Modify to edit the 

selected dial number. 

Alias – Enter the dial number’s alias. 

Dial Number – Enter the number to dial. 

5. Enter the dial number’s alias. 

6. Enter the number to dial. 

7. Click OK. 



Configuring XMS Systems 

You can configure XMS systems so that you can view Call Data 

Records (CDRs) using the Hammer E-XMS diagnostics, voice 

reports, and analysis tool directly from OneSight. 

When you have one or more XMS systems configured, OneSight 

displays the Diagnostics tab, which allows you to connect to an 

XMS system, as described later in this Chapter. 

Adding XMS Systems 

To add an XMS System: 

1. Click XMS Systems on the Configure tab. 

887



Add – Displays the Add Systems dialog box for adding a new 

XMS system. 

Modify – Displays the System Editor for modifying the selected 

XMS system. 

Remove – Removes the selected XMS system. 

Check Box – Lets you select systems. 

In Use – Shows whether the system is in use. 

System – Displays the system name or IP address. 

Device Type – Displays the type of device. 

Operating System – Displays the operating system type. 

User Group – Displays the user group to which this system 

belongs. 

2. Click Add. 

System name – Enter the system name or IP address. 

Username – Enter the user name for accessing the system. 

Password – Enter the password. 

Device Type – Select the device type. 

3. Enter the system name or IP address. 



4. Enter the system name or IP address. 

5. Enter the user name and password for the XMS system. 

6. Select the device type. 

7. Click OK. 

System Tab – The fields are automatically filled in based on the 

information entered in the previous dialog box, however, you 

can make changes here. 

Device Type – Displays the device type. 

DNS Name – Displays the DNS name. 

IP address – Displays the IP address 

NetBIOS name – Displays the NetBIOS name. 

Chapter 17: Configuring XMS Systems 889


XMS Username – Displays the user name. 

XMS Password – Hides the password. 

Attributes Tab Settings – Attributes are used in OneSight to sort 

the monitors, monitor groups, profiles, and systems on the 

status page. You can assign custom attribute values to specific 

monitors and use the Group by selection on the status page to 

show only those monitors, monitor groups, profiles, or systems 

assigned to a specific attribute set. 

All Attributes – Shows the name of the attribute set and its 

attribute values. 

Selected Attributes – Shows the list of attribute values applied 

to this system. Use the Add and Remove arrow buttons to 

customize the list of attribute values applied to the monitor, 

monitor group, profile, or system. 

Attribute Editor – Opens the Attribute Editor for adding and 

deleting attributes and attribute values. 

Access Control Tab – The Access Control tab lets you specify 

which user groups can read, write, or delete this system. 


Owner – The user group for this system. A system can be 

directly owned by a user group. 







Modifying XMS Systems 

8. OneSight fills in the System tab based on the entries in the 

previous dialog box. From here, you can assign attributes to the 

system and configure who can access this system. make any 

changes and click OK. 

9. Click Close to exit the XMS Systems dialog box. The 

Diagnostics Tab will be displayed where you can access an 

XMS System. 

Modifying XMS Systems 

To modify an XMS system: 

1. Click XMS Systems on the Configure tab. 

2. Select the XMS system that you want to modify and click the 

Modify button. 


Deleting XMS Systems 


4. Click Close to exit the XMS Systems dialog box. 

Deleting XMS Systems 

To delete an XMS system: 

1. Click XMS Systems on the Configure tab 

2. Select the XMS system that you want to delete and click 

Remove. 

3. Click OK to confirm the deletion. 

4. Click Close to exit the XMS Systems dialog box. 


Viewing Call Data Records 


You can access a configured XMS system from the Diagnostics tab. 

This tab is only displayed when there are one or more configured 

XMS systems. 

This page displays a table that contains one line for each XMS 

system that is configured. It has the following columns: 

XMS Server Name – Displays the server name or IP address. 

XMS Server IP – Displays the IP address. 

Link to XMS System – Shows a link for connecting to the XMS 

system. 



Click in the Link to XMS System field for the XMS system that you 

want to access. The E-XMS Diagnostics, Voice Reports, and 

Analysis tool is displayed. 

Refer to the E-XMS documentation for information on using this 

tool. 

Note: If you are using Internet Explorer 8.0, you may have a 

problem connected to the XMS system from this link. You must add 

the XMS server to the local intranet sites in your browser. To do 

this, click Internet Options from the Tools menu in IE. Click the 

Security tab, then click the Sites button. Click Advanced. Enter the 

OneSight server URL and click Add. 



OneSight Utilities 

Trace Route 

OneSight provides the following utilities on the Configure page: 

Trace Route – lets you run a trace route from the specified 

location to a specified host to validate connectivity to the host 

device. 

Regex Tester – lets you test a regular expression that you want to 

use in OneSight. 

MIB Browser – lets you view objects in a MIB file, and create 

metrics and profiles. 

In addition, the OneSight Support and Diagnostic Page, available 

when you click Support in the Main Menu, lets you access the 

support utilities that are currently available on the OneSight support 

page. 

The Trace Route utility lets you run a trace route from the specified 

location to a specified host to validate connectivity to the host 

device. To trace a route: 


895

Regular Expressions 

2. Click Trace Route. 

3. Enter the host name or IP address. 

4. Click Run. The results are displayed in the OneSight Trace Route 

field. 


The Regex utility lets you test a regular expression that you intend 

to use in OneSight. Refer to Using Regular Expressions for Pattern 

Matching in Chapter 5 for more information about regular 

expressions. 

To test a regular expression: 




2. Click Regex Tester. 


Content – Enter or paste in the text that you want to test the 

regular expression against. 

Perl Regular Expression – Enter the regular expression that you 

want to test. 

Search for – Select whether to search for a string match or a 

numeric value. 

Test Results – Displays the results of the test. 

3. Enter or paste in the text that you want to test the regular 

expression against. 

4. Enter the regular expression that you want to test. 

5. Select whether to test for a string or numeric value. 

Chapter 18: OneSight Utilities 897

MIB Browser 

MIB Browser 

6. Click Test. The results are displayed in the Test Results field. 

The MIB Browser lets you view objects in a MIB file. You can then 

copy an OID and paste it into OneSight when you are configuring 

monitors. You can also select objects and create metrics and 

profiles using the Metric Creation Wizard. 

To view a MIB file: 


2. Click MIB Browser. 


Load MIB – Enter the MIB file that you want to browse or select 

Browse to find a file. 


MIB Browser 

MIB Configuration 

Host – Specify the name or IP address of the host. 

Community – Specify the SNMP password of the system. The 


Port – Specify the port number used on this system by the 


SNMP Version – Specify the SNMP version used on this 

system. 

Location – Select the location to use for sampling. 

Object ID 

Object ID – Displays the object ID for the selected object. 

Clicking GO displays the object’s value in the Object Value 

field. 

Launch Metric Wizard – Starts the Metric Creation Wizard for 

creating metrics. 

Object Value – Displays the object’s value on the configured 

host device when you click GO. 

Syntax – Displays the syntax of the selected object as found in 

the MIB file. 

Access – Displays the type of access of the selected object as 

found in the MIB file. 

Description – Displays a description of the selected object as 

found in the MIB file. 


MIB Browser 

3. Select the MIB file you want to view and click GO or select 

Browse to find a file that is not in the list. 

4. Expand the tree and select the object you are interested in. Its 

OID is displayed in the Object ID field. 

5. Enter the MIB Configuration information for the host on which 

you want to check the object’s value. 

6. Click GO in the OID section to get the object’s value as shown 

in the following example. 


MIB Browser 

Creating Metrics 

You can add a metrics from the MIB browser. 

1. Click Launch Metric Wizard. 

Node Name – Select the node that you want to add. 

OID Column – Select Object ID column. 

Sample Every (sec) – Specify how often you want this metric to 

query the monitored web component for data. In general, the 

higher the number, the more efficiently the database operates. 

Translation Type – Translation Type settings control how 

OneSight translates a metric’s data when displayed on the 

OneSight Alerts page and in Reports. If you are modifying a 

metric that is provided as part of a profile, use the existing 

Translation Type setting: 

No Translation – OneSight presents the metric’s data as it is 


Rate (minutes) – OneSight presents the metric’s data as a 

delta, per minute. If the time interval between two samples 


MIB Browser 

was 10 minutes, and 50 errors were found, the Rate (minutes) 

would be five (5) errors per minute. 



does not return data this way, use No Translation. For example, 

some network metrics from the UNIX System data source are 

returned as the number of errors since the machine was 

rebooted. To get the error rate per minute, use Rate (minutes). 

Search String –Enter the string or regular expression that 

OneSight will search for in the Table Get OID column that you 

specify. 

Sample For Each – Sample for Each settings correspond with the 

items under Components in the System Editor. Use the Sample 

for Each settings to make the metric sample each component of 

that type that it finds on the monitored web component. Take, 

for example, a metric that measures Queue Length that has Disk 

as its Sample for Each setting (Disk: Queue Length). When Disk: 

Queue Length is applied as part of a profile to an NT machine 

that has four logical disks, four instances of the Disk: Queue 

Length metric will be created, one metric instance for each 

logical disk. 

The Sample for Each setting called System does not replicate 

metrics. Use System to measure “one of a kind” items on a 

machine. 

Add Metric – Adds the selected metric to the list at the bottom of 

the screen. 

Metric name prefix – Enter a prefix to place in front of the 

metric name. 

Profile name – Enter a name for the profile that you want to 

create using these metrics. This profile can be viewed when you 

select Profiles on the Configure tab. 

Remove – Removes the selected metrics. 


Support and Diagnostics 

Create Metrics – Creates the selected metrics. 

2. Select the node for which you want to create a metric. 

3. Select how often to sample the metric, the translation type, 

search string, and the sample for each settings. 

4. Enter a prefix if desired. 

5. Enter a profile name if you want to create a profile for the 

selected metrics. 

6. Click Add Metric. 

7. Repeat for as many metrics as you want to add. 

8. Click Create Metrics. A message is displayed when the metrics 

have been created. 

9. Click OK. The metrics can be viewed by selecting Metrics on the 

Configure tab. If you entered a profile name, the profile can be 

accessed by clicking Profiles on the Configure tab. 


The support and diagnostics page is available when you click 

Support on the Main Menu. It provides utilities that let you view the 

overall status of OneSight. Some utilities also affect how OneSight 

functions. 

The support and diagnostics page should only be used with the 

assistance of OneSight technical support. 

This option is only available to those users that can view all user 

groups and that have configuration rights. 






Troubleshooting 

Viewing Administration Notifications 

The OneSight Administration Notifications feature lets you view a 

description of internal errors that have occurred. The 

Administration Notifications icon appears in the top right-hand 

corner of the Status, SLA Status, and Alerts tabs only if internal 

errors have occurred. Click on the icon to display the OneSight 

Administration Notifications dialog box. 


Date – Displays the date the error occurred. 

Description – Displays a description of the error. 

Resolution URL – Click on this link to either correct the problem or 

view more information about the problem. For example, for critical 

logs, the support log file dialog box would be displayed. 

Remove – Removes the error from the list. 

905

Troubleshooting Setup 

Remove All – Removes all errors from the list. 


Use the following sections for tips on how to solve problems that 

may occur during OneSight Setup: 

Determining which Service Pack you have 

Out of Disk Space 

Out of Disk Space 

Moving the OneSight database to a remote SQL server after setup 

If you see database installation or connection errors 

If you try to install OneSight on a Windows 2000 server using 

Windows Terminal Services 

If your system drive (in most cases, C:\) is low on disk space and 

even if you are installing OneSight on a drive other than your 

system drive, you may get the following error message during 

OneSight Setup: 

Out of disk space. The highlighted volumes do not have 

enough disk space available for the selected features. 

This message appears because OneSight Setup must copy these files 

to your system drive: 

Setup also copies Microsoft InstallShield files (120 MB) to your 

system drive’s Program Files\Common Files\Wise Installation 

Wizard and Winnt\Installer folders. 

There is no workaround to avoid having the above two file types 

copied to your system drive. You will have to make room for those 

files (approximately 260 MB). 



Setup also copies additional MSI files (60 MB) to your system 

drive’s TEMP or TMP folders. To reduce the amount of disk space 

required on your C:\ drive, do the following: 

1. On the OneSight Server, click Start, then point to Settings, then 

click Control Panel. 

2. Double-click System. 

3. Click the Advanced tab and then click the Environment 

Variables button. 

4. Under User Variables for , highlight TEMP. Click Edit. 

5. In the Value box, type a drive other than your system drive, 

followed by TEMP, for example, D:\TEMP. Click OK to save 

these changes. 

6. Do the same for TMP: Under User Variables for , 

highlight TMP, then in the Value box, type a drive other than 

your system drive, followed by TMP. 

7. Click Set to apply your changes, then click OK to close the 

System Properties dialog box. 

You can also minimize impact on the C:\ drive by adding space for 

a Paging File on additional drives. In Control Panel, open System. 

On the Performance tab, click the Change button for Virtual 

Memory. If you have additional fixed disk drives, you can allocate 

more space for virtual memory paging on these drives and decrease 

the space allocated on the system (C:\) drive. The machine must be 

restarted to have these changes take effect. 

Moving the OneSight Database to a Remote SQL Server 

When you first run Setup, you can choose to use a remote SQL 

server. However, if you installed MSDE or Microsoft SQL Server on 

Chapter 19: Troubleshooting 907


the OneSight Server and then decide to move the OneSight database 

to a remote SQL server, use the steps below. 

To move the database, you will be using Enterprise Manager and 

Query Analyzer, which are Microsoft SQL Server Client Utilities. 

Note: This procedure assumes that the name of the OneSight 

administrative user is “OneSightAdmin” in the database section of 

the OSServer.properties file. The Onesight administrator’s name is 

identified with the property Database.UserName in the 

OSServer.properties file. If you changed this name, you must edit the 

script file OneSightEmpirix\db\sp_CreateUsers.sql and replace all 

occurrences of OneSightAdmin with the name of the OneSight 

administrative user as it appears in the OSServer.properties file. You 

must then execute this script file in a Query Analyzer window to 

modify the stored procedure before executing the procedure in step 

5 below. 

1. Confirm that the remote SQL Server database you intend to use 

has the same character set and sort order. The OneSight 

database is configured as US English, dictionary sort-order, 

case-insensitive. 

2. Stop the Onesight service. 

3. Use Enterprise Manager to back up the OneSight database (by 

default, named OneSight). Move the database backup device 

file, (OneSight_backup.bak, typically located in the mssql7\backup 

folder) to the remote SQL server. If you do not see a backup file 

with this name, use Enterprise Manager to check the path for 

the OneSight_backup device. 

4. Restore the database on the new server from the backup file. 

Note: Make sure you restore the same version of backup that 

you created on the other server. SQL Server supports multiple 

backups in the same device file. 



5. Use Query Analyzer to execute the stored procedure that 

creates the users and logins for the remote SQL server. 

Assuming the default name of OneSight, select the OneSight 

database and execute the following command 

exec SP_createusers 'OneSight' 

6. Use Enterprise Manager to change the password of the 

OneSightAdmin login on the remote SQL server to agree with 

the password in the OSServer.properties file on the OneSight 

server. (This is necessary only if you have changed the 

OneSight default password, null, to something else.) 

7. Change the SQL Alias machine specification. Open Enterprise 

Manager, then run the Client Network Utility. 

Version 2.0 

The Server alias is the machine name, and the same machine 

name is also specified in the Connection Parameters column. 

Change both of these machine name designations to the 

machine name of the new HWM database machine and edit the 

TCP port number if applicable. 

Version 2.1 and above 

The Server alias named HWMDatabase has the machine name in 

the Connection Parameters column. Change this machine name 

to the machine name for the new HWM database machine and 

edit the TCP port number if applicable. 

Note: By default, the server alias name is HWMDatabase. The 

alias name is based on the specification in the 

Database.ServerAlias value in the \properties\OSServer.properties 

file for SQL. The Server alias string does not need to be 

changed when moving the database. 

8. Use Query Analyzer to confirm that you can connect to the 

OneSight database on the new server using the OneSight 

administrative user and password as specified in the 

OSServer.properties file on the OneSight Server. 


Oracle Test for Web Applications Error Messages 

9. Using Notepad, edit the OSServer.properties file on the OneSight 

Server. Change the ServerName, ServerPort, Detail.DataDirectory, 

and Detail.BackupDirectory properties to reflect the location of the 

remote SQL server. 


Database Installation or Connection Errors 

Refer to Technical Note 10056, “Troubleshooting Database 

Installation and Connection Error Messages,” available on the 

OneSight support web site, www.empirix.com/support. 

Installing OneSight Using Windows Terminal Services 

If you use Windows Terminal Services to install OneSight on a 

Windows 2000 server, you will see the message "Unable to connect 

to database server" after installation is complete. You must uninstall 

OneSight and then reinstall from the server without using Windows 

Terminal Services. 

Oracle Test for Web Applications Error 

Messages 

The following are descriptions for the various error messages that 

may be generated by Oracle Test for Web Applications 

Transactions. These messages can appear in the following places in 

OneSight: 

in the popup text string that appears when you move the mouse 

cursor over an Oracle Test for Web Applications Transaction 

monitor Health indicator on the Status page; 

in the Status Detail pages of Oracle Test for Web Applications 

Transaction monitors; 



in the results window that appears when you use the TEST button 

when configuring Oracle Test for Web Applications Transaction 

monitors. 

There are four types of Oracle Test for Web Applications 

Transaction error messages: 

Transaction errors detected or generated by Oracle Test for Web 

Applications Visual Scripts; 

Errors detected by OneSight while running or attempting to run 

an Oracle Test for Web Applications Transaction monitor; 

RSWISERV Error returned by the Thin agent; 

HTTP Status Codes and the Win32 Internet API Constants. 

Transaction Errors Detected or Generated by Oracle 

Test for Web Applications Visual Scripts 

OneSight classifies Oracle Test for Web Applications failures into 

the following error types: 

Custom Test Failure 

Failure 

Fatal Dialog 


Page Timeout 

Scriptlet Failure 

RealPlayer Test Failure 

Server Response Test Failure 

Text Matching Test Failure 

VBA Failure 



Windows Media Player Test Failure 

These messages appear in the following formats: 

: 

-or- 

: (Record : ) 

-or- 

: 

-or- 

: (Record : ) 

Where: 

type – is one of the above error types. 

name – is the name of a test in the Oracle Test for Web 

Applications Visual Script (i.e. Text Matching test name, Server 

Response test name, etc.). 

description – is a description of the error (i.e. Failed to find 

navigation path, etc.) 

Record : – is an OATS DataBank record number and 

data values. 

The following is an example of a Visual Script page error message: 

Navigation Failure: Failed to find navigation path 

window(0).link(text='Customize My Page' | 48), 

href=http://products/asp_pages/Popular%20Configurations.asp 

Important. (2/6/03 2:40 PM) 

This message indicates that Visual Script failed to find a recorded 

Visual Script navigation element in the page. The element is an 

HTML link () with the display text of "Customize My 

Page". The HTML link element is the 49th link element on the Web 

page in source order (zero-based index value). The URL the Visual 

Script navigation is attempting to find is: 

http://products/asp_pages/Popular%20Configurations.asp 



Errors Detected While Running Oracle Test for Web 

Applications Transaction Monitor 

The following error messages can be generated by OneSight while 

running Oracle Test for Web Applications Transaction monitors: 

OATS must be upgraded to or greater (currently installed: 

) 

The version of OATS installed on the Data Collector is older than 

the version supported by OneSight. 

Installed OATS version is lower than the version used 

to record the script 

The Visual Script cannot be played back because the version of 

OATS installed on the Data Collector is older than the OATS 

version used to record the Visual Script. Upgrade the version of 

OATS installed on the Data Collector to the same version used to 

record the Visual Script. 

The Oracle Test for Web Applications monitor is not available on the 

specified location(s) or collection host. 

This message may occur when you are creating a new Oracle Test 

for Web Applications monitor after you have upgraded to OneSight 

version 5.0. The Data Collectors running Oracle Test for Web 

Applications transactions must be upgraded as well. Data Collectors 

that are not running Oracle Test for Web Applications transactions 

do not have to be upgraded. 

No data source found. 

This message may occur if no Data Collector is available. Some of 

the possible reasons are: 

a disconnected Data Collector 

a configuration error 



an old Data Collector. Transaction monitors require Data 

Collectors to be version 5.0 or later. 

OATS not installed (OneSight requires OATS version or 

greater) 

OATS was not installed on the Data Collector. Install OATS on the 

Data Collector. 

Agent communication lost 

Communication between OneSight and the Oracle Test for Web 

Applications agent terminated unexpectedly. This usually means the 

Oracle Test for Web Applications agent terminated due to 

overloaded conditions on the Data Collector. Try reducing the 

demand on the system resources on the Data Collector machine (i.e. 

run fewer transactions on the Data Collector machine). You can 

also try upgrading hardware or use a higher performance system as 

the Data Collector machine. 

Agent exception 

Indicates a problem detected during Visual Script playback. Contact 

Empirix Customer Support. 

Failed to deploy script 

The script could not be copied to the OneSightDBCache! directory 

on the Data Collector. This could be due to file protection 

problems. If a shared directory is used (not recommended), then this 

could indicate network connection problems between the Data 

Collector and the shared directory. 

Cannot connect to OATS 

The OATS Agent Starter Service (empstart) is not running. Try 

starting this service using the Windows Services control panel 

applet. 



Failed to start OATS agent: 

Indicates a bug detected while attempting to start an OATS agent 

process. Contact Oracle Customer Support. 

OATS agent did not finish within available time (see help for possible 

causes) 

The timeout expired before playback completed. The timeout is 

specified in the transaction monitor configuration. 

This message can occur: 

1. during initial setup of a transaction monitor, in which case it is 

preceded by a "Discovery failed due to the following:" 

message. 

2. during scheduled playback, in which case the message appears 

on the status screen. 

Possible causes for this error are: 

Cause: The script was running normally but took longer than the 

allotted time. 

Resolution: Shorten the Visual Script or increase the timeout 

value in the Transaction monitor configuration. 

Cause: The web server was down, causing the script to take 

longer than normal, and longer than the time limit. 

Resolution: Shorten the OATS page timeout for the Visual Script 

or increase the timeout value in the Transaction monitor 


Cause: The script does not run to completion in Minimal Client 

(Thin). 

Resolution: Try using Full Browser (Thick) or alter the Visual 



Script to run successfully in Minimal Browser (verify dynamic 

HTML used for page navigation does not cause the agent to stop 

responding). 

OATS fatal error: 

Indicates a problem detected in the OATS agent. Contact Oracle 

Customer Support. 

Error closing handle on OATS agent process (, pid 

): 

Error waiting for OATS agent process termination (, pid 

): 

Error terminating OATS agent process (, pid ): 

Indicates a problem encountered while attempting to terminate an 

OATS agent process. 

OATS skipped page playback 

Playback completed, but OATS did not report on pages marked 

with this message. This could be the result of a navigation failure 

on a previous page or of VBA code that caused pages to be skipped. 

OATS agent stopped responding 

The OATS agent is no longer responding to the OneSight heartbeat 

monitor. Check and verify that any custom programming code in 

Visual Script Test Scriptlets or Custom VBA code is not causing 

looping conditions. If looping conditions are not the cause, Contact 

Empirix Customer Support. 

RSWISERV Error codes returned by the Thin agent 

The following table lists the RSWISERV error constants: 

100 RSW_NO_RESULTS_TO_REPORT 



101 RSW_CONNECT_BUCKET_TIMEOUT 

200 RSW_DLL_UNINIT_COMPLETED 

1000 RSW_ERROR_INVALID_PARAMETERS 

2000 RSW_INET_LAYER_NOT_INITD 

2001 RSW_OPEN_REQUEST_FAILED 

2002 RSW_ADD_REQUEST_HEADERS_FAILED 

2003 RSW_SEND_REQUEST_FAILED 

2004 RSW_QUERY_INFO_FAILED 

2005 RSW_FAILED_TO_CLOSE_HANDLE 

2006 RSW_ERROR_NO_SESSION_HANDLE 

2007 RSW_INTERNET_SET_OPTION_FAILED 

2008 RSW_INTERNET_QUERY_OPTION_FAILED 

2010 RSW_INTERNET_LOGIN_FAILURE 

2011 RSW_AUTH_LOGIN_PARMS_NOTAVAILABLE 

2012 RSW_CANNOT_CREATE_AUTH_OBJECT 

2013 RSW_READ_REQUEST_FAILED 

2014 RSW_INTERNET_REQUEST_TIMEOUT 

3000 RSW_UNABLE_TO_CREATE_EVENT 

3001 RSW_UNABLE_TO_CREATE_THREAD 

3002 RSW_UNABLE_TO_CREATE_NEW_REQUEST 


Thick Client Problems Using an Oracle Test for Web Applications Transaction Monitor 

3003 RSW_UNABLE_TO_CREATE_NEW_THEAD_ENTRY 

3004 RSW_UNABLE_TO_CREATE_MUTEX 

3005 RSW_UNABLE_TO_CREATE_NEW_OBJECT 

3006 RSW_UNABLE_TO_ALLOCATE_NEW_MEMORY 

HTTP Status Codes and the Win32 Internet API 

Constants 

For additional information about HTTP Status Codes and the 

Win32 Internet API Constants, see the following Web resources: 

Section 10 of the Hypertext Transfer Protocol – HTTP/1.1 

Request for Comments: 2616 

Microsoft MSDN Win32 Internet API Constants 

MSDN Knowledge Base article Q193625 

Thick Client Problems Using an Oracle Test for 

Web Applications Transaction Monitor 

If the html page in the Oracle Test for Web Applications 

Transaction monitor script is larger than 1M, thick client may not 

work properly. To correct this issue: 

1. Stop the Data Collector service. 

2. Open the dc_services.properties file in a text editor. 

3. Uncomment the line: JHP.commandline= 

-DentityExpansionLimit=64000 

4. Increase the value of DentityExpansionLimit. For example: 

JHP.commandline= -DentityExpansionLimit=200000 


Critical State Error Messages 

5. Start the Data Collector service. 

In the rare case when this fails to correct the issue, choose the Thin 

client option. 


Network Path Not Found (Windows only) 

This error message may occur when OneSight is trying to monitor a 

system that is off-line. Check the Host:Ping metric for this system. 

If OneSight shows a critical state for this metric, the system is 

probably off-line. 

Failed to Establish Connection (Sun or UNIX only) 

This error message may occur when OneSight is trying to monitor a 

system that is off-line. Check the Host:Ping metric for this system. 

If OneSight shows a critical state for this metric, the system is 

probably off-line. If the Host:Ping metric is showing a good state, 

make sure that you can authenticate to the system. OneSight uses 

either a telnet or SSH session to connect to the system. Make sure 

that you can connect using the session type and user name and 

password that OneSight is trying to use. 

Access is denied (Windows only) 

This error message occurs when the password that OneSight is 

trying to use to connect to this machine has changed. To change the 

password: 

1. On the Main OneSight menu, click Configure. 

2. Click Systems. 

3. Select the system displaying the error message and click Modify. 

4. Select the Windows NT tab. 



5. Enter the new password. 

6. Go back to the Status page and click the monitor group of the 

system. 

7. Click the Enabled checkbox to disable the monitor. 

8. Click the Disabled checkbox to enable the monitor and wait for 

the metrics to resample. 

Remote procedure call failed (Windows only) 

This error message may occur when OneSight had trouble reauthenticating 

its connection with the system after the system was 

rebooted. While viewing the monitor on the status page, click the 

Enabled button to disable the monitor. The monitor will move to the 

bottom of the list in the monitor group. Click the Enabled button to 

enable the monitor, forcing OneSight to re-authenticate with the 

system. 

Failed to load Perfmon name table (Windows only) 

This error message may occur when OneSight had trouble reauthenticating 

its connection with the system after the system was 

rebooted. While viewing the monitor on the status page, click the 

Enabled button to disable the monitor. The monitor will move to the 

bottom of the list in the monitor group. Click the Enabled button to 

enable the monitor, forcing OneSight to re-authenticate with the 

system. 

Missing counter value (Windows only) 

This message occurs when the indicated Windows perfmon metric 

does not exist on this system. In most cases, this is a system process 

that has stopped running. To resolve this problem: 

1. Log onto the system that is displaying the error message. 

2. From the Start menu, click Run and enter perfmon. 



3. Click the Add button in the icon bar. 

4. Select the object indicated in the OneSight error message from 

the Performance object dropdown. The object is the first thing 

listed after “Missing counter value system name |”. 

5. Select the counter that corresponds to the last name listed in the 

OneSight error message from the list of counters. 

6. Look for the instance in perfmon that corresponds to the one 

listed in the OneSight error message. It may not e listed because 

it does not exist on the system. 

7. If the object is a process, restart the process to list it in Perfmon 

again. 






Glossary 

Action – A specific response that you want OneSight to make. For 

example, sending an e-mail or an SNMP trap notification are 

possible actions. Actions are added to action plans. When an alert 

triggers an action plan, the actions in the plan are performed 

sequentially. 

Action plan – Specifies a sequence of actions that you want 

OneSight to perform if a monitor detects a problem. An action plan 

is invoked by an alert. The alert triggers the action plan to respond 

to problem conditions. 

Administrator – The category of OneSight users that can access all 

features of the Empirix OneSight. In particular, Administrators are 

allowed to see and use the Configure pages. See also Operator. 

Agent – In OneSight, refers to the OneSight Remote Agent, 

available for Windows and Solaris machines. 

Alert – One or more alerts are configured for each monitor. An alert 

does three things: 

Defines a problem condition, such as an exceeded threshold or a 





both. 

923

Glossary 

Ranks the seriousness of the problem. (Critical, Warning, or 

Informational) 

Alphanumeric – Consisting of English language letters, digits, or 

both, and occasionally containing control characters or other special 

characters. 

ASCII – American Standard Code for Information Interchange. Files 

including ASCII contain standard keyboard characters but no 

formatting information. 

Community strings – Strings that function as “passwords” embedded 

in every SNMP packet and authenticate access to the SNMP 

Management Information Base (MIB). 

Cookie – Bits of information about a user that web servers store on 

the client computer for later use. For example, web servers can use 

cookies to store the user’s web site configuration, to remember 

items placed in a “shopping cart” at an online shopping site, or to 

store account and password information for subscription sites. 

Critical state – A OneSight indicator of the state of a metric, 

monitor, or monitor group. OneSight reports use the term “Error” to 

identify a Critical state. Typically, web components that are in a 

Critical state require your immediate attention. In OneSight, Critical 

status is represented by a red diamond icon. When you configure 

monitor group monitors, you define the performance criteria that 

you want to track, associating the configuration with conditions, 

such as an exceeded threshold or a sample failure, that you want to 

be alerted about. In response to an alert, OneSight can either trigger 

an action plan, change a monitor’s health, or in some cases, do both. 

Data collector – The process that collects data from the machines 

you want to monitor and returns the data to the OneSight Server. It 

can be installed on the OneSight server or on another machine. 

Data source – Acts as the “information gatherer” for a profile metric 

or dedicated monitor. Each metric can have one or more data 


Glossary 

sources. In other products, data sources are sometimes referred to as 

agents. 

Dedicated monitor – A monitor with a single purpose: to test the 

availability or functionality of a specific web component, such as an 

FTP, DNS, or mail server, a subnet or set of machines on a subnet, a 

file, a host, or a web site or page. OneSight then reports the health 

of that component or reports any problems. Dedicated monitors are 

applied to individual web components. They allow you to measure 

and manage how users experience your site. When adding a 

dedicated monitor, you always define unique performance criteria 

for the monitor. In contrast, a profile monitor can be applied to 

more than one back-end web component of the same type and it will 

use the same set of performance criteria (a profile) for each of those 

web components. See also Profile and Profile monitor. 

DNS – Domain Name System (or Service). An Internet service that 

translates domain names into IP addresses. 

Escalation timeout – Amount of time (in minutes) that a OneSight 

action exists before escalating to the next action in the Action Plan 

sequence. 

Good state – A OneSight indicator of the state of a metric, monitor, 

or monitor group. In OneSight, a Good state is represented by a 

green circle. When you configure monitor group monitors, you 

define the performance criteria that you want to track, associating 

the configuration with conditions, such as an exceeded threshold or 

a sample failure, that you want to be alerted about. In response to an 

alert, OneSight can either trigger an action plan, change a monitor’s 

health, or in some cases, do both. 

Host name – The name of a specific server on a specific network. 

HTTP – HyperText Transfer Protocol. The Internet protocol used to 

exchange HTML documents. 

Chapter 20: Glossary 925

Glossary 

HTTPS – Hypertext Transmission Protocol, Secure. A variation of 

HTTP used by Netscape to exchange documents securely. See also 

SSL. 

IIS – Internet Information Server. Microsoft’s web server that runs 

on Windows NT platforms. It is tightly integrated with the Windows 

operating system. IIS is available only for the Windows platform, 

whereas Netscape’s web servers run on all major platforms, 

including Windows NT, OS/2, and UNIX. 

ISP – Internet Service Provider. A company that provides access to 

the Internet. In addition to serving individuals, ISPs also serve large 

companies, providing a direct connection from the company’s 

networks to the Internet. 

Latency – The time delay of data traffic through a network or 

switch. 

Load balancing – Distributing processing and communications 

activity evenly across a computer network so that no single device 

is overwhelmed. Busy web sites typically employ two or more web 

servers in a load balancing scheme. Load balancing can also refer to 

the communications channels themselves. 

Metric – A measurement of a specific aspect of a web component, 

such as how much disk space a server has used. A metric can use 

one or more data sources (for example, SNMP or Perfmon) to gather 

information. Most metrics provided with OneSight are grouped into 

profiles. See also Data source and Profile. 

MIB – Management Information Base. A formal description of a set 

of network objects that can be managed using the Simple Network 

Management Protocol (SNMP). The format of the MIB is defined as 

part of the SNMP. Empirix OneSight supports specific profiles and 

metrics for RFC 1213 (MIB -II, available on any system that 

supports SNMP), and the Host Resources MIB (based on RFC 1514, 

available on many Linux and AS/400 systems), and the UCD 


Glossary 

package (University of California, Davis), available on many Linux 

systems. 

Monitor – A monitor checks the behavior of a specific web 

component using a defined set of performance standards. OneSight 

then reports the general health of the component or reports any 

problems. OneSight includes monitors for components such as 

URLs that are critical to the web site, monitors for Internet servers 

such as FTP, DNS, or Mail, and monitors for databases, web servers, 

and operating systems. See also Dedicated monitor and Profile. 

Monitor group – A collection of monitors used to measure and 

manage the availability and performance of your entire web site. 

Use monitor groups to group together monitors in any way that is 

logical to you. 

NetBIOS – The NetBIOS name is the Windows Computer Name. In 

Windows NT, this is on the Identification tab in Network 

Neighborhood properties tab. In Windows 2000, it is on the 

Network Identification tab in My Computer properties. In OneSight, 

NetBIOS authentication allows access to data for the Service 

Monitor and finding components on Windows systems. 

OID – Object Identifier. A sequence of integers used to represent a 

node in the MIB tree. OIDs tell the SNMP data source which 

managed objects to monitor. See also MIB. 

OneSight Console – The tool you use to configure and view the 

status of your monitor groups. You can use a web browser on the 

OneSight Server to view the Console, or you can open a web 

browser on a remote machine. 

OneSight Remote Agent – An optional agent that you can install on a 

machine you want to monitor. This agent is necessary if you want to 

monitor remote logging information for the machine or execute a 

remote script, such as a system reboot if an alert occurs. 


Glossary 

OneSight Server – The server that runs OneSight. This is an 

Windows NT or Windows 2000 machine that manages all the 

performance statistics and the alerts that may be associated with 

them. You can use a web browser on the OneSight Server to view 

the Console, or you can open a web browser on a remote machine. 

Operator – The category of OneSight users that does not have 

access to any of the Configure pages within the Empirix OneSight 

Console. The online help available to Operators does not show any 

topics pertaining to OneSight configuration. See also Administrator. 

Perfmon – Performance Monitor. A Microsoft tool that runs on 

Windows NT and Windows 2000 platforms. Perfmon is a graphical 

tool for measuring the performance of your own computer or other 

computers on a network. 

Ping – Packet Internet Groper. A utility that determines whether a 

specific IP address is accessible. 

Port – In TCP/IP and UDP networks, an endpoint to a logical 

connection. The port number identifies what type of port it is. For 

example, port 80 is used for HTTP traffic. 

Priority – Alerts associated with a Critical status have a higher 

priority than those associated with Warning status. You can 

configure different action plans appropriate to these alert priority 

levels. Within profiles, priority determines the order in which 

OneSight responds to alerts associated with profile metrics. For 

example, OneSight triggers an action plan associated with a profile 

that has a priority of High (System) before a profile that has a 

priority of Medium (Application). See also Alert. 

Profile – A default set of performance criteria. When you want to 

monitor a back-end web component such as an IIS server, an Oracle 

database, an Windows NT or Windows 2000 operating system, or a 

UNIX operating system, OneSight provides a profile so you can 

monitor performance of various critical functions carried out by that 

component. You can use a profile as-is, modify it, or create a new 


Glossary 

one. A profile can be applied to a single web component or to 

multiple web components. For example, if you have a web farm of 

multiple NT servers, you can define the same performance criteria 

for all of them in a single profile. When you apply a profile to a 

specific machine, you create a profile monitor. See also Metric and 

Profile monitor. 

Profile monitor – A monitor that uses a number of metrics to test the 

performance of various critical functions carried out by a back-end 

web component. To create a profile monitor, you apply a profile to 

a web component such as an IIS server, an Oracle database, an NT 

operating system, or a UNIX operating system on a specific 

machine. As you add a profile monitor, you will need to identify the 

system and enter system-specific information to describe its 

properties. A profile monitor can be applied to more than one web 

component of the same type and it will use the same set of 

performance criteria for each of those web components. In contrast, 

a dedicated monitor only applies to one web component. When 

adding a dedicated monitor, you always define unique performance 

criteria for the monitor. See also Dedicated monitor, Metric, and 

Profile. 

Proxy server – A server that sits between a client application (such 

as a web browser) and a real server. It intercepts all requests to the 

real server to see if it can fulfill the requests itself. If not, it 

forwards the request to the real server. 

Remote agent – See OneSight Remote Agent. 

Service – Work performed (or offered) by a server. This may mean 

simply serving simple requests for data to be sent or stored (as with 

file servers, email servers, SQL servers, etc.). To see details about 

Windows NT and Windows 2000 Services, click Start and select 

Settings, then Control Panel. In Control Panel, open Services. 

SMTP – Simple Mail Transfer Protocol. A protocol used to 

exchange mail between computers. 


Glossary 

SNMP – Simple Network Management Protocol. A set of rules 

governing the management of networks and the monitoring of 

network devices and functions. See also MIB. 

Solaris – A UNIX-based operating environment developed by Sun 

Microsystems. Originally developed to run on Sun’s SPARC 

workstations, Solaris now runs on many workstations from other 

vendors. 

SSL – Secure Sockets Layer. Netscape’s public key encryption and 

authentication software. Both Netscape Navigator and Internet 

Explorer support SSL, and many web sites use the protocol to obtain 

confidential user information, such as credit card numbers. By 

convention, web pages that require an SSL connection start with 

“https” instead of “http.” OneSight supports SSL when specifying 

URLs for URL monitors. SSL can also be used in combination with a 

proxy server. Up to 128-bit encryption is supported if enabled on 

the browser for the Empirix OneSight server. 

Threshold – A measurement set for a metric that defines what is and 

is not acceptable performance for that metric. 

Trap – To intercept an action or event before it occurs, usually in 

order to do something else. See also SNMP. 

Warning state – A OneSight indicator of the state of a metric, 

monitor, or monitor group. Web components that are in a Warning 

state may require your attention. In OneSight, a Warning state is 

represented by a yellow triangle. When you configure monitors, you 

define the performance criteria that you want to track and the 

conditions under which you want to receive an alert. In response to 

an alert, OneSight can either trigger an action plan, change a 

monitor’s health, or in some cases, do both. 

Web component – Any part of your web site that you would like to 

monitor. This can include devices such as your NT server or UNIX 

web farm, the database that supports your web site transactions, the 

web server software, or mission-critical URLs within your web site. 


Glossary 

Web farm – A cluster of web servers. 

XML – Extensible Markup Language. A language that lets designers 

create their own customized tags to provide functionality not 

available with HTML. 


Glossary 



Index 

Access Control, 813 

Access Control Tab, 462 

Action, 77, 923 

Action Plan, 77, 923 

Action Plan Manager, 636 

Action Plans 

Adding Actions, 638 

Creating, 633 

Modifying, 707 

New, 635 

Not Associated With Alerts, 720 

Retiring, 720 

Specifying, 98 

Symbols, 634 

Triggering, 422 

Actions 

Delay, 680 

Email, 645 

HTTP Post/Get, 690 

Monitor, 683 

Scripting, 663 

SNMP, 668 

SNMP Set, 675 

Socket Connection, 686 

Syslog, 694 

Actions List Manager, 644 

Actions Plans 

e-Mail, 443 

Adding 

Attributes Sets and Values, 735 

Component Types, 575 

Data Sources, 522 

Date Intervals, 844, 847 

Dependency Nodes, 103 

Location Groups, 802 

Metrics, 505 

Monitor Groups, 86 

Multiple Systems, 571 

Profiles, 493 

Systems, 565 

Users, 819 

Adding Actions, 638 

Administration Notifications, 905 

Administrator, 923 

Advanced Settings, 251, 312, 352 

Agent, 923 

Agent Proxy, 39 

Uninstalling, 57 

Agent Proxy Installation, 40 

Agents 

SNMP, 74 

Updating Remotely, 69 

Alert, 77, 923 

Alert Dependencies 

Specifying, 99 

Alert Dependencies Tab, 99 

Alert Dependency Tree, 101 

Alert Editor, 425 

Alert Specifying 

Alert Dependencies, 99 

Alerts 

Adding to Monitors, 419 

Changing for Multiple Monitors, 

472 

Defining, 102 

Editing Response, 447 

Threshold, 444 

Alerts Rights, 810 

Alerts Tab, 419 

Alphanumeric, 924 

Applications, 3 

ASCII, 924 

Assigning Attributes, 741 

Attribute Matrix Views, 747 

Attributes 

Assigning, 741 

933

Index 

Configuring, 735 

Attributes Sets and Values 

Adding, 735 

Removing, 740 

Attributes Tab, 457 

Authentication, 115 

Authentication Data, 292 

Avaya Communication Manager 

Profile Monitors, 116 

Bad Strings, 416 

Bulk Location Modification, 625 

CDRs 

Viewing, 893 

Cisco Call Manager Profile 

Monitors, 129 

Clients 

PC, 7 

UNIX, 7 

Cloning 

Metrics, 505 

Profiles, 493 

Codec Comparison Chart, 884 

Community String, 924 

Component Types, 575 

Components, 76 

Compound Metric Monitors, 153 

Configuration Data, 66 

Configuration Rights, 808 

Configure Monitors Page, 113 

Configuring 

Attribute Matrix Views, 747 

Attributes, 735 

Avaya Communication Manager, 

116 

Cisco Call Manager, 129 

Compound Metric, 153 

Custom Status Views, 753 

Database Monitors, 167 

Database Storage, 795 

Date Intervals, 844 

DNS Monitors, 181 

Downtime, 723 

Event Log Monitors, 238 

FTP Monitors, 245 

Gomez GPN Monitors, 186 

Gomez GPN Profile Monitors, 

191 

IDMC Profile Monitor, 151 

JMX Monitors, 215 

LDAP Monitors, 252 

Locations, 452 

Locations, 795 

Log File Monitors, 256 

Mail Monitors, 264 


Monitors, 113 

OneSight Call Statistics Profile 

Monitors, 196 

OneSight Probe Monitors, 201 

OneSight Voice Quality - 

Advanced Profile Monitors, 

376 



Oracle OpenScript Profile 

Monitors, 272 

Oracle Test for Web Applications 

Monitors, 282 

Perfmon Monitors, 293 

Ping Monitors, 302 

Port Monitors, 306 

Process Monitors, 313 


Roles, 805 

Saved Status Groupings, 742 

Service Monitors, 318 

SNMP Monitors, 323 

SNMP Trap Monitors, 332 

State Machines, 365 

Systems, 565 

TCP Socket Monitors, 338 

URL Monitors', 344 

User Groups, 814 

Users, 805 

Virtual Agent Monitors, 356 

Voice Quality - Basic Profile 

Monitors, 371 

Voice Watch Monitors, 225 

Voice Watch Profile Monitors, 

231 

WMI Monitors, 387 


Index 

XMS Systems, 887 

Configuring Locations, 798 

Console, 927 

Cookie, 924 

CPU System, 577 

Creating 

SLAs, 829 

SLOs, 833 

Critical State, 924 

Custom Reports, 849 

Custom Status Views, 753 

Adding, 754 

Area, 770 

Creating Items, 758 

Deleting, 775 

Example, 775 

Frame, 772 

Image, 767 


Monitor Group and Monitor, 760 

Report, 758 

Text, 765 

Data Collector, 924 

Installing, 19 

Removing, 55 

Requirements, 32 

Windows Installation, 32 

Data Source, 925 

Adding, 522 

for Status Chart, 96 

Data Sources 

Custom Reports, 852 

JDBC, 524 

JMX File, 526 

Log File, 527 

NT Event Log, 532 

Perfmon, 535 

Ping, 537 

Port, 538 

Process, 539 

Service, 540 

SNMP, 542 

SNMP Trap, 546 

Socket, 548 

UNIX, 551 

URL, 554 

Virtual Agent, 557 

WMI, 561 

Database 

Moving, 907 

Transferring Configuration Data, 

66 

Using a Remote, 63 

Database Backup, 65 

Database Errors, 910 

Database Information 

Viewing, 58 

Database Instance System, 586 

Database Log File System, 586 

Database Maintenance, 63 

Database Monitors, 167 

Query Tab, 174 

Database Storage 


Database System, 579 

DataDirect Setup, 177 

Date Interval 

Adding, 844, 847 

Date Intervals 


Dedicated Monitor, 925 

Dedicated Monitors, 2 

Default Ports, 46 

Defining 

Alerts, 102 

Delay Actions, 680 


Deleting 

Location Groups, 803 

Roles, 813 

SLAs, 841 

SLOs, 844 

VQ Probes, 884 

Dependency Node Editor, 102 

Dependency Nodes 

Adding, 103 

Diagnostics Tab, 893 

Dial Numbers List 

Editing, 885 

Disabling 


Monitors, 471 

Index 935

Index 

System Components, 466 

Disk System, 586 

Diskperf, 51 

Displaying 

Windows Event Viewer, 451 

DNS, 925 

DNS Monitors, 181 

Downtime 


Monitor, 463 


Editing 

Dial Numbers, 885 


E-mail Action Plans, 443 

Email Actions 

Global, 700 


Email Actions, 645 

E-mail Connection Validation, 271 

Email Connections 

Validating, 653 

Email Notification 

Replying To, 651 

Email Validating Email 

Connections, 653 

e-Monitor 

Features, 1 

Enabling 


Monitors, 471 


Escalation Timeout, 925 

Event Log Monitors, 238 

Exporting 

Monitors, 399 

Profiles, 504 

Exporting Scripts, 279, 280, 291 

File System, 589 

FTP Monitors, 245 

Gauge Reports 

Creating, 853 

Getting Started, 75 

Global Action List Manager, 698 

Global Action Options, 698 


Global Actions 

Email, 700 

Incoming E-Mail, 705 

Scripting, 706 

Global Metric Manager, 504 

Global Options, 824 

Glossary, 923 

Gomez GPN Monitors, 186 

Gomez GPN Profile Monitors, 191 

Good State, 925 

Good Strings, 416 

H323 Parameters, 878, 879 

Host Name, 925 

HTTP, 925 

HTTP Post/Get Actions, 690 


HTTPS, 18, 926 

IDMC Profile Monitors, 151 

IIS, 926 

Importing 

Metrics, 502 

Monitors, 400 

Profiles, 500 

Importing Scripts, 278, 290 

Importing Systems, 571 

Installing 

Agent Proxy, 40 


Remote Agents, 19 

Installing OneSight, 12 

Installing OneSight, 11 

Interface System, 590 

Introduction, 1 

ISP, 926 

JDBC Data Source, 522, 524 

JDBC Driver Options, 168 

JMX Data Source, 526 

JMX Monitors, 215 

Latency, 926 

LDAP Monitors, 252 

Licenses, 62 

Load Balancer System Information, 

592 

Load Balancing, 926 

Location Groups 

Adding, 802 


Index 

Deleting, 803 

Location Tab, 452 

Locations 

Changing for Multiple Monitors, 

481 


Locations Tab, 798 

Log File Data Source, 522, 527 

Log File Monitors, 256, 416 

Log Profile Metrics, 439 

Mail Monitors, 264 

Mail Server, 704 


Message Templates, 654 

Metric, 926 

Metric Editor 

Access Control Tab, 521 

Attributes Tab, 518 

Data Sources Tab, 518 

General Tab, 511 

Metric Performance Data, 416 

Metrics 

Adding, 505 

Adding to Profiles, 498 

Cloning, 505 

Creating, 901 

Importing, 502 

Managing Non-operational, 465 


Modifying Data Source, 564 

Removing, 563 

Removing from Profiles, 498 

Metric's Sampling Interval, 562 

MIB, 927 

MIB Browser, 898 

Modifying 

Action Plans, 707 

Alerts for Multiple Monitors, 472 

Metrics, 505 


Monitors, 464 

Multiple Monitor Locations, 481 

Profiles, 493 

SLAs, 840 

SLOs, 842 

Users, 821 

Monitor, 77, 927 

Monitor Actions, 683 


Monitor Attributes Tab, 457 

Monitor Group, 76, 927 

Monitor Group Editor, 88 

Monitor Groups 

Adding, 86 

Adding Monitors to, 109 


Downtime, 106 

Enabling/Disabling, 107 

Modifying, 90 

Removing, 108 

Smartlink, 104 

Monitor Groups Page, 87 

Monitor Groups Tab, 461 

Monitors 

Adding Alerts, 419 

Adding Multiple, 486 

Adding to Monitor Groups, 109 


Downtime, 463 

Enabling/Disabling, 471 

Exporting, 399 



Removing, 472 

Testing, 467 

Multiple System Discovery, 623 

NetBIOS, 927 

Network Devices, 4 

Network Performance, 4 

NT Event Log Data Source, 522, 

532 

ODBC Setup, 176 

OID, 927 

OneSight Call Statistics Profile 

Monitors, 196 

OneSight Probe Monitors, 201 

OneSight Server Requirements 

OneSight Server, 5 

OneSight Service 

Starting, 57 

Stopping, 58 

Index 937

Index 

OneSight Voice Quality - Advanced 


OneSight Voice Transaction Profile 

Monitors, 205 

Opening 

the System Editor, 565, 577 

Operator, 928 

Oracle Database System, 579 

Oracle ODBC Setup, 176 

Oracle OpenScript Profile Monitors, 

272 

Oracle Test for Web Applciations 

Monitors, 282 

Out of Disk Space, 906 

Passwords, 824 

Changing System, 628 

Changing URL, 631 

Changing Virtual Agent, 631 

Changing Visual Script, 629 

Pattern Matching, 415 

Perfmon, 50, 928 

Perfmon Data Source, 522, 535 

Perfmon Monitors, 293 

Ping, 928 

Ping Data Source, 522, 537 

Ping Monitors, 302 

Port, 928 

Changing, 18 

Port Data Source, 538 

Port Monitors, 306 

Port System, 600 

Ports 

Default, 46 

Priority, 928 

Privileges 

User, 823 

Process Data Source, 539 

Process Monitors, 313 

Process System, 601 

Profile, 929 

Profile Manager, 404, 492 

Profile Monitor, 929 


Profile Symbols, 492 

Profiles 

Adding Metrics, 498 

Exporting, 504 


Main Settings, 494 

Removing, 500 

Removing Metrics, 498 

Updating, 18 

Profiles, 489 

Proxy Server, 929 

Proxy Server Settings, 190, 195, 

230, 237 

Proxy Settings, 281, 355 

Proxy Settings 

Changing, 487 

Query Tab, 174 

Regular Expressions, 415 

Testing, 896 

Remote Agent, 927 

Removing, 55 

UNIX Workstation Installation, 

27 

Windows Installation, 24 

Remote Agent Update, 69 

Remote Agents 

Installing, 19 

Requirements, 23 

Running UNIX, 30 

Remote Data Collectors, 20 

Removing 

Attributes Sets and Values, 740 


Metrics, 563 


Monitors, 472 

Profiles, 500 



User Groups, 818 

Report Templates, 849 

Properties File, 851 

Running, 850 

Sample Configuration File, 857 

Reporting Rights, 811 

Requirements 

Client Web Browser, 7 


OneSight Server, 5 


Index 


Web Components, 8 

Retiring Action Plans, 720 

Roles 


Deleting, 813 

Sample Every Settings, 395 

Sample Locations, 452 

Sampling Interval, 562 

Saved Status Groupings, 742 

Scripting Actions, 663 

Global, 705, 706 


Scripts 

Exporting, 279, 280, 291 

Importing, 278, 290 

Server, 928 

Server Port, 18 

Service, 929 

Service Data Source, 522, 540 

Service Level Agreements, 827, 

849, 863, 895 

Service Monitors, 318 

Service System Information, 593 

Session Timeout, 18 

SIP Parameters, 878, 879 

Skinny Parameters, 878 

SLA 

Creating, 829 

Deleting, 841 


SLO 

Creating, 833 

Deleting, 844 


SmartLink Tab, 453 

Smartlinks 


SMTP, 929 

SNMP, 49, 930 

SNMP Actions, 668 


SNMP Agent, 74 

SNMP Data Source, 522, 542 

SNMP Monitors, 323 

SNMP Set Actions, 675 


SNMP Trap Data Source, 523, 546 

SNMP Trap Monitors, 332 

Socket Connection Actions, 686 


Socket Data Source, 548 

Solaris, 930 

Specifying 

Action Plans, 98 

SQL 2005 Configuration, 17 

SQL Database System, 582 

SSL, 18, 930 

Starting Remote Agents, 31 

Starting the OneSight Service, 57 

State Machines, 365 

Status Chart 

Specifying the Data Source, 96 

Status Rights, 812 

Stopping Remote Agents, 31 

Stopping the OneSight Service, 58 

Support Utilities, 903 

syslog Actions 


Syslog Actions, 694 

System Adding 



Adding, 608 

Discovering Multiple, 623 


Removing, 627 

System Editor 

Opening, 565, 577 

System Modifying 


System Properties Information, 594 

System Requirements, 4 

Systems 

Adding, 565 

Adding Multiple, 571 


CPU, 577 

Database, 579 

Database Instance, 586 

Database Log File, 586 

Disk, 586 

Index 939

Index 

File, 589 

Interface, 590 

Load Balancer, 592 

Multiple Location Modification, 

625 

Oracle Database, 579 

Port, 600 

Process, 601 

Properties, 594 

Service, 593 

SQL Database, 582 

VM, 604 

VMProcess, 605 

Web Server, 606 

TCP Socket Monitors, 338 

Testing Monitors, 467 

Threshold, 930 

Threshold-based Alerts, 444 

Trace Route, 895 

Trap, 930 

Triggering Action Plans, 422 

Troubleshooting, 905 

Uninstalling OneSight, 53 

UNIX Data Source, 523, 551 

Updating Profiles, 18 

URL Data Source, 523, 554 

URL Monitors, 344 

User Groups 


Removing, 818 

User Rights, 823 

Users 

Adding, 819 



Validating 

E-mail Connections, 271 

Virtual Agent Data Source, 557 

Virtual Agent Monitors, 356, 417 

VM System Information, 604 

VMProcess System Information, 

605 

Voice Quality - Basic Profile 

Monitors, 371 

Voice Watch Monitors, 225 

Voice Watch Profile Monitors, 231 

VQ Probes 

Deleting, 884 

Editing, 871 


Warning State, 930 

Web Browser Requirements, 7 

Web Component, 930 

Web Component Configuration, 47 

Web Components Requirements, 8 

Web Farm, 931 

Web Server System, 606 

Windows Event Viewer, 451 

WMI Data Source, 561 

WMI Monitors, 387 

XML, 931 

XMS Systems 


XP_CMDSHELL, 17

OneSight Administrator Guide

Create successful ePaper yourself

Delete template?

Save as template?