BMC ProactiveNet User Guide

Supporting
BMC ProactiveNet version 8.5
October 2010

www.bmc.com

Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.

United States and Canada
Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 1 713 918 8800 or 1 800 841 2031 Fax 1 713 918 8000

Outside United States and Canada
Telephone +01 713 918 8800 Fax +01 713 918 8000

© Copyright 2009-2010 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. BladeLogic and the BladeLogic logo are the exclusive properties of BladeLogic, Inc. The BladeLogic trademark is registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BladeLogic trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. AIX, Current, NetView, Notes, Tivoli, and WebSphere are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Linux is the registered trademark of Linus Torvalds. Oracle is a registered trademark of Oracle Corporation. EJB, JVM, Java, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries. UNIX is the registered trademark of The Open Group in the US and other countries. The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation.

Restricted rights legend
U.S. Government Restricted Rights to Computer Software. UNPUBLISHED—RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.

Customer support
Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support. From this website, you can ■ ■ ■ ■ ■ ■ ■ ■ read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for problems similar to yours and possible solutions order or download product documentation download products and maintenance report a problem or ask a question subscribe to receive proactive e-mail alerts find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers

Support by telephone or e-mail
In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to customer_support@bmc.com. (In the subject line, enter SupID:yourSupportContractID, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC
Have the following information available so that Customer Support can begin working on your issue immediately: ■ product information ― ― ― ■ product name product version (release number) license number and password (trial or permanent)

operating system and environment information ― ― ― ― ― machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level

■ ■ ■

sequence of events leading to the problem commands and options that you used messages received (and the time and date that you received them) ― ― ― product error messages messages from the operating system, such as file system full messages from related software

3

License key and password information
If you have questions about your license key or password, contact BMC as appropriate for your location: ■ ■ ■ (USA or Canada) Contact the Order Services Password Team at 1 800 841 2031, or send an e-mail message to ContractsPasswordAdministration@bmc.com. (Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or send an e-mail message to password@bmc.com. (Asia-Pacific) Contact your BMC sales representative or your local BMC office.

4

BMC ProactiveNet User Guide

Contents
Chapter 1 Introducing the BMC ProactiveNet Operations Console 13 Accessing the Operations Console ...............................................................................13 Choosing the console type .............................................................................................15 Navigating the Operations Console .............................................................................16 Navigation pane ...................................................................................................17 Navigation tree .....................................................................................................23 Operations Console views ..................................................................................29 Breadcrumbs .........................................................................................................31 Chapter 2 Working with events 33 Event views in the Main drawer of the navigation pane ..........................................33 Customizing the display of the event list ....................................................................34 Viewing the default event list for All Event Collectors .............................................36 Viewing further information for a specific event from the Tools Menu ................38 Behavior of popup windows for Tools Menu options ...................................41 Viewing the event list for a specific component in the navigation tree ..................41 Selecting the type of event list to view ........................................................................43 Intelligent Events Details template ...................................................................44 Creating a new template for event list columns .........................................................45 Editing a default or user-defined template for event list columns ..........................46 Copying an existing template for event list columns ................................................46 Deleting a user-defined template for event list columns ..........................................47 Applying a default, global, or user-defined template for event list columns ........47 Adding a column to an event list .................................................................................48 Deleting a column from an event list ...........................................................................48 Viewing the event Details Notebook ...........................................................................49 Viewing related events ...................................................................................................52 Refreshing the event list .................................................................................................52 Organizing events in the event list ...............................................................................53 Using event and component folders .................................................................53 Filtering events .....................................................................................................64 Searching events ...................................................................................................71 Sorting events .......................................................................................................72 Creating shortcuts for Tools Menu options ................................................................74 Performing event operations .........................................................................................76 Exporting and copying event information ..................................................................79

Contents

5

Executing remote actions ...............................................................................................80 Ping Event mc_host_address .............................................................................81 TraceRoute to Event mc_host_address .............................................................82 Send EVENT as SMTP E-mail ............................................................................82 Modify Slot Value ................................................................................................82 Show Remote Action Environment ...................................................................82 Setup Sending SMTP E-Mails - Windows Only ..............................................83 Trigger Remedy Incident for Event ...................................................................83 BMC Atrium Orchestrator workflows ..............................................................83 Launching an originating BMC ProactiveNet Server ...............................................86 Customizing the display of events ..............................................................................86 Viewing the event list for remote cells ........................................................................88 Operations possible on the event list for remote cells ....................................91 Viewing predictive events .............................................................................................92 Viewing all abnormalities ..............................................................................................93 Adding a column to an event list for an abnormality ....................................95 Deleting a column from an event list for an abnormality ..............................95 Filtering event display for All Abnormalities ..................................................97 Viewing further information for an abnormality ............................................99 Viewing events and abnormalities by service ..........................................................100 Viewing further information for All Services => Grid View ....................102 Viewing monitor and device information under the All Services => Grid View ....................................................................................................................103 Viewing services in a hierarchical tree ......................................................................105 Controlling the display in the All Services => Tree View ........................106 Viewing events by group .............................................................................................107 Default groups ....................................................................................................110 Filtering event display for All Groups ............................................................110 Viewing further information for All Groups => Grid View ......................111 Viewing monitor and device information under the All Groups => Grid View ....................................................................................................................112 Viewing events for groups in a hierarchical tree .....................................................114 Controlling the display in the Tree View .......................................................115 Viewing events by device ............................................................................................116 Filtering event display for All Devices ...........................................................119 Viewing further information for All Devices ................................................120 Viewing events for monitored services .....................................................................121 Viewing further information for All Monitors ..............................................122 Acknowledging events ................................................................................................122 Closing events ...............................................................................................................124 Managing configuration changes ...............................................................................125

6

BMC ProactiveNet User Guide

Managing data collection .............................................................................................126 Distinction between new and upgrade users ................................................127 Pausing data collection .....................................................................................127 Resuming data collection ..................................................................................129 Diagnostics ..........................................................................................................129 Examining current data (FlashCheck) ............................................................130 About the Canvas view ................................................................................................131 Canvas view modes ...........................................................................................131 Canvas view details ...........................................................................................131 Setting up and using the Canvas view .....................................................................132 Using Edit mode to set up the Canvas view ..................................................133 Using View mode to monitor objects in the Canvas view ...........................138 About the Tile view ......................................................................................................140 Tile view modes .................................................................................................140 Tile attributes ......................................................................................................140 Tile preferences and defaults ...........................................................................141 Tile view details .................................................................................................142 Setting up and using the Tile View ...........................................................................143 Using Edit mode to change preferences in the Tile view .............................143 Saving tile preferences as defaults ..................................................................145 Using View mode to monitor objects in the Tile view .................................146 About the graph view ..................................................................................................147 Graph view modes .............................................................................................148 Graph view details .............................................................................................148 Setting up and using the Graph View ......................................................................149 Using Edit mode to change preferences in the Graph view ........................150 Using View mode to monitor objects in the Graph view .............................152 Viewing the Tile, Canvas, or Graph view Details notebook ..................................154 Chapter 3 Determining the probable cause for an event 159 What is probable cause analysis? ...............................................................................159 How BMC ProactiveNet performs probable cause analysis on events ................159 Time correlation .................................................................................................162 User-defined filters ............................................................................................163 Knowledge patterns ..........................................................................................163 Service model relationships .............................................................................164 Global relationships ...........................................................................................164 Data correlation ..................................................................................................165 Scoring .................................................................................................................165 Configuring BMC ProactiveNet to perform probable cause analysis ...................165 Configure complete monitor coverage ...........................................................165
Contents 7

Assign correct device types ..............................................................................166 Create monitors under the correct devices ....................................................166 Create service models for interdependent CIs ..............................................166 Associate monitors to the proper CI ...............................................................166 Set a polling interval of 5 minutes or less .......................................................167 Establish a reliable baseline ..............................................................................167 Ensure sub-categories are defined for external events .................................168 Viewing probable cause analysis for an event .........................................................168 Customizing the display of the Probable Cause Analysis list ...............................170 Filtering unrelated events to find probable cause ....................................................172 Changing the time correlation filter ................................................................172 Enabling user-defined filters ............................................................................173 Saving recurring conditions as a known probable cause ........................................174 Probable cause analysis in a scalable deployment environment ...........................175 Limitations of probable cause analysis in a scalable environment .............176 Probable cause analysis in a virtual environment ...................................................177 How probable cause analysis handles VMotion events ..............................177 Limitations of probable cause analysis in a virtual environment ...............177 Chapter 4 Event administration 179 Overview ........................................................................................................................179 For upgrade users ..............................................................................................179 Accessing the event administration options ..................................................180 Understanding event thresholds ................................................................................180 Baselines ..............................................................................................................182 Auto-baseline ......................................................................................................183 How abnormalities are generated ...................................................................183 Setting event thresholds ....................................................................................184 Managing event rules ...................................................................................................187 Default event rules .............................................................................................188 Filtering the event rule list ................................................................................190 Event rule types ..................................................................................................191 Event rules or event management policies ....................................................192 Adding a basic event rule type .......................................................................192 Adding an advanced rule type ........................................................................198 Editing a basic or an advanced rule ................................................................200 Deleting an event rule .......................................................................................201 Updating event actions .....................................................................................201 Enabling and disabling event rules .................................................................202 Supplying arguments to a server command ..................................................202 Defining email groups .......................................................................................204
8

BMC ProactiveNet User Guide

...............................................................................266 Monitor information tab ...........................................................270 Additional information for changing graph display .276 Sharing the graph page ................................................................................................................257 Creating a pie graph .........................................216 Managing the AlarmPoint integration ...................................229 Managing BMC ProactiveNet events BMC Atrium Orchestrator (formerly known as BMC Run Book Automation) .268 Button options .................................................................................261 Customizing monitor graphs ................................................................................................................................................................................................................271 Adjusting graph axes ........265 Attributes and indicators tab ...........................218 Managing BMC ProactiveNet events in the BEM environment .........................................Event actions: managing BMC ProactiveNet events in external environments ..............................................................205 Managing BMC ProactiveNet events through Run Command on Server ........276 Generating PDF ...273 Displaying all abnormalities for a graph .................................................................................................................................................................................250 Creating a line or area graph ............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................245 Integrating BMC ProactiveNet with Service Level Management ...........245 For upgrade users ...........268 Creating an individual/multiple monitor graphs ....................................................216 Managing BMC ProactiveNet events in the Remedy environment ......... 215 Managing BMC ProactiveNet events through Diagnostic Commands on the BMC ProactiveNet Server ..........................................................................256 Creating a Top N graph ...............................259 Creating a dial gauge graph .....251 Creating a x-y graph ...............................................237 Reducing events ...........205 Managing BMC ProactiveNet events through SNMP traps .......................................................................................................................................................................................244 Customizing event text ..247 Chapter 5 Customizing graphs 249 Creating custom graphs .............277 Chapter 6 Managing Views 279 What is a view? ..........................................................272 Exporting graph data to Excel .......................................................264 Graph tab .................................................................................................................................................................................................................................................275 Mailing the graph page .............279 Contents 9 ........................249 Limitations ..................................................................................

........................................................................................................................................................................................................325 Additional options ...................331 Printing a report ..............329 Generating a report ...........................................348 BMC ProactiveNet User Guide 10 ...................................................287 Managing view templates ...............................................Navigating the Views & Graphs drawer ..................................................287 Managing graph thumbnails for a view .............................................................................................................................................................331 Managing all reports .............................................................................................................................345 Recalculating SLO data for modified time periods .............................................................................329 Adding a report to a view ........................338 Deleting SLOs ...............................................................................................................................................................327 Adding comments to a report .............................................................335 The SLO Management Console ..................326 Deleting instances ......336 Managing SLOs ...........332 Points to Remember ................................341 Managing SLO types during SLO configuration .................................................................................................................................................330 Mailing a report ...................................................300 Asset ........................................................335 Customizing basic settings for SLO data display .....................298 Copying an existing report ..........294 Deleting a report ..............281 Customizing the basic screen layout on the Views tab .................................................................................................................................................................................................341 Managing schedules during SLO configuration ...........................299 Report types available in BMC ProactiveNet .................329 Exporting to Portable Document Format (PDF) ..........................298 Changing email settings in a report .....................................................................................................................................344 Requesting guidance for setting SLO thresholds ................................289 Chapter 7 Generating Reports 293 Overview ......................................................................................................................................................................................................................................................................................................................................................................................................................293 Creating or editing a report ............................................................................................................................................................337 Creating or editing an SLO ............................................................................................................................................................301 Report Scheduler ............330 Exporting to CSV ..............................342 Managing range sets during SLO configuration ...............................................................................................279 Managing views .............................327 Disable generation ..........332 Chapter 8 Managing service levels 335 What is an SLO? ...................................................................................................................................................328 Scheduling ............................................................................................................................

......................................................................................................................361 Controlling the display in the SLO Tree ..................................................................................................................................371 Special notes ...................................................367 Adding a downtime schedule ................................398 Overview of the Intelligent Event Suppression screen ...........................................372 Tracking changes to BMC ProactiveNet objects ................................................384 Managing relationships ......376 Managing attribute sets ..............................................................................................................................................................................................................410 Importing and exporting users ..................................................................................................................................................................................................................................................................................................................................................412 Contents 11 ......361 Viewing SLOs in a hierarchical tree ..............................358 Accessing the Watch List ...................380 Pausing baseline calculation ............351 Customizing the display of SLO status information .......................................................397 Defining Intelligent Event Suppression relationships .........................360 Viewing a graphical history of SLO compliance and violations ...............................................................................352 Viewing SLO compliance details and history .402 Adding or editing an Intelligent Event Suppression relationship ..........................................................................................366 Usage scenario ....................................................................................................................................................................350 Viewing the current status of SLOs ................................................................................................373 Viewing BMC ProactiveNet and PATROL agent statuses ....................................357 Comparing compliance objectives with actual results ............359 Filtering SLO records in the Watch List ..359 Drilling down to an individual SLO in the Watch List .............................................................Resetting SLO compliance data ....................374 Drill down from the agent status table .............400 Enabling or disabling Intelligent Event Suppression relationships ...................................................381 Resetting a baseline .................352 Viewing a summary of details and compliance metrics for an SLO .................................................362 Accessing further information from the SLO Tree .........................354 Viewing violation details for an SLO ....................................................................................................355 Viewing a history graph for an SLO ...............................383 Creating a separate baseline for seasonal or special dates .....................363 Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 365 Activating and deactivating data collection ...............................................360 Viewing instance details ...............................................................369 Edit/Delete downtime schedule ...................................................................377 Managing baselines ..............................................................................365 Scheduling downtime ...........409 Managing schedules ...........403 Deleting a relationship ............................................................357 Viewing a breakdown of SLO metrics for various time periods ................................................................

..............................................................................426 Creating new BladeLogic content ........................................435 Slots used during probable cause analysis ................................................................Viewing BMC ProactiveNet software information .................................430 Viewing BMC BladeLogic device history information .....................415 Viewing BMC ProactiveNet performance diagnostics .....415 Viewing BMC ProactiveNet license usage ......................................................................................431 Appendix A Event information used in probable cause analysis 435 Event classes not used by probable cause analysis .........................................421 Additional change information using snapshot job execution ..............................................................................................417 Downloads tab ...........415 Installation history .............................................................................................................................................................................................440 12 BMC ProactiveNet User Guide .................................428 Creating packages to deploy ProactiveNet Agents to BMC BladeLogic managed systems ...................................................................438 Monitors related to VMware ................................................................................................................................................................419 Setting up the integration between BMC BladeLogic and BMC ProactiveNet ...........................418 Chapter 10 Integrating with BMC BladeLogic 419 Benefits of BMC BladeLogic integration .............................................425 Installing the BMC ProactiveNet content .................................................................................................

5” on page 14 and “To enable multiple sessions on Internet Explorer version 8” on page 14. and password. use the following default values: — user name: admin — password: admin Chapter 1 Introducing the BMC ProactiveNet Operations Console 13 . For multiple logons. 3 In the BMC ProactiveNet Logon screen. 2 Enter the host name or IP address of the BMC ProactiveNet server. see “To enable multiple sessions on Firefox version 3. and launching different tabs within the same browser. Avoid multiple logons using the same browser. user name. enter a valid user name and password. Note To log on to the BMC ProactiveNet Operations Console 1 Open a Web browser. see the BMC ProactiveNet Getting Started Guide. For information about supported browser versions. ■ To log on for the first time after installation.1 Introducing the BMC ProactiveNet Operations Console Accessing the Operations Console The BMC ProactiveNet server is a Web-based application that you can access by logging on to the BMC ProactiveNet Operations Console using supported Web browsers such as Internet Explorer and Mozilla Firefox. as this might result in NO DATA or other unpredictable results.

3 Create a shortcut to Firefox. click Edit. execute the command Firefox.exe on your desktop or quickbar for each profile you made.5 By default. Related Topics Choosing the console type on page 15 Navigating the Operations Console on page 16 To enable multiple sessions on Firefox version 3. "F:\Program Files\Mozilla Firefox\firefox. 3 Enter the old password and the new password. BMC ProactiveNet encrypts the information relay from the Web interface for additional security. If you use HTTPS. To enable multiple sessions on Internet Explorer version 8 1 Go to File => New Session or 14 BMC ProactiveNet User Guide . 5 In the Target field specify the profile to use when launching Firefox. Firefox shares one session across all browser windows that you open. 2 In the General tab.exe -P. 6 Create a new environment variable MOZ_NO_REMOTE with a value 1. 2 Create as many profiles that you need from the Profile Manager window. 1 From the command line. For example. 7 Click on each Firefox icon and a separate session for each of your browser windows will open. and then click Apply. click the link Switch to Secure Mode on the log on page. To change your Operations Console password 1 Click the Options link at the top the Operations Console. Secure connection mode is indicated by the text You are using a secure connection now. 4 Right-click the icon for each shortcut and open the Properties window.Accessing the Operations Console Note The default protocol for this connection is HTTP. To log on using a secure HTTPS connection. 4 Click Log On. under User ID and Password.exe” -P “ProfileA".

see To set the default logon console on page 15. Table 1 on page 15 lists the console types available and the characteristics of each type. Table 1: Characteristics of console types Console Type Operations Console Purpose Displays an integrated view of all the events. You can select the appropriate console type from the Change Console list at the top of the Operations Console. devices. and monitors The Operations Console is the default console displayed when you log on to BMC ProactiveNet. Related Topics Accessing the Operations Console on page 13 Navigating the Operations Console on page 16 Chapter 1 Introducing the BMC ProactiveNet Operations Console 15 . measure. under Layout Preferences. and track SLOs. 2 In the General tab. Choosing the console type The BMC ProactiveNet Operations Console provides options to navigate through the system and view related information. abnormalities. To set the default logon console 1 Click the Options link at the top of the Operations Console.Choosing the console type 2 Add the -nomerge parameter to the end of the target on its properties page to launch a new window from a shortcut and double-click the shortcut icon. SLO Management Console Displays an integrated view of all Service Level Objectives (SLOs) These business views help define. services. 3 Click Apply. To change this setting. A window with a new session will open. groups. Several console views are available based on assigned access rights. select the console type that you want to set as the default when you log on to BMC ProactiveNet.

Use the view pane to view events and information related to each object. and navigation trees within each navigation drawer to group and select the objects displayed in the Operations Console. Use the smart icons in the toolbar in the Operations Console to switch between different views. “Navigating the Operations Console” on page 16 shows the default view in the BMC ProactiveNet Operations Console and the major areas within this console.Navigating the Operations Console Navigating the Operations Console Use the navigation pane. Figure 1: BMC ProactiveNet Operations Console 16 BMC ProactiveNet User Guide . navigation drawers within the navigation pane.

see “Changing navigation pane options” on page 18. You can select which drawers that you want displayed in the navigation pane by setting options in the Navigation Pane Options dialog box. rename. For details. and “Creating bookmarks in the delete bookmarks of objects and their navigation pane” on page 19 related views that you create in the navigation tree.Navigating the Operations Console Navigation pane In the navigation pane in the Operations Console is a series of drawers and links that enable you to navigate through BMC ProactiveNet. Provides a search mechanism so that you can search for CIs that meet the specified search criteria “Finding configuration items to view” on page 20 Further information Viewing the default event list for All Event Collectors on page 36 Reports Views & Graphs Find CI Related Topics Accessing the Operations Console on page 13 Choosing the console type on page 15 “Hiding the navigation pane” on page 18 Chapter 1 Introducing the BMC ProactiveNet Operations Console 17 . Table 2: Navigation drawers in the Operations Console Navigational element Main Other cells Description Provides access to event lists and displays event information and status Lists available remote cells connected to the BMC ProactiveNet Server and monitored by BMC ProactiveNet Enables you to generate and manage Generating a report on page 329 reports based on data collected by BMC ProactiveNet Provides options for the management of views and graphs in the Operations Console ■ “Managing view templates” on page 289 ■ “Managing graph thumbnails for a view” on page 287 Bookmarks Enables you to view. Table 2 on page 17 describes the available drawers in the navigation pane and discusses their functions. Only you can view and manage the bookmarks that you create.

18 BMC ProactiveNet User Guide . Hiding the navigation pane By default. 2 In the Navigation Pane Options dialog box. box. 3 To make changes to the objects displayed in individual drawers. b In the Other Cells drawer. 4 Perform one of the following actions: ■ Click Apply to save your changes and keep the Navigation Pane Options dialog box open.Navigating the Operations Console Changing navigation pane options If you have the appropriate permissions. the navigation pane is displayed when you log on to the BMC ProactiveNet Operations Console. ■ Click OK to save your changes and close the Navigation Pane Options dialog ■ Click Cancel to close the Navigation Pane Options dialog box without saving your changes. select the cells that you want to display in the cell navigation tree. click on the drawer name and perform the following additional steps. depending on which drawer that you select: a In the Main drawer. click Navigation Pane Options . To set navigation pane options 1 In the title bar of the navigation pane. select the drawers that you want to display in the navigation pane by clicking the check box next to the name of the drawer. you can select the drawers that you want to display in the navigation pane and select the objects that you want to display in the drawers. select the folders that you want to display in the navigation tree. You can adjust the size of the navigation pane or hide the navigation pane To hide the navigation pane 1 In the title bar of the Navigation pane. click the double left arrows .

click on the title bar.Navigating the Operations Console The Navigation pane is collapsed and the title bar is displayed vertically on the left side of the Operations Console. select an object in the navigation tree. To redisplay the Navigation pane. 2 In the right pane. To remove bookmarks 1 In the Bookmarks drawer of the navigation pane. other views are available for the objects associated with the bookmarked device. To create bookmarks 1 In any drawer of the navigation pane. Creating bookmarks in the navigation pane You can quickly access objects that you view frequently by creating a bookmark of the object and its associated view and viewing that bookmark in the Bookmarks drawer in the navigation pane. choose Bookmark Current View The object and view are bookmarked and saved. 4 Click the Bookmarks drawer in the navigation pane to view the bookmarked objects. only the Tile View is available when you view the bookmark. However. However. You cannot select other views of the object from the bookmark. 2 From the Navigation Menu at the top of the Bookmarks drawer. 3 From the Navigation Menu at the top of the drawer. For example. you can organize bookmarks into folders within the Bookmarks drawer and drag and drop the bookmarks among those folders. Note The bookmark does not show the object's status or the hierarchy in the navigation tree. choose Delete. select the object that you want to remove. See “To add a folder to the Bookmarks drawer” on page 20. Chapter 1 Introducing the BMC ProactiveNet Operations Console 19 . if you bookmarked a device that was displayed in Tile View. select a view for the object that you selected in the navigation tree. if you drill down on the device tile from the bookmark.

2 From the Navigation Menu at the top of the Bookmarks drawer. 2 In the Basic tab. To rename bookmark folders 1 In the Bookmarks drawer of the navigation pane. 2 Click on the new folder created in the Bookmarks drawer. Note To perform a basic search for a configuration item 1 In the Navigation pane. An advanced search lets you use a filter with defined parameters. If the user account that you are using to log on to the Operations Console has ReadOnly permissions. 3 Enter the new name for the folder and press Enter. You can now drag and drop bookmarks that you create into the new folder. The name of the folder is changed to an editable field. A basic search lets you search for a specific CI based on name and class type. The name of the folder is changed to an editable field.Navigating the Operations Console To add a folder to the Bookmarks drawer 1 From the Navigation Menu at the top of the Bookmarks drawer. Finding configuration items to view Use the Find CI tool to locate a particular configuration item in a BMC ProactiveNet cell and view it in the Graph View of the Operations Console. 20 BMC ProactiveNet User Guide . the Find CI drawer is not displayed in the navigation pane. choose Add Folder. choose Rename Folder. click Find CI. enter all or part of the name of the component that you want to search for. select the object that you want to rename. 3 Enter the name for the new folder and press Enter.

Chapter 1 Introducing the BMC ProactiveNet Operations Console 21 . For details. These CIs are considered the important components for your business. click Find CI. This number can be configured. select Propagates Priority. For details. see “To create a new filter to perform an advanced search for a configuration item” on page 22. You can drag and drop a CI from the results list to a static folder that you create in the navigation tree in the Main drawer. depending on the number of CIs. If you leave Name contains or Class blank. database. see “#unique_19” Note To use an existing filter to perform an advanced search for a configuration item 1 In the Navigation pane. the search could take a long time. This number can be configured. You can create filters in one of the following ways: ■ By accessing the CI Query Editor in the Find CI drawer. If you select Base Element. folder in the navigation tree in the Main drawer. select a component type. For details about creating static folders. see “#unique_19” ■ In the Add Component Folder dialog box when you create a new component 4 Click Find. application service. such as Computer System. 2 In the Find CI drawer.Navigating the Operations Console 3 From the Class list. For details. and so on. For details. the results list could be very long. click Advanced. All components matching the search criteria appear in the results list at the bottom of the Find CI pane up to a maximum 500. 5 Click Find. see the BMC ProactiveNet Administrator Guide. All components matching the search criteria appear in the results list at the bottom of the Find CI pane up to a maximum of 500. You should refine the search by specifying values in one or both of these fields. see the BMC ProactiveNet Administrator Guide. 3 From the Query list. Also. select the filter that you want to use to perform the search. all service CIs for all classes are returned. 4 To find only those CIs that propagate their priority to causal components.

The query will search for components with all of the attributes that you specify. then the query will search for components with any but not all of the values that you specify. select the type of component that you want to search for. 8 Begin building the parameters for your query by selecting the attributes for the class type that you selected. 2 In the Find CI drawer. click Find CI. select the filter from the Query list and click Edit Queries. select Create New Filter. 6 From the Class list. but specify different values. click Advanced. If you use the same attribute. If you select an existing filter than contains blank entries. indicated by the AND before the attribute names. see “#unique_19” To create a new filter to perform an advanced search for a configuration item 1 In the Navigation pane. click Edit Queries. An asterisk is placed next to the name of the query to indicate that it is global. To display additional attributes.Navigating the Operations Console You can drag and drop a CI from the results list to a static folder that you create in the navigation tree in the Main drawer. 5 (optional) To make the filter available to all users who log on to the operations console. 3 Perform one of the following actions: ■ To use an existing filter to create a new filter. the Find CI search assumes that it is a template and automatically opens the CI Query Editor dialog box. 4 In the CI Query Editor dialog box. expand the query builder options by clicking the plus button next to the Class list. perform the following actions: 22 BMC ProactiveNet User Guide . 7 If necessary. click the plus button next to the attribute name. ■ To create a new filter. indicated by the OR before the attribute names. select Make *Global (all users). Each new attribute that you add narrows and refines the search. 9 When you have finished building the filter. For details about creating static folders.

click Save and enter a name for the filter in the Enter Query Name dialog box. click Find. Also. only you can view and To further organize your display. software. then that tile can be moved to another device folder by using drag and drop. and formal documentation. ■ To execute the search. access that folder. you can drag and drop components from one folder that you create to another folder that you create within the navigation tree and you can drag and drop tiles from the Tile or Canvas view to an existing folder that contains the same type of component.Navigating the Operations Console ■ To save the filter. see “#unique_19” . buildings. people. ■ My Folders: When you create a folder under this node. You can drag and drop a CI from the results list to a static folder that you create in the navigation tree in the Main drawer. Chapter 1 Introducing the BMC ProactiveNet Operations Console 23 . For more information about CIs. Event and component folders are displayed in a hierarchical manner in the navigation tree. Navigation tree The navigation tree shows an at-a-glance synopsis of the events and views. A CI is any component that needs to be managed in order to deliver an IT service. for example. depending on your permissions. For details about creating static and dynamic folders. see the BMC ProactiveNet Service Modeling and Publishing Guide. all BMC ProactiveNet users can view and access that folder. The folders displayed in the navigation tree are divided into the following categories: ■ Global: When you create a folder under this node. You can use the new filter to create a static folder of CI objects or a dynamic folder in the navigation tree. CIs typically include hardware. such as process documentation and SLAs. All components matching the search criteria appear in the results list at the bottom of the Find CI pane and the new filter is displayed in the Query list. you can add event and component folders. including folders for configuration items (CIs) associated with a service model. if the tile represents a device. CIs are under the control of change management. beneath these top-level folders.

Each level of the collector is shown as a node under the event folder. the collector-based permissions on events do not apply when you view an event list from the following locations: ■ Drill-downs from All Groups. By default. you can change how the navigation tree is loaded. If this causes performance issues. For example. the severity icons for a collector dynamically change depending on the severity level of the events for that collector. For example. you might create an event folder for collectors that gather database warning events and allow only operators that are database administrators access to that event folder. Events and components can be grouped in the following ways: ■ Event folders ■ Event collectors ■ Component folders Event folders An event folder is a grouping of collectors that shows the relationship of events or abnormalities through the hierarchy of the navigation tree. Event and component folders Event and component folders enable you to organize cells and collectors to make event displays meaningful for operators. or All Monitors (Grid View and Tree View) ■ All Abnormalities. if there is a Critical event on one of the devices. when you open the navigation tree. This allows you to see the status of devices on your system immediately. or All Monitors nodes in the navigation tree the parent folders) ■ Parent event and component folders (not individual collectors within or outside In the navigation tree.mrl file of the collectors. An event list is associated with 24 BMC ProactiveNet User Guide .Navigating the Operations Console Users traversing the navigation tree can see and perform actions and operations on only those collectors to which they are granted access. see the BMC ProactiveNet Administrator Guide. indicating a Critical event. However. all nodes and subnodes are loaded even if a node is not expanded. All Services. All Services. All Groups. Administrators define event folders and associate them with one or more collectors. based on different roles in the . All Devices. For details. All Devices. then the green icon changes to a red icon.

Event collectors Event collectors gather events for display in an event list to provide operators with meaningful groups of events or abnormalities and to show relationship through the hierarchy of the nodes in the navigation tree. The parent level of a component folder represents all of the events associated with the groups. services. Administrators define component folders and associate them with one or more groups. Table 3 on page 25 shows the icons and describes the objects represented in the navigation tree. services. Chapter 1 Introducing the BMC ProactiveNet Operations Console 25 . The parent level of an event folder represents all of the events or abnormalities associated with the collectors.Navigating the Operations Console the lowest level nodes of an event folder. Event collectors are dynamic or static. Nodes for static collectors remain in the navigation tree whether events are present or not. the Global node contains the following default collectors: ■ All Event Collectors: Displays the entire event collector hierarchy ■ All Abnormalities: Displays all the abnormality events ■ All Services: Displays all the services ■ All Groups: Displays all the groups ■ All Devices: Displays all the devices ■ All Monitors: Displays all monitor categories Based on permissions. or devices. or devices through the hierarchy of the navigation tree. Table 3: Navigation tree objects and definitions Object icon Name and definition Navigation tree top-level node (Global). services. operators click the collector node in the navigation tree. Each level of the component folder is shown as a node under the parent component folder. users can create event and component folders under this node to organize the event view. or devices. To access the event list for a collector. services. Component folders A component folder is a grouping of groups. or devices from several different event lists (collectors) that shows the relationship of groups. Nodes for dynamic collectors appear or disappear from the navigation tree based on whether or not events are present that meet the collectors’ criteria. An event list is associated with the lowest level nodes of a component folder.

and then you can change the status by performing event operations or other actions on the event. For example. if you have configured the event list to use the severity color for the event line. based on permissions. Table 4 on page 26 lists the icons that are displayed in the event list to represent event status. a high severity level for an event in 26 BMC ProactiveNet User Guide . The BMC ProactiveNet Server assigns a status value to each event. a rule can change the status of an event automatically. users can create event and component folders under this node to organize the event view Event group collector. an event group subnode of the navigation tree toplevel node or another event group node Child collector node Child group node Child service node dynamic component folder with less than 500 configuration items Understanding event status The status of an event provides basic information about the event’s response activity. the color of the icon’s background varies with the severity of the event. Table 4: Event status icons Icon Event status Open Closed Acknowledged Assigned Blackout The color of the status icon is always the same.Navigating the Operations Console Object icon Name and definition Navigation tree top-level node (My Folders). In combination with status and priority. the severity level indicates the urgency of the need to take action. However. Also. Understanding event severity Each event has a severity level associated with it that indicates the seriousness of the event.

the event or component folder is displayed in the navigation tree with a Critical (red) severity indicator. For example. but a high severity level for an event in the Open status and with a priority of 1 indicates an urgent need for action. Understanding event priority In addition to a severity level. each event has a priority level. Distinguishing between severity and priority helps you to understand which event requires action first. if one event has a severity of Critical. Table 5 on page 27 lists the default severity levels and colors for the events that appear in the navigation tree and event list and shows the icons used in the event list. Chapter 1 Introducing the BMC ProactiveNet Operations Console 27 .Navigating the Operations Console the Closed status is no cause for alarm. Table 6 on page 28 lists the icons that are displayed in the event list to represent event priority. Table 5: Event severity levels Color red dark orange light orange yellow blue green grey red with a blue border dark orange with a blue border light orange with a blue border faint grey Icon in Event List Severity level Critical Major Minor Warning Information Ok Unknown Predictive Critical Predictive Major Predictive Minor No event The event with the highest severity level in an event or component folder determines the severity indicator that you see for the event or component folder in the navigation tree.

reflected in the priority icon ■ The last event operation performed on the event. Each event’s state depends on multiple factors: ■ Severity. with the direction of the arrow indicating the flow of the action. For information about performing event operations. Assign To. or Unacknowledge Event 28 BMC ProactiveNet User Guide . you can perform a Take Ownership. the state of the event changes according to Table 7 on page 28.Navigating the Operations Console Table 6: Event priority icons Icon Event Priority Priority 1 (highest) Priority 2 Priority 3 Priority 4 Priority 5 (lowest) Determination of event states The event list displays sufficient information for you to recognize an event’s current state quickly. Each arrow represents an action. The circles represent the event states. see “Performing event operations” on page 76. Table 7: Event states resulting from event operations Event operation performed Acknowledge Event Take Ownership Decline Ownership Assign To Close Event Unacknowledge Event Black Out Resulting state Acknowledged Assigned Acknowledged Assigned Closed Open Blackout Figure 2 on page 29 shows how an event in any state is affected by the operations that are valid for that current state. For example. reflected in the status icon When you perform an event operation on an event. if the event is currently in the Acknowledge Event state. reflected in the severity icon and color of the event line (based on the preference selected by the user) ■ Priority. Close Event.

Figure 2: How event operations affect event state Understanding the effect of event status on event count for collectors In the navigation tree (except the top-level node). depending on the object that you have selected in the navigation tree: Chapter 1 Introducing the BMC ProactiveNet Operations Console 29 . this count does not include closed. or acknowledged state. for that event to be in the Acknowledge Event state. The second count indicates the sum of all the events. Operations Console views In the Operations Console. and acknowledged events. blackout. For example. This counter decreases whenever the status changes from open to closed. you should perform an Acknowledge Event or Decline Ownership action. if the navigation tree displays Intelligent Events (8) 11. it means that the number of open intelligent events is 8 and the total number of intelligent events is 11. The first count is enclosed in parentheses and represents the number of unacknowledged (Open) events. assigned. Conversely. assigned. you can use the smart icons in the toolbar to select the following views. each event collector has two event counts.Navigating the Operations Console action. blackout.

However. the operations console changes to a view that is defined for that object type. The view that is available depends on what object that you have selected in the navigation tree.Navigating the Operations Console ■ Event View: displays information about events. The Graph View is available only for CI objects. In this case. When this option is enabled. events can be organized into different collectors and folders in the navigation tree ■ Tile View: displays a dashboard summary of event activity ■ Canvas View: allows you to create a graphical representation of objects that you are monitoring in your environment ■ Tree View or Graph View: the Tree View displays all service groups in a hyperbolic tree for a user-defined duration. you can enable a configuration option that allows the view to be changed automatically. the operations console automatically switches to the default view defined for the object type that you select in the navigation tree. The only exception is if the selected view is not available for a particular object type. The following table lists the default views defined for each object type. Object type Event collectors Event folder All Groups folder Group All Device folder Device All Services folder Configuration item (CI) Component folder Default view Event View Event View Grid View Grid View Grid View Grid View Tile View Graph View Tile View 30 BMC ProactiveNet User Guide . The view stays the same until you select a different view. with the option of expanding the tree to display the contents of the service groups and their infrastructure groups The Graph View displays a graphical representation of the configuration items (CIs) in a service model. Use the Graph View to monitor events for published service models that represent your business services. The same button is used for both views. ■ Grid View: allows you to re-calibrate events in the Event Status chart and display results based on groups set up by the BMC ProactiveNet administrator.

Breadcrumbs As you navigate through the operations console. or view. folder. The number of breadcrumbs that are displayed can be configured. For instructions. The view does not change if you select objects of the same type. You can return to an item by clicking on one of the breadcrumbs. By default. such as a navigation pane drawer.Navigating the Operations Console Note The view changes only if you select an object of a different type in the navigation tree. For details about how to enable this option. see the BMC ProactiveNet Administrator Guide. A new breadcrumb is created each time you click on a navigation item. then the first breadcrumb is dropped and the new breadcrumb is added to the end of the breadcrumb trail. see the BMC ProactiveNet Administration Guide. The breadcrumb is labeled based on the object that you selected. providing a history of the areas that you have viewed. a trail of breadcrumbs is created at the top of the operations console window. You can continue to use the toolbar buttons to manually change the view with this option enabled. five breadcrumbs are shown in the breadcrumb string. If you click more than five areas. Chapter 1 Introducing the BMC ProactiveNet Operations Console 31 .

Navigating the Operations Console 32 BMC ProactiveNet User Guide .

Each view is displayed as a separate node in the navigation tree in the Main drawer. Table 8 on page 33 summarizes the basic characteristics of each type of event view.2 Working with events Event views in the Main drawer of the navigation pane The Main drawer in the navigation pane in the Operations Console presents information about events in various tables and graphics. The event information and statuses are updated every two minutes. Abnormality Viewing all abnormalities on type events are events that are automatically detected page 93 from statistically significant abnormal trends. Table 8: Views of event information in the Main drawer View All Event Collectors All Abnormalities Description Displays a list of events for services and devices monitored by BMC ProactiveNet Further information Viewing the default event list for All Event Collectors on page 36 Displays a list of abnormality type events. based on the assigned access rights. Displays a list of events for configuration items (CIs) in a service model Displays a list of events for groups set by the BMC ProactiveNet administrator Displays a list of events for devices monitored by BMC ProactiveNet Displays a list of events for monitors created on the devices monitored by BMC ProactiveNet Viewing service model configuration items by service Viewing events by group on page 107 Viewing events by device on page 116 Viewing events for monitored services on page 121 All Services All Groups All Devices All Monitors Chapter 2 Working with events 33 .

By default. 34 BMC ProactiveNet User Guide . 2 In the Event List Preferences dialog box. The default refresh interval is 2 minutes.Customizing the display of the event list Customizing the display of the event list You can adjust the following aspects of the event list to suit your event monitoring and management preferences: ■ auto refresh ■ number of events to download per page ■ confirmation dialog boxes ■ tooltips ■ row color ■ icons ■ row numbering To customize display settings for the event lists 1 From the navigation bar.conf file. Table 9: Event list preference settings Field Auto Refresh Description Enables automatic refresh of the event list after a periodic interval. The recommended setting is 200. the more time required to refresh the events. Auto Refresh is enabled. Note: The event list pop-up window for configuration items is not refreshed even if you set a time interval in this field. click Preferences . and select View Events. Number of Events to Download Per Page Enables specification of the number of events to be downloaded per page. To view the event list pop-up window.alarmStatusView.refreshRate property in the installDirectory\ pw\pronto\conf\pronet. This can be configured by changing the pronet. The higher the value. use the information in Table 9 on page 34 to determine the appropriate settings. right-click a configuration item under All Services => Graph View.

Priority. confirmations are displayed for All event operations. Show Internal names of Event Attributes in Tooltips If selected. tooltips display internal names of event attributes in the header row of the event list and labels in the Details Notebook. Tools Menu. the header row of the event list and labels in the Details Notebook. 4 In the Event List Preferences dialog box. Filling Row with Severity Color Displays the severity color for the following options: ■ Entire event row ■ Only the first column (after the Status. a user can enter operation notes using confirmation dialog boxes. in both. By default. If cleared. and Severity Columns Row Numbering Displays rows that have events that are closed or blackout in white Displays rows that have events that are acknowledged or assigned in white Displays icons instead of text for these columns Displays the row number in the left-most column 3 Click Update All Views to save the changes and exit the dialog box. This setting is not applicable to slots related to Baseline and Threshold for Intelligent events. Tools Menu. Priority. Chapter 2 Working with events 35 .Customizing the display of the event list Field Confirmations Description Enables a notification when a user takes an action Displays confirmation for the following options: ■ All event operations ■ Close an event ■ None of the event operations When selected. click OK. and Severity columns) ■ No severity color in any row Make Closed and Blackout Events Rows White Make Acknowledged and Assigned Events Rows White Use Icons for the Status. tooltips display the same event attributes as displayed in the header row of the event list and labels in the Details Notebook.

Viewing the default event list for All Event Collectors Note The preference settings are applied to browser windows for a particular user logon on the same computer. Status Provides basic information about the event’s response activity. Events on the All Event Collectors screen are displayed in a tabular form as summarized in Table 10 on page 36. The default event list does not display events based on permissions of devices. All pop-up boxes reflect this change with a delay of a maximum of one minute. It displays all events based on the permissions of event collectors. The status of an event can be one of the following event: ■ Open ■ Assigned ■ Acknowledged ■ Blackout ■ Closed Note 36 BMC ProactiveNet User Guide . that is. Viewing the default event list for All Event Collectors The All Event Collectors screen lists all the events for services and devices monitored by BMC ProactiveNet. Table 10: Event information columns on the All Event Collectors screen Column Row number Description Displays the row number of the event This column appears only if you have selected Row Numbering in the Event List Preferences dialog box. displays the current status of the event.

In combination with status and priority. Priority Severity Determines which event requires action before the other Indicates the seriousness of the event. this menu provides a launch point.Viewing the default event list for All Event Collectors Column Tools Menu Description For events originating from BMC Impact Manager (cell). retrieve BMC BladeLogic device history.proactivenet. For multiple server deployment and BMC Atrium Explorer environments. Occurred Displays the date and time when the event occurred Chapter 2 Working with events 37 . this menu enables you to perform operations on an event. Also. the severity level indicates the urgency of the need to take action. set thresholds and manage data collection. execute remote actions/diagnostics.conf file. For events originating from the BMC ProactiveNet Server. and export the event.defaultSeverity property in the installDirectory\pw\pronto\conf \pronet. as follows: ■ Critical (red) ■ Major (dark orange) ■ Minor (light orange) ■ Warning (yellow) ■ Information (blue) ■ OK (green) ■ Unknown (grey) ■ Major and above ■ Minor and above ■ Warning and above ■ Information and above ■ OK and above ■ Unknown and above The default severity is Information and above. perform probable cause analysis for the event. add a change entry to track the changes in your environment. Severity is based on the comparison of metrics to defined thresholds. this menu enables you to perform all the actions that you can perform on the cell events. This can be configured by changing the bmc. you can perform diagnostics. view graphs and parent groups.

38 BMC ProactiveNet User Guide . For more information. Table 11: Further information options from the Tools Menu on the All Events screen Option Operations Remote Actions/Diagnostics Probable Cause Analysis Description Enable you to perform event operations such as open. the first event in the list is selected. and so on. Enables you to perform probable cause analysis on the selected event. It might also display the following icons: ■ Action Result ■ Detailed Diagnostics ■ Notes ■ Related Events ■ Suppressed Events (for upgrade users only) Host Displays the name of the host on which the event occurred When you navigate from one collector to another using the navigation tree. see How BMC ProactiveNet performs probable cause analysis on events on page 159. Related Topics Viewing the event list for remote cells on page 88 Note Viewing further information for a specific event from the Tools Menu The following summarizes the available options for further information about a specific event from the Tools Menu on the All Events screen. see Executing remote actions on page 80. Enable you to execute a remote action on a selected event.Viewing further information for a specific event from the Tools Menu Column Message Description Displays a short description of the reason for the event. Occasionally. no event is selected and highlighted in the event list. close. by default. For more information. For more information. see Performing event operations on page 76.

and Resetting a baseline on page 383. see Managing configuration changes on page 125. Show Graph(s) Show Parent Groups Threshold + Data Collection Additional options based on environment Launch ■ BMC Impact Model Designer: Enables you to launch BMC Impact Model Designer from BMC ProactiveNet and view the selected configuration item (CI) in BMC Impact Model Designer. Displays a graph and provides additional options to modify the graph. you can view BMC Service Level Management options for CMDB-published CIs. only if the CIs are sourced from the Configuration Management Database (CMDB). Chapter 2 Working with events 39 . Managing data collection on page 126. see Understanding event thresholds on page 180. see Launching an originating BMC ProactiveNet Server on page 86. For more information. Note: The Launch options are available for events associated with the CI and the CI itself. see Table 12 on page 40. Additional options for an Intelligent Event Intelligent Event History Diagnostics Displays event history details. XML. For more information. For more information. Enables you to use pre-configured and user-defined diagnostic tools to help monitor your system. Both these options are available in a multiple server deployment environment where devices are sourced from the CMDB.Viewing further information for a specific event from the Tools Menu Option Add Configuration Change Export Description Enables you to store and track configuration data. see Diagnostics on page 129. or CSV file. ■ Originating BMC ProactiveNet Server: Enables you to launch a BMC ProactiveNet Server from which events originated in a multiple BMC ProactiveNet Server deployment environment. For more information. For more information. Enables you to export information about all or only visible slots in a BAROC. If you have configured BMC Service Level Management with BMC ProactiveNet. For more information. see Exporting and copying event information on page 79. see Customizing monitor graphs on page 264. if available Enables you to set event thresholds and managed data collection. Displays the parent groups and subgroups. For more information. This option is available only when you have a multiple server deployment environment.

■ Remote Actions/Diagnostics ■ Tools Event Action History The history of actions (Intelligent or External events) performed on the event are displayed: ■ Time when the event action began ■ Severity level of the event ■ Event Rule Name—name of an event rule that triggered the action ■ Action Type—type of action initiated (for example: Detailed Diagnostics) ■ Action Details ■ Result More Information More information on the event are displayed: ■ Time when the event occurs ■ Message Related Topics Viewing all abnormalities on page 93 Viewing events by device on page 116 40 BMC ProactiveNet User Guide .Viewing further information for a specific event from the Tools Menu Table 12: Further information on the Intelligent Event Details page Option Event History Description The following event history details are displayed: ■ Time when the event got triggered ■ Device information ■ Severity of the event ■ Description of the event ■ Analyze .Click the Probable Cause or Service Impact icon to analyze the event.

Viewing the event list for a specific component in the navigation tree Viewing events by group on page 107 Viewing events for groups in a hierarchical tree on page 114 Acknowledging events on page 122 Viewing events and abnormalities by service on page 100 Viewing services in a hierarchical tree on page 105 Searching events on page 71 Behavior of popup windows for Tools Menu options on page 41 Behavior of popup windows for Tools Menu options When you navigate through various BMC ProactiveNet screens. Probable Cause Analysis. a device. open in a second popup window. and a monitor are almost alike. BMC ProactiveNet displays the events for the selected object in the event list pane. a service. a group. opens in a new window. and Show Parent Groups open in a popup window. Signature Instance Threshold. All further navigation that you perform from this popup window is limited to this popup window only. Absolute Instance Threshold. no matter from where they are launched. These operations do not reuse the popup window opened by operations listed in the first bullet point. Chapter 2 Working with events 41 . and Manage Data Collection. Show Graph(s). Signature Global Threshold. Viewing the event list for a specific component in the navigation tree The procedures for viewing events for an event collector. otherwise. the same operation. Threshold. Reset Baseline. you observe the following behavior for various options selected from the Tools Menu: ■ Operations such as Intelligent Event History. ■ Threshold + Data Collection operations such as Edit Violated Absolute Global ■ Add Change Entry operation reuses a popup window if one is already opened for ■ Diagnostics operations such as FlashCheck and Top Processes-CPU always open in a new popup window.

Viewing the event list for a specific component in the navigation tree To view the event list for a collector 1 In the navigation tree. see Applying a default. 3 Apply one of the following out-of-the box advanced filters: ■ All Abnormalities ■ Active Abnormalities ■ Inactive Abnormalities For more information. click the Global folder . or user-defined template for event list columns on page 47. To view the event list for a group 1 In the navigation tree. click Global. 2 Click All Groups. whose 2 Expand the hierarchy under All Event Collectors to locate the collector events you want to display. 3 Click the collector. click Global. 2 Click All Event Collectors => All Events. Tip You can also view the event list for abnormalities by performing the following steps: 1 In the navigation tree. 3 Expand the hierarchy to locate the group 4 Click the group. 42 BMC ProactiveNet User Guide . To view the event list for a service 1 In the navigation tree. 2 Click All Abnormalities. To view the event list for all abnormalities 1 In the navigation tree. click Global. global. whose events you want to display. click Global.

Each event class has defined slots. 2 Click All Monitors. The default slots in the event list provide basic information about an event. click Global. score. To view the event list for all monitors 1 In the navigation tree. host name on which the abnormality occurred. action count (number of occurrences). message produced by the intelligent event. while others are unique to an event class. Table 13: Out-of-the box event list templates Template Abnormality Information Columns displayed in the event list Status. severity. Some slots are common to all event classes. priority. click Global. and IP address of the host on which the intelligent event occurred Alarm Information Chapter 2 Working with events 43 . priority. whose events you want to display. 3 Expand the hierarchy to locate the service 4 Click the service. host name on which the intelligent event occurred. To view the event list for all devices 1 In the navigation tree. tools menu. By changing the slots presented in the event list. The Quick Columns Selector in the toolbar panel allows you to select the columns that are displayed in the event list. 2 Click All Devices.Selecting the type of event list to view 2 Click All Services. tools menu. message produced by the abnormality. and object (monitor) on which the abnormality occurred Status. date and time the abnormality occurred. you can view additional pertinent information or change the order in which event data is presented. Selecting the type of event list to view Slots identify information within an event class. BMC ProactiveNet provides the following out-of-the-box or default templates. date and time the intelligent event occurred. severity.

All Devices. metric. and score. priority. This template is available from the following drill-down options: ■ Event View => All Abnormalities. severity. date and time the intelligent event occurred. internal ID. severity. severity. host name on which the event occurred. All Devices. severity. priority. priority. and host name on which the event occurred Tools menu. tools menu. Event Incident Information Intelligent Events Information Predicted Events Information Remote Cell Events Information Supervisor Information Intelligent Events Details Intelligent Events Details template Administrator and other users cannot edit. priority. For more information. object (monitor) on which the event occurred and its class Status. date and time the event occurred. All Services. message produced by the event. and message produced by the event Status. incident ID. tools menu. and All Monitors ■ Event View => All components folders created by a user under the Global and My Folders folders ■ Tree View => All Groups and All Services and then right-clicking to select the All Events or Abnormalities options ■ Grid View => All Abnormalities. All Groups. date and time the event occurred. All Services. predicted severity. and All Monitors. date and time the event occurred. or copy the Intelligent Events Details (default or out-of the box) template. tools menu. date and time the event occurred. incident status. message. tools menu. message produced by the event. and then clicking the event counts displayed on these pages Related topics: Creating a new template for event list columns on page 45 44 BMC ProactiveNet User Guide . priority. All Groups. date time. and propagations Status. delete. incident priority. message produced by the event. see Intelligent Events Details template on page 44. host name on which the event occurred. severity. and object (monitor) on which the event occurred Status. severity. incident assignee.Selecting the type of event list to view Template Basic Information Columns displayed in the event list Status. tools menu. tool. predicted time. message produced by the event. object (monitor) on which the event occurred. tools menu. date and time the event occurred. host name on which the event occurred. and message produced by the event Status. owner of the event. device. ID. priority.

3 In the Event List Column Editor dialog box. and then. 7 Select Show in Quick Columns Selector so that this template appears in the Quick Columns Selector dialog box. 4 Specify a Name for the new template. on the left. Related topics: Chapter 2 Working with events 45 .Creating a new template for event list columns Creating a new template for event list columns An administrator can create a customized template so that the event list displays only those columns that are present in this newly created template. perform the following steps: a Click Event Class Selector . A global template is prefixed with an asterisk (*). To create a new template for event list columns 1 Click Quick Columns Selector. c Select a column name. Only an administrator user can delete a global template. 5 Select Make Global so that all users can view this template. e Click the Up or Down arrows to change the order in which the columns will be displayed. 8 Under Available Columns. d Click the right arrow. Tip b Select an event class. User-defined templates are not prefixed with an asterisk. click New Template . click Editor. 9 Click Save. 2 In the Quick Columns Selector dialog box. select the Templates tab. and then click OK. 6 Select Default for New Event Folders to use this template as a default for newly created event folders.

and then. 46 BMC ProactiveNet User Guide . select the Templates tab. click a default or user-defined template.Editing a default or user-defined template for event list columns Editing a default or user-defined template for event list columns on page 46 Copying an existing template for event list columns on page 46 Deleting a user-defined template for event list columns on page 47 Applying a default. or user-defined template for event list columns on page 47 Adding a column to an event list on page 48 Deleting a column from an event list on page 48 Adding a column to an event list for an abnormality on page 95 Deleting a column from an event list for an abnormality on page 95 Editing a default or user-defined template for event list columns Administrators can edit default or user-defined templates created by them or other users. To edit a default or user-defined template for event list columns 1 Click Quick Columns Selector. 2 In the Quick Columns Selector dialog box. 3 In the Event List Column Editor dialog box. Copying an existing template for event list columns Users with appropriate permissions can make a copy of a default template or a userdefined template created by them. click Editor. 5 Click Save. 4 Modify the information that you want to edit. global. on the left.

A template Copy of copiedTemplate appears on the left. Chapter 2 Working with events 47 . 3 In the Event List Column Editor dialog box. on the left. global.Deleting a user-defined template for event list columns To copy a default or user-defined template 1 Click Quick Columns Selector. click Editor. To delete a user-defined template 1 Click Quick Columns Selector. or user-defined template for event list columns All users can apply default. 3 In the Event List Column Editor dialog box. 4 Click . select the Templates tab. and then. and then. global. click a user-defined template. under the list of availabletemplates. select the Templates tab. Applying a default. global. 2 In the Quick Columns Selector dialog box. To apply a default. click a user-defined or default template. 4 Click Copy . or user-defined templates to an event list to view the columns present in these templates. Deleting a user-defined template for event list columns Administrators and other users can delete user-defined templates created by them. 2 In the Quick Columns Selector dialog box. or user-defined template 1 Click Quick Columns Selector. on the left. click Editor.

global. 48 BMC ProactiveNet User Guide . or user-defined template. on the left. Best practice Deleting a column from an event list All users can delete a single column from the event list for a specific event class. 4 Click . BMC recommends that you add a maximum of 30 columns to the event list to optimize the performance of refresh. 3 In the Event List Column Editor dialog box. and then click OK.Adding a column to an event list 2 In the Quick Columns Selector dialog box. The event list displays only those columns that are present in the selected template. The newly added column now appears in the event list and the same is removed from the Events List Column Editor dialog box. . click a default. select the Single Columns Selector tab. click Editor. 6 From the Event List Column Editor dialog box. click Editor. click Event Class Selector 5 Select an event class. and then. Adding a column to an event list All users can add a single column from any event class to the event list. This operation requires the event list and the Quick Columns Selector dialog box to be open simultaneously. To add a column to an event list 1 Click Quick Columns Selector. drag a column name into the header row of the event list. 2 In the Quick Columns Selector dialog box. select the Templates tab. 3 In the Event List Column Editor dialog box. 4 Under Available Columns.

owner. average value. Chapter 2 Working with events 49 . score. time to close. event rule history. object class. priority. and event operation history.Viewing the event Details Notebook To delete a column from an event list 1 Click Quick Columns Selector. repeated. and auto close Logs and Notes Historical Attributes Historical attributes of the event. received. this field includes additional information such as threshold. message. last modifier. such as status. monitor category. and Detailed Diagnostics Basic information about the event. event notification history. arrived. and action count (number of occurrences of actions) A user can enter additional information using the notes text area and click the Notes icon present in the Logs and Notes table to view the notes in a larger window. modified. object name. category. severity. Viewing the event Details Notebook The Details Notebook pane displayed below the event list provides all of the recorded information about an event. predict. reported by source. duration. class. history of any rule or policy applied. original severity and priority.s The cards or columns of the details notebook pane organize the information as described in the following table: Table 14: Event Details Notebook pane Column name Summary Sections in subtab Overview Description of contents Hyperlinks to launch Probable Cause Analysis. baseline type. and SLO For an intelligent event. Show Graph(s). 2 From the event list. baseline. such as date and time of occurrence. deviation. and detailed message Event Metric Event metric information such as metric and its value. origin time. drag a column name from the header row of an event list and drop it into the Event List Column Editor dialog box. date and time of occurrence. The Logs and Notes table displays notes added by the user. absolute deviation. host. minimum sampling window. repeated. comparison.

For more information. this field includes additional information about groups. attributes of a core event that are not displayed in other cards. including the tool name. such as the ID. rule. 2. By default. parameter unit and its threshold Device name. class. modification history. Host of Object Information about the host of the monitored object. For example. and type Information about the origin of the event. version. For more information. model. The event type is displayed before the slots present for that event type. timeout. tool class. tool ID. Service Model Component (SMC) impact. client address. tool address. tool suggestion. Access Control List (ACL). and URL For an intelligent event. Internals Tracking Tracking information. history. including class. abstractions. monitoring tool name. and 3.Viewing the event Details Notebook Column name Object Sections in subtab Object Monitored Description of contents Hyperlinks to launch Show Graph(s) and Tools Menu Information about the monitored object. component alias. type. address. such as VMWare host and ID Parameter Related Component Source Origin Reporter Monitor metric and its value. propagations. this card is not visible. relation source. manufacturer. provided the event type has slots that are not present in the remaining cards. adapter host. internal ID. and priority might be displayed in this card. and service For an intelligent event. associations. this card is not visible. collectors. product name. and event relations A list of undefined attributes and values Undefined Attributes Other dependOnTheSelectedEvent Information in this card changes according to the type of event selected. Relationships Information about events abstracted from this one. item. such as ITSM category. such as its name. and operation category 1. and severity Information about the adapter or gateway from which the event originated. this field includes additional information. location. see To select the cards to be displayed in the Details Notebook pane on page 51”. account. 50 BMC ProactiveNet User Guide . owner. ID. tool severity. company. causes and effects. and tool time (time when the event originated) By default. see To select the cards to be displayed in the Details Notebook pane on page 51”. such as its name. class. key. tool key. and Common Event Model (CEM) version Alarm ID is displayed in this section if the event selected is of ALARM type. location.

when you click Edit Preferences. If you select more cards than can be displayed. Note Chapter 2 Working with events 51 .Viewing the event Details Notebook To view and hide the Details Notebook 1 Select an event from the event list. In the Summary card. The permissions that a user has determine whether the user can perform an action on a hyperlink. use the tiny right and left arrows to the right and left of the Details Notebook to navigate through the cards. 4 Click Close . 2 In any of the cards listed in Table 14 on page 49 of the Details Notebook pane. . attributes related to Baseline and Threshold for Intelligent events are not available for selection and hence these attributes cannot be displayed in the default Summary card view. To select the cards to be displayed in the Details Notebook pane 1 Select an event from the event list. Tip To select the event attributes to be displayed within a card in the Details Notebook pane 1 Select an event from the event list. 2 Click the Up arrows 3 Click the Down arrows to the left of Details to view the Details Notebook. to hide the Details Notebook. The attributes available for selection depend on the type of event selected. 2 Click Edit Notebook Preferences . 4 Click Close. 3 Select the cards to be displayed in the Details Notebook pane. click Edit Preferences 3 Select the event information that must be displayed in the selected card.

and printing characters such as <.Viewing related events To view additional information about a card in the Details Notebook pane 1 In any of the cards listed in Table 14 on page 49 of the Details Notebook pane. you can manually refresh at any time to be sure that you have the most recent data. >. When you manually refresh the event list. . Note You cannot view related events after BMC Impact Manager (cell) purges data. select an event. Do not include nonprinting characters such as FS (0x1c) and RS (0x1e). 2 In the Logs and Notes card of the Details Notebook pane. ‘. A Notes icon is displayed in the selected event message. Refreshing the event list All of the event sources in the BMC ProactiveNet system can generate thousands of events. These characters are not supported. and “in the notes. The console updates the event list if changes are present. click More Info 3 Scroll down to the Logs and Notes section and enter the annotated text. You can configure refresh of the event list to occur automatically or manually. the BMC ProactiveNet Server is queried for any changes in events. . 52 BMC ProactiveNet User Guide . To add notes or annotate an event 1 From the event list. click More Info 2 Click Minimize . in an event list row. and even if you use the automatic refresh. click Related Event(s) in the Message column or the Tools Menu. 4 Click Save. Note Viewing related events To view events that are associated with an event. You can choose whether to view all of those events as they occur.

Using event and component folders BMC ProactiveNet has an organizational feature that provides event and component folders for operators and administrators to use to view and manage numerous events from different sources in meaningful ways. Also. If Auto Refresh is not enabled and an event is modified externally from the console. 2 In the Event List Preferences dialog box. Note To automatically refresh the event list 1 From the navigation bar. ■ Filter events to see only the ones of interest.Organizing events in the event list On the Internet browser. the F5 and Refresh buttons are not supported. the event is not updated until you manually refresh the event list by clicking Refresh in the navigation bar. Chapter 2 Working with events 53 . and Close buttons are also not supported. on some UI screens. select Auto Refresh. click Preferences . Forward. the event list might not be refreshed until the BMC ProactiveNet Server completes the current eventprocessing load. Organizing events in the event list You can use various techniques to organize events and view information about them: ■ Use event and component folders to arrange events from different sources. ■ Search events to see only the ones of interest. the Back. you can display events in a single tree node in the navigation tree. grouping events in your own ways. ■ Change the sorting of the event list. With these folders. Note If the BMC ProactiveNet Server is extremely busy.

The selected collector appears beneath the new event folder in This Folder’s Event Collectors . repeat the previous steps. see “Creating event folders” on page 54. and modify event folders. 6 To add another collector or subcollector. Tip You can also drag a collector or subcollector from Available Event Collectors and drop it into This Folder’s Event Collectors .Organizing events in the event list Note Folders are a prerequisite for image views. choose Add Folder => Event Folder. To remove the selected collector from This Folder’s Event Collectors . select a collector or subcollector to add to the new event folder. delete. 5 Click the right arrow to add the selected collector to This Folder’s Event Collectors . 4 Under Available Event Collectors. To add an event folder node 1 In the Main drawer of the navigation pane. 3 In the Add Event Folder dialog box. enter a name for the new event folder and optionally enter a description. You must first create an event or component folder to which you can add an image view. click the left arrow . see “Creating component folders” on page 56. click Global or My Folders . and how to move them within their hierarchy. see “Creating remote cell event folders” on page 61. For more information about creating component folders. 54 BMC ProactiveNet User Guide . For more information about creating remote cell event folders. Creating event folders The following procedures explain how to add. 2 From the Navigation Menu at the top of the drawer. For more information about creating event folders.

WARNING To move an event folder subnode within its parent folder node 1 In the Main drawer of the navigation pane. select how you want to filter the events in the event list. 3 From the Navigation Menu at the top of the drawer. Deleting a parent event folder deletes the event folder and all its descendants. To delete an event folder node 1 In the Main drawer of the navigation pane. perform the following additional steps: a Under This Folder’s Event Collectors. 3 From the Navigation Menu at the top of the drawer. choose Edit Folder. e Add event collectors to each subfolder as specified in step 4 through step 6. select the event folder subnode or collector that you want to move. 4 In the Delete Folder confirmation dialog box. 4 In the Edit Event Folder dialog box.Organizing events in the event list 7 Scroll down on the dialog box and underEvent List View . click Global or My Folders. Chapter 2 Working with events 55 . click Global or My Folders . click Yes. 9 Click OK. perform the following actions: ■ From Event List Columns. select the newly created event folder. select a template to use to determine which columns to display in event list. ■ From Event List Filter. c Specify a name for the newly created event subfolder. 2 Select a folder in the navigation tree. 2 Select a folder in the navigation tree. b Click Add Subfolder . choose Delete. d Repeat the previous steps to add more event subfolder. 8 (optional) To add a subfolder.

perform any of the following actions: ■ Modify the name of the existing event folder ■ Add or modify the description ■ Add. To edit an event folder node 1 In Main drawer of the navigation pane. click Global or My Folders . To add a component folder node 1 In the Main drawer of the navigation pane. 3 From the Navigation Menu at the top of the drawer.Organizing events in the event list 5 Click the Move Up or Move Down arrow button to move the event folder or collector subnode within the parent folder node hierarchy. 2 From the Navigation Menu Component Folder. click Global or My Folders. 2 Select a folder in the navigation tree. if any ■ Change the template for the event list ■ Change the filter for the event list 5 Click OK. delete. 6 Click OK. 4 In the Edit Event Folder dialog box. choose Add Folder => 3 In the Add Component Folder dialog box. or move event folder subnodes or collectors. and how to move them within their hierarchy. specify a name for the new component folder and optionally enter a description. select one of the following options to determine what components are displayed in the folder that you are creating: 56 BMC ProactiveNet User Guide . Creating component folders The following procedures explain how to add. and modify component folders. at the top of the drawer. 4 Under Folder Contents. choose Edit Folder. delete.

see the BMC ProactiveNet Administrator Guide. The list of components changes over time based on the filter criteria. High level or general search criteria could return too many results. depending on what type of folder you are creating. use the following guidelines when you create CI folders: ■ Be specific when you enter the search criteria to determine what CIs will be included in the folder. enter additional attributes in the search criteria to narrow the search. b Enter the search criteria for the name of the group or device that you want to search for. ■ Dynamic. 2 If you selected Groups and Devices. Chapter 2 Working with events 57 . select one of the following types of components to include in the new folder: ■ Groups and Devices: proceed to step 2. use Test Filter to verify approximately how many CIs match the search criteria that you enter. When you create a dynamic folder. select to search for Groups or Devices or All. perform the following additional steps: a Under Available Components. For details. If the search results in too many CIs. Continue with the following procedures.search for components based on the filter criteria that you specify.Organizing events in the event list ■ Static List of Objects .conf file. “To add a static folder node” on page 57 “To add a dynamic folder node” on page 59 To add a static folder node 1 If you selected Static List of Objects. ■ CIs from Service Model: proceed to step 3. You can configure this number in the pronet.search for components and select the components that you want to include in the folder from the list returned in the search results. The maximum number of CIs that a static or dynamic folder can hold is 500. The Groups and Devices list is automatically filtered based on the search criteria that you entered. To avoid performance issues when the navigation tree loads.Contents Change .

click Find. c From the Class list. but specify different values. 58 BMC ProactiveNet User Guide . b (optional) If you want all users that log on to the BMC ProactiveNet Operations Console to access the query that you are creating. To display additional attributes. d To add another group. The query will search for components with all of the attributes that you specify. expand the query builder options by clicking the plus button next to the Class list. select Make *Global (all users). Tip You can also drag a group or device from Available Components and drop it into This Folder’s Components. repeat these steps. An asterisk is placed next to the query name to indicate that it is global and is available to all users. select the type of component that you want to search for. f When you have finished specifying the query attributes. indicated by the OR before the attribute names. If you use the same attribute. indicated by the AND before the attribute names. 3 If you selected CIs from Service Model. select the CI to add to the new component folder. create a query to search for the CIs that you want to include in the folder by performing the following additional steps: a Select Create New Filter from the Filter list. then the query will search for components with any but not all of the values that you specify. e Begin building the parameters for your query by selecting the attributes for the class type that you selected. Each new attribute that you add narrows and refines the search. or device.Organizing events in the event list c Select the group or device that you want to include in the folder and click the right arrow to move it into This Folder's Components. d If necessary. service. click the plus button next to the attribute name. g Under Results.

select the newly created component folder. 5 On the Add Component Folder dialog box. To add a dynamic folder node 1 If you selected Dynamic . The selected item appears beneath the new component folder in This Folder's CIs. d Repeat the previous steps to add more component subfolders. A device added to a CI folder node or subnode is not visible in the navigation tree but is useful in the Tile view. 4 (optional) To add a subfolder. and click OK. You can also drag a component or subcomponent from Results and drop it into This Folder's CIs. create a query to search for the CIs that you want to include in the folder by performing the following additional steps: a Select Create New Filter from the Filter list. click OK. b (optional) If you want all users that log on to the BMC ProactiveNet Operations Console to access the query that you are creating. An asterisk is placed next to the query name to indicate that it is global and is available to all users. The saved query can also be used to search for CIs in the Find CI drawer in the navigation pane. click Save. perform the following additional steps: a Under This Folder’s CIs. Tip Note c Specify a name for the newly created component subfolder.Contents Change. Click the left arrow to remove the selected item. select Make *Global (all users).Organizing events in the event list h Click the right arrow to add the selected CI to This Folder's CIs. enter the Query Name. Chapter 2 Working with events 59 . i To save the query to use again. b Click Add Subfolder .

click Save. the CIs that match the search criteria are displayed up to a maximum of 500. but specify different values. 2 Select a folder in the navigation tree. select the type of component that you want to search for. d If necessary. To delete a component folder node 1 In the Main drawer of the navigation pane. indicated by the OR before the attribute names. enter the Query Name. f When you have finished specifying the query attributes. click Yes. expand the query builder options by clicking the plus button next to the Class list. Deleting a parent component folder deletes the component folder and all its descendants. g Under Results. h To save the query to use again. To display additional attributes. 2 On the Add Component Folder dialog box. and click OK. 4 In the Delete Folder confirmation dialog box. then the query will search for components with any but not all of the values that you specify. click Global or My Folders . 3 From the Navigation Menu at the top of the drawer. Each new attribute that you add narrows and refines the search. click OK. If you use the same attribute. indicated by the AND before the attribute names.Organizing events in the event list c From the Class list. choose Delete. The query will search for components with all of the attributes that you specify. WARNING 60 BMC ProactiveNet User Guide . click Test Filter. e Begin building the parameters for your query by selecting the attributes for the class type that you selected. click the plus button next to the attribute name.

services. 4 In the Edit Component Folder dialog box. Tip To edit a component folder node 1 In the Main drawer of the navigation pane. select the component folder subnode that you want to move. 2 Select a folder in the navigation tree. choose Edit Folder. and modify remote cell event folders. click Global or My Folders . Chapter 2 Working with events 61 . 3 From the Navigation Menu at the top of the drawer. 4 In the Edit Component Folder dialog box. service. perform any of the following actions: ■ Modify the name of the existing component folder ■ Add or modify the description ■ Add. or move component folders. Creating remote cell event folders The following procedures explain how to add. and how to move them within their hierarchy. click OK. 5 Click the Move Up or Move Down arrow button to move the component folder or collector subnode within the parent folder node hierarchy. if any 5 To save your changes. 6 Click OK. 3 From the Navigation Menu at the top of the drawer. delete.Organizing events in the event list To move a static component folder subnode within its parent folder node 1 In the Main drawer of the navigation pane. or device within its parent folder node. 2 Select a folder in the navigation tree. You can use this procedure to move a group. choose Edit Folder. click Global or My Folders . or devices. delete. groups.

5 Under Available Event Collectors. perform the following additional steps: a Under This Folder’s Event Collectors. To remove the selected collector from This Folder’s Event Collectors . select a template to use to determine which columns to display in event list. select a collector or subcollector to add to the new event folder. at the top of the drawer. Note Tip You can also drag a collector or subcollector from Available Event Collectors and drop it into This Folder’s Event Collectors . The selected collector appears beneath the new event folder in This Folder’s Event Collectors . ■ From Event List Filter. 7 To add another collector or subcollector. 3 From the Navigation Menu Folder. choose Add Event 4 In the Add Event Folder dialog box. click Other Cells. perform the following actions: ■ From Event List Columns.Organizing events in the event list To add a remote cell event folder node 1 In the navigation pane. 6 Click the right arrow to add the selected collector to This Folder’s Event Collectors . 62 BMC ProactiveNet User Guide . 8 Scroll down on the dialog box and underEvent List View . The self collector is the top level collector in the Available Event Collectors list and has the same name as the remote cell. enter a name for the new event folder and optionally enter a description. select the newly created event folder. select how you want to filter the events in the event list. repeat the previous steps. You cannot add the self collector to a remote cell event folder. 2 Select a remote cell for those listed in the Other Cells navigation tree. 9 (optional) To add a subfolder. click the left arrow .

e Add event collectors to each subfolder as specified in step 4 through step 6. 4 In the Edit Event Folder dialog box. 3 From the Navigation Menu at the top of the drawer. All remote cell event folders are global folders. 4 In the Delete Folder confirmation dialog box. choose Edit Folder. 2 Select a folder in the navigation tree. d Repeat the previous steps to add more event subfolder. 2 Select a folder in the navigation tree. the user account that is used to log on to the operations console must belong to a user group that has permission to view and perform actions on the remote cell for which the folder is created. To delete a remote cell event folder node 1 In the navigation pane. 10 Click OK. WARNING To move a remote cell event folder subnode within its parent folder node 1 In the navigation pane. 6 Click OK. select the event folder subnode or collector that you want to move. To view a remote cell event folder in the operations console. Deleting a parent event folder deletes the event folder and all its descendants. c Specify a name for the newly created event subfolder. 3 From the Navigation Menu at the top of the drawer. click Other Cells . meaning they can be seen by all users who access the operations console with the correct permissions. 5 Click the Move Up or Move Down arrow button to move the event folder or collector subnode within the parent folder node hierarchy. click Other Cells . Chapter 2 Working with events 63 . choose Delete.Organizing events in the event list b Click Add Subfolder . click Yes.

event type. severity level. or move event folder subnodes or collectors. The Quick Filter in the filters panel provides an easy way to view only those events in an event or component folder. Filtering events Using filters available in the filters panel located above the event list. you can narrow the scope and number of events displayed. device. delete. BMC ProactiveNet offers the following filtering methods: ■ quick filters. By default. The Show Filter on and off. time. 3 From the Navigation Menu at the top of the drawer. if any ■ Change the template for the event list ■ Change the filter for the event list 5 Click OK. or an event collector that satisfy a single or multiple criteria for filtering. click Other Cells . Examples of event folders are: 64 BMC ProactiveNet User Guide . 4 In the Edit Event Folder dialog box. 2 Select a folder in the navigation tree. choose Edit Folder.Organizing events in the event list To edit a remote cell event folder node 1 In the navigation pane. which show events based on a specific status. or groups ■ global filters. which an administrator or user creates and are available to any user logged on to the server where the global filter was created Using quick filters BMC ProactiveNet displays the filters panel below the navigation bar. perform any of the following actions: ■ Modify the name of the existing event folder ■ Add or modify the description ■ Add. the Quick filters panel is button in the navigation bar toggles the filters panel displayed.

and acknowledged events. select an event or component folder. or an event collector.Organizing events in the event list All Event Collectors and All Abnormalities under the Global folder and userdefined event folders created under the My Folders or Global folder Examples of component folders are: All Groups. click the down arrow next to the Severity list. All Services. Note To filter events using severity 1 From the navigation tree. Chapter 2 Working with events 65 . select an event or component folder. 2 In the filters panel. ■ A list of event statuses is displayed: — All Open (includes open. but does not include closed and blackout events) — Open (includes open events only) — Acknowledged — Assigned — Blackout — Closed 3 Select the event status that you want to use to filter the event list. 4 Click Filter. click the down arrow next to the Status list. All Devices. By Status. and All Monitors under the Global folder and user-defined component folders created under the My Folders or Global folder Examples of event collectors are: All Events. assigned. Select No filter from the Status list to return to the default event list view. 2 In the filters panel. or an event collector. and so on To filter events by status 1 From the navigation tree. Intelligent Events.

on page 66 or List item. 3 Select the severity level that you want to use to filter the event list. 3 In the Quick Filter Time Selector dialog box. 66 BMC ProactiveNet User Guide . 2 In the filters panel. select an event or component folder.Organizing events in the event list ■ A list of severity levels is displayed: — Critical — Major — Minor — Warning — Information — OK — Unknown — Major and above — Minor and above — Warning and above — Information and above — OK and above — Unknown and above By default the Information and above severity filter is applied to all the nodes in the navigation tree. on page 67. click the Edit Time (calendar) icon next to the Time field. 4 Click Filter. perform either List item. To filter events by time 1 From the navigation tree. 4 Select Relative time and proceed with the following substeps: a Click the down arrow below Relative time.

and skip to List item. click Clear to return to the default event list view. ■ A list of event types is displayed: — Alarm — Abnormality — Predictive — Configuration Change 3 Select the event type that you want to use to filter the event list. or an event collector. Select No filter from the Event Type list to return to the default event list view. 2 In the filters panel. select the number of minutes. or an event collector. select an event or component folder. Chapter 2 Working with events 67 . weeks. 4 Click Filter. b Select the To date and time. days. Note To filter events by device 1 From the navigation tree.Organizing events in the event list b From the list. 7 Click Filter. click the down arrow next to the Event Type list. Note To filter events by type 1 From the navigation tree. select an event or component folder. In the Quick Filter Time Selector dialog box. or months. on page 67. 5 Select Absolute time and proceed with the following substeps: a Select the From date and time. hours. 6 Click OK.

These filters are not available for the All Abnormalities event folder 68 BMC ProactiveNet User Guide . select a component folder. 2 In the filters panel. To filter events by groups 1 From the navigation tree. c Select the groups. select the way in which you want to display the groups by selecting one of the following options: ■ Tree: Displays the parent group nodes. perform the following substeps: a From the list on the left. such as All Devices or All Monitors. intermediate nodes.Organizing events in the event list 2 In the filters panel. e From the list on the right. 3 In the Groups Filter dialog box. and the child nodes in a hierarchy as shown in the navigation tree ■ Flat List: Displays the parent and child group nodes only b Expand or collapse the groups. Use the Ctrl or Shift key to select multiple groups. f Click Apply. and then click the right arrow. select the groups that you want to use to filter the event list. 4 Click Filter. 3 Click Filter. select Include or Exclude to include or exclude the groups in the filter criteria. click Groups. Tip Using global filters Administrators and users can create global or advanced filters and make them accessible to all users who are logged on to the server where the filters were created. d In the box on the right. Global or advanced filters are available for the All Event Collectors event folder and all its subnodes. enter the device name in the Device field.

on page 69 through List item. Chapter 2 Working with events 69 in the corresponding filter condition row. h Repeat List item. 7 In theEnter Filter Name dialog box. 5 To filter events according to one or more event attributes. enter a name for the filter. You can use these filters to adjust the view of the event list just as you use the quick filters. on page 69 to add as many filter conditions as you want. Tip To remove a filter condition. and All Monitors and all the drill-downs associated with all the component folders. . AND or OR. b Select an event attribute. 6 Click Save. click g Select a logical operator. click . and then click OK. specify the following information for each attribute: a (optional) Select a left parenthesis or a NOT condition. d Enter a value against which you want the filter to compare. click Advanced Filters . e (optional) Select a right parenthesis. All Devices. and then click . f To add another filter condition (event attribute). .Organizing events in the event list and all the component folders: All Groups. the advanced filter selected in the filters panel is applied to the event list. c Select a comparison operator. To create a filter 1 In the filters panel. 8 Click OK. By default. 2 Click Create New Filter 3 Click the down arrow next to the Class list. All Services. 4 Select an event class.

Note To clear a filter 1 In the filters panel. click Start Over.Organizing events in the event list The new filter is displayed in the Name list. 5 Click Apply. click Advanced Filters. 4 Modify one or more filter conditions. click Advanced Filters. 2 Click the down arrow next to the Name list. The conditions that you change in an existing filter are not saved until you click Save. To apply an out-of-the-box-or user-defined filter 1 In the filters panel. 3 Select a filter. 4 In the Filter Change Confirmation dialog box. 3 Select a filter. To apply a filter without saving changes 1 In the filters panel. 4 Modify one or more filter conditions. click Advanced Filters. 2 Click the down arrow next to the Name list. 5 To clear a filter condition. The selected filter is applied to the event list. 3 Select a filter. 70 BMC ProactiveNet User Guide . click Yes. The modified filter conditions are discarded and the original filter is applied to the event list. 2 Click the down arrow next to the Name list.

available in the toolbar panel located above the event list. Note Searching events Using Find Events . 4 Click Delete. 5 In the Cancel Filter Confirmation dialog box. To delete a filter 1 In the filters panel. 4 Click Cancel. 5 In the Filter Delete Confirmation dialog box. The most recently applied filter is canceled and the previously selected filter is applied to the event list. Administrator and other users can delete user-defined filters they create. 2 Click the down arrow next to the Name list. However.Organizing events in the event list To cancel a filter 1 In the filters panel. 2 Click the down arrow next to the Name list. 3 Select a filter. click Yes. The search functionality is available for event collectors only. The selected filter is removed from the Name list. Search is performed only on those slots of a CORE_EVENT class that are visible to you in the event list at that instance. click Advanced Filters. you can narrow the scope and number of events displayed. neither an administrator nor other users can delete default or out-of-thebox filters. Search is Chapter 2 Working with events 71 . click Advanced Filters. click Yes. 6 Click OK . 3 Select a filter.

Organizing events in the event list case sensitive and considers blank spaces. Single-click sorting You can use single-click sorting by clicking the header of the column that you want to use as the basis of your event list sort. type a query to search. All Abnormalities. either by adding or removing slots or by rearranging them. or any user- WARNING defined event folder) in the navigation tree ■ If the search query contains the following characters: ■ Left square parenthesis([) ■ Right square parenthesis (]) ■ Backward slash (\) ■ Single quotes (') ■ Single character To find an event 1 From the navigation tree. select an event collector. 2 In the search box. 3 Click Find Events. Sorting events The set of slots presented in the event list is called the slot order. you must enter the exact search criteria to retrieve results. 72 BMC ProactiveNet User Guide . Therefore. Search is ineffective in the following cases: ■ If the search is based on the date slot ■ If you select a component folderin the navigation tree ■ If you select an event folder (All Event Collectors. When you change the slots presented. you change the slot order.

you can click any column header that is not part of the designated multiple sort order to reset sorting. Figure 4: -Multiple-column sorting indicators In the following procedures. and the column on which you clicked is designated as the first. 2 Press the Ctrl key and click a second column header. To add a column to the sort order 1 Click a column header that you want to use as the first criterion to sort the event list. and All Monitors and all the drill-downs associated with all the component folders. press the Ctrl and Shift keys.Organizing events in the event list Even if a multiple sort order has been established. Chapter 2 Working with events 73 . re-click the column header. This action establishes single-column sorting. To remove the sort order. Figure 3: Single-click sorting indicators Multiple-column sorting Designating multiple columns for a sorting order is useful in resolving sort-order conflicts in the event list. and click the column header. However. this feature is not available for the All Abnormalities event folder and all the component folders: All Groups. All Services. You can set a multiple-column sort order as shown in Figure 4 on page 73 . column in the new sort order. you can select or clear the column headers that you want to use to sort the contents of the event list. Multiplecolumn sorting is available for the All Event Collectors event folder and all its subnodes. All Devices. and only. To reverse the sort order.

in the By default. the following shortcuts are available in the toolbar panel right above the the event list only if a user has permissions for all these operations. If a user does not have permission for a particular operation. and actions. you can create shortcuts for performing event operations. Show Toolbar navigation bar toggles the toolbar panel. then shortcuts for all the following operations. you can: ■ Click one of the columns to re-sort the event list based on that single column. Edit Toolbar is visible only if a user has permissions to view it. the toolbar panel is available to all the users. and click a column header contained in the sort Creating shortcuts for Tools Menu options Using Edit Toolbar .Creating shortcuts for Tools Menu options 3 Repeat List item. ■ Press the Ctrl key and click a column header contained in the sort order to toggle that column’s display between ascending and descending order. order to remove that column from the sort order. Tip If you have established a multiple sort order in the event list. on page 73 to add more columns to the sort order for the event list. available in the toolbar panel located above the event list. except Close are displayed. ■ Acknowledge ■ Close ■ Take Ownership ■ Decline Ownership ■ View Remote Action Results ■ Copy ■ Export ■ Set Priority ■ Intelligent Event History 74 BMC ProactiveNet User Guide . executing commands. ■ Press the Ctrl and Shift keys. for example. However. By default. Close.

if an event is acknowledged. the Acknowledge button in the Menu Buttons section is disabled. and then drop it into the toolbar panel right above the event list: ■ Menu Buttons: For all event operations. operations available in the Tools Menu. However. they are context-sensitive. For example. they are saved as user preferences and available to that user on the subsequent logon. select and drag one icon at a time that you want to remove. To remove shortcuts for menu buttons. the Acknowledge button is enabled. Chapter 2 Working with events 75 . 3 Click Close. 2 From the toolbar panel. and actions 1 In the toolbar panel. and then drop it into the Edit Toolbar dialog box. commands. if the event is not acknowledged. ■ The shortcuts appear in the toolbar panel. Once a user changes the toolbar buttons. commands. right above the event list. click Edit Toolbar. 2 Click Close. and actions 1 In the Edit Toolbar dialog box. select and drag one icon (not the icon label) at a time from the following list.Creating shortcuts for Tools Menu options ■ Probable Cause Analysis ■ Operations Menu ■ Tools Menu To create shortcuts for menu buttons. and remote actions ■ Spacers: For adjusting the space between the shortcut buttons ■ Commands: For individual operations and commands ■ Actions: For individual remote actions Note The number of buttons that you can select and drag depends on the available space in the toolbar panel.

Table 15: Event operation descriptions Event operation Take Ownership Description Assigns ownership of an Open or Acknowledged event to self. disables any further event operation Assigns a priority level to the event Changes the state of an event to Open. puts the event in the Assigned state Assigns ownership of an Open. priority. puts the event in the Assigned state Removes ownership of an event in Assigned event. You can perform these operations on a maximum of 500 events. and ensure that you click the Tools Menu on the last selected event. if you choose to use the Tools Menu or the Operations Menu in the Status column. 76 BMC ProactiveNet User Guide . or the Ctrl key to select multiple non-continuous events. puts the event in the Acknowledged state Changes a previously Acknowledged event back to the Open state Puts an Open. Assigned or Acknowledged event in the Closed state. However. This operation is displayed only for remote event management cells. Acknowledged. press and hold the Shift key to select multiple continuous events. Your user role determines the event operations that you can use.Performing event operations Performing event operations Event operations change the status. Tip BMC recommends that you use the toolbar to perform operations on multiple events. or ownership of an event. puts the event back in the Acknowledged state Recognizes the existence of on Open event. Assign To Decline Ownership Acknowledge Event Unacknowledge Event Close Set Priority Reopen Event The following topics provide instructions for performing event operations. ignores the event in calculating status. or Assigned event to self or another person in the same account.

Performing event operations Although all the event operations that are available to your user role are available when you select two or more events in the event list. If Confirmations in the Event List Preferencesdialog box. Under Event Administration. 4 In the Assign To dialog box. Chapter 2 Working with events 77 . and the events are not changed. and then the Administration tab. on the Operations Console select the Options link. select an event that you own. select the person to whom you want to assign the event. is not set for All Event Operations. To access this screen. 4 In the confirmation dialog box. Note To take ownership of an event 1 From the event list. select an event of which to take ownership. column. an operation is performed only on the selected events whose status makes the operation valid. For more information. If the operation is not valid for some selected events. 2 Click one of the wrench icons. Note To assign an event to an individual 1 From the event list. see Customizing the display of the event list on page 34. 3 Click Operations => Assign To. 2 Click the wrench icon in the Tools Menu column. and then click OK. Note To decline ownership of an event 1 From the event list. The list of users in the Assign To dialog box contains only those users selected in the Assign to User List screen. you do not receive a confirmation when you take ownership of an event. (that is available) in the Tools Menu 3 Click Operations => Take Ownership. or . click OK. 2 Click the wrench icon in the Tools Menu column. select one or more events to assign. click Edit next to Assign to User List. a message box reports the internal IDs of those events.

it may take some time to close the event. select one or more open events designated with 2 Click the wrench icon in the Tools Menu column. select an event that is acknowledged.Performing event operations 3 Click Operations => Decline Ownership 4 In the confirmation dialog box. select an event that is open. This can cause a discrepancy between the status of the event in the Notebook Summary tab and the status of the event in the Status column until the event closes and the two views of the event become synced. 3 Click Operations=>Acknowledge Event. To Unacknowledge an event 1 From the event list. Note ■ When the Close Event operation is performed on an intelligent event. click OK. click OK. 3 Click Operations => Close Event. click OK. ■ The Close Event operation is not available for abnormality events. 4 In the confirmation dialog box. To acknowledge an event 1 From the event list. 4 In the confirmation dialog box. click OK. 2 Click the wrench icon in the Tools Menu column. . or acknowledged. 3 Click Operations=>Unacknowledge Event. assigned to you. To close an event 1 From the event list. 78 BMC ProactiveNet User Guide . 2 Click the wrench icon in the Tools Menu column. 4 In the confirmation dialog box.

4 Select Visible Slots to export information about the visible slots only or All Slots to export information about all the slots. or CSV file or copy information about all the slots into the clipboard. Chapter 2 Working with events 79 . the operation initiated by the user is not executed. select the format in which you want to export the event column information. 6 Click OK. 4 In the Set Priority dialog box.Exporting and copying event information To set the priority for an event 1 From the event list. 3 In the Export Events dialog box. 2 Click the wrench icon in the Tools Menu column. These operations enable you to send the event information to BMC Impact Manager (BMC IM or cell) using CLI commands. Note Exporting and copying event information You can export information about all or only visible slots in a BAROC. If a user has initiated a status change operation on an event and the status of that event is changed due to an event rule or policy before the execution of the status change operation from the Operations Console. select an event. select an event. 2 Click the wrench icon in the Tools Menu column. select the priority level for the event. You can perform the export and copy operations on a maximum of 500 events. To export event information 1 From the event list. XML. and then click Export. 5 (optional) Add notes. 3 Click Operations => Set Priority.

in those slots that have a list of strings. For example. When you use a remote action.Executing remote actions Note When you export all the slots of an event. 6 Select a location to save the slot information. The copied event information is available in BAROC format in the clipboard and can be pasted into a new text or Microsoft Word document. and actions on page 75. These remote actions are created by an administrator as a response to specific events as required for your environment. 3 Click Copy Event. change the double-quotes to single quotes. The device must be configured so that it allows the remote action to be executed on it. To copy an event to the clipboard 1 Create a shortcut for Copy Event as explained in To create shortcuts for menu buttons. 4 In the Copy to clipboard dialog box. You can also copy one or more events using the Ctrl and K keys. The number of remote actions that you can execute depends on the event type. commands. Copy is the only operation that you can perform using keyboard keys. select an event. Tip Executing remote actions You can respond to a selected event by executing a remote action. To respond to an event by using a remote action 1 From the event list. core event or intelligent event. make minor edits to the file. and click Save. 2 Select one or more events to copy. 80 BMC ProactiveNet User Guide . To import the BAROC file. 5 Click Save. click OK. it is issued from your local console but executed on the computer where the BMC Impact Manager (cell) or the BMC ProactiveNet cell is installed. You can perform remote actions on events that have been associated with or mapped to devices through a device alias. the generated BAROC file is not in a format that can be imported directly using the mposter command.

50. Maximum = 35ms. Note The remote actions Modify Slot Value.50.10: 209. 3 Click Remote Actions/Diagnostics and then select a remote action.10: 209.10: Packets: Sent = 5. Show Remote Action Environment. Approximate round trip times in milli-seconds: Minimum = 33ms.10: 209.50.50. The output of a successful ping command.97.50. ■ To access the results of the remote action. Average = 34ms Chapter 2 Working with events 81 . available from the Action Result(s) option. 4 In the Execute Action dialog box. 5 Click Execute.97. you can perform the following operations: — Export the information about the remote action to a file by selecting the action information and clicking Export.10 with 32 bytes of data: Reply Reply Reply Reply Reply from from from from from 209. consists of ping statistics: Pinging 209. and details about the remote action by clicking the corresponding tab. Received = 5. enter the appropriate values required to run the selected remote action.97. — View the output. Lost = 0 (0% loss). errors.10: 209. Ping Event mc_host_address This remote action executes a ping command against the target host defined by the mc_host_address slot.10: bytes=32 bytes=32 bytes=32 bytes=32 bytes=32 time=33ms time=34ms time=34ms time=35ms time=35ms TTL=242 TTL=242 TTL=242 TTL=242 TTL=242 Ping statistics for 209.Executing remote actions 2 Click the blue wrench icon in the Tools Menu column.97.50.97.97. An exit code of 0 indicates a successful ping and a working connection between the local system and the target host. click Action Result(s) in the Message column or the Tools Menu. In the Event Remote Action Results dialog box. and Trigger Remedy Incident for Event do not display an associated Action Result(s) or Related Events option.50. in the event list row.97.

Send EVENT as SMTP E-mail This remote action allows you to send a selected event to a designated e-mail recipient through the msend_email executable.out displays remote environment information that includes. where installDirectory by default equals Program Files\ProactiveNet\pw or /usr/pw. It does not display the action results in the GUI. BMC recommends that you do not change the severity of an intelligent event by executing the Modify Slot Value remote action. The selected event must contain a specified host name. Modify Slot Value This remote action allows to change the value of a specified slot for the selected event... class. ALLUSERSPROFILE=C:\Documents and Settings\All Users ASANY9=C:\Program Files\ProactiveNet\pw\sybase ASANYSH9=C:\Program Files\ProactiveNet\pw\sybase\shared BMC_PROACTIVENET_HOME=C:\Program Files\ProactiveNet\pw CATALINA_HOME=C:\Program Files\ProactiveNet\pw\tomcat CELLCONFDATAPATH=%MCELL_HOME%\etc ClusterLog=C:\WINDOWS\Cluster\cluster..Executing remote actions TraceRoute to Event mc_host_address This remote action executes a traceroute command to identify the path of the event from its origin to its destination. the sample output file installDirectory \server\tmp\ cellName\ result. The event information that is sent includes event severity. Instead. status. You can view the change in the Details pane. Note Show Remote Action Environment This feature is designed to display information about the remote action environment. In the following example. and the server cell name. the action results are captured in an output file in the installDirectory \server\tmp\ cellName path.13. IBRSD_HOME=C:\PROGRA~1\PROACT~1\pw\INTEGR~1\ibrsd JAVA_HOME=C:\Program Files\ProactiveNet\pw\jre 82 BMC ProactiveNet User Guide .log CommonProgramFiles=C:\Program Files\Common Files . handle Id. but is not limited to. the following data: This is the Local Action execution environment.

. each workflow applies to all event types. (Refer to the BMC ProactiveNet Administrator Guide for descriptions of the remote action policies designed to launch these workflows automatically.C:\WINDOWS\system32.. Setup Sending SMTP E-Mails .) Before you can launch these workflows. Note Launching a workflow on demand from the Events Console By default.. Follow these steps to select and launch a workflow from the Events Console: Chapter 2 Working with events 83 . RULE_NAME=Show Remote Action Environment REQUESTOR=admin CLASS=EVENT .C:\Perl\bin. To enable this action.. BMC Atrium Orchestrator workflows These workflow actions are designed to be launched on demand or through remote action policies.. You specify the destination host to which to send the event.Executing remote actions MCELL_HOME=C:\PROGRA~1\PROACT~1\pw\server NUMBER_OF_PROCESSORS=2 OS=Windows_NT Path=C:\Perl\site\bin. you must perform configuration steps on the BMC ProactiveNet server side and the BMC Atrium Orchestrator BEM adapter on the BMC Atrium Orchestrator server side.Windows Only You can use this remote action in conjunction with the Send Event as SMTP E-mail action. This topic addresses the on-demand workflow. Here. . Trigger Remedy Incident for Event This remote action enables to generate BMC Remedy Service Desk incident for the selected event. you can define the SMTP server you want to use as the e-mail server for sending events. See the BMC ProactiveNet Administrator Guide for the configuration steps.. you must be integrated with the BMC Remedy Service Desk application.

and click the Tools icon to display the menu. It does not attempt to restart the host.Executing remote actions To launch a workflow on demand from the Events Console 1 Identify the appropriate event for the workflow. which executes volume clean-up commands based on the operating system. When launched this workflow uses the corresponding OS command to check for disk space usage on the system where the configuration item resides. An Execute Action dialog box opens containing input parameters that are specific to your workflow selection. Triage Host Down For a complete description of the workflows. 3 Select the workflow. Is used when a monitored host system is down. It only confirms that the host is unreachable. After updating related events and incidents with the disk usage metrics. It then launches the remediation task. see the BMC Software Triage and Remediation Solution Getting Started Guide for BMC ProactiveNet. This workflow uses a series of ping and traceroute commands to verify whether the host specified in the event is actually down. Note 84 BMC ProactiveNet User Guide . the workflow undertakes a change management process to generate the change form and associate it with the incident information. 2 Choose Remote Actions => Atrium Orchestrator Actions to display the list of workflows. Table 16: BMC Atrium Orchestrator workflows Workflow type Triage and Remediate Disk Full Description Is used when the operating system disk space reaches or exceeds its capacity.

Change Request Type String: Specifies the type of change request (normal or preapproved) Create-Update Incident Boolean: True or false indicator that shows whether you want to create an incident in the incident management system. The exit code 0 indicates a successful execution. 5 Verify the event notes in the Details pane.Executing remote actions Table 17: Input parameters for BMC Atrium Orchestrator workflow types Workflow type Triage and Remediate Disk Full Execute Action input parameters Create Change Request Boolean: True or false indicator that shows whether you want to create a change request in BMC Service Desk. Remediate Boolean: True or false indicator that shows whether you want to proceed with the remediation action. Triage Host Down Create Incident Boolean: True or false indicator that shows whether you want to create or update an incident in the specified incident management system. the exit code defaults to -1. If you choose false. and click Execute to launch the workflow. errors. Otherwise. An information event is returned indicating the action and the target host. filter. then workflow updates the existing incident information. and perform actions on consequent events that are related to the workflow launch. If an incident already exists. To check the results of the workflow action 1 Click the Action Results icon to display the Event Remote Action Results dialog box. The event notes describe the stages of the workflow’s execution and indicate whether the workflow has been launched successfully. the Change Request Type parameter is ignored. Chapter 2 Working with events 85 . and details associated with the workflow action. You can view output. 4 Make your selections in the Execute Action dialog box. To view related events 1 Click the Related Events icon to open the Event List window. An Action Results icon and a Related Events icon are displayed in the event row. You can view.

2 Click the blue wrench icon in the Tools Menu column. you can launch BMC ProactiveNet Servers from which events originated. Customizing the display of events Through the Options screen. All functionality is available in the Operations Console of the originating BMC ProactiveNet Server (also called a child BMC ProactiveNet Server). You might need to enter a user name or password. 86 BMC ProactiveNet User Guide . Table 18: Event Display Preferences for customizing event display Setting Home page Description Select the default view to be displayed whenever you access the Events Console tab. 2 Click the Operations tab. 3 Choose Launch => Originating BMC ProactiveNet Server.Launching an originating BMC ProactiveNet Server Launching an originating BMC ProactiveNet Server When monitoring events from a central BMC ProactiveNet Server in a multiple BMC ProactiveNet Server deployment environment. click the Options link at the top right. To launch an originating BMC ProactiveNet Server 1 From the event list. The default is the All Events view. 3 Modify the settings described in Table 18 on page 86 under Event Display Preferences as necessary. select an event. depending on your system authentication policies and procedures. see the Administrator Guide . To customize the event display 1 In the Operations Console. you can customize the overall layout of the events to suit your preferences. For details about configuring this kind of deployment.

Customizing the display of events

Setting Events Console Groups 3.a

Description Configure the display of groups in the Events Console => All Groups (Events View, Tile View, Canvas View, Tree View, and Grid View). Click Edit and then use the arrow icons to select groups and to set the order of groups. The Show all groups check box on the top left enables you to display all groups dynamically, including all future groups.

Events Console Monitor Categories Configure the display of monitor categories in the Events Console => All Monitors => Grid View. Click Edit and then use the arrow icons to select monitor categories and to set the order of monitor categories. The Show all monitor categories check box on the top left enables you to display all monitor categories dynamically, including all future monitor categories. Show All Devices with Counts Show Devices in Hierarchy Show All Groups with Counts Show Suppressed Events 3.b Display events in the Events Console => All Devicesview with the actual numerical count of the events. Set the hierarchical view as the default view on Events Console => All Devices view. Display events in the All Groups => Grid View with the numerical count of the events (rather than the default event severity icons). View suppressed events in the following locations: ■ Status column in the All Events view ■ Event counts in the All Groups => Grid View and All Devices ■ Status-based border color in graphs ■ Status icons in the navigation tree for All Events, All Devices, and All Groups => Grid View Show Predictive Events Display a separate symbol for predictions on the Tile View and Canvas View

a This feature is available only for unrestricted users of groups. b Available only for upgrade users 4 Click Apply.

To set layout preferences
1 In the Operations Console, click the Options link at the top right. 2 Click the Operations tab.

Chapter 2 Working with events 87

Viewing the event list for remote cells

3 Under Layout Preferences, select the views, described in Table 19 on page 88, that you want to see: Table 19: Layout Preferences settings
Setting Show Navigation Tree Show Dashboard View Description Displays the navigation tree on the left (default) Displays a list of user-defined views These views are displayed in the top right portion of the Grid View and Tree View. This enables the user to get a snapshot of the most important attributes being monitored. Note: You can select only graph-based views as dashboard views. You cannot select folder-based views. The Dashboard is not displayed on the Event View, Tile View, and Canvas View. Show Home View Displays the selected view as the default view

4 Click Apply.

To set tab preferences
1 In the Operations Console, click the Options link at the top right. 2 Click the Operations tab. 3 Under Tab Preferences, select the tabs that you want to display as navigation tabs in the Operations Console. 4 Click Add Tab. 5 Click Apply. Related Topics Customizing the display of the event list on page 34

Viewing the event list for remote cells
You can view events on a standalone remote cell, or a remote cell in High Availability (HA) mode once you configure the remote cell for viewing on the Operations Console. BMC ProactiveNet supports BMC Impact Manager (cell) from version 7.1 onwards only as remote cells. BMC recommends that you do not add a second BMC ProactiveNet cell as a remote cell.

88 BMC ProactiveNet User Guide

Viewing the event list for remote cells

To configure a standalone remote cell for viewing on the Operations Console
1 Add an entry for the remote cell in the cell_info.list file located at installDirectory \pw\pronto\conf\ by entering the following command: iadmin -ac name=remoteCellName:key=mc:primaryHost=hostName:primaryPort=portNumber:e nvironment=Production:usergroups=* The parameters are defined as follows:
■ name is the name of the remote cell that you want to display as defined in the

mcell.dir file.

■ key is the encryption key of the cell; the default is mc. ■ primaryHost is the computer where the cell is located. Specify the computer

name and the domain name.

■ primaryPort is the port on which the remote cell is listening; the default is 1828 ■ environment is the type of environment where the cell is used, either

Production or Test.

■ usergroups is the name of the user groups that can access the remote cell. To

allow access to all user groups, enter an asterisk (*). To specify only certain user groups, enter the group names separated by commas. If a user group contains spaces, enclose the entire entry for this parameter with double quotes.

iadmin -ac name=qa:key=mc:primaryHost=qa.company.com:primaryPort=1828:environment=Produ Access, Read Only" 2 Add an entry for the remote cell in the mcell.dir file located at installationDirectory \pw\server\etc\ as follows:
cell cellName mc computerNameWithDomain: portOnWhichCellIsInstalled

Example

Example cell qa mc qa.company.com:1828

To configure a remote cell in HA mode for viewing on the Operations Console
1 Add an entry for the remote cell and its counterpart in HA mode in the cell_info.list file located at installDirectory\pw\pronto\conf\by entering the following command:
Chapter 2 Working with events 89

Viewing the event list for remote cells

iadmin -ac name=remoteCellName:key=mc:primaryHost=hostName:primaryPort=portNumber: failoverHost=hostName:failoverPort=portNumber:environment=Production:usergr oups=* The parameters are defined as follows:
■ name is the name of the remote cell that you want to display as defined in the

mcell.dir file.

■ key is the encryption key of the cell; the default is mc. ■ primaryHost is the computer where the cell is located. Specify the computer

name and the domain name.

■ primaryPort is the port on which the remote cell is listening; the default is 1828 ■ failoverHost is the computer where the failover cell is located. Specifiy the

computer name and the domain name.

■ failoverPort is the port on which the failover remote cell is listening ■ environment is the type of environment where the cell is used, either

Production or Test.

■ usergroups is the name of the user groups that can access the remote cell. To

allow access to all user groups, enter an asterisk (*). To specify only certain user groups, enter the group names separated by commas. If a user group contains spaces, enclose the entire entry for this parameter with double quotes.

Example iadmin -ac name=ha_cell:key=mc:primaryHost=host1.company.com:primaryPort=2344:failoverHost=
2 Add an entry for the remote cell and its counterpart in HA mode in the mcell.dir file located at serverInstallationDirectory \server\etc\ as follows:
cell cellName mc computer1NameWithDomain: portOnWhichCellIsInstalled

computer2NameWithDomain: portOnWhichHACellIsInstalled

Example cell ha_cell mc host1.company.com:2344 host2.company.com:2344

To view the event list for remote cells
1 In the Operations Console, click Navigation Pane Options .

90 BMC ProactiveNet User Guide

Viewing the event list for remote cells

2 In the Navigation Pane Options dialog box, click Other Cells. 3 Select a remote cell from the list and click Apply. If multiple remote cells are configured, select each cell that you want to display.

4 Click OK to close the Navigation Pane Options dialog box. 5 In the navigation pane, click Other Cells. 6 Select a remote cell from the list. The event list for the remote cell is displayed in the Event List view of the operations console. For details about the actions you can perform on remote cells, see Operations possible on the event list for remote cells on page 91. For details about creating a remote cell event folder, see “Creating event folders” on page 54.

Operations possible on the event list for remote cells
You can perform the following operations from the event list for remote cells:
■ All event operations, remote actions, export, and copy operations ■ Quick filters, sort, and search events ■ All the operations (menu buttons, commands, and actions) added as shortcuts

from the main event lists page to the toolbar panel

■ View the slots included in the Remote Cell Events Information default template or

any slots added or removed from this default template from the main event lists page

■ View event list preferences applied from the main event lists page

You cannot perform the following operations from the event list for remote cells:
■ Operations specific to intelligent events ■ Advanced filters ■ Add or remove icons from the toolbar because Edit Toolbar is not available Chapter 2 Working with events 91

Viewing predictive events

■ Change the slot order since Quick Columns Selector is not available ■ Change the event list preferences since Preferences is not available ■ View the event details notebook

Viewing predictive events
In addition to the normal events generated after a problem arises, BMC ProactiveNet can also generate predictive events. Predictive events are early warning events that BMC ProactiveNet generates before an event condition occurs on an existing metric. Such events enable you to identify potential problems before the condition causes impacts to business services and before the end users notice the problem. The typical predictive window is three hours or less, which means most predictive events are generated up to three hours before an actual event condition would occur. BMC ProactiveNet treats predictive events like normal events and displays them in all the standard event screens. Predictive events target persistent anomalies that might go undetected for most of the day (during the off-peak periods) but become serious issues at peak load periods. These kinds of problems are typically caused by configuration changes or user load shifts. For example, if you make a change to a load balancer that accidentally redirects more end-user transactions to one of the servers in the pool, that server might now have much more load than the other servers in the pool. However, this would not be obvious during low traffic periods. As the peak load period approaches, the imbalance would become more serious and the server load issue would become obvious, eventually causing an event on an end user transaction and performance or availability issues for all transactions routed through that server. In this scenario where BMC ProactiveNet events are used, an abnormality is generated as soon as the first change in behavior is detected, a predictive event would be generated two to three hours before any impact or before a real event condition. Predictive events are enabled through the absolute threshold settings. The predictive algorithm leverages the hourly baseline in conjunction with the threshold setting to determine when to create a predictive event.

To view predictive events using quick filters
To view predictive events, on the Operations Console select the Options link, and then the Operations tab. Under Event Display Preferences, ensure that you select the Show Predicted Events check box. You cannot view predictive events from the navigation tree as no default event collector is available under the Global folder for them. 1 In the filters panel, click Quick Filters.

92 BMC ProactiveNet User Guide

Viewing all abnormalities

2 From the Event Type list, select Predictive. 3 Click Filter.

To view predictive events using advanced filters
1 In the filters panel, click Advanced Filters 2 From the Name list, select one of the following out-of-the box advanced filters:
■ Predicted Events-Active (Not Closed) ■ Predicted Events-All ■ Predicted Events-Inactive

Viewing all abnormalities
The All Abnormalities => Events View lists all abnormality events for groups, services, devices, and monitors monitored by BMC ProactiveNet.
Table 20: Columns of event information on the All Abnormalities screen Column Status Description Provides basic information about the abnormality’s response activity, that is, displays the current status of the abnormality. The status of an event can be one of the following: ■ Open ■ Acknowledged ■ Assigned ■ Blackout ■ Closed

Chapter 2 Working with events 93

Viewing all abnormalities

Column Tools Menu

Description For events originating from BMC Impact Manger (cell), this menu enables you to perform operations on an event, execute remote actions/diagnostics, perform probable cause analysis for the event, retrieve BladeLogic device history, and export the event. For events originating from the BMC ProactiveNet Server, this menu enables you to perform all the actions that you can perform on the cell events. Also, you can perform diagnostics, view graphs and parent groups, add a change entry to track the changes in your environment, set thresholds and manage data collection. For multiple server deployment and BMC Atrium Explorer environments, this menu provides a launch point.

Priority Severity

Determines which abnormality requires action first Indicates the seriousness of the abnormality. In combination with status and priority, the severity level indicates the urgency of the need to take action. Severity is based on the comparison of metrics to defined thresholds. The severity of the abnormality event is Info (blue). Indicates how closely the event relates to the probable cause of the problem Displays the date and time when the abnormality occurred Displays a short description of the reason for the abnormality. It might also display the following icons: ■ Action Result ■ Detailed Diagnostics ■ Notes ■ Related Events

Score Occurred Message

Host Object

Displays the name of the host on which the abnormality occurred Displays the name of the object monitoring the abnormality

Note The BMC ProactiveNet administrator can set up specific user-defined rules that can help you keep track of frequent events and their causes. For instance, if you continually receive an event and you realize that the event is triggered by a recognizable pattern, you can set up rules that replace BMC ProactiveNet probable cause description with specific information related to that event. In other words, you can override BMC ProactiveNet’s generic probable cause information by attaching a rule to a specific abnormality that adds known information and domain knowledge into the system.
Related Topics Adding a column to an event list for an abnormality on page 95

94 BMC ProactiveNet User Guide

Viewing all abnormalities

Deleting a column from an event list for an abnormality on page 95 Filtering event display for All Abnormalities on page 97 Viewing further information for an abnormality on page 99

Adding a column to an event list for an abnormality
All users can add a single column from an event class to events of abnormality type for groups, devices, and monitors by selecting the Event View on the All Abnormalities screen.

To add a column to an event list for an abnormality
1 Click Quick Columns Selector. 2 In the Quick Columns Selector dialog box, click Edit Columns. 3 In the Event List Column Editor dialog box, under Available Columns, click Event Class Selector .

4 Select Abnormality as the event class, and then click OK. 5 Drag a column name into the header row of the event list. The newly added column now appears in the event list and the same is removed from the Events List Column Editor dialog box. Related Topics Deleting a column from an event list for an abnormality on page 95

Deleting a column from an event list for an abnormality
All users can delete a single column from the event list for an abnormality by selecting the Event View on the All Abnormalities screen. This operation requires the event list and the Quick Columns Selector dialog box to be open simultaneously.

To delete a column from an event list for an abnormality
1 Click Quick Columns Selector.

Chapter 2 Working with events 95

Viewing all abnormalities

2 From the event list, drag a column name from the header row of an event list and drop it into the Event List Column Editor dialog box.

Tip To view the columns in the default template, in the Event List Column Editor dialog box, click Intelligent Event Details.
The All Abnormalities => Grid View has different subtabs that display different information about abnormalities. The Device View tab groups events by device with the option of expanding any device for information about its events, and the All View tab lists all events regardless of their device association. Table 11 on page 38 summarizes the columns of information available for events on the All Abnormalities screen. When you search for abnormality based on service name, it also displays direct impact abnormalities. Table 21: Columns of alarm information on the All Abnormalities >Grid View screen
Column Description Device View Select Device Selection column for further information and analysis Name of the device In the case of an event on Aggregate Monitors (Resource Pool Monitors and Abnormality Index Monitors), No associated device is displayed. Num Events Severity Total number of events opened for the device Indicates whether it is a Threshold problem or a Signature problem Signature problems are described as 'Abnormal'. Threshold issues are shown as 'Critical', 'Major', or 'Minor'. Score Indicates how closely the alarm relates to the probable cause of the problem All View or event under expanded device Select Time Opened Monitor Severity Selection column for further information and analysis Date and time when the event took place Monitor instance to which this event belongs Indicates whether it is a Threshold problem or a Signature problem Signature problems are described as 'Abnormal'. Threshold issues are shown as 'Critical', 'Major', or 'Minor'.

Note

96 BMC ProactiveNet User Guide

Viewing all abnormalities

Column Description

Description Provides an indication of why the event went off On Mouse over, the tool tip on the icon displays the abnormality details. The tabular data provides Baseline, Hourly, Daily, and Weekly values. For attributes of Poisson Type, the abnormality details show 10%, median, and 90% values. However, for attributes of Normal Type, the abnormality details show the Min (Minimum), Avg (Average), and Max (Maximum) values.

Analyze Score

The Probable Cause Analysis icon launches the Probable Cause Analysis screen. Indicates how closely the event relates to the probable cause of the problem Each event listed in the table is given a score between zero and 100 percent, indicating the possibility that this event is the cause of the problem. The percentage is determined by applying a Smart Filter Algorithm to the event and calculating the score value.

Tools Menu

Additional tools for further information about the event and for setting the event thresholds

Filtering event display for All Abnormalities
Note The BMC ProactiveNet Administrator can set up specific user-defined rules that can help you keep track of frequent alarms and their causes. For instance, if you continually receive an alarm and you realize that the alarm is triggered by a recognizable pattern, you can set up rules that replace BMC ProactiveNet probable cause description with specific information related to that alarm. In other words, you can override BMC ProactiveNet’s generic probable cause information by attaching a rule to a specific abnormality that adds known information and domain knowledge into the system.
You can filter events using the criteria listed in Table 22 on page 97 by selecting the Grid View instead of the default Event View on the All Abnormalities screen. These filters correspond to probable cause analysis only. Table 22: Filter options on All Abnormalities screen
Filter option Status Description Choose the status of the events you want to see. The menu lets you to choose either all open, open, acknowledged, assigned, blackout, closed, or no filter.

Chapter 2 Working with events 97

Viewing all abnormalities

Filter option Time

Description Time boundary of the event or event selected for probable cause analysis. This link displays all time-correlated events that occurred during the period. Input the following to specify the period: ■ Minus: Start time of the period; time of the event or event selected for the probable cause analysis - time selected in minutes. ■ Plus: End time of the period; time of the event or event selected for the probable cause analysis + time selected in minutes. All events that occurred during this time range are queried for probable cause based on the Smart Filter check box selection. The Time Filter on probable cause Analysis page does not filter based on the selected time range (even though the filter results heading indicates the time range). This is 'as designed'. By default, if you are doing probable cause analysis on a non-availability (up or down) problem, then events or events that were opened up to 24 hours ago are included, as long as they are still open in the time window the user specified. This is configured in installDirectory /usr/pronto/conf/pinpoint.conf filterRules.TimeFrameForPastOpenEvents=86400. This design accommodates degradation issues resulting from something that happened several hours earlier. For example, if a process starts using an abnormal amount of memory at 10:00 AM and memory usage continues to grow to the point, that at 4:30 PM, it affects some transactions to that device.

Device Name Group Monitor Category Score

Specify the device name (already set up) to view corresponding records. Select a group from the list to limit the displayed records to those that are associated with the group. Select a monitor category by which to filter one of the following: user transactions, application, network, system, or database. Indicates how closely the event relates to the probable cause of the problem Each event listed in the table is given a score between zero and 100 percent, indicating the possibility that this event is the cause of the problem. The percentage is determined by applying a Smart Filter Algorithm to the event and calculating the score value.

Smart Filter

Select this option to apply Smart Filters (built-in Probable Cause Analysis algorithm to find out the most probable cause). This filter limits events to a selected set based on type and other attributes. If you clear the check box, BMC ProactiveNet displays all events that occurred during the selected period. For details, see To set the filter criteria on page 99.

98 BMC ProactiveNet User Guide

Viewing all abnormalities

BMC ProactiveNet supports the following relationships:
■ service to service ■ service to group ■ group to group ■ group to service ■ service to device ■ group to device

Note

The service definition is always maintained as the source of the relationships. For example, when you search for an abnormality based on service name it also displays direct impact abnormalities in the underlying relationships.

To set the filter criteria
1 Click Edit to set the filtering criteria. 2 Select one of the following options to apply filter criteria:
■ Show all events for each monitor instance ■ Show one event per attribute for each monitor instance ■ Show only top scored event for each monitor instance

3 Select the Save as default option if you want to set current setting as default filter criteria. 4 Click Apply.

Viewing further information for an abnormality
You can view further information for an abnormality by selecting the Grid View instead of the default Event View on the All Abnormalities screen, expanding the + icon in the Select column, and then clicking the wrench icon in the Tools Menu column.

Chapter 2 Working with events 99

Viewing events and abnormalities by service

Table 23: Further information options on the All Abnormalities screen Option View a statistics graph View the parent group of a subgroup View abnormality details View Probable cause Analysis for the abnormality View graphical representation of an event record Details Choose Tools Menu => Show Graph. BMC ProactiveNet provides additional options to modify the graph. Choose Tools Menu => Show Parent Groups. Place your mouse over the i icon in the Description column Click the Probable Cause Analysis icon in the Analyze column Select the check box in the Select column and click Show Graph(s). The Graph Display screen provides additional functionality through icons on the right side of the graph. Use these icons to zoom in on graphs, add the graph to a view, and perform other functions.

Viewing events and abnormalities by service
The All Services => Grid View summarizes events and abnormalities of all service groups, and helps you visualize event and abnormality information for services. To access All Services => Grid View, select the Events Console => All Services subtab, and click the Grid View icon. You can filter the list of services using the fields described in Table 24 on page 100.
Table 24: All Services => Grid View filter fields Field Status Description Displays a list of status values such as: ■ Open ■ Acknowledged ■ Assigned ■ Closed The default value is No Filter.

100 BMC ProactiveNet User Guide

Viewing events and abnormalities by service

Field Severity

Description Displays a list of severity values such as: ■ Critical ■ Major ■ Minor ■ Warning ■ Information The default value is No Filter. The severity values Predictive Critical, Predictive Major, and Predictive Minor are available only if you select the Show Predictive Events option under Options > Operations > Event Display Preferences. For more information, see Customizing the display of events on page 86.

Absolute Time Range Relative Time

Enables you to restrict the list of services to a specified beginning and ending time and date range. By default, this option is unchecked. Displays a list of date and time values that lets you restrict the list of services to a time range between the current time and the selected time. The values range from one hour to three months before the current date and time. The default value is No Filter. Text string, full or partial, that retrieves matching service names. The default value is blank.

Service Name

After selecting your values, click Filter. Table 25 on page 101 summarizes the columns of information available for events on the All Services => Grid View screen.
Table 25: Columns of event information on the All Services > Grid View screen Column Service information Name Displays the service name Click the link to drill down to a list of subservices or a list of monitors and devices. If an arrow is displayed before the service name it indicates dependent service. Note: This column expands when there are too many IT group dependencies. Description

Chapter 2 Working with events 101

Viewing events and abnormalities by service

Column Status

Description Displays the highest severity status of its monitors, devices, and subservices Tool tip displays the number of open, assigned, and acknowledged events of all severities.

Details IT Group Dependencies Name

Click the icon to view the service details.

Displays the name of the IT group of this service, sub-services, and dependency groups Note: If there are too many IT group dependencies associated with a service some part of the All Services > Grid View table goes out of view. You need to scroll horizontally to view the other columns.

Monitor Category ■ User Transactions ■ Application ■ Network ■ System ■ Database ■ Other Tools

Displays the IT group name and event or abnormality status of the IT group categorized by monitor type

Additional tools for further information about data collection, change logs, adding change entry, and for setting event thresholds

Related Topics Viewing further information for All ServicesGrid View on page 102

Viewing further information for All Services => Grid View
The following table summarizes the available options for further information about a specific event on the All Services => Grid View screen.

102 BMC ProactiveNet User Guide

The Service Details page does not include information about external events. current status. abnormalities. see Viewing further information for All GroupsGrid View on page 111.Viewing events and abnormalities by service Table 26: Further information options on the All Services => Grid View screen Options Event History Details Displays the name. Displays a graphic representation of the services from the last 24 hours along with service information Displays the service name. event count. both of which comprise the service. source agent. service description. For information on tool tips. In the Monitors tab. If a service has both a dependency and a container relationship with the same subservice or device. and predictive events. monitor type. then the container relationship takes precedence over the dependency relationship. and event summary. Viewing monitor and device information under the All Services => Grid View In the All Services => Grid View screen. and relationships Event Summary Graph Service Information Limitations The All Services => Grid View does not support Group to Service and Group to Device relationships. you can view the following information described in Table 27 on page 103: Table 27: Monitor details: All Services Column Monitor Name Monitor Type Source Agent Open Description String description of the monitor Functional category of monitor Agent to which the monitor belongs The highest severity event Chapter 2 Working with events 103 . Clicking an event or abnormality icon opens the event list screen. you can click the service name to drill down to a detailed view of the monitors and devices. From the count of events you can drill down to the event list. IT groups.

Viewing events and abnormalities by service Column Closed Collect Data Tools Description Number of closed events Check box that indicates whether data collection for the monitor is turned on Options are: ■ Show Graph ■ FlashCheck ■ Manage Data Collection ■ Thresholds ■ Show Parent Groups ■ Add Change Entry ■ Reset Baseline In the Devices tab. such as those from external sources 104 BMC ProactiveNet User Guide . you can view the information described in Table 28 on page 104: Table 28: Device details: All Services Column Device Name Agent Type User Transactions Application Network System Database Other Description String description of the device Associated agent name Functional category of device Events under the Web-URL monitor Events under the rate monitor Events under the Ping monitor Events under the Windows File System monitor Events under a database monitor Miscellaneous events.

database. The color of this icon is ■ Intelligent events and external events that are associated with a device (device- associated events) that have the highest severity are displayed. network. its severity color based on a direct impact check. Viewing services in a hierarchical tree The All Services => Tree View displays all service groups in a hyperbolic tree for a user-defined time duration. and Services tabs are displayed only if the relationships exist. Devices. application. a dashed line is shown with Chapter 2 Working with events 105 . Group to Device. Monitors. or other) based on the severity of the predictive event. The All Services => Tree View supports the following probable cause analysis relationships: Service to Group. system. and Service to Device. ■ If there are any events related to a dependent group. with the option of expanding the tree to display the contents of the service groups and their infrastructure groups. The following information is displayed in the All Services => Tree View: ■ Categorization of the aggregate event status for each service by category (user transactions.Viewing services in a hierarchical tree Column Tools Description Options are ■ Device at a glance ■ Manage Data Collection ■ Add Change Entry ■ Show Change Log ■ Show Parent Groups ■ Close Events ■ Diagnostics Some options are available only when certain events are selected. Note When you drill-down a service. ■ The Predictive icon is displayed next to the category icon. Group to Group. Group to Service.

Table 29: Controlling the display in the All Services => Tree View Objective Change the focus point on the tree Change the data refresh interval Display or hide the legend Instructions Drag any point on the Tree. This is due to known issues with the browser.conf. To ensure the proper display of the Group tree correctly on Firefox 1. Various icons indicate the severity of system objects (application. Data refresh interval (in seconds) for the Group Tree can be specified using the property 'pronet. perform the following on Windows 2000 or XP: 1 In the Windows Control Panel.applet. and then change the default Use browser settings option to Direct connection. 106 BMC ProactiveNet User Guide . double-click the Java icon.0. Note Related Topics Controlling the display in the All Services Tree View on page 106 Controlling the display in the All Services => Tree View This topic summarizes the various actions that you can perform to control the display of information on the All Services => Tree View. ■ Services containing metrics which belong to SLO (Service Level Objective) are highlighted with an indication whether the SLO has open violations or no open violations If BMC_ProactiveNetServer is within the firewall and the Operations Console is outside the firewall. click Network Settings.5. 2 In the Java Control Panel. transactions.grouptree. database. then the Group tree might not be displayed properly in Firefox 2. Indicators are aggregated at each level and propagated upwards.Viewing services in a hierarchical tree ■ Aggregate abnormality score for each service (as a purple thermometer bar) ■ Dependency events can be propagated by accessing Options > Administration > Advanced > Edit Relationships and selecting the Direct Impact check box. network. the impact on services. and other). you can display a legend by clicking Show Legend. and the abnormality score (it indicates how close the event abnormality is to failure) For a full list of icons. system.refreshRate' in installDirectory/ pw/custom/ conf/pronet. the impact on SLOs.

To enable dependency event propagation.propagateDependencyEventsBasedOnDirectImpact property in the pronet. dependency events are not propagated in the service tree. ■ All Events ■ All Abnormalities ■ Manage data Collection ■ Add Configuration Change ■ Show Configuration Changes ■ Service Details ■ Set As Root Services are displayed based on the access level and event display preferences of the user. if a relationship is created for Service A to Service B and again Service B to Service A. Click the list to choose an appropriate time by which to filter the display.Viewing events by group Objective Change the time list Filter the displayed services Instructions The default time is None.applet.tree. Instead. determined by your operating needs. Viewing events by group On the All Groups => Grid View screen you can re-calibrate events in the Event Status chart and display results based on groups set up by the BMC ProactiveNet administrator. a user might be restricted to view only a subset of services that exist in the system.propagateDependencyEventsBasedOnDirectImpact= true Limitation If cyclic service-to-service relationships are created. For example.applet.tree. then tree does not behave as expected. Groups contain selected set of devices or applications.conf from false to true: pronet. it displays the first service that is encounters and ignores the other service with the same name. change the value of the pronet. special monitoring of devices and applications Chapter 2 Working with events 107 . The service tree does not display duplicate services at the same level. For example. then the tree does not behave as expected. For example. Propagate dependency events By default.

The number of records for a particular page displayed at the bottom right corner in this view considers only the parent groups and will not consider the child groups under it. You can switch between hierarchical/flat view. BMC ProactiveNet administrator selects the groups available to a user in the corresponding User Profile. or individual. The All Groups table displays only top level groups that is. Related Topics Default groups on page 110 Filtering event display for All Groups on page 110 Viewing further information for All GroupsGrid View on page 111 Table 30: Columns of event information on the All Groups >Grid View screen Column Group Name Description Information about the associated device When you bring the mouse over the group name the following details are displayed as tool tip: ■ Group Path ■ Group Name ■ Group Description ■ Source is displayed only if it is CMDB auto sync 108 BMC ProactiveNet User Guide .Viewing events by group might be setup by building. If no virtual solution is configured then flat view is the default view The display on this screen differs. depending on the configuration of display— whether with counts or with severity icons (see Customizing the display of the event list on page 34). Hierarchical view is the default view only if there are groups in the system that can be displayed in hierarchy. list of groups which are not part of any other group. Table 42 on page 154 summarizes the columns of information available for events on the All Groups => Grid View screen. department. The counts displayed in the Grid View include intelligent events and external events that are associated with a device (deviceassociated events).

The severities are displayed as an icon. including options to view graphs. Events of each type.Viewing events by group Column Numbers of events by severity ■ Critical ■ Major ■ Minor ■ Predictive ■ Warning ■ Information ■ Closed a Description The number of events for each severity The color indicates severity of the events. set thresholds. Additional tools for further information about the event. Chapter 2 Working with events 109 . These devices are displayed. When you place your mouse over this column. and view diagnostics under Device at a Glance. depending on user configuration (see “Viewing all abnormalities” on page 85). the numbers of events of each severity is displayed. a Events are displayed with either number of events or severity icons. Both the icon and the color represent event severity. Events by type Step 1 on page 119 ■ User Transactions ■ Application ■ Network ■ System ■ Database ■ Other Devices Tools Devices contain monitors that are under a group.

Time Range option allows the Start and End Time selections to reflect either a particular day and hour or a particular duration of time. closed. Table 32: Filter options for All Groups => Grid View Filter option Status Severity Description Choose the status of the events you want to see. or no filter. System-related default monitors like System. Table 31: Default groups available in BMC ProactiveNet Group name BMC_ProactiveNet BMC_ProactiveNetServer BMC_ProactiveNetAgent Description BMC_ProactiveNet is a parent group. Default Agent status monitor is grouped under BMC_ProactiveNetAgent. The menu lets you to choose either open. week. is created for this default group. i do not see severities marked in red? or no filter Choose the events in the specified time. information. major. Specify the group name to which the events that you want to view are associated Absolute Time Range Relative Time Group Name 110 BMC ProactiveNet User Guide . such as the last four hours. assigned. File System and Process monitors are grouped under BMC_ProactiveNetServer. Choose the severity level of the events you want to see. This contains two child groups namely BMC_ProactiveNetServer and BMC_ProactiveNetAgent. predictive major. Use this option to show the events in the specified time range. The menu lets you to choose critical. predictive critical. DefaultRule-BMC_ProactiveNet. predictive minor. The menu lets you choose from 1 hour up to 3 months. minor. Table 32 on page 110 describes the available filter options. major and above.Viewing events by group Default groups The following groups are available in BMC ProactiveNet. You can change the time and date when you want to view resource data for the previous day. warning. Filtering event display for All Groups All Groups => Grid View offers filters to query and view specific records. by default. acknowledged. or hour to compare measurements. and the action type is email notification. The default event rule.

View group details Choose Tools => Group Details to display a graphic representation of events issued for the group over the past 24 hours along with group information and a history of all events from the past 24 hours. it only lists devices belonging to the selected group. This screen gives the monitor details for the group. see . For information on tool tips. The Show Device screen is similar to All Devices. see Setting event thresholds on page 184. Limitation The Group Details page does not include information about info. However. Note: The Group Details page does not display external events. Click Sub Groups to view subgroup information. devices that are part of more than one subgroup are listed only once.Viewing events by group Viewing further information for All Groups => Grid View The following table summarizes the available options for further information about a specific event on the All Groups => Grid View screen. For more information. the Device drill-down displays all devices belonging to the subgroups. In case of groups made up of subgroups. Links are available to a drill-down Event List. which is made of other groups (subgroup-based). the navigation displays all subgroups under the main group (even if you have not selected the individual subgroups). abnormality. If you select a group. Further drill-down to individual monitors is available from the Show Device screen. However. and predictive events. abnormalities. warning. Click Edit Thresholds. or predictive events. Chapter 2 Working with events 111 . View devices associated with a group Click Devices to view all devices associated with the group. The All Groups => Grid View table might contain subgroup information. Use the Tools list to get additional information. Table 33: Further information options on the All Groups => Grid View screen Option Drilling down to monitors associated with a group Drilling down to subgroups Details Click the Group Name link to navigate to the selectedGroupName screen.

monitor name the tool tip displays device name. instance name. you can click the group name to drill down to a detailed view of the monitors and devices.VMware Adapters: Do a mouse-over at the instance hierarchy level on Viewing monitor and device information under the All Groups => Grid View In the All Groups => Grid View screen. and monitor name. ■ Tool Tip . you can view the following information described in Table 34 on page 112: Table 34: Monitor details: All Groups Column Monitor Name Monitor Type Source Agent Open Closed Collect Data Description String description of the monitor Functional category of monitor Agent to which the monitor belongs Displays the highest severity icon and the tool tip displays the severity and status counts separately. and host name.TMART Adapters: Do a mouse-over at the instance hierarchy level on ■ Tool Tip . monitor name the tool tip displays the device. Number of closed events Check box that indicates whether data collection for the monitor is turned on 112 BMC ProactiveNet User Guide . location. ■ Tool Tip .Viewing events by group Tool Tip description for various adapters at instance hierarchy level. ■ Tool Tip . both of which comprise the group.Portal: Do a mouse-over at the instance hierarchy level on monitor Note name the tool tip displays absolute path and hierarchy of the instance. In the Monitors tab. The instance hierarchy level is displayed only if there is hierarchy. and host server. project.Native Adapters: Do a mouse-over at the instance hierarchy level on monitor name the tool tip displays device name.

Viewing events by group Column Tools Description Options are ■ Show Graph ■ FlashCheck ■ Manage Data Collection ■ Thresholds ■ Show Parent Groups ■ Add Change Entry ■ Reset Baseline ■ View Service Impact Graph In the Devices tab. you can view the information described in Table 28 on page 104: Table 35: Device details: All Groups Column Device Name Agent Type Description String description of the device Associated agent name Functional category of device User Events under these categories TransactionsApplicationNetworkS ystemDatabaseOther Tools Options are ■ Device at a Glance ■ Manage Data Collection ■ Add Change Entry ■ Show Change Log ■ Show Parent Groups ■ View Service Impact Graph Chapter 2 Working with events 113 .

■ The Predictive icon is displayed next to the category icon. To ensure the proper display of the Group tree correctly on Firefox 1. The color of this icon is ■ Intelligent events and external events that are associated with a device (device- associated events) that have the highest severity are displayed. application.5.Viewing events for groups in a hierarchical tree The functionality is similar to that described for the All Services => Grid View screen under Viewing monitor and device information under the All ServicesGrid View on page 103. The entire group hierarchy and devices are all visible on a hyperbolic pane mapped to a circular display region.5. Information is displayed for Monitors that are not part of the explicitly mentioned monitor types which are listed under the 'Other' category. perform the following on Windows 2000 or XP: 1 In the Windows Control Panel. database. or other) based on the severity of the predictive event. then the Group tree might not be displayed properly in Firefox 1. interactive visualization of the event status for a user-defined time duration. ■ Aggregate abnormality score for each service (as a purple thermometer bar) If BMC_ProactiveNetServer is within the firewall and the Operations Console is outside the firewall. double-click the Java icon. system. and then change the default Use browser settings option to Direct connection. 2 In the Java Control Panel. Related Topics Controlling the display in the Tree View on page 115 Note 114 BMC ProactiveNet User Guide . This is due to known issues with the browser. network. Viewing events for groups in a hierarchical tree The Group Tree provides a real-time. click Network Settings. ■ Categorization of the aggregate event status for each service by category (user transactions.

system. Change the data refresh interval Data refresh interval (in seconds) for the Tree View can be specified using the property 'pronet. For example. Controlling the display in the Tree View This topic summarizes the various actions that you can perform to control the display of information in the Tree View. network. Filter the displayed groups ■ All Events ■ All Abnormalities ■ Manage data Collection ■ Add Change Entry ■ Show Change Log ■ Group Details ■ Set As Root ■ View Service Impact Graph Groups are displayed based on the access level and event display preferences of the user. Change the focus point on the tree Drag any point on the tree Display or hide the legend Chapter 2 Working with events 115 . Dependent relationships are indicated by dotted lines. you can display a legend by clicking Show Legend.applet. and the abnormality score (indicates how close the event is to failure) For a full list of icons.conf Various icons indicate the severity of system objects (application. transactions. the impact on SLOs.grouptree.Viewing events for groups in a hierarchical tree Note Group to group dependent relationships are not represented in hierarchical fashion. and other). Table 36: Controlling the display on the Tree View Objective Instructions Indicators are aggregated at each level and propagated upwards. the impact on services. Container relationships between groups are supported and depicted by connecting bold lines. database.refreshRate' in installDirectory/ pw/custom/conf/pronet. a user may be restricted to view only a subset of groups that exist in the system. Only IT dependent relationships are permitted between services and groups.

116 BMC ProactiveNet User Guide .Viewing events by device Objective Filter the displayed devices Instructions ■ All Events ■ All Abnormalities ■ Device at a Glance ■ Manage data Collection ■ Add Change Entry ■ Show Change Log ■ Show Parent Groups ■ Diagnostics Filter the displayed monitors ■ All Events ■ All Abnormalities ■ Show Graph ■ Flash Check ■ Manage data Collection ■ Thresholds ■ Show Parent Groups ■ Add Change Entry ■ Reset Baseline ■ Diagnostics Viewing events by device When BMC ProactiveNet discovers a problem with a device. the monitor setup for that device activates an event triggered by the specific conditions set up for that device (sometimes also called the Monitored Resource). A monitored resource does not generate an event unless the event conditions are specified in the Event Profile.

see. ■ Device is marked for deletion (displayed for devices that are marked for deletion). providing a quick view of the overall health of the system. The All Devices screen. The number of records for a particular page displayed at the bottom right corner in this view considers only the parent devices and will not consider the child devices under it. The icon displays a cross mark next to the Device Name.Viewing events by device The Event Profile consists of Event Thresholds (to generate an event) and Event Rules (to send event notifications). The counts displayed in the Grid View include intelligent events and external events that are associated with a device (device-associated events). ■ Multiple IP address (displayed only for CMDB devices that have multiple IP addresses) Chapter 2 Working with events 117 . Table 37: Columns of event information on the All Devices screen Column Device Name Description Information about the associated device. The BMC ProactiveNet administrator sets event profiles. All Devices screen under the Events Console tab. For more information on event profiles. the BMC ProactiveNet Administrator Guide. Hierarchical view is the default view only if there are devices in the system that can be displayed in hierarchy. depending on the configuration of display—whether with counts or with severity icons (see Customizing the display of the event list on page 34). If no virtual solution is configured then flat view is the default view. Table 37 on page 117 summarizes the available options on the All Devices screen. When you bring the mouse over the device name the following details are displayed as tool tip: ■ Device Name ■ IP address ■ Device Description or OS Name. displays information about the events that were issued for all devices that BMC ProactiveNet is monitoring. You can switch between hierarchical or flat view. you can view the device hierarchy on clicking Show Hierarchy. the out-of-box default screen displayed on the Events Console tab. You can expand the physical host node to see the virtual computers running in the system. Default settings are also available in BMC ProactiveNet for automatic configuration. The display on this screen differs.

118 BMC ProactiveNet User Guide . Events by type Step 1 on page 119 ■ User Transactions ■ Application ■ Network ■ System ■ Database ■ Other Events of each type. Both icon and color represent event severity. Numbers of events by severity The number of events for each severity a The color indicates the severity of the events. and a red Unplugged icon indicates the agent is disconnected. ■ Critical ■ Major ■ Minor ■ Predictive ■ Warning ■ Information ■ Abnormal ■ Closed The severities are displayed as an icon. When you place your mouse over this column. either connected or disconnected.Viewing events by device Column Agent Description Displays the status of the agent attached to the device. A green Plugged icon indicates that the agent is connected. server or web server). When you bring the mouse over the agent icon the following details are displayed as tool tip: ■ Status ■ OS Name Type Displays the type of device (for example. the numbers of events of each severity is displayed.

Filtering event display for All Devices You can filter the listed events using the criteria listed in the following table. Available groups are displayed either as Hierarchy or as Flat. major. The menu lets you to choose either open. a Events are displayed with either number of events or severity icons. or no filter. warning. predictive major. Specify the name of a device to limit the display to events associated with a specific device. or hour to compare measurements. Absolute Time Range Relative Time Group/Services Device Name To include or exclude a group 1 Click the link corresponding to group to open the Group Filter window. The menu lets you to choose critical. assigned. closed or no filter. You can change the time and date when you want to view resource data for the previous day. Parent and child devices are displayed to make the hierarchy complete. set thresholds. and view diagnostics under Device at a Glance. minor. Time Range option allows the Start and End Time selections to reflect either a particular day and hour or a particular duration of time. 2 Expand or collapse the groups. Use the arrows to move the selected groups. Select the groups. Choose the severity level of the events you want to see. Chapter 2 Working with events 119 . The menu lets you choose from 1 hour up to 3 months. You can include or exclude the groups to view the events that are associated to it. including options to view graphs. Use hierarchy on or off to switch over to the corresponding view type. acknowledged. Use this option to show the events in the specified time range. information.Viewing events by device Column Tools Description Additional tools for further information about the event. predictive critical. major and above. Choose the events in the specified time. such as the last four hours. Table 38: Filter options for All Devices Filter option Status Severity Description Choose the status of the events you want to see. week. Select No Filter option to consider all the events of the available groups. predictive minor. depending on user configuration (see “Viewing all abnormalities” on page 85). If the filter criteria is not matching then the parent is displayed in italics.

or Exclude Selected Groups. From this screen. then Closed Time will be displayed for all closed events. you can show graphs and create rules. you can click Status. device Click the Severity icon (or the Count) link to view open events. ■ Exclude Selected Groups: To exclude the selected groups. ■ No Filter: To consider all the groups. No time value is displayed in the Closed Time Column if the event is in open condition. If Status selected is No Filter. Analyze. Selected groups will be displayed in the All Events screen. ■ Include Selected Groups: To include the selected groups. Viewing further information for All Devices The following table summarizes the available options for further information about a specific event on the All Devices screen. Table 39: Further information options on the All Devices screen Option Drilling down to monitors associated with a device Details Click the Device Name link to navigate to Show Monitors: All Events screen. The probable cause link on the Event List opens the Probable cause Analysis screen for selected events and indicates the open events associated with the event. Included groups will be displayed with (+) sign and excluded groups will be displayed with (-) sign. Use the Tools list to get additional information. and Tools links to get additional information. Drilling down to an event list for a The middle columns indicate triggered events (if any) on the Device.Viewing events by device 3 Select No Filter. Show Monitors screen gives the monitor details for the device. see the BMC ProactiveNet User Guide. For details. all closed events will have Open Time and Closed Time and open events will have only Open Time. 120 BMC ProactiveNet User Guide . which you can modify as required. Include Selected Groups. View event history and graphs for a device Analyze probable cause This opens the Event History screen and Graph Display. From the Event List screen. If Status selected is Closed. 4 Click Apply.

The number of events for each severity The color indicates the severity of the events. system. Numbers of events by severity ■ Critical ■ Major ■ Minor ■ Predictive ■ Closed The severities are displayed as an icon. Chapter 2 Working with events 121 . Choose Tools => Show Parent Groups. Table 40: Columns of event information on the All Monitors screen Column Monitor Category Current Status Description Application. Choose Tools => Device at a Glance.Viewing events for monitored services Option Device at a Glance Details Device at a Glance allows easy navigation from the graph to other related attributes graphed below without having to re-implement graph selections. BMC ProactiveNet filters and re-calibrates the displayed events based on the monitored services. Open events with highest severity are displayed. When generated. network. Table 40 on page 121 summarizes the columns of information available for events on the All Monitors screen. the open event status. and number of closed events for each service. Choose Tools => View Service Impact Graph. When you access All Monitors. The severity icon can be critical. View the parent group of a subgroup Viewing devices that are associated to a CI Viewing events for monitored services All Monitors displays information about services monitored by BMC ProactiveNet. the Device At a Glance page shows a stacked line graph for all monitors on the device. user transactions. major or minor. This option can also be accessed from the Graph Display page. database. Click the severity icon to drill-down to Event List screen. other Displays the severity of the open events. If there are no open events green icon is displayed.

122 BMC ProactiveNet User Guide . Acknowledging an event triggers the associated event rules. Click the link to view all monitors in that category. Choose Tools => View Service Impact Graph. click the Monitors link to view the list of monitors by type. This feature is helpful when you want to know who has addressed the event or who is responsible for the event. This options is available only if the monitor has a valid CI. see Viewing further information for All GroupsGrid View on page 111. View a statistics graph View the parent group of a subgroup Viewing monitors that are associated to a CI Choose Tools => Show Graph(s) BMC ProactiveNet provides additional options to modify the graph. Choose Tools => Show Parent Groups. Acknowledging events BMC ProactiveNet provides the option of acknowledging events and add messages to those events. the associated event rules are not triggered. You can choose to either expand or collapse all the monitor names. Monitor names are displayed hierarchically based on the relationship between the parent and child monitor instances for the selected monitor type. Table 41: Further information options on the All Monitors screen Option Drilling down to view Monitor types To view monitors in a specific category Details Click the link to view Monitor Types under the particular service. From here. If acknowledging is cleared. You cannot drill-down from the instances that do not have stats attributes. Viewing further information for All Monitors The following table summarizes the available options for further information about a specific event on the All Monitors screen. Instances that satisfy the filter criteria are shown normally and those that do not satisfy the filter criteria are also displayed in italics to complete the hierarchy. An ellipsis (three-dot) icon displayed along with the monitor name indicates that the monitor is an Aggregate Monitor. For information on tool tips.Acknowledging events Column Monitor Types Description Click the link to view all monitors in that category. This column is collapsed by default. click the Monitors link to view the list of monitors by type. From here.

1 From the All Events tab go to Tools Menu => Operations => Acknowledge Event. select the Acknowledge check box. and is not valid when the severity status of the event changes. To set the acknowledgement message 1 On the All Events tab. 4 Enter the acknowledgement message text (up to 128 characters) in the Message box. you must be assigned “Allow Acknowledge Event” privileges by the BMC ProactiveNet administrator. major. 2 On the Intelligent Event Details page. Acknowledgment is applied only to event instances of the same severity (minor. 3 If you want to assign the event to yourself. BMC ProactiveNet updates the event status screen advising others on the event acknowledgment. select Tools => Acknowledge Event. 5 Click Submit. see Viewing all abnormalities on page 93. Summary views set to show counts do not display Acknowledged events. choose Tools => Intelligent Event History . 2 In the Acknowledge Event Confirmation box. add a note and click Yes if you are sure you want to acknowledge the event. Related Topics To acknowledge a specific event on page 123 To set the acknowledgement message on page 123 To view operations history on page 124 To acknowledge a specific event Note To acknowledge events. or critical) as at the time of acknowledgement. Chapter 2 Working with events 123 .Acknowledging events To limit the display of events to events that have not yet been acknowledged. Acknowledged events are available only to the person acknowledging the event. Your message is displayed together with the event on the Intelligent Event History screen.

(s) from the tool tip (s) from the tool tip ■ All Devices => Grid View: do a mouse over on Tools and select Close Event ■ All Groups => Grid View: do a mouse over on Tools and select Close Event ■ Specific event on the All Events tab.Closing events To view operations history 1 On the All Events tab. choose Tools => Close Event on the row of the relevant object: ■ Service on the All Services => Grid View tab. 124 BMC ProactiveNet User Guide . 2 On the Intelligent Event Details page. or the Probable cause analysis screen 2 Click OK on the confirmation message. but after a week it is removed from the system. When closing events from the service object. Closing events The Close Event feature allows you to close events manually. along with timestamp details. When you close an event it can be viewed in the system for a week. This feature is useful if the Auto Close option for automatically closing events (set through the Event Thresholds Setting screen) was not selected or could not be selected for lack of appropriate authorizations. choose Tools => Intelligent Event History . the system considers only container events. Related Topics To close an event or a group of object events on page 124 To close multiple events on page 125 To close an event or a group of object events 1 From the appropriate display of events. The Operation History for selected Event window contains all operations or messages associated with an event. Dependency events are not closed. select Tools => Operation History. the Event Details screen.

Chapter 2 Working with events 125 . select the relevant events through the appropriate check box in the Select column. This option is available on all event screens. 2 Click Close Event above the list of events. and provides information on the possible impact to your Web environment.Managing configuration changes To close multiple events 1 On the All Events tab. Related Topics To add a configuration change entry on page 125 To view and manage all configuration changes that have been submitted on page 126 Note To add a configuration change entry 1 From the appropriate display of events. Add Configuration Change can also be accessed through Options => Administration tab. 3 Click OK on the confirmation message. choose Tools => Add Configuration Change on the row of the relevant object: ■ Event on the All Events tab ■ Abnormality on the All Abnormalities tab (All View) ■ Service on the All Services => Graph View tab ■ Group on the All Groups => Grid View tab ■ Device on the All Devices => Grid Viewtab ■ Monitor on the Show Monitors screen accessed from the All Monitors tab ■ CI on the All Services => Tile View or All Services => Graph View. Managing configuration changes Add Configuration Change screen stores and tracks configuration data.

group. ■ The time when the event was generated. such as an urgent server maintenance task that must be carried out. Note Managing data collection The Manage Data Collection function gives you the flexibility to pause and resume data collection by a device. name of contact person. or service. 3 Click Apply. date and time. In the graph.Managing data collection 2 Enter the specifications of the configuration change event: user. you can filter the change entries by date and time. Change entry events (Configuration Change Events) which were generated during the previous releases does not get migrated to the current version. or groups of monitors. ■ The description given while generating the event. Users with Allow Collect Data Management privileges can use the Manage Data Collection feature to start or stop data collection for a monitor. monitor. choose Tools => Show Change Log on the row of the relevant object: 1 device on the All Devices => Grid View 2 group on the All Groups => Grid View 3 service on the All Services => Tile View or All Services => Graph View. This feature enables you to stop data collection by entities immediately during unforeseen situations. device. when you place the cursor on the Configuration Change Event icon the tooltip displays the following: ■ Configuration Change Event ■ The date when the event was generated. To view and manage all configuration changes that have been submitted From the appropriate display of events. select Show External Events option from the Custom Graphs while generating the graph. On the Configuration Change screen. To view the configuration change event. and long description. device. 126 BMC ProactiveNet User Guide . summary. and group or service.

The Pause period that you define and assign is a one-time setting and not recurring.pause. ■ The following configurable properties that control the Manage Data Collection function are listed in the pronet. will be displayed in the Operations Console.minutes. You can choose to stop event generation. upgrade users have the ability to pause or resume the following options: ■ Event Generation ■ EventRule Action or Notification ■ Calculate Baseline ■ Data Collection Pausing data collection The Pause feature allows you to specify a time range during which a selected device. New users can pause or resume Data Collection only from the Manage Data Collection dialog.defaultVal indicates the default pause duration that Distinction between new and upgrade users Just as in the Scheduled Down Time feature. or data collection by the entity during this latent phase. event notification. new and upgrade users have different options available to them.Managing data collection Note ■ Schedules set using the Schedule Device Downtime feature of the Administration Console cannot be modified using the Operations Console.pausepollperiod denotes the time interval that the scheduler looks for pause or resume requests. The minimum and default value is 60 seconds. In the Manage Data Collection dialog box. Chapter 2 Working with events 127 .server. ■ pronet. monitor. The current time is the start time of the Pause period.conf file (located in installDirectory/ pw/pronto/ conf): ■ pronet. or group of monitors will be temporarily inactive.

4 If you want to stop only certain instances of the Device or Group or Service. click the displayed link to see the status of the instances and manage the activity of specific instances. To pause data collection 1 From the appropriate display of events. for setting to On or Off) only if you select to keep data collection on. you can pause an entity for any duration without any predefined values. Event or Event Generation. 3 If you want to pause data collection. and choose when to start pausing (either immediately or after a delay that you specify).Managing data collection The Pause feature can be configured with restrictions when maximum values are defined in the pronet. and Calculate BaseLine are available for selection (that is. ■ If you want to stop only certain instances of the object. click the displayed link to see the status of the individual instances and manage the activity of specific instances. choose Tools => Manage Data Collection on the row of the relevant object: ■ device on the All Devices => Grid View tab ■ group on the All Groups => Grid View tab ■ service on the All Services => Grid View tab ■ abnormality on the All Abnormalities tab (All View) ■ event on the All Events tab ■ monitor on the Show Monitors screen accessed from the All Monitors tab 2 On the Manage Data Collection screen. If configured without restrictions. BMC ProactiveNet scheduler processes pause schedules prior to schedules defined from the Administration Console. (This is the only selection available to new users.) Note For upgrade users. Event Rule Action or Notification. specify the duration for which the object must be paused. choose Data Collection.conf file. 128 BMC ProactiveNet User Guide . A pause period that you define from the Operations Console cannot overlap an upcoming downtime schedule set from the Administration Console. except for other runtime parameters such as polling interval of the scheduler thread and any upcoming downtime schedules defined using the Schedule Device Downtime function (Administration Console).

choose Tools => Manage Data Collection on the row of the relevant object: ■ device on the All Devices => Grid View tab ■ group on the All Groups => Grid View tab ■ service on the All Services => Grid View tab ■ abnormality on the All Abnormalities tab (All View) ■ event on the All Events tab ■ monitor on the Show Monitors screen accessed from the All Monitors tab 2 On the Manage Data Collection screen. Resuming data collection The Resume feature enables you to activate an entity currently in the Pause state. This option performs a full download of the Web page (for Web monitors) or Web pages (for Chapter 2 Working with events 129 . 3 Click Resume. The Get URL option is available for Web or Web Transaction monitors. To resume data collection 1 From the appropriate display of events. without having to wait for the Pause period to complete. The Diagnostics option is not available on the Event Details page for any event that is open for more than seven days. All event-related data is archived at the end of seven days. Diagnostics BMC ProactiveNet offers both pre-configured and user-defined diagnostic tools to help monitor your system.Managing data collection 5 Click Apply. You cannot resume a device or group whose downtime schedule has been defined from the Administration Console. See Diagnostics Wizard section of the BMC ProactiveNet Administration Guide for detailed instructions on using these commands. You can only resume entities that are currently paused. select the schedules to be resumed.

FlashCheck does not influence the statistics collected in BMC TM ART Central. monitors do not retry polling. 2 Run FlashCheck according to the current view: ■ (Event View) Choose Tools => Diagnostics => FlashCheck. By triggering a poll. If FlashCheck exceeds the timeout period before data is displayed. wait a few moments and run FlashCheck again. Get URL is also an integral part of Diagnostics tool. During FlashCheck. Note FlashCheck for the BMC TM ART adapter monitors has the following differences from other BMC ProactiveNet monitors: ■ FlashCheck can only be run for active synthetic transactions. select an event in the Event View or Grid View. Data is 130 BMC ProactiveNet User Guide . ■ FlashCheck triggers the Run Now feature in BMC TM ART Central. you can quickly examine current data values from a selected monitor. ■ (Grid View) Choose Tools => FlashCheck. To examine the current data values of a monitor 1 In the Operations Console. ■ FlashCheck does not update BMC TM ART data in BMC ProactiveNet. Examining current data (FlashCheck) With FlashCheck. Results might take several minutes to appear in the FlashCheck window. A separate browser window opens with the current parameter values for the selected monitor. and to update data for newly added or edited monitors. Selecting this option displays results in a separate browser window. which executes the monitor immediately.Managing data collection Web Transaction monitors). FlashCheck triggers an instant poll from the agent running on the selected monitor. updated with the next scheduled poll. You typically use FlashCheck to determine whether a previously detected condition still exists. and shows the breakdown of all objects in those pages and their download times. you can also use FlashCheck to close resolved issues for an event before the next scheduled poll. and displays the results in a separate browser window.

and selecting the display options for those objects. the following additional cards are displayed in the Details notebook and the KPIs and Prediction cards are not displayed: Chapter 2 Working with events 131 . represented in a tile. The Details pane displays the following cards: ■ Latest 10 Events: displays the event list for the first 10 events that you select in the Canvas view ■ Summary: displays a summary of the object attributes ■ KPIs: displays violations of parameters set for Key Performance Indicators associated with the Group or Device that you select in the Canvas view object that you select in the Canvas view ■ Prediction: displays a prediction graph that shows the future status trends for the If the object displayed in the tile is a CI. device. The objects can be graphics. group. ■ Edit mode: Use this mode to create the view by selecting a background. Canvas view details You can view event details for the objects in the Canvas view in the Details notebook pane that is displayed at the bottom of the Canvas view window. or service that you select in the navigation tree by clicking the Canvas View button in the toolbar in the right pane view of the Operations Console. such as images or connectors. or metrics information. Canvas view modes The Canvas view has the following modes: ■ View mode: Use this mode to monitor the objects that you select to display in the Canvas view. adding objects. The components are represented by objects that can be placed on a background image. You can create and display a Canvas view for any event collector.About the Canvas view About the Canvas view The Canvas view in the Operations Console lets you create a graphical representation of the components that are being monitored in your environment.

or Graph view Details notebook on page 154 .Setting up and using the Canvas view ■ Status: Displays the applicable status levels of the selected object ■ Priority and Cost: Displays the schedule status. impact priority. To switch to Edit mode 1 Click the Preferences button in the toolbar. set up the objects that you want displayed in the view. click the More Info button Related topics: Setting up and using the Canvas view on page 132 Viewing the Tile. Canvas. You can create a Canvas view for static and event folders but not dynamic folders. return to View mode to monitor the object status. the page is in View mode and no objects are displayed. and then after you have set up the objects. 132 BMC ProactiveNet User Guide . devices. creation and modification time. groups. and services. you must first change to Edit mode. and consumers of the selected object ■ Schedule: displays the times when the selected component is in service ■ Advanced: displays information on identification. and the Canvas View Preferences dialog box is displayed in the Canvas view pane. possible problems. You can create a Canvas view for event collectors. When you access the Canvas view initially. To create objects in the Canvas view. and read/write permissions for groups for the selected object service level agreement associated with the component ■ SLM: if BMC Service Level Management is installed. The view is changed to Edit mode. shows information about the To expand a card to view more information. Setting up and using the Canvas view Use the Canvas view to create a graphical representation of objects that you are monitoring in your environment. providers. and impact cost for the selected object ■ Related CIs: Displays information on status causes.

2 Drag and drop an object from the list to where you want that object displayed on the background image. see “Using View mode to monitor objects in the Canvas view” on page 138 Using Edit mode to set up the Canvas view When the Canvas view is in Edit mode. To sort objects in the Monitored Objects pane. For more information about setting up the Canvas view. click the number 1 that appears in the title bar after the objects are sorted the first time. click Name in the title bar. To create the Canvas View background 1 Click the Preferences button to change the Canvas view to Edit mode. To add objects to the Canvas view 1 In the Canvas View Preferences dialog box. select the object for which you want to create a canvas view and then click the Canvas View button in the Events Console toolbar. and to choose which objects that you want to display and how you want to display them. Before you begin In the navigation tree. 2 In the Background pane in the Canvas View Preferences dialog box. click Monitored Objects. For more information about using the Canvas view to monitor objects. To reverse the sort order. see “Using Edit mode to set up the Canvas view” on page 133 .Setting up and using the Canvas view Where to go from here To return to View mode. you use the options in the Canvas View Preferences dialog box to determine how you want the Canvas view to look. ■ Select the Image option and then use the list to select the background image that you want to display. The objects are sorted in alphabetical order. Chapter 2 Working with events 133 . perform one or both of the following actions: ■ Select the Color option and then use the palette to select the color that you want to display. close the Canvas View Preferences dialog box.

■ Select the number of arrowheads: — None for no arrows — One for one arrow that by default points to the right — Two for an arrow on each end of the connector ■ To change the size of the connector. You can — Icon with severity background: displays an image of the object type on a colored background that represents the object’s current severity. Continue with List item. 5 If you selected Canvas as the object type. edit the tile attributes as follows: 134 BMC ProactiveNet User Guide . depending on the object type that you select. click the lower right corner of the boundary box and drag it until the connector is the size that you want. 4 If you selected Connector as the object type. Continue with List item. click the circle to the right of the boundary box and move it until the connector is pointing in the direction that you want. To change object attributes in the Canvas view 1 Select an object in the Canvas view. 2 In the Canvas View Preferences dialog box. on page 136. select the connector order and style as follows: ■ Bring the image to the front of the view or send it to the back of the view. on page 134. click Properties of Selected Object.Setting up and using the Canvas view After you drag and drop the object onto the Canvas view background. — Canvas: displays a tile view of the object that is being monitored. a tile is created for that object. 3 Select one of the following object types. The color of the connector shows the current status of that object. ■ Editing options are displayed. on page 134. — Connector: shows a relationship between two objects in the Canvas view. Continue with List item. Continue with List item. on page 135. To rotate the connector. resize the tile and change the attributes in the tile display. for example. if the object is in OK status. then the color of the connector is green.

For example. tiles onto the view. 6 Select the attributes that you want to display on the tile by clicking the attribute and dragging and dropping it onto the tile area. b Select the attribute that you want to display in the tile. ■ Resize Tile: use the slider bar to make the tile smaller so that you can fit more ■ Object Type Icon: select to include an icon of the object type in the title bar of ■ Not Being Worked on: indicates that an event has not been assigned and is Continue with List item. place the mouse pointer over the tile. on page 136. 7 If you selected Icon with severity background as the object style. devices have a broader list of attributes to select than services. To see the tile details. currently not being addressed. on page 135. The attributes that you can select to display depend on the object type that is displayed in the tile. selecting a tile and clicking Bring to Front displays the selected tile in the front of the other tiles in the Canvas view. If you select a KPI attribute. For example.Setting up and using the Canvas view ■ Tile order: Use the Bring to Front and Send to Back buttons to layer the order of tiles in the Canvas view. the Attribute Selection for Information Capsule dialog box is displayed. and click Apply Selection. Perform the following additional steps: a Click the item at the end of the row until a list of attributes is displayed. if the object that you are monitoring is a server. At the smallest size. For example. Continue with List item. the tile. a server icon is displayed before the object name. select the icon image and order as follows: ■ Select the image icon that you want to display: — Application — Application Server — Database — Database Server — Firewall Chapter 2 Working with events 135 . the tile is shown as an icon of the object’s current status.

To add labels and additional icons to the Canvas view 1 To add a label to the object that you are monitoring. 9 Close the Canvas View Preferences dialog box to save your changes. 136 BMC ProactiveNet User Guide . click the lower right corner of the boundary box and drag it until the image is the size that you want. 10 Click Refresh to display data for the new metrics. on page 134 through List item. on page 136. The Canvas view is returned to View mode. in the Background pane in the Canvas View Preferences dialog box. 8 Repeat List item. To change the size of the image. Continue with List item.Setting up and using the Canvas view — Mail Server — Network — Other — Remote Agent — Router — Server — Switch — System — User Transaction — Web Server — Arrow — Box — Line ■ Bring the image to the front of the view or send it to the back of the view. on page 135 for each object that you add to the Canvas view. drag and drop the Label icon onto the Canvas view and position it near the object that you want to label.

4 Click Apply. in the Background pane. 5 To add an additional icon near a tile object that you are monitoring. 6 Click Properties of Selected Object and select the icon image and order as follows: ■ Select the image icon that you want to display: — Application — Application Server — Database — Database Server — Firewall — Mail Server — Network — Other — Remote Agent — Router — Server — Switch — System — User Transaction — Web Server — Arrow Chapter 2 Working with events 137 . enter the text that you want to display in the Label Options text box and use the additional formatting options to select the text font. drag and drop the Clip Art Image icon onto the Canvas view and position it near the tile object that you want it to represent. size. 3 In the Properties of Selected Object pane. and style.Setting up and using the Canvas view 2 Click Properties of Selected Object.

you can monitor the event status of the objects and perform actions on those objects. 2 Click the tile and then drag the lower right corner to adjust the height and width. click the Preferences button to change to Edit mode. 3 Close the Canvas View Preferences dialog box to save your changes. click the Preferences button to change to Edit mode. 3 Close the Canvas View Preferences dialog box to save your changes. 2 Click an object and drag the object to the Thrash Can icon at the bottom of the Canvas view pane. 7 Close the Canvas View Preferences dialog box to save your changes. click the lower right corner of the boundary box and drag it until the image is the size that you want. To change the size of the image. 138 BMC ProactiveNet User Guide . Using View mode to monitor objects in the Canvas view When the Canvas view is in View mode. To adjust the height and width of a tile 1 If you are in View mode.Setting up and using the Canvas view — Box — Line ■ Bring the image to the front of the view or send it to the back of the view. To turn on predict mode 1 Click Predict on the toolbar. The Canvas view is returned to View mode. To remove an object from the Canvas view 1 If you are in View mode. You can also remove metrics from tile objects by clicking on the metric and dragging it to the trash can icon.

Major. If the object’s severity is Critical. 2 Click the right arrow in the tile title bar to drill down further. is displayed at the top of each tile. Example To drill down on a tile in the Canvas view To drill down on a tile object in the Canvas view. Minor. and Critical are displayed and all tiles with a status of Informational and OK are not displayed. and OK. 1 In the tile title bar. Warning. divided into increments. if the object’s severity is Minor. Informational. 2 Select Show Predictive Events in the Operations tab of the Options window to display the Predict button on the Canvas view. The prediction severity is displayed only if that severity is higher than the object’s current severity. all tiles with a status of Warning. The tiles that have the severity that you select and higher are displayed in the Canvas view.Setting up and using the Canvas view A graph. showing what the potential status of the object will be and at what point in time that status will be achieved. Canvas. To filter tiles 1 Click the down arrow next to the filter option in the toolbar. you must create Canvas views for all objects that have dependency relationships with that tile object. or Graph view Details notebook on page 154 Chapter 2 Working with events 139 . click the right arrow . Major. Minor. 2 Select to filter the tiles based on event severity type: Critical. For details about setting this option. For example. the prediction severity is not displayed if it is predicted to change to Minor. see Customizing the display of events on page 86. If you select Warning. Related topics: About the Canvas view on page 131 Viewing the Tile. the prediction severity is displayed if it is predicted to change to Major. The objects that have dependency relationships with the parent object are displayed in the Canvas view.

Major — Light Orange . in the toolbar in Tile view modes The Tile view has the following modes: ■ View mode: Use this mode to monitor the objects that are displayed in the tiles in the Tile view. device.Minor — Yellow . group. ■ Edit mode: Use this mode to customize various aspects of the tile display. and optionally.Critical — Dark Orange . such as the background image and attributes displayed in the tiles. You can display a Tile view for any event collector.Warning 140 BMC ProactiveNet User Guide .About the Tile view About the Tile view The Tile view in the Operations Console displays an encapsulated view of event metrics for the components that are being monitored in your environment. to save your customizations as defaults. the tiles in the Tile view display the following attributes: ■ Name of the component ■ Icon and type of component ■ Current severity ■ Events severity counters (number of events of a specific severity) color coded as follows: — Red . or service that you select in the navigation tree by clicking the Tile View button the right pane view of the Operations Console. Tile attributes By default. Use the Tile view to get a dashboard summary of event activity.

if you have administrative privileges. Chapter 2 Working with events 141 . you can optionally save those preferences and apply them to all tiles that do not have any customizations or. Tile preferences and defaults In Tile view Edit mode. By default. see “Viewing further information for a CI from the Tools Menu”.About the Tile view ■ Event priority counters (number of events of a specific priority) ■ Current status ■ Event severity by monitor category ■ Abnormality score (how close the event is to failure) ■ IP Address Optionally. even for those tiles that have customizations. For more information on the CI Tools Menu. you can display key performance indicators (KPIs). which show where the component status might be in the future. such as setting manual status or maintenance mode. or you can choose to display the same metrics for all tiles. After you set the tile preferences and metrics. tiles that represent configuration items display the following attributes: ■ Name of the component ■ Icon and type of component ■ Current status ■ CI indicators ■ Event severity by monitor category indicators ■ Owner and owner contact information ■ Not being worked on flag CI tiles also include a Tools Menu that is displayed in the title bar when you select the tile. and predictive status and trend. Preferences remain persistent until you change them again. which are the primary metrics defined to show the health of business services. You can display different metrics for each tile. you can select and change tile preferences. to all tiles for all users. The Tools Menu lets you view additional information about the CI and perform certain task.

shows information about the To expand a card to view more information. Canvas.About the Tile view Tile view details You can view event details for the objects in the Tile view in the Details notebook pane that is displayed at the bottom of the Tile view window. and consumers of the selected object ■ Schedule: displays the times when the selected component is in service ■ Advanced: displays information on identification. providers. the following additional cards are displayed in the Details notebook and the KPIs and Prediction cards are not displayed: ■ Status: Displays the applicable status levels of the selected object ■ Priority and Cost: Displays the schedule status. or Graph view Details notebook on page 154 142 BMC ProactiveNet User Guide . Viewing the Tile. possible problems. creation and modification time. impact priority. click the More Info Related topics: “Setting up and using the Tile View ” on page 143 button. and impact cost for the selected object ■ Related CIs: Displays information on status causes. The Details pane displays the following cards: ■ Latest 10 Events: displays the event list for the first 10 events that you select in the Tile view ■ Summary: displays a summary of the object attributes ■ KPIs: displays violations of parameters set for Key Performance Indicators associated with the Group or Device that you select in the Tile view object that you select in the Tile view ■ Prediction: displays a prediction graph that shows the future status trends for the If the object displayed in the tile is a CI. and read/write permissions for groups for the selected object service level agreement associated with the component ■ SLM: if BMC Service Level Management is installed.

and devices. you can optionally save the changes that you make to the Tile view preferences as default values that can be applied either to all Tiles that do not have customized settings. or to all tiles for all users regardless of customized settings. Using Edit mode to change preferences in the Tile view When the Tile view is in Edit mode. change tile preferences and metrics. By default. You can select the attributes that you want to display in each tile or use the default attributes. For more information about saving tile preferences as defaults. The view is changed to Edit mode. services. see “Using View mode to monitor objects in the Tile view” on page 146. you must first change to Edit mode. For more information about setting up the Tile view.Setting up and using the Tile View Setting up and using the Tile View Use the Tile View in the Operations Console to display a dashboard summary of event activity for event collectors. and then after you have made your changes. and the Tile View Preferences dialog box is displayed in the Tile view pane. and to choose which metrics that you want to display in the individual tiles. To edit the objects in the Tile view. To switch to Edit mode 1 Click the Preferences button in the toolbar. return to View mode to monitor the object status. the page is in View mode and tiles are displayed for the object that you select in the navigation tree. see “Saving tile preferences as defaults” on page 145. For more information about using the Tile view to monitor objects. Where to go from here If you are logged on to the BMC ProactiveNet Operations Console with a user account that has Administrator privileges. tiles are created for each node that your administrator or you create in Global or My Folders in the navigation tree. see “Using Edit mode to change preferences in the Tile view” on page 143. Chapter 2 Working with events 143 . When you access the Tile view. you use the options in the Tile View Preferences dialog box to determine how you want the tiles to look. groups.

5 Close the Preferences dialog box to save your changes. devices have a broader list of attributes to select than services. b Select the attribute that you want to display in the tile. 3 To change the tile metrics. ■ The attributes that you can select to display depend on the object type that is displayed in the tile. If you select a KPI attribute. click the Preferences button to change to Edit mode. To change tile attributes and preferences 1 If you are in View mode. and then click Metric Selection in the Tile View Preferences dialog box. perform one or both of the following actions: ■ Select the Color option and then use the palette to select the color that you want to display. 4 In Metric Selection. ■ The Tile view is returned to View mode. 2 In the Background pane in the Tile View Preferences dialog box. 144 BMC ProactiveNet User Guide . Perform the following additional steps: a Click the item at the end of the row until a list of attributes is displayed. For example. select the folder that contains the object that you want to display in the Tile view and then click the Tile View button in the Operations Console toolbar. and click Apply Selection. ■ Select the Image option and then use the list to select the background image that you want to display. the Attribute Selection for Information Capsule dialog box is displayed. click a tile. click the attribute that you want to add and then drag and drop that attribute from the Tile View Preferences dialog box to the tile that you selected. 6 Click Refresh to display data for the new attributes.Setting up and using the Tile View Before you begin In the navigation tree.

and click Apply. if you are logged on to the BMC ProactiveNet Operations Console with an account that has Administrator privileges. Chapter 2 Working with events 145 . if you are an administrator. 2 In the Tile Metrics tab. Optionally. select Only Change Views That Are Using Defaults. perform one of the following actions: ■ To save the changes as the default values for all tiles that are using default values (no customized settings). perform the one of the following actions: ■ To save the changes as the default values for all tiles that are using default values (no customized settings). you can apply those changes for all users who have access to the BMC ProactiveNet Operations Console. the default values (customized settings). select Change ALL Views. To save tile metrics as defaults 1 In the Tile View Preferences dialog box. ■ To save the changes for all tiles including those that have settings other than Optionally. select Only Change Views That Are Using Defaults. ■ If you are an administrator and you want to apply the changes as the default values for all tiles that are using default values (no customized settings) and for all users who log on to the BMC ProactiveNet Operations Console. and click Apply. and click Apply. in All Users Tile Views. 2 To save preferences for your tile views only. click Defaults Selection.Setting up and using the Tile View Saving tile preferences as defaults You can apply the changes that you make in the Tile View Preferences dialog box to all tiles in your tile view that use default values. perform one of the following actions: ■ To save the changes as the default values for all tiles in your tile views that are using default values (no customized settings). ■ To save the changes for all tiles including those that have settings other than the default values (customized settings). To save tile preferences as defaults 1 In the Tile View Preferences dialog box. In the All Users Tile Views section of the Background and Images tab. select Change ALL Views. click Apply. you can save tile preferences as the default values for all users. click Defaults Selection. in the My Tile Views section of the Background and Images tab. and click Apply. in My Tile Views. click Apply.

At the smallest size. 2 Select Show Predictive Events in the Operations tab of the Options window to display the Predict button on the Tile view. If the object’s severity is Critical. click the right arrow . enter the letters or numbers that you want to search on. To drill down on the tile 1 In the tile title bar. To sort tiles 1 Click the down arrow next to the sort option in the toolbar. For details about setting this option.Setting up and using the Tile View Using View mode to monitor objects in the Tile view When the Tile view is in View mode. For example. To search for tiles 1 In the text box in the toolbar. is displayed at the top of each tile. showing what the potential severity of the object will be and at what point in time that severity will be reached. only icons of the object severity are displayed in the Tile view. the prediction severity is displayed if it is predicted to change to Major. 146 BMC ProactiveNet User Guide . Place the mouse pointer over the tile icons to display a pop up window that shows the tile details. To turn on predict mode 1 Click Predict on the toolbar. the prediction severity is not displayed if it is predicted to change to Minor. The prediction severity is displayed only if that severity is higher than the object’s current severity. divided into increments. A graph. see Customizing the display of events on page 86. you can monitor the event status of the objects and perform actions on those objects. To size tiles 1 Move the slider control in the toolbar to the left and right. if the object’s severity is Minor.

Use the graph view to monitor events for published service models that represent your business services. If you select Warning. and OK. 2 Select to filter the tiles based on event severity type: Critical. The tiles that are have the severity that you select and higher are displayed in the Tile view. Minor. 1 Select a CI tile. the tile displays the CI Tools Menu that you can use to access additional information about the CI and perform tasks. all tiles with a status of Warning. For information about the CI Tools Menu. the current severity. Informational. Canvas. and Critical are displayed and all tiles with a status of Informational and OK are not displayed. To filter tiles 1 Click the down arrow next to the filter option in the toolbar. or the type of object that is being monitored. Related topics: About the Tile view on page 140 Viewing the Tile. Minor. Warning.About the graph view 2 Select to sort the tiles based on the name of the monitored objects. Chapter 2 Working with events 147 . Major. see “Viewing further information for a CI from the Tools Menu” About the graph view The graph view in the Operations Console displays a graphical representation of the configuration items (CIs) in a service model and shows how those CIs relate to each other. 2 Click the Tools Menu icon in the tile title bar. Major. or Graph view Details notebook on page 154 Example To access the Tools Menu for CIs If the component that is displayed in the Tile view is a CI.

shows information about the To expand a card to view more information. creation and modification time. and impact cost for the selected object ■ Related CIs: Displays information on status causes. impact priority. possible problems. and read/write permissions for groups for the selected object service level agreement associated with the component ■ SLM: if BMC Service Level Management is installed. in the toolbar in the right pane view of the Graph view modes The Graph view has the following modes: ■ View mode: Use this mode to monitor the CI objects that you select to display in the Graph view. click the More Info icon Related topics: 148 BMC ProactiveNet User Guide . and consumers of the selected object ■ Schedule: displays the times when the selected component is in service ■ Advanced: displays information on identification. ■ Edit mode: Use this mode to customize various aspects of the service model display in the Graph view. . providers. Graph view details You can view event details for the objects in the Graph view in the Details notebook pane that is displayed at the bottom of the Graph view window.About the graph view You can display the graph view for any service that you select in the navigation tree by clicking the Graph View icon Operations Console. The Details pane displays the following cards: ■ Latest 10 Events: displays the event list for the first 10 events that you select in the Graph view ■ Summary: displays a summary of the object attributes ■ Status: Displays the applicable status levels of the selected object ■ Priority and Cost: Displays the schedule status.

or Graph view Details notebook on page 154 Setting up and using the Graph View Use the Graph View in the Operations Console to display a configuration item (CI) and its relationships in a graphical service model that represents your important business services. close the Graph View Preferences dialog box. you must first change to Edit mode. and the Graph View Preferences dialog box is displayed in the Graph view pane. service model objects are created for each CI that is displayed in the Global or My Folders nodes in the navigation tree. Canvas. Where to go from here For more information about setting up the Graph view. By default. When you access the Graph view. and then after you have made your changes. To switch to Edit mode 1 Click the Preferences button in the Graph View toolbar. To edit the objects in the Graph view. You select how you want to display the service model objects and the relationships between those objects in the Graph View.Setting up and using the Graph View “Setting up and using the Graph View ” on page 149 Viewing the Tile. see “Using View mode to monitor objects in the Graph view” on page 152" Chapter 2 Working with events 149 . return to View mode to monitor the CI object status. the page is in View mode and CI objects are displayed for the object that you select in the navigation tree. change service model preferences and metrics. The view is changed to Edit mode. see “Using Edit mode to change preferences in the Graph view” on page 150 For more information about using the Graph View to monitor objects. To return to View mode.

Optionally select the orientation of the service model. ■ Orthogonal: Arranges CIs in a more compact design with provider components shown perpendicular to their consumer components. set the following options: a Select one of the following layout formats as the default when the Graph View is opened: ■ Circular: Groups related CIs in circles to help you visualize how the groups are related. d Select to show numbers for the lines that indicate a component's impact on another component. To change CI attributes and preferences 1 If you are in View mode. click the Preferences button to change to Edit mode. select the CI object that you want to display in the Graph View and then click the Graph View button in the Operations Console toolbar. ■ Hierarchic: Arranges CIs according to their hierarchy in the service model. and lines that indicate a component's impact on another component (Impacted Lines). This number indicates the impact percentage on the graph between the two components. either by the object's name or its short description. c Select the thickness of the lines that indicate relationships between components for both lines that indicate consumer and provider relationships (Regular Lines). ■ Organic: Groups CIs according to their relationships with each other. 2 In the Layout Options pane of the Graph View Preferences dialog box. Right to Left. Top to Bottom. you use the options in the Graph View Preferences dialog box to determine how you want the configuration item (CI) objects in the service model to look. or Left to Right.Setting up and using the Graph View Using Edit mode to change preferences in the Graph view When the Graph View is in Edit mode. with space between groups. 150 BMC ProactiveNet User Guide . b Select how you want the label of the object to be determined. Bottom to Top. Before you begin In the Services node in the navigation tree.

the more severe is the status or the more important is the priority. You can set the following options for the spotlight: Color select what you want the color of the spotlight to indicate.Setting up and using the Graph View e Select if you want to use the status color of the component for the lines that indicate relationships between the components. The darker the color. not propagated from other CIs Brightness: select what you want the brightness of the color associated with the CI to indicate: — Direct Events: the CI has events directly associated with it. select what you want the size of the spotlight to indicate: — Priority: the impact priority of the CI Size based on either on its own priority or on the priority of another impacted CI which propagates its priority to it defined for the CI — SLA: the status of the the worst SLA — Not Being Worked On: the CI has events that have not been assigned — Direct Events: the CI has events directly associated with it. The default for Consumers is 1. 3 Click Indicator Icons Options and select the icons and indicators that you want to display for each component in the service model: ■ Spotlight: Displays a highlighted circle behind the CI icon. not propagated from other CIs Chapter 2 Working with events 151 . the color of the lines is black. If this option is not selected. and the default for Providers is 2. You can select a specific number for both consumers and providers or have no limits on the number of levels displayed. either the status or the priority of the CI based on the most recent event. f Select the how many levels you want to show in the service model by selecting the number of consumer CIs and provider CIs that you want displayed when the Graph View is opened.

To set the Graph view layout 1 At the top of the display pane. not propagated from other CIs for the CI ■ SLAs . ■ Click Cancel to close the Graph View Preferences dialog box without saving your changes. 152 BMC ProactiveNet User Guide .Status of Worst Targeted SLA: the status of the the worst SLA defined ■ Prediction Event is Present: the CI has an event that predicts that its future status will become worse than its current status ■ Substatus: the worst status propagated up from any provider CIs 4 Perform one of the following actions: ■ Click Apply to save your changes and keep the Graph View Preference dialog box open. 5 Click Refresh . select one of the following layouts: ■ Circular: Groups related CIs in circles to help you visualize how the groups are related. you can monitor the status of the CI objects in the service model. Using View mode to monitor objects in the Graph view When the Graph view is in View mode. ■ Click OK to save your changes and close the Graph View Preferences dialog box.Setting up and using the Graph View — Not Being Worked On: the CI has events that have not been assigned ■ Status icon: the CI's current status ■ Priority Icon: the impact priority of the CI based on either on its own priority or on the priority of another impacted CI which propagates its priority to it ■ Not being worked on: the CI has events that have not been assigned ■ Direct Events From Component are Present: the CI has events directly associated with it.

Alternatively. ■ Use the Zoom Fit button to resize the service model so that all CIs and their relationships fit in the viewable area of the display pane. The Show Overview button lets you view the effect of your changes on all the instances in the display pane. For details. Bottom to Top. and the to make the objects appear larger. Any changes you make to instances in the display pane are immediately reflected in this box. Left to Right. or Right to Left layout. to display an overview of the entire contents of the display pane in a box next to the zoom bar. ■ Hierarchic: Arranges CIs according to their hierarchy in the service model. A highlight is displayed behind the CI objects displayed in the Graph View. drag the slider between the Zoom Out and Zoom In buttons. or use the scroll wheel on a mouse.Setting up and using the Graph View ■ Organic: Groups CIs according to their relationships with each other. see “Using Edit mode to change preferences in the Graph view” on page 150 Chapter 2 Working with events 153 . ■ Use the Show Overview button To view details on CI objects 1 Perform one of the following actions: ■ Click the Details icon in the CI object tile ■ Open the Details notebook at the bottom of the Graph view window To turn the spotlight on and off 1 Click the Show Spotlight button on the Graph View toolbar . ■ Orthogonal: Arranges CIs in a more compact design with provider To size the CI objects in the Graph view 1 Use the zoom bar on the left side of the Graph view to resize the CI objects in the service model as follows: ■ Use the Zoom Out button Zoom In button to make the objects appear smaller. You can select the properties of the spotlight in the Graph View Preferences dialog box. Select a Top to Bottom. components shown perpendicular to their consumer components. with space between groups.

The Details notebook event list shows the same information that is displayed in the Events List view. The cards of the Details notebook pane organize the information. and Graph views provides all of the recorded information about the events associated with the objects that are displayed in the tiles in these views. Canvas. Canvas. Canvas. The following indicator icons are displayed around the CI objects displayed in the Graph View: ■ Status ■ Priority ■ Not Being Worked On ■ Direct Events From Component are Present ■ Substatus To expand and collapse the CI hierarchy 1 Click the plus or minus buttons at the top and bottom of the CI objects. Viewing the Tile. 154 BMC ProactiveNet User Guide . Canvas. or Graph view Details notebook To turn indicator icons on and off 1 Click the Display All Indicators button on the Graph View toolbar . or Graph view Details notebook pane for all objects Card name Latest 10 Events Description Lists the most recent 10 events for the object (tile) selected in the view.Viewing the Tile. or Graph view Details notebook The Details notebook pane displayed below the Tile. and provides toolbar options so that you can search and take actions on these events. Table 42: Cards displayed in the Tile. as described in Table 42 on page 154.

Impacting. and BladeLogic Device History ■ Monitors associated with Devices: Show Parent Groups. prediction status. additional cards are displayed as described in Table 43 on page 156. Also includes hyperlinks to launch the Tools Menu. Flash Check. any actions taken on the last known event. if applicable. Tree View. Device at a Glance. If the object’s severity is Critical. object type icon. and Predictions). and where applicable Remote Actions/Diagnostics commands KPIs Displays violations of the parameters set for Key Performance Indicators (KPIs) if the object that you select in the navigation tree is a Group or Device Displays a graph that shows what the object’s status will be and at what time that status will be reached. Direct. such as object name. View Serivce Impact Graph.The Key Performance Indicators (KPIs) and Prediction cards are not displayed for CIs. the prediction severity is not displayed if it is predicted to change to Minor. and Predictions). Impacting. Canvas. description. the prediction severity is displayed if it is predicted to change to Major. or Graph view Details notebook Card name Summary Description Displays basic information about the object (tile) that you have selected in the Tile or Canvas view. and Group Details commands ■ Devices: Add Configuration Changes. Changes.Viewing the Tile. if the object’s severity is Minor. Manage Data Collection. Chapter 2 Working with events 155 . The menu commands that are available depend on what object is displayed in the selected tile as follows: ■ Services: Operations (Set Manual Status. current event severity status. Show Configuration Changes. short description. Prediction If you select a CI object. View Events (All. View Service Impact Graph ■ Groups: Monitors+Devices. View Events (All. Clear Manual Status. The prediction severity is displayed only if that severity is higher than the object’s current severity. Clear Maintenance Mode). Changes. Show Parent Groups. and object description. Set Maintenance Mode. Show Monitors. Direct. For example.

providers. Canvas. and consumers of the selected component type. manual status. SLM Shows information about the service level agreement associated with the component Note: This tab is visible only when BMC Service Level Management is installed. Schedule Advanced Displays the times when the selected component is in service ■ Identification ■ Time Stamps ■ Permission Groups Displays information on identification. 1 Select an object in the Tile. and computation statuses. or Graph view Details notebook Table 43: Additional cards displayed in the Tile. To view the Details notebook By default.Viewing the Tile. and read/write permissions for groups for the selected object. creation and modification time. 156 BMC ProactiveNet User Guide . Canvas. impact priority. To display the Details notebook. This subtab also lets you view other components that have relationships with the selected component. Canvas. or Graph view Details notebook pane for CI objects Card name Status Sections in card ■ Summary ■ Status Details ■ Status Computation Priority and Cost Displays the schedule status. possible problems. or Graph view. maintenance mode. click the Up arrows . Description Displays the applicable status levels of the component: Service Level Agreement. or Graph view. and impact cost. ■ Summary ■ Priority Details ■ Time-Variable Properties Related CIs Displays information on status causes. perform the following steps. 2 In the Details notebook title bar. the Details notebook is not displayed when you open the Tile. Canvas.

click the Down arrows . Tip To view additional information in a card in the Details notebook pane 1 In any of the cards listed in Table 42 on page 154 or Table 43 on page 156of the Details notebook. use the tiny right and left arrows to the right and left of the Details notebook to navigate through the cards. 4 Click Close . 3 In the Preferences dialog box. To select the cards to be displayed in the Details notebook pane 1 Select an object in the Tile. select the cards to be displayed in the Details notebook pane. If you select more cards than can be displayed.Viewing the Tile. Canvas. or Graph view. or Graph view Details notebook To hide the Details notebook 1 In the Details notebook title bar. Chapter 2 Working with events 157 . Canvas. 2 Click Edit Notebook Preferences . click More Info .

Canvas. or Graph view Details notebook 158 BMC ProactiveNet User Guide .Viewing the Tile.

see Configuring BMC ProactiveNet to perform probable cause analysis on page 165. the following events are not considered during probable cause analysis: ■ administrative events—Administrative events include all events that belong to specific event classes within the MC_CELL_EVENT class. For more information. ■ VMware-related VMotion events — Events related to use of a virtual machine are Chapter 3 Determining the probable cause for an event 159 . the more accurate probable cause analysis will be. You can increase the accuracy of probable cause analysis by providing relationships between devices and monitors. For more information see.3 Determining the probable cause for an event What is probable cause analysis? By gathering data from different sources and applying filters to rule out unrelated events. These event classes are listed in Event information used in probable cause analysis on page 435 handled differently from other events. This process of gathering and filtering data to determine the cause for an event is called probable cause analysis. The more data that is provided about an event. How BMC ProactiveNet performs probable cause analysis on events Probable cause analysis focuses on events that are able to impact other events in unexpected ways. The probable cause analysis process analyzes data and displays the relevant events automatically. Probable cause analysis in a virtual environment on page 177. Therefore. BMC ProactiveNet can determine the most-likely causes for an event. such as an attribute that is outside the desired range.

and so on. In this case. but the thresholds are not set on all the metrics. The Service model is well defined and thresholds are on all the metrics that represent the health of all the CIs that are present in the model. In this case. severity. PCA can be used to sort the events by score computation and by looking at various factors like data correlation. ■ The Service Model is present. ■ blackout events—Blackout events include all events that occur during a defined The Root Cause Analysis(RCA) in SIEM computation is useful in finding the root causes for the up or down issues. For a list of slots used by probable cause analysis to analyze events. Probable cause analysis can be performed on internal events and external events. time correlation. ■ The Service Model is present in a detailed or high level. but lot of many events are ■ The Service model is not present. Because these events come from a source that is external to BMC ProactiveNet. 160 BMC ProactiveNet User Guide . ■ When trouble shooting system resource related issues in virtual environments and BMC adapter for VMware is used for data collection. and configuration change events.How BMC ProactiveNet performs probable cause analysis on events ■ predictive events—Predictive events are early warning events that BMC ProactiveNet generates before a severe event occurs on an existing metric. external events. internal and external events are handled differently during the probable cause analysis process. An internal event is an event that is generated by the BMC ProactiveNet Server. PCA can be very effective by looking at relevant abnormalities. blackout period for an adapter. see “Event information used in probable cause analysis” on page 435 External events are events that are received from an external source such as a remote cell or an event adapter. The Probable Cause Analysis(PCA) in BMC ProactiveNet computation is useful in trouble shooting performance related issues. Because internal and external events vary in the amount and type of data that they supply. Internal events also are referred to as intelligent events or data events because these events include a large and rich amount of data. shown as impacting events. these events do not have the data associated with them that an internal event does. PCA is used for finding the root causes after the occurrence of the event. ■ Impact computation is available only for open events.

Figure 5: Probable cause analysis process for an intelligent event Because external events do not contain data as internal events do. as illustrated in Figure 6 on page 161.How BMC ProactiveNet performs probable cause analysis on events Because internal events are rich in data. it applies a series of filters to the internal event. these events go through more analysis steps than external events. Figure 6: Probable cause analysis process for an external event Chapter 3 Determining the probable cause for an event 161 . probable cause analysis for external events uses fewer filters. in the order shown in Figure 5 on page 161. When BMC ProactiveNet is analyzing an internal event to determine if it could be a probable cause for another event.

which might make it the cause of the result event. the longer the period of time between the probable cause event and the result event. In general. the less likely it is that the probable cause event is the cause of the result event.How BMC ProactiveNet performs probable cause analysis on events Time correlation The first measure used to determine if an internal or external event might be the cause of another event is whether the event being analyzed as the probable cause occurred during a logical timeframe. 162 BMC ProactiveNet User Guide .

Knowledge patterns If you have determined that a certain set of criteria usually results in the same probable cause event. see Changing the time correlation filter on page 172. that internal event is then compared against any saved knowledge patterns. For instructions on modifying the time specified by the time correlation filter. service model. These following user-defined filters are applied depending on whether the event is internal or external: ■ Device Name—filters all internal events and external events that are associated with a device that exists within BMC ProactiveNet ■ Group—filters all internal events and external events if the external event is associated with a BMC ProactiveNet device and that device is part of the specified group relationships and less scoring events. User-defined filters Once the event has passed the time correlation filter. For information about the userdefined relationships filter. Also filters external events that are not associated with a computer system and displays event outside the model. see Service model relationships on page 164.How BMC ProactiveNet performs probable cause analysis on events If the probable cause event occurs within the time specified by the time correlation filter. ■ Event level . then the probable cause event is assessed against the user-defined filters. using global For instructions on configuring these filters. but with lower scores. If an external event passes through the user-defined filters.Filters based on the non-KPI metrics. see Enabling user-defined filters on page 173. then you can create a knowledge pattern of that criteria so that BMC ProactiveNet can compare internal events against that criteria to quickly identify whether or not that internal event is a probable cause event. BMC ProactiveNet examines the user-defined relationships for the external event to determine if the external event might be a probable cause event. see Knowledge patterns on page 163. If an internal event passes through the user-defined filters that have been applied. For more information about knowledge patterns. you can filter probable cause events based on a collection of filters that you define. Chapter 3 Determining the probable cause for an event 163 .

then those relationship filters are applied. For more information about the mc_event_subcategory slot. For more information about service model relationships. If the event belongs to any CI instance relationships. you must set them yourself. Service model relationships The relationships between configuration items (CIs) identify potential probable cause events. For information about defining knowledge patterns.How BMC ProactiveNet performs probable cause analysis on events If an internal event is compared to a knowledge pattern and matches. Because these relationships are unique to your environment. If the event instance does not belong to any instance relationship. see the BMC ProactiveNet Administration Guide. BMC ProactiveNet examines the CI relationships for the internal event to determine if the event might be a probable cause event. If an internal event does not match any of the saved knowledge patterns. then that event is displayed immediately as the probable cause event. see Saving recurring conditions as a known probable cause on page 174. see the BMC Knowledge Base Development Reference Guide. BMC ProactiveNet analyzes the event based on global relationship rules. BMC ProactiveNet examines the relationships of the CI for the potential probable cause event. out-of-the-box domain knowledge provided for existing BMC ProactiveNet monitors. Service model relationships are analyzed for all internal events and for external events if the relationship is based on a CI and the external event is associated with that CI. Global relationships Global relationships are pre-defined. Service model relationships capture relationships between CIs. Global relationships are analyzed for all internal events and all external events that have a sub-category specified in the mc_event_subcategory slot. This domain knowledge cannot be modified. 164 BMC ProactiveNet User Guide .

This includes monitors at the system level. Disk monitors. Chapter 3 Determining the probable cause for an event 165 . application level. such as TCP monitors. System monitors. Data correlation is applicable only to internal events. Process monitors. Application Server monitors. Scoring Scoring of probable cause analysis events is based on a combination of factors computed by BMC ProactiveNet that determine the likelihood that the event is a probable cause event. Log File monitors. For example. then probable cause will show that no events are correlated. and DNS monitors. such as Web Server monitors. and network level. then it is virtually impossible to get to the granular cause of a problem.Configuring BMC ProactiveNet to perform probable cause analysis Data correlation Data correlation is computed using the data collected for the result event and the probable cause event. Interface monitors. but you also need to create a monitor for all resource dependencies that support it. Configure complete monitor coverage You must configure complete monitor coverage for your entire infrastructure. if you have a Web site in your environment. you should configure your BMC ProactiveNet system as recommended by these guidelines. as well as all System Resource monitors for each of the computers these run on. If there is not enough coverage. If monitors are not covering all dependencies in your infrastructure. Complete monitor coverage is key for probable cause pinpointing to work correctly. Configuring BMC ProactiveNet to perform probable cause analysis To maximize the capabilities of BMC ProactiveNet probable cause analysis. Database monitors. Ping monitors. you must make sure to create a monitor for it using the Web URL or Web Transaction monitor.

You can create service models using the Administration Console or BMC Impact Model Designer. 166 BMC ProactiveNet User Guide . conversely. This device should be the target computer where the application being monitored is running . probable cause analysis can incorrectly eliminate an event as a probable cause event because it is eliminating all events of a certain device type.Configuring BMC ProactiveNet to perform probable cause analysis Assign correct device types You must ensure that the correct device types are assigned to all devices in your infrastructure. ensure that you associate the montior to the proper CI. Associate monitors to the proper CI When you create a service model by using the Associate Monitor feature in the Administration Console. unrelated events may appear. This information is important for the probable cause analysis process to draw conclusions about the relationship of monitors with respect to one another. BMC ProactiveNet system uses device type information to isolate and relate problems across different computers. Probable cause analysis can use the device as a way of filtering out unrelated events. For information see the BMC ProactiveNet Administrator Guide and the BMC ProactiveNet Service Modeling and Publishing Guide. Conversely. there is a chance that an event that is correlated to the result event will not be displayed or. if events that are unrelated to the result event may be pinpointed as probable cause events because that event has an incorrect device type. you should verify that this device type is correct. If the monitor assignment is not correct. however. If the device type is set incorrectly. When creating a monitor. A device type is assigned to each device by default. Create monitors under the correct devices Each monitor in the BMC ProactiveNet system is located under a specific device in the Administration Console.either virtually or physically. Create service models for interdependent CIs You must create service models for CIs that have dependencies on one another. ensure that the monitor is created under the correct device in the Administration Console.

At 10:00 AM the CPU USED is higher than 90%. The longer the monitor has been collecting data. Probable cause analysis will not display events that are outside the specified timeframe before or after the result event.Configuring BMC ProactiveNet to perform probable cause analysis For information on associating the montior to the proper CI. However. the monitor should be collecting data consistently for at least a week. the more reliable the probable cause analysis process becomes. For example. Set a polling interval of 5 minutes or less BMC ProactiveNet recommends using the default polling frequency. if you decide to change the polling frequency. you create a threshold that creates a CRITICAL event when server CPU USED is above 90% (condition) for 1 hour (duration). keep in mind that polling frequency affects probable cause analysis. see the BMC ProactiveNet Administrator Guide. However. it is best to configure the smallest polling interval that does not affect the performance of the device. this event might not be displayed. The following types of threshold settings impact the probable cause analysis process: ■ Absolute/Signature Event Thresholds—the duration of these thresholds is critical for correlating events that occur closely in time to the original event. Establish a reliable baseline To ensure a reliable baseline for a monitor. Therefore. an event will be generated only at 11:00 AM if the CPU USED percentage stays above 90% until 11:00 AM. Chapter 3 Determining the probable cause for an event 167 . For example. the CPU usage problem will not be displayed as a probable cause event because the duration for this event has not yet passed. if the default time correlation filter of one hour before the event and 30 minutes after the event is being applied and the polling frequency is 45 minutes. then too few data points are will be available within the default period to reliably pinpoint probable cause. If there is another event created at 10:15 AM because of this high CPU consumption and you are trying to perform probable cause analysis on the event that occurred at 10:15AM. A greater number of data points increases the likelihood that the probable cause analysis process will be successful. An event is not generated until the condition exists for the duration specified in the threshold definition. If this duration period is too long and if you are trying to find the probable cause analysis as soon as the problem event is created.

1 From the event list. To view probable cause analysis for an event You can view the probable cause analysis from the Tools menu or by clicking on the icon. see the BMC Knowledge Base Development Reference Guide. Ensure sub-categories are defined for external events For external events to be analyzed based on global relationships. For information about the mc_event_subcategory slot. 2 You can launch into the probable cause analysis page from the ■ Tools menu icon ( or ) in the Object column of the event Details area and choose Probable Cause Analysis Probable Cause Analysis icon located in one of the following locations: ■ a above the event list b in the Summary column of the event Details area c to the right of any monitor graph display 168 BMC ProactiveNet User Guide . the mc_event_subcategory slot must be set for each external event. This screen displays the probable cause events that remain after all the relevant filters have been applied. select the event for which you want to determine probable cause.Viewing probable cause analysis for an event ■ Abnormality Event Thresholds—BMC Software recommends that you keep the default settings for these thresholds. Viewing probable cause analysis for an event The probable cause analysis information for an event is displayed in the Probable Cause Analysis For Selected Event screen in the Operations console.

1 By Score: This tab sorts the probable cause events based on the highest score. see “Customizing the display of the Probable Cause Analysis list” on page 170. The BladeLogic icon Chapter 3 Determining the probable cause for an event 169 . see Saving recurring conditions as a known probable cause on page 174. This section includes: 1 Severity level 2 Time at which the event occurred Probable Cause Events section This section enables you to set the user-defined filters. Secondary events pane The bottom pane of the Probable Cause Analysis page contains the list of probable cause events that are determined for the primary event after all the event filters have been applied.Viewing probable cause analysis for an event Event Being Analyzed section This section of the Probable Cause Analysis For Selected Event screen displays information about the event for which you are trying to find the probable cause (also called the primary event). 3 By Device: This tab sorts the probable cause events by device. From the Probable Cause Analysis For Selected Event screen. 3 Monitor information for the selected event. For information about defining a knowledge pattern. BMC ProactiveNet will instantly identify those conditions as the probable cause for the event. If you determine that particular conditions for a particular instance always indicate probable cause. 2 Click on the Detailed Diagnostics icon to view detailed diagnostics for the event. When that pattern is encountered again. the By Score and the By Device tabs. 2 The attributes and indicators for the selected event. For instructions on enabling these filters. The tools menu also is available for this event from the Probable Cause Analysis For Selected Event screen. There are two tabs in this pane. If the device for this event includes BladeLogic job which has run before 24 hours before and 30 minutes after the primary event the icon for the job type is displayed in the Most Recent BladeLogic Job Type column. you can set up a knowledge pattern that saves and recognizes those particular conditions. you can view: 1 A graph of the raw data for the selected event.

click Preferences . ■ By Device: displays the events sorted by devices of the events. The tooltip displays the time of the last run BladeLogic job with respect to the primary event. Description 170 BMC ProactiveNet User Guide . ■ By Score: displays the events sorted on the score. For more information about integration with BMC BladeLogic. Time Enables the time specification based on the secondary event time out interval.Customizing the display of the Probable Cause Analysis list depends on the latest job that is executed. The default view is By Score. use the information in the following table to determine the appropriate settings. The default time interval is -1 and +30. Customizing the display of the Probable Cause Analysis list You can customize the following aspects to suit your probable cause event monitoring: ■ view ■ time ■ events filter ■ analysis ■ event filter levels ■ number of devices and events displayed To customize display settings for the PCA lists 1 In the Probable Cause Analysis page. see Integrating with BMC BladeLogic on page 419. 2 In the Probable Cause Analysis Preferences page. Table 44: Probable cause analysis preferences settings Field General View Displays the events sorted by score or by device. Click the Tools menu icon for the event and choose BladeLogic Device History to view BladeLogic device history page.

but lower scores Select this option to display only the event with the highest score.Customizing the display of the Probable Cause Analysis list Field Events Filter Description Enables the levels of event filter for the following options: ■ Level 1 ■ Level 2 ■ Level 3 ■ Level 4 By default. Event Filter Levels Filter levels on non-KPI metrics Select this option to filter by non-Key Performance Indicators (KPI).co-relates data between the metric of the primary event against other metrics for the time periods at which the primary metric was abnormal in the past. the results may take up to 3 times longer to return. Select this option to filter events based on the impact relationships defined for the CI associated with the primary event. Analysis Enables you to correlate information in the following ways: ■ Time Correlation . (subject to data retention limits). ■ Correlate metric data within time window . if you select . ■ Data Correlation . level1 is displayed.enables you to display the secondary events in the same timeframe as the primary event.enables the computation of data using the data collected for the resulting event and the probable cause event. Show only highest scoring event per metric Filter using service model Displays event outside the model.1 hour and + 1 hour in the time window slider. Chapter 3 Determining the probable cause for an event 171 . ■ Correlate metric data during previous abnormalities on event's metric . Select this option to show the events that are not associated with the impacting CI's based on the model identified above.co-relates the metric data of the primary event against the metric data of each candidate event. then up to 2 hours of data are analyzed. However. For a given metric there could be multiple abnormalities and threshold events. Data correlation is applicable only to internal events. For example. Only the metric data within the analysis window is analyzed. This can produce more accurate data correlation results at the cost of increased processing time.

After the probable cause analysis identifies the probable cause events.Max Number of Devices to Display By Device . To change the time correlation filter 1 Access the probable cause analysis for the selected event.Max Number of Events to Display By Device . Filtering unrelated events to find probable cause There are many ways to filter unrelated events to find the probable cause of an event. Advanced By Score . BMC ProactiveNet only considers events that have occurred one hour before or 30 minutes after the primary event. Changing the time correlation filter The timeframe during which a probable cause event and a result event is most likely to occur is specified in a time correlation filter. By default. Enables you to determine the maximum number of devices to display in the PCA results window. The following topics explain how to configure these filters. you must change the time correlation filter.Filtering unrelated events to find probable cause Field Description Filter using global relationships Select this option to control whether the built-in global relationships are used to determine probable cause.Max Number of Events per Device to Display Enables you to determine the maximum number of events to display in the PCA results window based on the score of the events. each event is scored and only the events whose score is above the specified limit are shown as root cause in the probable cause analysis page. Filter events not associated with a computer system or CI Filter events scoring less than Select this option to filter an event that is not associated with a device or a CI Select this option to filter events with a score lower than that entered in this field. If you want to increase or decrease the time correlation between the primary and the second event. 172 BMC ProactiveNet User Guide . Enables you to determine the maximum number of events per device to display in the PCA results window.

To filter by events 1 In the Events Filter list.Filtering unrelated events to find probable cause 2 From the Sliding bar. This filter adds all the events that are associated with the group that you specify and click Filter on the Probable Cause Events section. To filter by group 1 Click No Filter next to the Group field. drag the sliding pointer to set the time window before or after the timestamp of the primary event. then events for all devices will be displayed. select the desired level for the events that you want to filter and display. Click Filter on the Probable Cause Events section. ■ To edit the group filter. Enabling user-defined filters User-defined filters limit the events to be considered as probable cause events based on criteria that you define. ■ To remove the group filter. click on X next to the enabled group filter. These user-defined filters can be configured in the Probable Cause Analysis Events section. click on the filter displayed. 2 From the Group Filter dialog box. ■ Select Tree from the drop-down list to display the hierarchical group view. You may enable one or more of these filters at the same time. 3 Click Apply. To filter by device name 1 In the Device field enter the name of the device to see the associated events. This enables you to filter out the unrelated events. ■ Select Flat List from the drop-down list to list all the available groups. If no name is specified in the Device field. This filter removes all events from the probable cause event list that are not associated with the device that you specify. select the group and click Apply. Chapter 3 Determining the probable cause for an event 173 .

Saving recurring conditions as a known probable cause When you run a probable cause analysis on an event and find a pattern which you want to reuse in future.Saving recurring conditions as a known probable cause This filter adds all events of the specified level from the probable cause event list that are associated with the level that you specify. The available conditions will change based on the event that you have selected. select the event that you want to use for your knowledge pattern. ■ For example. 2 In the Event list. select the check box or check boxes to add further conditions to the knowledge pattern. 6 In the Name field. The levels can be modified in the preference page. BMC ProactiveNet immediately applies this pattern to similar conditions and does not run probable cause analysis. 3 Click Create Knowledge Pattern. To create a knowledge pattern 1 Access the Probable Cause Analysis For Selected Event dialog box. Once a knowledge pattern is available. ■ The Create Knowledge Pattern screen is displayed. 4 Select the instance or instances for which you want the knowledge pattern to apply: ■ all instances in group — allows you to define the knowledge pattern for all instances of a selected group ■ only instance monitor_name —allows you to define the knowledge pattern for the selected instance of the selected monitor ■ all instances of monitor_name —allows you to define the knowledge pattern for all instances of the selected monitor 5 If required. capture it by creating a knowledge pattern. if you created a knowledge pattern for a scenario where there is an event on Application Availability and Ping Availability to the same device 174 BMC ProactiveNet User Guide . enter the text that you want displayed in the Probable Cause Analysis for Selected Event dialog box when these conditions occur for the instances that you have selected.

After you have created one or more knowledge patterns. Chapter 3 Determining the probable cause for an event 175 .Probable cause analysis in a scalable deployment environment where the application is running you might name it Application Server Not Available. on page 174. ■ Continuing the example from List item. 8 Click Save. probable cause analysis must be performed on the central BMC ProactiveNet Server. If you want to perform probable cause analysis on all the events in the environment. enter details for the probable cause knowledge pattern. This text would appear on the screen when the server is not responding to ping requests and probable cause analysis is initiated for the PING AVAILABILITY event. you could enter the action that an operator should take if this knowledge pattern is encountered. Probable cause analysis in a scalable deployment environment In a scalable deployment environment events are propagated from the local BMC ProactiveNet servers to a central BMC ProactiveNet Server. Knowledge patterns are saved in the database. you can access an edit or delete dialog box for modifying or deleting your knowledge patterns. 7 In the Description field. such as Reboot server.

Figure 7: Event propagation in a scalable environment Limitations of probable cause analysis in a scalable environment Data for the intelligent events on the local servers is not propagated to the master BMC ProactiveNet Server. 176 BMC ProactiveNet User Guide .Probable cause analysis in a scalable deployment environment Figure 7 on page 176 illustrates how events are propagated in a scalable environment. This data loss causes probable cause analysis on the master BMC ProactiveNet Server to lose accuracy because no data correlation is available on the master BMC ProactiveNet Server. This causes the propagated intelligent events to be treated as external events.

How probable cause analysis handles VMotion events In addition to considering system resource events. BMC ProactiveNet displays all the system resource issues on the VMWare ESX Host from where the VM is moved. When probable cause analysis is requested for a VMotion event. probable cause analysis also displays relevant virtual machine migration events for the host of the event for which probable cause analysis is requested. If you add monitor instances of the type that are part of the VirtualSystem Attribute Set to the devices imported from he BMC Atrium CMDB. Limitations of probable cause analysis in a virtual environment By default. as well as issues with the ESX host server itself.Probable cause analysis in a virtual environment Probable cause analysis in a virtual environment BMC Proactivenet handles probable cause analysis differently for system resource issues on VMware ESX hosts or virtual machines. see Event information used in probable cause analysis on page 435 Chapter 3 Determining the probable cause for an event 177 . probable cause analysis in a virtual environment is confined to VMWare metrics. For a list of monitors related to VMware. When probable cause analysis is requested for a system resource-related event on an ESX host or a virtual machine. ESX host and VM relationships imported from the BMC Atrium CMDB cannot be used in probable cause analysis unless monitors of the type that are included in VirtualSystem Attribute set are added to these devices. if that event is on the virtual machine or ESX host. probable cause analysis will leverage the ESX host and/ or the virtual machine relationship between these devices. BMC ProactiveNet takes into account the issues with all the virtual machines running on that host.

Probable cause analysis in a virtual environment 178 BMC ProactiveNet User Guide .

you can use the event management escalation policy available through the BMC ProactiveNet Administration Console (see the BMC Software ProactiveNet Administrator Guide for information on the event management policies). the escalation actions are removed from the event rule and consequently are not triggered by the event. Instead of the BMC ProactiveNet escalation feature. A specified number of event recurrences can also trigger escalation of an event. You can also use an AlarmPoint integration to handle event Chapter 4 Event administration 179 . An escalation policy raises or lowers the priority level of an event after a specified period of time. If you have created an event rule with an associated escalation action. advanced. you can create a notification policy to alert users of changes to an event’s severity level.4 Event administration Overview Event administration includes the following tasks: ■ Defining threshold values that determine when events are generated ■ Filtering the event rule list ■ Defining and updating basic. then after you upgrade. and other event types ■ Eliminating duplicate events and limiting the number of events that are generated and sent ■ Using variables to compose and customize event text to be incorporated into email messages For upgrade users The BMC ProactiveNet event escalation feature has been deprecated in this release. Along with the escalation policy.

an absolute threshold is specified for attributes that have common accepted values beyond which performance is known to degrade. Accessing the event administration options Access the event administration options through the BMC ProactiveNet Operations console by selecting Options => Administration from the top menu bar to display the Administration tab. This requires precise knowledge of the environment and is not very scalable in terms of administration.Understanding event thresholds escalations. The features are listed on the Administration tab under the Event Administration heading. The traditional approach requires the definition of hard thresholds that need to be customized for each instance. Absolute thresholds are better suited for attributes that change status. it may result in performance issues. Support for the TelAlert product is discontinued. Paging capability is no longer supported. 180 BMC ProactiveNet User Guide . In general. Table 45: Types of event thresholds Threshold type Absolute threshold Description Absolute thresholds represent an absolute value above or below which an event is generated. Table 45 on page 180 describes the types of event thresholds that BMC ProactiveNet offers. For example. See Managing the AlarmPoint integration on page 216 for general guidelines. In this case. The approach BMC ProactiveNet takes to detect abnormal behavior is different from the traditional threshold approach. if the total CPU utilization of Solaris System is above 80%. Choose the corresponding Edit button to access detailed information about each option. you can specify an Absolute threshold of 80% for this attribute. Understanding event thresholds Events are generated when Event Threshold values are exceeded.

■ To disable the abnormality threshold select Suppress event and click Apply in Advanced option. as the baseline is autogenerated. Abnormality thresholds are automatically set (out of the box) on all metrics. and network application services. Abnormality Event threshold BMC ProactiveNet Abnormality thresholds operate in the same way that Signature thresholds work. reporting readings above or below the baseline. BMC ProactiveNet uses the default values to generate events. baselines are not generated and events are not triggered for those attributes. It is used to set the minimum deviation from the high and low baseline established by BMC ProactiveNet for a monitor whose overall baseline is considered too low. it is a much more scalable approach in managing thresholds Signature thresholds focus on performance metrics such as response time. and are automatically closed when the generating condition no longer exists. Abnormalities are used in Probable cause analysis. they generate abnormality events utilized by Probable cause Analysis correlation rather than generate events. generally do not generate events. In case no signature threshold is enabled by the user. Signature thresholds are better suited for attributes that degrade over time. ■ Predefined Abnormality Event thresholds cannot be removed or cleared for any of the attributes. Users do NOT need to set a threshold value. This is important because users do “not” need to do anything in order to start seeing the value of the abnormalities in context of Probable cause analysis correlation. LANs. WANs. utilization. Signature thresholds allow you to control the number of events generated by a monitor. errors for network devices. ■ If the abnormality threshold is suppressed for any of the attributes. servers. Chapter 4 Event administration 181 . Because of this.Understanding event thresholds Threshold type Signature threshold Description Signature thresholds are dynamic thresholds that use the baseline as the threshold. However.

a pattern captured at hourly intervals may be best. ■ They reduce false events to a large extent.Understanding event thresholds Threshold type Intelligent threshold Description Signature and Absolute Thresholds can be combined to create an Intelligent Threshold that will generate events when a metric value falls outside its baseline and it is above its Absolute Threshold. taking a weighted average of these values over time. The accuracy of the baseline improves over time.Each hour of the day has a high or low value that is tracked. or under. Intelligent thresholds provide the following benefits: ■ They reduce the aggravation to manually set and maintain hundreds of absolute thresholds. BMC ProactiveNet captures the following baseline patterns: ■ Hourly baseline . For example. ■ They facilitate faster detection of potential problems. by guessing what the threshold should be for each attribute and device at any time or day of week. To track the anomalies in behavior for different attribute types different patterns are required. which is best suited for capturing frequent changes. This allows you to fix problems proactively. Hourly interval ranges represent a smaller number of data points and will have a tighter range. for attributes that change frequently. The baseline is calculated by collecting the values for a monitor’s attributes and metrics over a specified time period and establishing a low baseline value (consisting of the 10th percentile of all the values for a given time period) and a high baseline value (consisting of the 90th percentile of all the values for a given time period). This eliminates the problem of over. and is repeated for each 182 BMC ProactiveNet User Guide . These help to alleviate issues with Absolute values that are set too low for the normal operating environment. A higher weight is given to the latest data being factored into the baseline average. This tracks the pattern for that metric on an hourly basis. alerting. Related Topics Setting event thresholds on page 184 Baselines The baseline is the expected normal operating range for a metric or attribute of a monitor.

and Sunday. days share the same 24-hour baseline. How abnormalities are generated Abnormalities are generated when the data values from a monitor fall outside of the normal baseline range for a statistically significant number of points within the sample window specified in the signature threshold. A weekly baseline is initialized after the monitor instance is created and 168 hours of data collection has occurred.Baseline is calculated separately for the weekend . artificially will raise or lower the baseline. this works well in majority of the cases. An hourly baseline is initialized after the monitor instance is created and 24 hours of data collection has occurred. Daily. or All baselines. Auto-baseline Out of the box thresholds are set to use Hourly.Baseline is calculated separately for pre-determined days when your business experiences out of the ordinary workloads or other special behavior. ■ Weekday Pattern . causing unnecessary abnormalities. A daily baseline is initialized after the monitor instance is created and 24 hours of data collection has occurred. but the user has to set threshold with auto-baseline option manually. All these ■ Weekend Pattern . Weekly.A high or low value is derived from the moving average of each consecutive day.Saturday ■ Seasonal baseline . These days.Baseline is calculated daily from Monday to Friday. but it might be more appropriate to use one specific baseline type in order to catch the exceptional behavior. Chapter 4 Event administration 183 . By default auto-baseline feature is enabled for new customers. This high or low range is taken from a larger number of data values and consequently will be a wider range than the hourly. ■ Daily baseline . These two days share the same 24-hour baseline. Auto-baseline analysis engine automatically detects abnormality in any monitor instance attribute and determines the best baseline to be used depending on the behavior of the monitor instance. if calculated into the baseline. out of the box thresholds will have auto-baseline option set. For upgrade users the Auto-baseline feature is enabled.Understanding event thresholds day.

By default. even if no explicit global or instance signature threshold is set. which records which baseline was exceeded for a significant number of points (helping determine the severity of the abnormality). Generally. Setting event thresholds Use the following procedure to set event thresholds. abnormalities are still generated. A minimum of five data points are required. For this reason. select the threshold to create based on the type of threshold (absolute. 184 BMC ProactiveNet User Guide . To set event thresholds 1 On the Event Summary tab. according to the type of threshold that you want to define. or abnormality) and the level of coverage (either global for all instances or for a particular monitor instance or event). For example. it is better to use lower polling rates for monitors. if you set a sample window to 10 minutes on a specific monitor attribute but the polling rate of that monitor is 5 minutes. if no signature threshold is set. the abnormality will be closed. if six out of seven data points out of range are statistically significant. By default. signature. 3 From the Tools list. and abnormalities that exceed Daily baseline are more serious in nature than ones that exceed Hourly baseline. If the sample window is set too small (sample window is set in time duration). abnormalities that exceed Weekly baseline are more serious in nature than ones that exceed Daily baseline. then as soon as the last exceeded points drop to five out of seven points. Abnormalities are closed when the number of data points exceeded in the last window sample size is not considered significant.Understanding event thresholds The abnormalities generated have a severity field. the algorithm will still automatically wait for five data points to come in. BMC ProactiveNet will generate abnormalities for above baseline conditions. For example. select any one of the following tabs: ■ Group Matrix ■ Device Matrix 2 Click the Device link of the device name to view the list of monitors under the device. 25 minutes must pass before an abnormality is generated.

click Edit link beside Abnormality Events. Parameters specific to absolute thresholds Comparison This is a reference point for comparison of the actual measurements with the defined threshold values. The supported operators for comparison are >. 4 Set threshold values for the relevant attributes using the parameters displayed on the Edit Thresholds screen. The range of values for which events are triggered. if you select the >= operator for an attribute and set the threshold value to 90%. This is available only for the Absolute Global and Instance Thresholds.Understanding event thresholds Note Alternatively. The same duration is required to close an event. Name of the monitored attribute to which the threshold setting applies. Major. >= or <=. events are generated when the threshold value is greater than or equal to 90%.An event is generated if data is continually greater than the threshold for the specified duration. To set Abnormality Event thresholds. starting with the first data point where threshold is no longer violated. Severity of the event created—Minor. you can reach the threshold setting through the Options => Administration tab. as summarized in Table 46 on page 185. Table 46: Parameters for thresholds Item Enabled KPI Attribute Severity Duration Description Allows you to select an attribute to set its threshold value Parameter value represents a key performance indicator for the application class. Most application classes have 1–2 parameters that are KPIs for the application. This range does not include the threshold. or Critical (not relevant for Abnormality thresholds) The duration (in minutes) of delay from when the threshold is violated to when an event is generated. Threshold Chapter 4 Event administration 185 . ■ Below checked . For example. Click the Edit link beside Intelligent Event Thresholds and then click Edit for the relevant monitor type and threshold type.An event is generated if data is continually lesser than the threshold for the specified duration. ==. <. For example: ■ Above checked .

and deviation is set to 2.b on page 187 Define minimum window of time to keep raw data points that will be considered for intelligent threshold computation. which must be met for the Signature Event to be generated.b Deviation is a way of introducing tolerance into the baseline values.Below the Low baseline ■ Auto-baseline . and so on). For more information. baseline high value is 100. Parameters for signature or abnormality thresholds Above or Below Reference point for the following parameters: ■ Above High .an event is generated accordingly. Weekly. Predict Auto Close Select this option to generate predictive events. then a signature event will be generated when the average of all data values inside the threshold duration goes above 102 or below 38. Absolute DeviationStep 4. The deviation value is additive (not multiplicative) and is given in the same units being measured by the particular monitor attribute (that is #. 186 BMC ProactiveNet User Guide . when it returns to normal state. milliseconds. This is useful to filter out insignificant abnormalities. Data points outside this range are usually discarded.Understanding event thresholds Item Outside Baseline Description The baseline to associate with the threshold. Clear this option if you do not want BMC ProactiveNet to automatically close the triggered event. deviation can be set to ignore this small change. Minimum Sampling WindowStep 4. This is useful for events that have a very short duration. see Viewing predictive events on page 92. For example. Hourly and Daily and All Baselines. associating the response time with appropriate baseline will cover any false event.a on page 187 ThresholdStep 4. if baseline low value is 40. In this case. Other options are Hourly. Daily. For more information see Auto-baseline on page 183. bytes. The default value for Absolute deviation is 5 units. If you select Auto-baseline on page 183 an event is generated accordingly. it additionally requires the data to be above or below the threshold value. Weekly. Daily.%. response time may be higher during peak time. Usually. Other options are Hourly. If there is on page 187 a small change in baseline that is not significant for reporting purposes. For example. Hourly and Daily and All Baselines. This helps to reduce false events associated with latest trends.Above the High baseline ■ Below Low . a signature event is generated if the data values go outside the baseline range. The threshold field is used as an additional constraint. When the threshold field is set.

absolute deviation. 5 Select the Enabled check boxes for all relevant attributes. No event is generated if a single value is exceeded. Suppress Event Step 4. threshold. as an administrator. and Percentage Deviation are additional filters for triggering events. To display the Event Rule Administration page. you must be assigned Allow Event Rule Management privileges by the BMC ProactiveNet administrator. Depending on your privileges. Absolute Deviation.Managing event rules Item Percentage DeviationStep 4. This option is applicable only for Signature and Abnormality Event thresholds. Related Topics Understanding event thresholds on page 180 Note Managing event rules Event rules define the set of actions that can be performed when an event occurs. you can view all event rules. The Event Rule Administration page displays the list of event rules. Click the Advanced link to set thresholds with minimum sampling window. All set values must be exceeded to trigger an event. choose Edit next to the Event Rules entry under the Event Administration heading on the Administration tab. and then click Apply.a on page 187 1 Advanced parameter 2 Threshold. and percentage deviation. You perform event rule management from the Event Rule Administration page. Chapter 4 Event administration 187 .The default value for percentage deviation is 5%. you can see your event rules or. except that the actual value of the deviation is expressed in terms of a percent of the baseline value (rather than an absolute value). To define event rules. (Abnormality events only) If suppress event is enabled baselines projection and abnormality detection will not happen for that specific attribute.b on page 187 Description Percent Deviation has the same meaning as the existing deviation field.

Top Processes by Memory Included Monitors Included Attributes Solaris System Swap Space Used 188 BMC ProactiveNet User Guide .Top Processes by Memory Included Monitors Included Attributes Selected Action(s) Linux System Swap Space Used DD_Command: Top Processes-Mem(Linux) Oracle . Process CPU time Diagnostics/Remote Actions: JVM Detail Diagnostics Default event rule Linux .Managing event rules Default event rules A group of default event rules are provided out-of-the-box. Oracle Query CPU Usage by Sessions.Top IPs by Traffic Included Monitors Included Attributes Selected Action(s) SolarisTM TCP Bytes Received. Database Free Space. Response Time DD_Command: Top SQL-DiskReads(Oracle) Solaris .Top Processes by CPU Included Monitors Included Attributes Selected Action(s) Solaris System Total CPU Utilization DD_Command: Top Processes-CPU(Solaris) Solaris . When any one of the threshold values are exceeded.Top SQL Statements Included Monitors Included Attributes Selected Action(s) Solaris . The default event rules all apply to the 00:00 hours to 00:00 hours of day range and include all days of the week. Table 47: Attributes of default event rules Event rule JVM Monitor Included Attributes Selected Action(s) JVM/Thread Count. Bytes Sent DD_Command: Top IP Traffic Oracle Intelliscope.Top Processes by CPU Included Monitors Included Attributes Selected Action(s) Linux System Total CPU Utilization DD_Command: Top Processes-CPU(Linux) Linux . an event is triggered.

Web App Response Time DD_Command: TopEJBs-WebSphere WebSphere Thread Pool Maxed. EJB Passivates.Top Processes by Memory Included Monitors Included Attributes Selected Action(s) Windows System Swap space used DD_Command: Top Processes-Mem(Windows) Chapter 4 Event administration 189 .Top Processes by CPU Included Monitors Included Attributes Selected Action(s) Windows System System CPU Utilization. User CPU Utilization DD_Command: Top Processes-CPU(Windows) Windows . Total CPU Utilization.0.Active Info Included Monitors Included Attributes Selected Action(s) WebSphere .Top Servlets Included Monitors Included Attributes Selected Action(s) Web URL . Web App Response Time DD_Command: TopServlet(WebSphere) Web URL Total Response Time DD_Command: Get URL Windows .Top IPs by Traffic Included Monitors Included Attributes Selected Action(s) Windows TCP Total Segments DD_Command: Top IP Traffic Windows .Get Page Included Monitors Included Attributes Selected Action(s) Default event rule DD_Command: Top Processes-Mem(Solaris) WebLogic Server 6. EJB Avg Method Response Time.1.Top EJBs Included Monitors Included Attributes Selected Action(s) WebSphere . EJB Total Method Calls. Execute Queue Usage DD_Command: ActiveInfo-WebLogic WebSphere Thread Pool Maxed.1 JVM Memory Used. EJB Activates. or 8. EJB Total Method Calls. 7. EJB Activates. EJB Avg Method Response Time. EJB Passivates.Managing event rules Event rule Selected Action(s) WebLogic .

To perform the filtering action 1 On the Event Rule Administration page.Managing event rules Event rule Default event rule a The default event rule will not be created if the administrator E-Mail ID is not provided during server installation. choose values from among the following filter criteria described in Table 48 on page 190. Consequently all event rules that you have permission to view are displayed. Filtering the event rule list The Action Type. Table 48: Event rule filtering criteria Fields Action Type Options List containing values indicating the actions that you can associate with an event. To focus on specific categories of event rules. You can specify one or more filter criteria. These actions include: ■ No Filter ■ E-Mail ■ SNMP Trap ■ Run Server Command ■ Remote Actions/Diagnostics ■ E-Mail Group ■ RSD Incident ■ BEM event ■ AO event 190 BMC ProactiveNet User Guide . and Status lists display the No Filter value by default. The remaining filtering fields are left blank. you can filter the list according to the various criteria for managing event rules. Rule Type.

you can choose to select an intelligent event type. acknowledged. event. and/or assigned) filter. Click No Filter to open the Groups/Services Filter dialog box. and predictive event filter options. Valid values are ■ No Filter ■ Basic ■ Advanced Rule Name Rule Type Status List of the event status values: ■ No Filter ■ Enable ■ Disable Email groups associated with event rules cannot be filtered.Managing event rules Fields Groups/Services Options Lists the available groups and/or services that you associate with the event. Text box where you can enter a full or partial string to retrieve matching event names List that contains the available rule types. Table 49: Event rule types Type Basic Description This rule type is used to trigger the full range of actions for BMC ProactiveNet intelligent events. and abnormality. It is often used to trigger email notifications. for external device-associated events. then you can specify only the severity level and event state (open. you can specify the full range of monitor type. You can choose to include or exclude selected groups or services. Chapter 4 Event administration 191 . Note Event rule types Event rules are designated by one of the following types described in the following table. close. click Apply. and for external events triggered by event adapters. When distinguishing a basic event rule type. After making your selection. an external event type. or both (the default). If you select an external event. If you select an intelligent event type only.

click Edit next to the Event Rules entry to display the Event Rule Administration page. Generally speaking. an event state filter notification for the event statuses open. if you are building an advanced rule type that uses multiple event slot values. close. Event rules or event management policies Event rules can trigger actions that overlap with actions that event management policies can also trigger. event rules are easier to configure and execute than event management policies.) For example. using an event management notification policy with detailed event selector criteria might be the preferred choice. To add a basic event rule 1 On the Administration tab. Adding a basic event rule type Add a basic event rule type to trigger email notifications for monitored events and external events on systems on which a BMC ProactiveNet device has been defined. together with their attributes. 2 Click Add to display the Add Event Rule (Page 1/3) window. Alphanumeric string that describes the name of the event Description of the event 192 BMC ProactiveNet User Guide . (See BMC ProactiveNet Administrator Guide for a discussion of event management policies which you can access from the Event Management Policies tab of the BMC ProactiveNet Administration Console. complete or modify the text boxes and selections listed in the following table: Table 50: Fields on the Add Event Rule (Page 1/3) window Item Event Rule Name Description Description Required. and assigned. When distinguishing an advanced rule type. It is often used to trigger diagnostic and remote actions. an event rule can trigger an email notification in much the same way as an event management notification policy can. and an abnormality event filter. Nevertheless. you can specify monitor types and instances. acknowledge.Managing event rules Type Advanced Description This rule type is used to trigger the full range of actions for ProactiveNet intelligent events. not external events. 3 On the Add Event Rule (Page 1/3) screen.

Select this option to include the day of the week. Complete the options listed in the following table: Chapter 4 Event administration 193 . ■ Include Selected Groups: Applies the event rule to the selected group ■ Exclude Selected Groups: Does not apply the event rule to the selected group. Use hierarchy on or off to switch over to the corresponding view type. see Managing schedules on page 410 Temporarily disable Event Rule Event Rule Type Groups Filter ■ No Filter/Include Selected Groups/Exclude Selected Groups Disables the event from being applied immediately Click Basic Event Rule. See the Event Policy tab of the BMC ProactiveNet Administration Console. ■ No Filter: Applies event rule to all included monitors irrespective of the group they belong to. For detailed steps. Time Range: ■ Time of Day Range . Use the arrows to move the selected groups. ■ Days of Week . Schedule: Click New to create a new schedule or Edit to edit an existing schedule from the list.Select the time range in days.Managing event rules Item Time Range/Schedule Description You can select either the Time Range or the Schedule option. I f you choose either the Include Selected Groups or Exclude Selected Groups option. then only device-associated events trigger the event rule. To include 24 hours. ■ Available Groups ■ Selected Groups Hierarchy Expand or collapse the groups. select “00:00”-”00:00”. then both device-associated and nondeviceassociated events can trigger the event rule. 4 Click Next to display the Add Event Rule (Page 2/3): Select Event/Monitor/ Severity Information page. Use an event management policy to trigger nondevice-associated events exclusively. If you choose No Filter.

monitor. and Assigned Upon selecting both Intelligent Events and External Events options. You can select one or both options. By default. BMC ProactiveNet Operations Manager (POM) users do not see Intelligent Events. apply only to Intelligent Events. then the event rule is upgraded and mapped to a basic event rule with the Intelligent Events option selected and the External Events option unchecked. or Down) ■ Event states Open. then you enable the filter options that apply to both options: ■ Event severity filter (but not the relationship direction Any. the following filters are disabled: ■ Monitor Type filter options ■ Relationship direction Any. When you select both Intelligent Events and External Events options. ■ External Events: External events refer to device-associated events and events received from external event adapters. Acknowledge. however. or Down options of the event severity level ■ Abnormality and Predictive event filters For External Events. Monitor Type Filter Description 194 BMC ProactiveNet User Guide .Managing event rules Table 51: Event. Up. Close. Up. Note for upgrade users: If you have an existing basic event rule without external events. remote actions apply only to device-associated events. If you have an existing basic event rule with external events. both options are selected. and severity options of event rules on the Add Event Rule (Page 2/3): Select Event/Monitor/Severity Information window Options Event Type Filter ■ Intelligent Events ■ External Events ■ Intelligent Events: These are internal events: BMC ProactiveNet events that are generated when you have data collection and monitoring enabled on the BMC ProactiveNet system. Run Agent Diagnostic actions. then the event rule is upgraded and mapped to a basic event rule with the External Events option selected and the Intelligent Events unchecked.

The event severity levels are: ■ Info ■ Warning ■ Minor ■ Major ■ Critical ■ Info-Warning ■ Minor-Major ■ Major-Critical ■ Info-Warning-Minor ■ Warning-Minor-Major ■ Minor-Major-Critical ■ Info-Warning-Minor-Major-Critical Up Down Open Close Triggers event rule every time the new severity is higher than the old severity Triggers event rule every time the new severity is lower than the old severity Triggers event rule every time a new event is opened Triggers event rule every time an event is closed Chapter 4 Event administration 195 .Managing event rules Options No Monitor Type Filter/Select Monitor Types Description ■ Select No Monitor Type Filter. Severity/State Filter Event tab Any Triggers event rule for any severity level that matches the specified severity. ■ Select Monitor Type to assign the type of filter by choosing from the Available Monitor Types pane and moving them to the Selected Monitor Types pane. if no specific monitors are needed. By default. this will enable all available monitors.

Valid values are ■ Minor ■ Major ■ Critical ■ Minor-Major ■ Major-Critical ■ Minor-Major-Critical Open Close Acknowledge Assigned Triggers an event rule each time a predicted event is opened Triggers an event rule each time a predicted event is closed Triggers an event rule each time a predicted event is acknowledged Triggers an event rule each time a predicted event is assigned 5 Click Next to display the Add Event Rule (Page 3/3): Action Information for Event Rule complete the options listed in the following table: Table 52: Action options of event rules on the Add Event Rule (Page 3/3): Action Information for Event Rule window Options Actions to Perform Send Email action From Your e-mail address. Description Lists the actions that you have associated with the event after clicking the Add button corresponding to the action 196 BMC ProactiveNet User Guide .Managing event rules Options Acknowledge Assigned Abnormality tab Open Close Abnormality Score >= Predictive tab Select Predicted Severity Description Triggers event rule every time an event is acknowledged Triggers the event rule each time an event is assigned Triggers event rule every time when a new abnormality is opened. Specifies the severity level of the predicted event. Use this option to filter abnormal events that have abnormality score from the list. Triggers event rule every time when an abnormality is closed.

See also Managing the AlarmPoint integration on page 216. create an event rule using the AlarmPoint command. the event is sent to the default user. and click Add.Managing event rules Options To Message Format Description Recipient e-mail address. see To create or edit an E-Mail Group on page 205 Customizes the settings for all email alerts.u userName in the Path field. Click Add to include a Send Email action. Note: To add an AlarmPoint notification for a data-only implementation. For detailed information on the run command. See also Managing BMC ProactiveNet events through Diagnostic Commands on the BMC ProactiveNet Server on page 216. Run Agent Diagnostic actions apply to intelligent events. E-mail will be sent to the configured user. Run Agent Diagnostics For systems running BMC ProactiveNet agents. and click Add. For detailed information see. see Managing BMC ProactiveNet events through Run Command on Server on page 215. Then click Add. Enter the pw_AlarmPoint . For more information. Select one of the following: ■ Full Page ASCII ■ One-line Summary ASCII ■ Full Page HTML/GIF E-Mail Group Event Text Customization Option to create E-mail groups. Then choose the process to inquire about from the list. Send SNMP Trap action SNMP Host (Name/IP) To send events to a management system that accepts standard SNMP traps. Chapter 4 Event administration 197 . For detailed steps. add a preconfigured command to an event rule using the Agent Diagnostics Command. Run Command on Proactive Server action Path Include the file path where you wish to run specified executables or scripts and execute an application or script when an event occurs. enter the SNMP host name or IP address. see Customizing event text on page 245. Managing BMC ProactiveNet events through SNMP traps on page 205. If you do not enter the user name.

Then choose the process to inquire about from the list. Send event to BMC Atrium Orchestrator Integrate with BladeLogic Execute Blade Action Runs the snapshot on BladeLogic automatically. Integrate with BMC Remedy Service Desk.Managing event rules Options Run Remote Actions/Diagnostics Description For systems without BMC ProactiveNet agents. on monitored. Integration configuration for event actions (Remedy Service Desk) on page 218.Integration configuration for event actions (BEM) on page 229. Send event to BMC Event Manager Sends an event to BMC Event Manager (BEM). For more information see. For more information see. Managing BMC ProactiveNet events BMC Atrium Orchestrator (formerly known as BMC Run Book Automation) on page 237. For more information see “Integrating with BMC BladeLogic” on page 419. create and register a userdefined command to associate with the event rule. where the device is the target system on which the remote action is executed. click Done to save the event rule type and its attributes. Advanced rule types apply only to intelligent events. and click Add. For detailed information see. The device must have its authentication credentials defined so that the remote action can access the device. Note Adding an advanced rule type Add an advanced event rule type to trigger actions. Sends an event to BMC Atrium Orchestrator. 198 BMC ProactiveNet User Guide . The triggering of action happens on any specified event when the event rule is satisfied even when the other slots or information are changed. BMC Event Manager and BMC Atrium Orchestrator actions Create incident in BMC Remedy Service Desk Creates an AR system request in BMC Remedy Service Desk (BRSD). Remote actions are triggered by device-associated events. Do not use this action for any other event rule apart from DefaultRule-BladeEvent. including remote and diagnostic actions. See also Managing BMC ProactiveNet events through Diagnostic Commands on the BMC ProactiveNet Server on page 216. 6 After adding actions to the event. ■ The newly created event rule is displayed in the event rule list of the Event Rule Administration page. attribute-level events. The event must be mapped to the device through a device alias.

and click Next. The attributes are displayed in the Selected Attributes table. or Severity Filter selections are based on the filter options you chose to include or exclude on Page 1/3. You can select and add monitor types and attributes together with monitor instances and attributes. Instance. You can choose from the following severity levels: ■ Abnormality ■ Predictive Minor ■ Predictive Major ■ Predictive Critical Note Chapter 4 Event administration 199 . The monitor instances and respective attributes are displayed. The instances and attributes are displayed in the Selected Attributes table. specify a severity level for each attribute. select Monitor Instance and Attribute and click Add to display the Instance Selector window. and then click Apply. to include specific instances of a monitor. 2 Click Next to display the Add Advanced Rule (Page 2/3): Select Attribute Information page. 3 To include all instances of a particular monitor type. Be sure to select the Advanced Rule option under Event Rule Types.Managing event rules To add an advanced rule 1 Complete steps 1 through 3 as described under To add a basic event rule on page 192. The default is abnormality. select the monitor type or types. The Attribute. b Select one or more instances and attributes. 5 In the Selected Attributes table. a In the Monitor Type Filter dialog box. a Select one or more monitor types. b Select one or more of the corresponding attributes. and click Add to display the Monitor Type Filter dialog box. and click Add. The corresponding attributes are displayed. select Monitor Type and Attribute under Attribute/Instance/Severity Filter. 4 Alternatively.

select one or more of the following options: ■ Open to trigger the event rule every time a new event or event is opened ■ Close to trigger the event rule every time an event or event is closed ■ Acknowledge to trigger this event rule every time an event is acknowledged ■ Assigned to trigger this event rule every time an event is assigned 9 To set a filter for abnormality events. The procedures are the same as for adding an event rule.Managing event rules ■ Minor ■ Major ■ Critical 6 Indicate whether you want to include severity levels greater than the selected one by selecting the and higher option. or no filter under Abnormality Score Filter. 7 Select which attributes you wish to associate with the event. you can edit any field except for the event rule type. 10 Click Next to display the Add Event Rule (Page 3/3): Action Information 11 Complete the options listed in Table 52 on page 196. click Edit next to the corresponding rule in the event rule list of the Event Rule Administration page. specify a value. (You can click Delete to remove selected attributes. 8 Under Event State Filter.) Note The selections that you make in the Selected Attributes table are based on the current filter selection. 12 Click Done to save the event rule type and its attributes. If you modify the filter selection later. Editing a basic or an advanced rule To edit any of the rule types. 200 BMC ProactiveNet User Guide . the selected attributes remain the same because they are based on the original filter selection. In the Event Rule wizard.

modify or delete any actions of the event rule. you can add. Deleting an event rule The deletion action removes the event rule and its related actions from the BMC ProactiveNet server. 2 Click the Delete tab. To update event action 1 On the Event Rule Administration window. would be removed from the event rule definition. select the event rule which requires changes. By default. the Update Action tab is disabled. To select all the event rules click Select All. BMC ProactiveNet deletes the event rule and refreshes the Event Rule Administration window. select the corresponding check box under the Select column to delete an event rule. 2 Click Update Action. To delete an event rule 1 On the Event Rule Administration screen. or of both types would have on actions that are already assigned to the event rule. The Update Action screen appears. then any Run Agent Diagnostic actions. 3 Click OK in the confirmation screen. if you edit a rule that originally applied to both external and intelligent event types so that now it applies to external events only. Chapter 4 Event administration 201 .Managing event rules WARNING When editing an existing basic event rule. intelligent event type. 4 Click Apply to update the action. For example. Updating event actions Through the Update Action tab. 3 Select the desired Action Type to update action. Any updates to an event automatically trigger corresponding notification events. which apply to intelligent events only. you need to determine the impact that the selection of an external event type.

the server passes nine arguments to the script or program that is executed as a result of an event action launch. if an event transitions from high to critical. Event ID is different for each new event that affects the state of the event. click Enable. The status of the selected event rule gets changed. run scripts on remote target. They are as follows: ■ <rule_name>: Name of the event rule ■ <time_stamp>: Time when the event occurred ■ <Device_Name>: Name of the device hosting the monitor from where the event originated ■ <Severity>: Severity associated with the event ■ <Status>: Current status of the event ■ <Description> . Supplying arguments to a server command By default. When the event closes. To enable or disable an existing event rule 1 On the Event Rule Administration screen. click Disable.Managing event rules Enabling and disabling event rules Event rules are associated with different actions such as sending an email. ■ To disable an event rule.Description of the event ■ <Event ID>: Unique ID of the event associated with the event. send events to BEM and so on. 202 BMC ProactiveNet User Guide . select the corresponding check box under the Select column to enable or disable the event rule. You can suppress these actions by disabling the entire event rule. 2 Click the relevant option: ■ To enable an event rule. Enabling event rule would re-instantiate all the actions. 3 Click OK in the confirmation screen. that is a new event. that is also a new event. For example. accompanied by it's own event ID.

When additional user arguments are specified. the source agent will always be the IP Address of machine hosting the BMC ProactiveNet Server. Intelligent Event ID remains constant for the duration of the intelligent event. Here’s an example: /usr/pw/pronto/usr_apps/bin/notify.The default arguments are passed in the order given above.csh value1 value2 rule_name time_stamp device_name severity status description eventId AlarmId Note Default arguments are passed into the script. followed by the default arguments.Managing event rules ■ < Intelligent Event ID>: Unique ID of the intelligent event. see /usr/pw/pronto/bin/ generic_script. Device IP is a string denoting the 4 octets of the device IP address. For an example of a script that uses these parameters.pl. they are passed into the script before the default arguments. Note the use of the 'flags' parameter: /usr/pw/pronto/usr_apps/bin/notifycce.e. The scripts can simply ignore these arguments if they are not needed.csh rule_name time_stamp device_name severity status description eventId AlarmId DeviceID Source_AgentIP Additional user arguments can be passed into the event scripts by appending them to the script name. Here’s an example of a script that was launched with only the default arguments: /usr/pw/pronto/usr_apps/bin/notify. Here’s an example of passing 'value1' and 'value2' into the event script. For event actions triggered by SNMP based monitors. ■ <Device IP>: IP address of the device hosting the monitor from where the event originated. User-defined arguments are passed first to the server. regardless of whether the event scripts intend to use them or not.csh&flags=value1&flags=value2 Separating the values using the ampersand and the term flags (&flags) is optional. until it closes. i.. Note Chapter 4 Event administration 203 . ■ <Source Agent IP>: IP address of the device hosting the BMC ProactiveNet Agent.

port=25 These entries are dynamically generated. The workaround is to write the command in a script file and execute the script using Command On Server Action. 204 BMC ProactiveNet User Guide . relevant graphs can be viewed.host=mail. It is important that your ISP. e-mail client. When setting up event rules. ProactiveNet Server will execute the command ‘chmod x abc.sh'. For example.smtp.Managing event rules While passing arguments to command on server.com pronet. If your e-mail client supports HTML format. Details of the SMTP Server to be used for email alerts are stored in pronet. This may lead to unexpected results.api.api. BMC ProactiveNet can send event notifications through e-mail when an event is generated. and network support HTML e-mails. you must determine the way in which event notifications will be sent. Similarly. if the Command on Server is specified as 'chmod +x abc. event e-mails contain the same information as the events viewed from the event Summary page. subject and body of a particular Email Alert can also be customized using Event Text Customization for Individual Event Rules.sh’.emailer.bmc. E-mails can be sent in HTML format. which includes the event listing. HTML provides for enhanced report layout and inclusion of graphs.emailer. along with the event graph. E-mail notification. Note Defining email groups An email group is a group of email addresses by which event rule actions. The group consisting of email addresses is notified. Please refrain from editing these without prior impact assessment.smtp. do not pass “+” character as an argument. is similar to how it would be viewed from the BMC ProactiveNet Operations console. You can add. modify or delete any e-mail group by accessing the E-Mail Group Administration dialog through the E-Mail Group Administration button on the Event Rule Administration page.conf under installDirectory /pw/custom/conf: pronet. Any changes to these entries will impact all mail related BMC ProactiveNet actions (event notification/reports/alerts). can be sent to an email group. The character “+” is used as a keyword internally by the BMC ProactiveNet Server. HTML event notifications contain partial GIFs of the event summary detail. HTML format is preferred if your e-mail client supports it.

4 Select the preferred E-mail type from the list. This external environment also refers to integrations with the following BMC products: BMC Remedy Service Desk. you can manage all events in the external environment monitored by BMC ProactiveNet. Note To create or edit an E-Mail Group 1 On the Event Rule Administration page. 5 Click Add to add the E-mail group. and BMC Atrium Orchestrator. 6 Click Done to save the E-mail group options. Check with your administrator. Managing BMC ProactiveNet events through SNMP traps In the BMC ProactiveNet Administration console. Table 53: SNMP trap options Option Standard Description Works with any management system that accepts standard SNMP traps Chapter 4 Event administration 205 . The actual time of event generation could be much later. Event actions: managing BMC ProactiveNet events in external environments Through the action options of event rules on the Add Event Rule (Page 3/3): Action Information for Event Rule window. 2 On the E-Mail Group Administration page.Event actions: managing BMC ProactiveNet events in external environments Some ISPs do not allow or only allow an image of a certain size to be mailed. In case of notification through HTML e-mail. File size is often limited to 2MB. click the E-Mail Group Administration tab. BMC Event Management. timestamp included in the subject refers to the time when the threshold was first crossed. select the appropraite option to specify event notification by SNMP traps. depending on threshold duration and polling interval. click Add 3 Type the name of the group and list of e-mail address.

3287. Remote Agent.4.6. Other.6.6.3.7 1.2.1.3 1.1. Abnormality score.1.4.1. Values are 4 (CRITICAL).1.14 1.3287.3.1.3287. Applicable to all instances of specified monitor type157: Crossed signature threshold. DBServer.1.5 1.1.1.1.3287. 3 (MAJOR).3.6.1.1.2.3.1. By default.1.1.4.1. Can either be OPEN or CLOSED event description Device types to which this event is related are AppServer.10 1.6. 1.1.1.1.1. Applicable to a specific monitor instance162: Crossed signature threshold.3287.1.3.4. FireWall.1.3287.1.1. Switch.1.3287.3287.1. 2 (MINOR).15 206 BMC ProactiveNet User Guide .4.1.2.2. Severity of the event.6.6. Signature. By default.1.4 1.3.2.1.1.6.2.3.1.1.1.6 1.1.1.2.1. Threshold Type is an integer defined as 156: Crossed absolute threshold.1.1.1.4.1.1.1.4.8 1.4.3.4.3287.2.6.3287. Applicable to a specific monitor instance event rule name.2. ChangeEvent or Imported Event.1. This indicates how closely the event relates to the probable cause of the problem.1.11 1.3.3.4. ifType of Interface.1.1.3.4.2.1.6.3287. Router.3. Mail Server.4. Variable bindings that are sent as part of the BMC ProactiveNet trap are: Table 54: BMC ProactiveNet Trap Variable Bindings OID 1.4. Threshold type that is whether it was Absolute.6.1 1.1. Applicable to all instances of specified monitor type158: External events that are imported using pw user event or using SNMP trap receiver monitor159: Change Event.2.1.1.1.1.Event actions: managing BMC ProactiveNet events in external environments Option HP OpenView Tivoli CA Unicenter NSM Description Integrates with HP OpenView traps Integrates with TEC and NetView traps Integrates with Computer Associates Unicenter NSM traps BMC ProactiveNet SNMP trap details The BMC ProactiveNet Enterprise OID is 1.2.6.6.1.4. Server.12 Description event ID Time when the event was generated Path of the monitor instance that generated the event IP address of the trap-sending BMC ProactiveNet Server IP address of the device that generated the event ifNum of interface.1.3.3.6. this OID is sent blank.2.1.6.3287.2. 1 (ABNORMAL) Status of the event. WebServer.1.1.1.1.1.3287.4.161: Crossed absolute threshold.1.3287.3.2.1. the value is set to 100.1.1.1.3287.1.9 1.2.13 1.1.1.1.1.1.1.

1.6.18 1. Escalation information.20 1.1.1.3287.1.21 1. BMC ProactiveNet provides an enhanced integration package for HP OpenView.6.3287.1.1.Event actions: managing BMC ProactiveNet events in external environments OID 1. The traps are correctly formatted and displayed in the Event Console.4.3.1.4. Integration (for version 6. event suppression. If set to true.3287.6.4.1.3287.4.17 1.1.1.22 1.1.1.1.2.23 Description The URL of the page on BMC ProactiveNet web server where detailed information of the event can be found. The enhancements include: ■ A link to the Event Details page for individual BMC ProactiveNet events ■ The severity of the event displays on the HP Open Views map ■ Device Level Event Matrix from the node is displayed on the HP OpenView Console Chapter 4 Event administration 207 .6.1.2. Note See the BMC ProactiveNet Release Notes for compatible versions of HP OpenView Network Node Manager.2. HP OpenView integrates BMC ProactiveNet traps into Network Node Manager (NNM).2.1.1.4.6.3287.1.1.3.3.1.1.1.1.1.41 and later) In addition to the integration package.3287.19 1.1.1.16 1.3. It also allows you to launch BMC ProactiveNet from the pop-up menu as well as the menu bar.6.3.4.6.1.1.1. Device name.1. MIB for the BMC ProactiveNet Server is also loaded so that you can use the MIB Browser and navigate down BMC ProactiveNet Server MIB.4.3. All BMC ProactiveNet traps are seen under the Pronto Proactive Events category. Device description.1.2.3287.1.3. Monitor type.1.2.1.2.4.6. More Info is an important piece of information for determining the reason for event.3287.1. the event suppresses other BMC ProactiveNet events. HP OpenView integration You can use HP OpenView in conjunction with the BMC ProactiveNet Server and Proactive Remote Agent (UNIX).1.1.3.2. Instance name.1.1.1.1.

the installer installs the required registration. ■ The default path for ov. Once the browser path is determined. 5 After the installation is complete.envvars.envvars. a message is displayed to supply the complete path to the browser. 4 Run the following command: ■ ./instl-proactivenet-ov. 2 Change directory to ovproactivenet.sh A welcome note displays. and icon files in the appropriate directory. For supported versions. executable. The default path for ov. 2 Untar the ovproactivenet. see the BMC ProactiveNet Release Notes. a read-write enabled Open View Map must be opened on the computer where the BMC ProactiveNet Integration package has been installed. 208 BMC ProactiveNet User Guide . This can be done by sourcing ov.sh or ov./uninstall to uninstall BMC ProactiveNet Package for HP Open View.Event actions: managing BMC ProactiveNet events in external environments Prerequisites ■ The correct version of HP OpenView Network Node Manager must be installed on a supported version of HP-UX. 3 Change directory to ovproactivenet.sh or ov. details of the installation log and its availability. To install the new integration package 1 Source the Open View environment.sh under UNIX is /opt/OV/bin. restart the Open View User Interface (ovw) to activate the BMC ProactiveNet package. To uninstall the new integration package 1 Source the Open View environment. A confirmation message to install the package appears.envvars. For installation and uninstallation. This can be done by sourcing ov. ■ For a status change to be reflected when a BMC ProactiveNet event is received. The ovproactivenet directory is created. symbol.csh.csh. 3 Execute .sh under UNIX is /opt/OV/ bin. it is not necessary that Open View Map be open.envvars. Click y (yes) The installer tries to determine the path to the browser executable.envvars.tar file.envvars. If the executable is not found in the default path.

choose Options => Event Configuration. Chapter 4 Event administration 209 . 4 Close Event Categories Window. To send SNMP Traps for events. Click Status corresponding to BMC ProactiveNet events to open the Event Browser for BMC ProactiveNet events. 3 Delete the BMC ProactiveNet Events category. 5 Remove BMC ProactiveNet Events category manually. BMC ProactiveNet Remote Agent that raised the event because of which the trap was generated. All BMC ProactiveNet events forwarded to HP OpenView can be viewed under a separate event category called BMC ProactiveNet events in the Event Categories window of NNM. create an event notification rule on the BMC ProactiveNet Server. Viewing BMC ProactiveNet events on event browser After installing BMC ProactiveNet Integration package. 2 On the Event Categories Window. choose File => Save.Event actions: managing BMC ProactiveNet events in external environments 4 Restart Open View User Interface (ovw). 5 On the NNM Event Configuration window. choose Edit => Configure => Event Categories. To delete BMC ProactiveNet events from the event browser: 1 On NNM Event Configuration Window. Time of the computer where HP OpenView is installed. configure the required BMC ProactiveNet Server to forward BMC ProactiveNet events as SNMP traps to the computer where HP OpenView Integration package has been installed. This deletes the BMC ProactiveNet Events category. Table 55: event message options Option Date Trap Sending Agent Description Time when BMC ProactiveNet trap was received. Each event message is shown in the following format: date trapSendingAgent trapMessage The options are listed in Table 55 on page 209.

2 Select Actions => Additional Actions. select Open ProactiveNet Event Page and click OK. such as in which event source will each event go. The necessary file appears as part of the BMC ProactiveNet Server or BMC ProactiveNet Agent (UNIX) installation. If no browser instance is open currently. Use the instructions in the Tivoli manual for installing the Tivoli Module. then a new browser instance is opened. and Unknown. 4 Select the Selected events check box. mapping of the event severity for the incoming event is done through this file. 3 On the Additional Actions for BMC ProactiveNet Events screen. There are four event classes for four different event types. The event severities are mapped as follows: ■ Critical => Fatal ■ Major => Critical 210 BMC ProactiveNet User Guide . and then run the installation as follows. The severity of the incoming event must be mapped to one of these. Minor. To accomplish this. modify the tecad_snmp. Critical. The event severity must be mapped because the TEC server understands only these severities: Fatal. the user is required to log on to the BMC ProactiveNet Server. Harmless. 1 Select a BMC ProactiveNet event. 5 Click OK to open the corresponding event details page.cds and tecad_snmp. Warning. Tivoli Tivoli integration requires you to untar the file provided on your BMC ProactiveNet Server.oid files. Also. but must be customized so it can understand and listen to BMC ProactiveNet traps. The SNMP adapter by itself cannot receive and understand all SNMP traps coming in on that computer.Event actions: managing BMC ProactiveNet events in external environments Option Trap Message Description event received on ProactiveNetAgentHostname Description: ProactiveNetEventDescription event URL: URLToOpenProactiveNet EventDetailsPage To view the event details page. These files also contain information. The content of these files must be appended with the Event Class definitions. In this case.

BMC ProactiveNet Plus module There are two operational tasks in this Plus module: ■ Set up TEC Event server for BMC ProactiveNet ■ Set up Event adapter for TEC To install the plus module 1 Start the Tivoli desktop. which is inherited from the base SNMP Class.x listed in the Install Product window is displayed. 7 Right-click the Setup Event Adapter for TEC icon and click Modify Job.baroc file defines the new event class.Event actions: managing BMC ProactiveNet events in external environments ■ Minor => Minor ■ Abnormal => Harmless Once done. ProactivePlus Module for Tivoli. 6 Once the Plus module is installed successfully.image/Cfg directory. 4 Choose Set Media&Close. The four new event classes defined in tecad_snmp. 5 Select the node name that is installed and then click Install and close.1. The product name. click the TivoliPlus icon on the Tivoli Desktop. select Desktop => Install => Install Product. select the endpoint/managed node where SNMP adapter is running from the Available Task endpoints frame. Version 1. Remove all the other node names from this frame. ■ Double-click Setup Event Adapter for TEC or right-click the icon and click Run job to run the task. pw_plus. Then click ProactivePlus for Tivoli. Chapter 4 Event administration 211 . In this window. Click the arrow so that it shows up in the Selected Task endpoints frame. which in turn are forwarded to the TEC server. 2 From the menu bar. 8 Before running the Setup TEC Event Server for BMC ProactiveNet task. 3 Choose Select Media and select the path to the ProactivePlus. This task should always be executed before running Setup TEC Event Server for BMC ProactiveNet. On successful installation the two icons for the Operational Task are displayed. This rule_base might exist if this task was executed in a previous installation. the TEC server must be customized so that it understands the traps received by the adapter. Then click Change and close.cds are inherited from the main event class defined in this BAROC file. ensure that the rule base ProactivePlus does not exist.

run ■ BINDIR/.sh d $BINDIR/.8 / 3. One of the event sources is BMC ProactiveNet.sh Otherwise. The system prompts you for the rule_base to clone. and are available under usr/pw/apps3rdparty/tivoli/3.9 install script. select the SNMP option and enter the TEC console location in the entry field provided.9 on the BMC ProactiveNet Server./ generic_unix/TME/PLUS/Proactive/PLUSproduct-info. 2 Run the removepw. 4 Double-click Tivoli Plus.sh script that was provided in the original tar file. then double-click ProactivePlus for Tivoli. To uninstall the Plus module: 1 If Framework 3.9 integration To integrate Tivoli TEC 3. 6 Once this is done. ■ The Tivoli setup is now complete. 9 Double-click Setup TEC Event Server for ProactiveNet. Select ProactivePlus and then select Edit => Delete from the menu.. Remove all components from within the Plus module. skip this step. From the BMC ProactiveNet Server. The BMC ProactiveNet events is displayed.Event actions: managing BMC ProactiveNet events in external environments ■ To delete this rule base. Ensure that all these individual components have all the icons under them deleted before actually deleting the main icon.. right-click the Event Server icon and select rule bases./generic_unix/TME/PLUS/LINK/PLUSuninstall.8/ProactiveNetPLUS directory 212 BMC ProactiveNet User Guide .8/3.8 and 3. the TEC console opens from the Tivoli Desktop. 3 Go to the Tivoli desktop and choose Desktop => TMR Connections => Top Level Policy Regions from the menu bar. 10 Once these two tasks are executed correctly.6 is installed. run the Tivoli TEC 3. 5 Delete all the listed components. go to /tivoli/tec_rules and delete the directory ProactivePlus. Tivoli TEC 3. Select default values in this case. The install scripts are part of the BMC ProactiveNet Server installation. Double-click the icon.

Warning. ■ Appends tecad_snmp. The Tivoli TECAD SNMP adapter receives these traps and forwards them to the TEC Server for display on the Event Console of Tivoli.baroc file to the Rule base. There are four event classes for four different event types. Installing the plus module (for TEC 3. Harmless. If there are spaces in the path.Event actions: managing BMC ProactiveNet events in external environments BMC ProactiveNet sends events to Tivoli as SNMP Traps. Critical.oid also contain information. event severity (Fatal. This file contains new event classes inherited from the base SNMP Class. Minor. To achieve this coordination with TECAD SNMP adapter. BMC ProactiveNet PLUS installer performs the following configuration changes: ■ Modifies tecad_snmp.8/3.oid files with entries regarding BMC ProactiveNet SNMP Traps.8/3.cds and tecad_snmp.9) Ensure that there are no spaces in the path specified while installing TEC Server on Windows. tecad_snmp. The severity of incoming event is mapped to the default mapping listed in Table 56 on page 213. Table 56: Default mapping BMC ProactiveNet Severity Critical Major Minor Abnormal Tivoli TEC Severity Fatal Critical Minor Harmless The BMC ProactiveNet PLUS installer configures the TEC server by adding the pw_plus. and Unknown) mapping for incoming event. Related topics: To install BMC ProactiveNet Plus module. BMC ProactiveNet PLUS module installation will fail.9): on page 215 Chapter 4 Event administration 213 .cds and tecad_snmp. on page 214 To delete an existing BMC ProactiveNet rulebase on page 214 To setup TEC Event server for BMC ProactiveNet on page 214 To uninstall the ProactiveNetPlus module (for TEC 3.cds and tecad_snmp.oid files with Event Class definitions. such as event source mapping.

2 Select ProactiveNet and delete using the Edit menu. click TivoliPlus. 4 On the new window. right-click Setup SNMP Adapter for BMC ProactiveNet and choose Modify Job. select the endpoint/managed node using arrow keys where TECAD SNMP adapter is running and make the required selections. 8 On the Operational Tasks window. To setup TEC Event server for BMC ProactiveNet 1 Run TEC Event Server. 3 On the Tivoli desktop. 6 On the Modify Job screen. Alternatively. right-click and choose Run job. 2 Double-click Setup TEC Event Server for ProactiveNet. 7 Click Change and close. Note ■ Execute this task before running Setup TEC event server for BMC ProactiveNet. double-click Setup SNMP Adapter for ProactiveNet.sh script. ■ Delete any rulebase from previous installations. To delete an existing BMC ProactiveNet rulebase 1 Right-click Event Server and select rule bases. 214 BMC ProactiveNet User Guide . ■ The following icons are displayed under the Operational Tasks: — Setup SNMP Adapter for ProactiveNet — Setup TEC Event Server for ProactiveNet 5 Under Operational Task. right-click and choose Run job. 1 Start Tivoli Desktop. Alternatively.Event actions: managing BMC ProactiveNet events in external environments To install BMC ProactiveNet Plus module. click ProactiveNetPlus for Tivoli. 2 Run the ProactiveNetPLUSinstall.

as well as event integration with other notification systems. — Specify another rulebase for Tivoli Event Server.9): 1 Navigate to installDirectory /usr/pw/apps3rdparty/tivoli/3. Such applications or scripts can be used for escalation management.8/ProactiveNetPLUS / plusmoduleremove 2 Run the script by using the following commands ■ paremove. Managing BMC ProactiveNet events through Run Command on Server Server commands run specified executables or scripts and execute an application or script when an event occurs. open the TEC console to view BMC ProactiveNet events. — Delete the BMC ProactiveNet rule base from /tivoli/tec_rules. ■ After successful execution of the two tasks. The script can be modified and moved to the installDirectory /pw/pronto/usr_apps/bin directory.8/3. They can also be used to send events directly to ticket systems such as BMC Remedy Service Desk. The installDirectory /pw/pronto/bin/generic_script.sh This script uninstalls all BMC ProactiveNet PLUS components. Chapter 4 Event administration 215 . To uninstall the ProactiveNetPlus module (for TEC 3. BMC ProactiveNet Administrator will choose the application or create the script and decide whether to run the application or script. such as AlarmPoint. After BMC ProactiveNet PLUS module has been removed. which is provided as a model.pl script. on the server or on the agent system where the event occurred.Event actions: managing BMC ProactiveNet events in external environments 3 Select default values for the Rulebase to clone prompt. shows how arguments can be passed to the script. ■ Path: Enter the script you want to execute when an event occurs. You run the executables or scripts through the Run Command on Server You can run an application or script when an event occurs.

See the BMC ProactiveNet Administrator Guide for information about diagnostic commands. You can select one to execute it. The “+” character is used as a keyword internally by Proactive Server. For example. This may lead to unexpected results. this log file can be checked for errors. Managing the AlarmPoint integration The AlarmPoint integration for BMC ProactiveNet provides the ability to notify AlarmPoint users who are monitoring a device about BMC ProactiveNet events that meet specified escalation criteria. The workaround is to write the command in a script file and execute the script using Command On Server Action. do not enter the “+” character as an argument. when the target system does not have an installed and running agent Both diagnostic commands are used to gather information about the top system processes on the target system. Any exception that occurs while executing the command will be recorded in the ProactiveNet. The Run Agent Diagnostics commands are predefined. Managing BMC ProactiveNet events through Diagnostic Commands on the BMC ProactiveNet Server You can define two types of diagnostics commands to execute on remote systems: ■ Run Agent Diagnostics. If the target system does not have an agent. when a BMC ProactiveNet agent is installed and running on the system ■ Run Agent-less Diagnostic/Remote Actions.log file in the installDirectory /pw/pronto/logs directory. if the command on Server is specified as chmod +x abc. Limitation: The BMC ProactiveNet Server executes the commands on a different thread to prevent it from terminating unexpectedly. So the event action history will record Run Server commands successfully. you must define and register the remote action command and use the appropriate remote login protocol to retrieve the process information. If the BMC ProactiveNet Server stops responding.Event actions: managing BMC ProactiveNet events in external environments Note While entering arguments to send server commands. Proactive Server will execute the chmod x abc.sh.sh command. 216 BMC ProactiveNet User Guide .

e-mail. Enter the BMC ProactiveNet CLI pw_AlarmPoint -u userName in the Path field. the AlarmPoint user can perform management actions on the event. close. Event-only implementation In the event-only implementation.com. In the event-only implementation. In page 3/3 of the event rule wizard. v. it triggers the notification policy. and so forth. Data-only implementation To prepare the data-only implementation.alarmpoint.conf file to enable AlarmPoint to communicate with the Product Short Server. which forwards it to the AlarmPoint server and to the designated AlarmPoint users of the configured device—whether it be SMS. When an incoming event matches the event criteria formula. Follow the installation and configuration directions in the AlarmPoint documentation. assign. The AlarmPoint user cannot reply to the event with an action such as acknowledge. 2. When the event matches the event rule criteria. the AlarmPoint user goes through the BMC ProactiveNet Administration Console to create a notification event management policy specifically for AlarmPoint users. The AlarmPoint integration can satisfy an event-only and a data-only implementation. Both implementations leverage the same AlarmPoint products. such as acknowledge. The AlarmPoint users are identified through a specially defined event criteria formula.0. perform the additional configuration step described in the Remote Actions/Diagnostics chapter of the BMC ProactiveNet Administrator Guide. the event is escalated and the AlarmPoint user is notified. and AlarmPoint Server 4. or phone messages. Be sure to install the AlarmPoint client on the system where the BMC ProactiveNet cell server resides.Event actions: managing BMC ProactiveNet events in external environments BMC ProactiveNet 8. You can create an event rule for AlarmPoint. you must configure the installDirectory / custom/conf/pronet. The notification policy forwards the event to the AlarmPoint client. The data-only implementation is unidirectional. See the Remote Actions/Diagnostics chapter of the BMC ProactiveNet Administrator Guide .0 is compatible with AlarmPoint for BMC Event and Impact Management (Advanced Edition). You can find the compatible AlarmPoint products at http://www. Chapter 4 Event administration 217 . For the data-only implementation. The notifications are then displayed in the Event List.1. you use the Run Command on Proactive Server action to define the action. These actions are processed by the BMC ProactiveNet cell server.

2 Choose the gateway entry from the IBRSD Gateway list. if the Create Incident in BMC Remedy Service Desk option is selected in the Add Event Rule (Page 3/3): Action Information for Event Rule screen. — To edit an existing RSD Configuration.5. Ensure that Integration to BMC Remedy Service Desk (IBRSD) is installed to integrate BMC ProactiveNet and BMC Remedy Service Desk 7.1. BMC ProactiveNet events based on Abnormalities also create AR System Requests. The description for the ARS Requests created out of BMC ProactiveNet events based on Abnormalities and Predictive events are prefixed with the word Abnormal: and Predictive: respectively to distinguish it from the other BMC ProactiveNet events. The severity of predictive events is changed to Warning before the AR System Request is changed. if an event notification fails. Managing BMC ProactiveNet events in the Remedy environment An event generated in BMC ProactiveNet creates an AR system request in BMC Remedy Service Desk.Event actions: managing BMC ProactiveNet events in external environments In either implementation. To add a new RSD Configuration 1 Click New to display the Add RSD Configuration Details window. click Edit and then click Delete. The Edit RSD Configuration Details window opens. you can enable the debug option of the BMC ProactiveNet server and check for exception errors. the status of the AR system request gets changed accordingly as per the IBRSD setting. When the event is closed in BMC ProactiveNet. click Edit. 218 BMC ProactiveNet User Guide . — To delete an RSD Configuration.0. Integration configuration for event actions (Remedy Service Desk) ■ Select Create incident in BMC Remedy Service Desk in the Add Event Rule (Page3/3): Action Information for Event Rule window to add/edit an AR System Request: ■ Click the relevant option: — For a new RSD Configuration. The Add RSD Configuration Details window opens. click New. or 7. 7.

and then click Close to return to the Add Event Rule (Page3/3): Action Information for Event Rule window.dir file of the BMC ProactiveNet server cell. ■ The added action is displayed under Actions To Perform.dir for the Web Services Server is C:\Program Files \BMC Software\Impact\webServices\mcell. The default path of the mcell. Specify all the actions for the event rule.dir for the BMC ProactiveNet server is C:\Program Files\ProactiveNet\pw\server \etc. click Add . 4 After specifying the action for the event rule. BMC ProactiveNet returns to the Event Rule Administration screen. 3 Click Done. To remove a selected action 1 Select the action from Actions To Perform.dir file of the BMC ProactiveNet implementation that points to the IBRSD server. 3 Click Done. Note Chapter 4 Event administration 219 .Event actions: managing BMC ProactiveNet events in external environments The gateway entries are populated from the mcell. cell cellName mchostIPaddress:3115 The default path of the mcell. The updated event rule list is displayed. For upgrade users of the BMC Remedy Service Desk integration You can upgrade your previous integration with BMC Remedy Service Desk by following these steps: To upgrade the integration with BMC Remedy Service Desk 1 Manually copy the IBRSD entries of the mcell.dir of the BMC Impact Integration Web Services Server that is used by the BMC Remedy Service Desk installation to the mcell. Note By default the Event Class is Event and Status is Active. 2 Click Remove.

its severity level is set to warning.ibrsd mchostIPaddress:3115 gatewayName 3 Restart the BMC ProactiveNet server using the following command: pw sys start In the integration with BMC Remedy Service Desk. before an abnormality event is sent to the target application.ibrsd. gateway. Note 220 BMC ProactiveNet User Guide .Event actions: managing BMC ProactiveNet events in external environments 2 Rename the cell entry to the gateway entry gateway.

■ The PN Event Sender reads the configuration file PN-ARS-Integration. ■ IBRSD communicates with the IBRSD module installed in the AR Server and creates an AR System Request on the AR Server. When the event is closed in BMC ProactiveNet. Figure 8: BMC ProactiveNet integration with AR system using IBRSD ■ When an event is generated in BMC ProactiveNet. Chapter 4 Event administration 221 . an AR System Request is created simultaneously.xml (the XML configuration file under the installDirectory/ pw/pronto/conf folder) to determine the cell name pointing to IBRSD. ■ Transforms the event data to proper format and send the event data to IBRSD.Event actions: managing BMC ProactiveNet events in external environments How the BMC ProactiveNet integration works with the AR System The following block diagram explains the BMC ProactiveNet integration with AR System using IBRSD. the status of the AR request is changed in accordance with the IBRSD configuration.

the other details also get updated in the AR System Request. If details. only the status fields get updated. If you change the AR System Intelligent Incident business rule. are sent to AR System. 7. the same ARS Request is updated at the AR System. The event data available at the time of event generation from BMC ProactiveNet. This is the business rule for Intelligent Incidents. or 7.6 Setting up intelligent incident mappings Navigate to Quick Links on the Home Page of the BMC Remedy User application. If the event Id is the same for multiple BMC ProactiveNet events. the workflow at the AR System needs to be changed. Related topics: External dependency on page 222 Setting up intelligent incident mappings on page 222 Limitation on page 224 Troubleshooting on page 224 High level flow chart on page 225 Event slots to AR system form field mapping on page 226 Note External dependency ■ BMC Remedy Service Desk 7. In this case.1.0. 222 BMC ProactiveNet User Guide .Event actions: managing BMC ProactiveNet events in external environments Related topics: Configuration file details on page 222 Configuration file details The configuration file details are as follows: ■ IBRSD Gateway Name ■ AR System Field Default Values (if required) ■ BMC ProactiveNet Event Details ■ BMC ProactiveNet Event Fields to IBRSD Event Slot Mapping Create individual ARS requests for each unique BMC ProactiveNet event.5. 7. other than the status fields are to get updated in the AR System Request.

Figure 9: BMC Remedy Home Page Figure 10: Custom configuration tab 2 Expand Integration for BMC Remedy Service Desk. 3 Expand Integration Configuration.Event actions: managing BMC ProactiveNet events in external environments To set up intelligent incident mappings 1 Click the Custom Configuration tab. Chapter 4 Event administration 223 .

Limitation ■ Once an AR System Request is closed in the Incident Management form. Mention the status of the request when the event is closed. map it to the appropriate priority in the AR System. Map each income severity to the appropriate severity in the AR system. Similarly for each incoming priority.Event actions: managing BMC ProactiveNet events in external environments 4 Select BMC Event Manager Incident Integration Setup. Figure 11: Incident integration setup 5 Add the contact information. Troubleshooting Here are some points to be noted while setting up: ■ Once the AR System with Remedy Service Desk and ITSM Patch-4 are installed. 224 BMC ProactiveNet User Guide . use the AR System User Interface to check whether the Incident Management and Problem Management Applications are enabled. it cannot be re-opened.

use the msend CLI to test the msend -a EVENT -r CRITICAL -m "TestMessage" -b "mc_priority=PRIORITY_1. ■ Check whether the data exists in the Staging Form. Chapter 4 Event administration 225 . Send one event data point to IBRSD. the event data will be logged into the UnsentEvent log of the IBRSD. If the data exists in the Staging Form and not in Incident Form. ■ Check the UnsentEvent log file in the IBRSD server. Use the following syntax: This should create an entry in the Incident form. then the data point would have violated some of the workflow rules.mc_ueid=UID_001.Event actions: managing BMC ProactiveNet events in external environments ■ Once the IBRSD configuration is complete. If there is a failure in sending the data.status=OPEN” –n @<IBRSDServer>:<IBRSDPort>#mc installation. High level flow chart This flow chart explains the functions of a PN Event Sender module.

Event actions: managing BMC ProactiveNet events in external environments The following flow chart explains the workflow in the AR System. ■ Change the event slot names to AR System Form Field mapping. Note 226 BMC ProactiveNet User Guide .map file if you have installed the IBRSD component that is part of the ProactiveNet server 8. You do not need to edit the DefaultMapping.map in the IBRSD server conf directory. ■ Use BEMUseCase maps for the changes. Event slots to AR system form field mapping To map the Event Slots to AR System: ■ Edit DefaultMapping. The following event slot names are used to create the event data.0 installation package.

When the event is created and if the Reconciliation ID is not blank. Reconciliation ID is not sent. Submitter Notes Notes Notes Notes Notes Notes Notes Notes Notes Notes Notes Notes Notes mc_parameter mc_parameter_value mc_parameter_unit Notes Notes Notes Chapter 4 Event administration 227 .CLOSED] BMC ProactiveNet DeviceInfo eventURL PNServerIP eventTime eventRule MonitorInstance PNServerName MonitorType EventScore HasDD eventAckStatus eventAckMessage BPMReconId. Hence CRITICAL will be mapped to PRIORITY_1. WARNING] Status [OPEN. send it. Host level Reconciliation ID stored in PN. When the event is modified. Otherwise send the device level Reconciliation ID. eventAttribute AttrValueCausedEvent AttrValueUnit severity status submitter device_info event_url pn_server_ip event_time event_rule monitor_instance pn_server_name monitor_type pn_event_score pn_event_has_diagnostics pn_event_ack_status pn_event_ack_message mc_smc_id Event_Severity Status_Event Event_Requester.Event actions: managing BMC ProactiveNet events in external environments Table 57: Event slot details Event Slot Name mc_ueid msg mc_priority AR System Form Field Mc_ueid Event_Message Event_Priority Event Data eventId eventDescription In the BMC ProactiveNet event there is no concept of priority.MAJOR. MAJOR will be mapped to PRIORITY_2. and Minor will be mapped to PRIORITY_3 Severity [CRITICAL. If the instance level Reconciliation ID is not blank. if the Reconciliation ID is blank. send that. don’t send it. In the case of BPM Adapter Monitor the Reconciliation ID is at the instance level.MINOR.

mc_smc_alias.mc_parameter. The Event Slot to AR System field mapping is done in the IBRSD DefaultMapping.monit or_type.pn_event_ack_message.monitor_instance.slot.msg Event_Priority=slot.sl ot.event_time.slot.slot.mc_ueid.slot.product_tier2 Product_Categorization_Tier_3=slot. Event_Requester=slot.mc_parameter_unit.slot.map file in the IBRSD installation’s conf directory.pn_serve r_name.event_rule. Follow the same mapping to modify the events.status Mc_ueid=$Format("%s_%s". Short_Description=slot.mc_parameter_value.slot.pn_server_ip).slot.slot. Note The above mapping is for the new events.slot. The BMC ProactiveNet event fields given in the diagram are fields that are available for use and they are case sensitive.product_tier1 Product_Categorization_Tier_2=slot.cell_name Notes=$Format"event Id: %s\nevent Rule: %s\nevent Time: %s\nDevice: %s \nMonitor Type: %s\nMonitor Instance: %s\nevent URL: %s\nPNSever IP: %s \nPNSever Name: %s\nEvent Score: %s\nevent Rule Has DD: %s\nevent Acknowledged: %s\nevent Ack Message: %s\nReconciliationId: %s\nComponent Alias: %s\nevent Attribute: %s\nAttr Value Caused event: %s\nAttr Value Unit: %s\nMoreInfo: \n %s".slot.mc_priority Event_Severity=slot.xml file under the installDirectory /pw/pronto/conf directory in the BMC ProactiveNet server.Event actions: managing BMC ProactiveNet events in external environments Event Slot Name mc_smc_alias AR System Form Field Notes Event Data ComponentAlias The mapping between BMC ProactiveNet event fields and event slots is done in the PN-ARS-Integration.msg $if(slot.slot.device_info.slot.slot.slot.slo t.mc_ueid.more_info).map mapping file located in the conf directory of the IBRSD server.pn_event_has_dd.product_tier3 $endif Event_Message=slot.slot. Ensure that the following code is present in the DefaultMapping.slot.mc_smc_id. The Work Info History list box in the Work Info Tab of BMC Remedy Service Desk’s Incident Management form captures the following details when a BMC ProactiveNet event is generated and if the AR System Request is created: Note 228 BMC ProactiveNet User Guide .slot.severity Status_Event=slot.0" Submitter=slot.slot.submitter z1D_CellName=slot.event_url.pn_server_ip.slot.pn_event_ack_status.pn_event_score.submitter Event_Type="NEW" Keyword="BEM" z1D_FirstName="BEM" z1D_LastName="User" Application_Version="ITSM 7.product_tier1 != "") Product_Categorization_Tier_1=slot.

if the Send event to BMC Event Manager option is selected in the Add event Rule (Page3/3): Action Information for Event Rule screen. the ARS Request will have the severity of the latest event. The severity of predictive events is changed to WARNING before the system creates the BEM Event. Note The Send event to BMC Event Manager option is addressed to BMC ProactiveNet upgrade users who are sending events to a BMC Event Manager instance and who wish to retain their current settings. New users should use the BMC ProactiveNet event processing mechanisms. the corresponding BEM Event also gets closed. Note Managing BMC ProactiveNet events in the BEM environment An event generated in BMC ProactiveNet creates an event in BMC Event Manager. When the event is closed in BMC ProactiveNet. if multiple events are coming with the same mc_ueid. BMC ProactiveNet events based on Abnormalities also create BEM events. The description for the BEM Events created out of BMC ProactiveNet events based on Abnormalities and Predictive events are prefixed with the word Abnormal: and Predictive: respectively to distinguish it from the other BMC ProactiveNet events. Ensure that BMC Impact Solution is installed to integrate BMC ProactiveNet and BMC Event Manager.Event actions: managing BMC ProactiveNet events in external environments ■ Priority ■ Severity ■ Status ■ Source ■ Time and Date The Work Info History list captures the above details for all the events. When multiple events are generated with the same event id (correlated events) but different severities. Integration configuration for event actions (BEM) ■ Select Send Event to BMC Event Manager in the Add Event Rule (Page 3/3): Action Information for Event Rule screen to add/edit a BEM Event: ■ Click the relevant option: Chapter 4 Event administration 229 .

Specify all the actions for the event rule. Ensure that the cell you do select does not contain a propagation rule or policy that propagates events back to the local ProactiveNet server cell. WARNING Do not select the local ProactiveNet server cell. The updated event rule list is displayed. By default the Event Class is PROACTIVE_INTELLIGENT_EVENT and the status is ACTIVE. 1 Select the action from Actions To Perform. click Delete. To add new BEM configuration details 1 Click New to open the Add BEM Configuration Details window. To remove a selected action. click Edit. 2 Select the BEM cell from the BEM Cell name list. 3 Click Done. 230 BMC ProactiveNet User Guide . The Add BEM Configuration Details window opens. Selecting the local ProactiveNet server cell or selecting a cell that propagates events back to the local ProactiveNet server cell can result in unpredictable application behavior. BMC ProactiveNet returns to the Event Rule Administration screen. The Edit Configuration Details window opens. 4 After specifying the action for the event rule. click Add. 2 Click Remove. 3 Click Done. ■ The cell name entries are populated from the mcell. The added action is displayed under Actions To Perform.dir file of the ProactiveNet implementation that points to the BEM cell. and then click Close to return to the Add Event Rule (Page 3/3): Action Information for Event Rule window. click New. — To edit an existing BEM event.Event actions: managing BMC ProactiveNet events in external environments — For a new BEM event. — To delete an BEM event.

dir of the BMC Impact Integration Web Services Server that is used by the BMC Event Management installation to the mcell. How the BMC ProactiveNet integration works with the BEM environment The following block diagram explains the BMC ProactiveNet integration with BEM Event. 2 Restart the BMC ProactiveNet server using the following command: pw sys start Note Note In the integration with BMC Event Management.Event actions: managing BMC ProactiveNet events in external environments For upgrade users of the BMC Event Management integration You can upgrade a previous BMC Event Management integration by following these steps: To upgrade a previous BMC Event Management integration 1 Manually copy the BEM entries of the mcell. The default path of the mcell.dir for the BMC ProactiveNet server is C:\Program Files\ProactiveNet\pw\server \etc. Chapter 4 Event administration 231 . cell cellName mchostIPaddress:1828 The default path of the mcell.dir file of the BMC ProactiveNet server cell.dir for the Web Services Server is C:\Program Files \BMC Software\Impact\webServices\mcell. before an abnormality event is sent to the target application. its severity level is set to warning.

■ The PN Event Sender reads the configuration file PN-BEM-Integration. Related topics: Configuration file details on page 232 Configuration file details The configuration file details are as follows: ■ Cell Name 232 BMC ProactiveNet User Guide . a BEM Event is created simultaneously. ■ Transforms the event data to proper format and sends the event data to BEM.xml (the XML configuration file placed in the installDirectory /pw/pronto/conf) to determine the cell name pointing to BEM. When the event is closed in BMC ProactiveNet.Event actions: managing BMC ProactiveNet events in external environments ■ When an event is generated in BMC ProactiveNet. the corresponding BEM Event is also closed.

Chapter 4 Event administration 233 . For information on supported versions of BMC Impact Solutions.Event actions: managing BMC ProactiveNet events in external environments ■ BEM Event Default Values (if required) ■ BMC ProactiveNet Event Details ■ BMC ProactiveNet Event Fields to BEM Event Slot Mapping Related topics: High level flow chart on page 233 BMC ProactiveNet – BEM Event mapping on page 235 External dependency Install a supported version of BMC Impact Solutions. see the BMC ProactiveNet Release Notes . High level flow chart This flow chart explains the functions of a BEM Integrator module.

234 BMC ProactiveNet User Guide .Event actions: managing BMC ProactiveNet events in external environments The following flow chart explains the workflow at the BEM System.

xml file. This is required if multiple PN servers are sending events to the same BEM String description of the event AlarmDescription msg Chapter 4 Event administration 235 . make the entries in the PN-BEM-Integration.xml file using the following mapping details: Table 58: Mapping details PN Event Data AlarmId_PNServer IP Event Slot mc_ueid Comments Combination of eventId & PN Server IP. To create an event in BEM. This is located in the installDirectory /pw/ pronto/conf directory in the BMC ProactiveNet server.Event actions: managing BMC ProactiveNet events in external environments BMC ProactiveNet – BEM Event mapping The mapping between BMC ProactiveNet event Fields and CEM complaint Slots is done in PN-BEM-Integration.

down. priority describes the business urgency (high. low. WARNING] [OPEN. in between). MAJOR will be mapped to PRIORITY_2.MAJOR. We send the eventURL to the mc_tool_uri slot. The pn_event_ack_message is defined as a slot in the event class for the PN Events AlarmAckMessage pn_event_ack_message 236 BMC ProactiveNet User Guide . somewhere in between).1 release of BMC Impact Solutions. Severity determines how bad the technical problem is (device is up. The value is calculated instead. and so on) can usually not assess priority. Data collection layer (PN. and Minor will be mapped to PRIORITY_3. Something that is “down” may have low urgency (for example if it happens on a Sunday). Hence CRITICAL will be mapped to PRIORITY_1.Event actions: managing BMC ProactiveNet events in external environments PN Event Data no equivalent mapping field. This is required if multiple PN servers are sending events to BEM event Rule More Info Monitor Instance Name Monitor Type The pn_event_score is defined as a slot in the event class for the PN Events Severity AlarmStatus Submitter DeviceIP PNServerIP PNServerIP PNServerName DeviceName AlarmURL Severity Status mc_origin mc_host_address adapter_host mc_tool_address mc_tool mc_host mc_tool_uri AlarmId_PNServer IP mc_tool_key AlarmRule MoreInfo MonitorInstance MonitorType EventScore HasDD AlarmAckStatus mc_tool_rule mc_tool_suggestion mc_object mc_object_class pn_event_score pn_event_has_diagnostics The pn_event_has_dd is defined as a slot in the event class for the PN Events pn_event_ack_status event Acknowledgement status. [CRITICAL. The pn_event_ack_status is defined as a slot in the event class for the PN Events event Acknowledgement message.MINOR. CLOSED] BMC ProactiveNet Device IP Address For backward compatibility PN Server IP Address PN Server Name Device Name Cross launch is implemented in the BMC IX Console for the field mc_tool_uri in the post 7. Event Slot mc_priority Comments In the BMC ProactiveNet event there is no concept of priority. PATROL. Combination of eventId & PN Server IP.

The attribute that caused the event.06. When multiple events are generated with the same event id (correlated events) but different severities. BMC ProactiveNet only supports unidirectional integration with RBA 3.Event actions: managing BMC ProactiveNet events in external environments PN Event Data BPMReconId Event Slot mc_smc_id Comments Host level Reconciliation ID stored in PN. All subsequent references to RBA in the User Guide would collectively mean BMC Run Book Automation and BMC Atrium Orchestrator. In the case of BPM Adapter Monitor the Reconciliation ID is at the instance level. Please refer to the appropriate version of the BMC Atrium Orchestrator Development Studio User Guide for developing RBA Rules and RBA Workflow. Note Chapter 4 Event administration 237 . don’t send it. send it. Otherwise send the device level Reconciliation ID. In the case of external events this will not be present The attribute value that caused the event The unit of the attribute value ComponentAlias coming from the BMC TM ART adapter monitor. send that. the BEM Event will have the severity of the latest event.5. and after the successful rule validation an appropriate RBA Workflow is triggered depending on the specified logic. Managing BMC ProactiveNet events BMC Atrium Orchestrator (formerly known as BMC Run Book Automation) When a BMC ProactiveNet event is generated the event action Send Event to BMC Atrium Orchestrator sends event data to the BMC Run Book Automation environment. When the event is created and if the Reconciliation ID is not blank. AlarmAttribute mc_parameter AttrValueCausedEven mc_parameter_value t AttrValueUnit ComponentAlias mc_parameter_unit mc_smc_alias Note The History tab of the event in the BMC Impact Explorer captures only Last Modifier Cell and the last update time. When the event is modified. If the instance level Reconciliation ID is not blank. BMC ProactiveNet also supports unidirectional integration with BMC Atrium Orchestrator 7.00.0. if the Reconciliation ID is blank. The active RBA Rules processes the event or event data. Reconciliation ID is not sent.

3 Click Done. click Delete. ■ Click the relevant option: — For a new BMC Run Book Automation event.dir file of the BMC ProactiveNet implementation that points to the BMC Atrium Orchestrator server. Note To remove a selected action 1 Select the action from Actions To Perform. The added action is displayed under Actions To Perform. — To edit an existing AO event. The Add AO Configuration Details window opens.Event actions: managing BMC ProactiveNet events in external environments Integration configuration for event actions (BMC Atrium Orchestrator) ■ Select Send Event to BMC Atrium Orchestrator in the Add Event Rule (Page3/3): Action Information for Event Rule screen to add or edit a BMC Run Book Automation event. The IMCOMM entries pointing to the BEM-RBA gateways are populated from the mcell. and then click Close to return to the Add Event Rule (Page3/3): Action Information for Event Rule window. window opens. 2 Click Remove. click New. 4 After specifying the action for the event rule. 3 Click Done. To add new AO configuration details 1 Click New to open the Add AO Configuration Details window. Specify all the actions for the event rule. 238 BMC ProactiveNet User Guide . 2 Select the IMCOMM gateway from the AO Gateway Cell list. click Edit. The Edit Configuration Details — To delete an AO event. click Add. By default the Event Class is PROACTIVE_INTELLIGENT_EVENT and the status is ACTIVE.

Event actions: managing BMC ProactiveNet events in external environments BMC ProactiveNet returns to the Event Rule Administration screen.dir file of the BMC ProactiveNet server and by updating existing event rules that apply to the BMC Atrium Orchestrator integration. The updated event rule list is displayed. For upgrade users of the BMC Atrium Orchestrator integration You can upgrade your previous integration with BMC Atrium Orchestrator by following upgrading the mcell.imcomm to the mcell.imcomm ao mchostIPaddress:1859 2 Restart the BMC ProactiveNet server using the following command: pw sys start 3 Next. 7 Select previously existing actions that were used by the BMC Atrium Orchestrator installation. and click Edit to open the Edit Event Rule wizard. Chapter 4 Event administration 239 .dir file from the AO Gateway Name list. and choose Options => Administration => Event Administration => Event Rules => Edit to open the Event Rule Administration page. To update existing event rules that apply to the BMC Atrium Orchestrator integration 1 Open the BMC ProactiveNet Operations Console. and BMC Atrium Orchestrator title. To upgrade BMC Atrium Orchestrator integration 1 Add the gateway entry gateway.dir file of the BMC ProactiveNet server: gateway. you edit existing event rules that apply to the BMC Atrium Orchestrator integration. 6 Click Add next to the Send Event to BMC Atrium Orchestrator list to post the new action to the Actions to Perform list. 3 Go to page 3/3 of the wizard. 4 In the Add AO Configuration Details window. and click New next to the Send Event to BMC Atrium Orchestrator list under the Integration with BMC Remedy Service Desk. and click Remove. choose the gateway entry you’ve added to the mcell. BMC Event Manager. 2 Select the event rule from the list. 5 Click Done to close the Add AO Configuration Details window.

its severity level is set to warning. before an abnormality event is sent to the target application.Event actions: managing BMC ProactiveNet events in external environments 8 Click Done to save your changes and close the wizard. Note 240 BMC ProactiveNet User Guide . In the integration with BMC Atrium Orchestrator.

Event actions: managing BMC ProactiveNet events in external environments How BMC ProactiveNet integration works with BMC Atrium Orchestrator The following block diagram explains BMC ProactiveNet integration with BMC Atrium Orchestrator. Figure 12: How BMC ProactiveNet integrates with BMC Atrium Orchestrator ■ The BEM-RBA monitor adapter receives event or event data from BMC ProactiveNet ■ The BEM-RBA monitor adapter formats the input and sends it to active RBA rules ■ The event is evaluated against active RBA Rules. the appropriate RBA Workflow is triggered A list of integration features follows: Chapter 4 Event administration 241 . If the rule validation succeeds.

RBA events are created when the BMC ProactiveNet event is opened. Mapping BMC ProactiveNet event fields for RBA Event slots Table 59: Mapping details PN Event Data AlarmId_PNServer IP Event Slot mc_ueid Comments The following table lists Product Short event fields for the Event Slots of RBA events. Something that is “down” may have low urgency (for example if it happens on a Sunday). (CRITICAL. Hence CRITICAL is mapped to PRIORITY_1. or in between).Event actions: managing BMC ProactiveNet events in external environments ■ Creating RBA events . Severity determines how bad the technical problem is (device is up. MAJOR is mapped to PRIORITY_2. etc. down. Msg mc_priority Severity AlarmStatus Submitter DeviceIP PNServerIP PNServerIP PNServerName DeviceName Severity Status mc_origin mc_host_address adapter_host mc_tool_address mc_tool mc_host 242 BMC ProactiveNet User Guide . and the severity of the predictive event is changed to warning an RBA event is created. The BMC ProactiveNet abnormality event description is prefixed with the word Abnormal to distinguish it from the other BMC ProactiveNet events before the RBA event is created. The value is calculated instead. RBA Events can be created for BMC ProactiveNet abnormalities as well.MAJOR. low. For DHCP enabled systems. acknowledged. PATROL. string description of the event In BMC ProactiveNet event there is no concept of priority. RBA events can be created for BMC ProactiveNet predictive events. Data collection layer (PN. it is a combination of event Id and host name of the PN Server. The predictive event description is prefixed with the word Predictive to distinguish it from the other BMC ProactiveNet events. or closed based on the action set for the event. Combination of event Id & PN Server IP is required when multiple PN servers are sending events to the same RBA.) can usually not assess priority. priority describes the business urgency (high. or in between).MINOR. WARNING) (OPEN. and Minor is be mapped to PRIORITY_3. CLOSED) BMC ProactiveNet Device IP Address For backward compatibility PN Server IP Address PN Server Name Device Name AlarmDescription no equivalent mapping field.

Otherwise send the device level Reconciliation ID. This is required when multiple PN servers send events to RBA. pn_event_ack_status pn_event_ack_message Event Acknowledgement status Event Acknowledgement message The pn_event_ack_message is defined as a slot in the event class for the PN Events. Attribute value that caused the event Unit of the attribute value ComponentAlias from the BMC TM ART adapter monitor External setup For external setup the following installation and configuration is required: ■ RBA or Atrium Orchestrator must be installed. Combination of eventId and PN Server IP. Event Rule More Information Monitor Instance Name Monitor type The pn_event_score is defined as a slot in the event class for the PN Events. Sends the eventURL to the mc_tool_uri slot. send it. ■ Configure the BEM-RBA monitor adapter used for the BEM-RBA integration to accept events from BMC ProactiveNet.1 release of BMC Impact Solutions.Event actions: managing BMC ProactiveNet events in external environments PN Event Data AlarmURL Event Slot mc_tool_uri Comments Cross launch is implemented in the BMC IX Console for the field mc_tool_uri in the post 7. AlarmAttribute AttrValueCausedEvent AttrValueUnit ComponentAlias mc_parameter mc_parameter_value mc_parameter_unit mc_smc_alias Attribute that causes the event It is not present for external events. AlarmId_PNServer IP mc_tool_key AlarmRule MoreInfo MonitorInstance MonitorType EventScore HasDD AlarmAckStatus AlarmAckMessage mc_tool_rule mc_tool_suggestion mc_object mc_object_class pn_event_score pn_event_has_diagnostics The pn_event_has_diagnostics is defined as a slot in the event class for the PN Events. If the instance level Reconciliation ID is not blank. BPMReconId mc_smc_id Host level Reconciliation ID stored in PN In the case of BPM Adapter Monitor the Reconciliation ID is at the instance level. See the Release Notes for the supported versions of these products. Chapter 4 Event administration 243 .

Each threshold with Outside Baseline enabled activates when the data exceeds the specified baseline and absolute threshold. The event suppression rule defines a relationship between the application and host system. this causes the application to be unavailable. clear the Enable Intelligent Events check box to map absolute threshold to the baselines. 3 In the Event Administration area. For more information. The outside baseline column can be set to Not Enabled. or Weekly Baseline. see “Setting event thresholds” on page 184. Note 244 BMC ProactiveNet User Guide . For example. To configure intelligent events 1 Click Options on the top right of the BMC ProactiveNet Operations console. see “Defining Intelligent Event Suppression relationships” on page 398. This creates a new outside baseline column in the Event threshold administration screen. However. If the system is offline. but an alert is sent only for system availability. availability events related to application A are suppressed by the availability events on system B. The Event Reduction screen is displayed. 1 On Event Reduction screen. Auto.Reducing events Reducing events BMC ProactiveNet allows you to limit the flow of events. For full information on setting thresholds. clear the Enable Event suppression check box to disable the suppression rules. 2 Choose the Administration tab. BMC ProactiveNet does not send an alert for the application availability. Hourly Baseline. Daily Baseline. 4 On the Event Reduction screen. click the Edit link to the right of Intelligent Event Reduction. 5 Click Apply. because the relationship is defined. To suppress events The event suppression option is available only if you are upgrading to the current version of BMC ProactiveNet and you used the relationship administration or event suppression functionality in a previous version of the product.

Note By default. For example. However. To enable or disable non KPI metrics 1 On Event Reduction screen. Upgrade users can enter the new variables that they need directly in the wizard. this check box maintains the same non-KPI status that it had before the upgrade. 2 Click Apply. for event text customization. They are: ■ $EVENTID ■ $MC_LONG_MSG ■ $INSTANCE_NAME ■ $ABNORMALITY When applied to external events. if the check box was enabled before the upgrade. clear the Enable Abnormality Detection and Baseline Generation for non-KPI metrics check box to stop further baseline projection and abnormality detection for non-KPI attributes. and $MC_PRIORITY. $MC_HOST. for upgrade customers. See the table below for a complete list.0 provides additional out-of-the-box variables. Upgrade users cannot immediately select these additional variables. these variables will have blank values.Customizing event text 2 Click Configure Event Suppression link. it remains enabled. the Enable Abnormality Detection and Baseline Generation for non-KPI metrics check box is disabled. Chapter 4 Event administration 245 . They have to add them manually. Certain event text customization variables are only available for ProactiveNet intelligent events. For upgrade users BMC ProactiveNet 8. for fresh installations. the Relationship Administrator screen opens and you can define the relationships. such as $Status. Customizing event text Event text customization enables you to insert event text for all email alerts.

2 On the Administration tab.Customizing event text To customize event text 1 Click the Options tab at the top right of the BMC ProactiveNet Operations Console. Table 60: Variables for customizing event text Variable ($VAR) $ABNORMALITY $ACK $ACK_MSG 3. customize the subject and body of the Email Alerts. 3 On the Global Event Text Customization screen. You can choose from among the following variables listed in in the table below.a Description abnormality used in pinpointing acknowledgement status Acknowledgement message name of event rule that applies to this event attribute name such as “availability” name of the device under which the monitor instance is shown Description about the device under which the monitor instance is shown BMC ProactiveNet Intelligent Event ID First Time Threshold was exceeded in ASCII Full path to the Monitor Name of the Monitor instance Last value when Event was generated Last Time data was collected in UTC seconds Last Time data was collected in ASCII Fully-qualified name of the host on which the problem occurred Network address of the host on which the problem occurred Location at which the managed object resides More info of a BMC ProactiveNet Intelligent Event List of free text annotations added to the event Subcomponent of the host to which the event is related Identifies the class of an object $ALARMRULE_NAME $ATTR_NAME $DEVICE $DEVICE_DESCR $EVENTID $FTIME_ASC $FULL_PATH $INSTANCE_NAME $LAST $LTIME_UTC $LTIME_ASC $MC_HOST $MC_HOST_ADDRESS $MC_LOCATION $MC_LONG_MSG $MC_NOTES $MC_OBJECT $MC_OBJECT_CLASS 246 BMC ProactiveNet User Guide . choose Event Text Customization Edit link.

4 Select Include MoreInfo in E-Mail Body to receive the detailed information in an email. encoded for safe use in URLs a ACK_MSG retains the latest operations message. Name of the Monitor instance. 5 Click Apply. Network Ping Text description of the event Severity of the event Status of the event The IPAddress of Remote Agent where Monitor Instance is actually created Event Time formatted as "MM dd HH:mm" Units in which Threshold value is measured Class name of the event.Integrating BMC ProactiveNet with Service Level Management Variable ($VAR) $MC_ORIGIN $MC_ORIGIN_CLASS $MC_OWNER $MC_PRIORITY $MC_TOOL $MC_TOOL_CLASS $MC_UEID $MO_TYPE $MSG $SEVERITY $STATUS $SCRIP $TIME $UNITS $CLASS $URL_INSTANCE_NAME Description Event management systems that is closest to the source of the event as possible Identifies the event management system type Current user assigned to the event Priority of an event with respect to their impact on the SIM model Represents whether the event is coming from within a mc_tool_class value User-defined categorization of the tool reporting the event Universal identifier of the event Managed Object Type such as.Performance data collected by BMC ProactiveNet is exposed in Service Level Management to be utilized in Performance Based Service Targets. Managing BMC ProactiveNet with Service Level Management (SLM) . The metrics can be from BMC ProactiveNet Monitors that are packaged with the product as well as from adapters Chapter 4 Event administration 247 . Integrating BMC ProactiveNet with Service Level Management This section provides information on integration of BMC ProactiveNet with Service Level Management.

BMC ProactiveNet only supports unidirectional integration with SLM. For more information on using the BMC ProactiveNet integration with SLM. Probable cause analysis from BMC ProactiveNet is shown in SLM as a link so that an impacted SVT can be linked to the reason behind the impact.Integrating BMC ProactiveNet with Service Level Management to other enterprise performance monitoring solutions. see the BMC Service Level Management User’s Guide and the BMC Service Level Management Configuration Guide. Note 248 BMC ProactiveNet User Guide .

You can choose the type of graphing format that works best for you. but do not allow you to chart thresholds or indicators. such as Baseline. Peak. and so on. ■ create graphs for multiple monitors showing a single attribute but view the statistics from multiple sites. see Creating an individual/multiple monitor graphs on page 270. you can select a combination of monitors and attributes. see Creating an individual/multiple monitor graphs on page 270. Customizing graphs helps you to: ■ choose the type of graphing format that works best for you. Click the Custom Graphs icon in the Views & Graphs drawer in the navigation pane to choose from the following options before creating your graph: ■ Line Graph ■ Area Graph ■ X-Y Graph Chapter 5 Customizing graphs 249 . and correlate data effectively. ■ create graphs that show data from an individual monitor type or multiple attributes.5 Customizing graphs Creating custom graphs The Custom Graphs feature is used to generate individual and multiple graphs based on resources monitored by BMC ProactiveNet. Multiple data type graphs enable you to compare data across sites. as they only relate to a single attribute. Using this feature. This feature gives you more control over information than the Show Graph option on the Tools menu. For more information. For more information. Custom Graphs that focus on an individual monitor enable you to chart thresholds and other indicators.

This problem is being addressed. ■ No more than two measurement types can be displayed on a graph.0 with updates Q321232 and Q323759. ■ However. then all four appear in the graph because Y1 or Y2 allows a graph to have two likemeasurements each. ■ When choosing any Indicator.Creating custom graphs ■ Top N Graph ■ Pie Graph ■ Dial Gauge Graph Related Topics Limitations on page 250 Creating a line or area graph on page 251 Creating a x-y graph on page 256 Creating a Top N graph on page 257 Creating a pie graph on page 259 Creating a dial gauge graph on page 261 Limitations When creating graphs. one being measured in units. only one Attribute can be selected because the ■ Currently there is a problem that Custom Graph settings are not preserved when adding graphs. ■ Graph displays NO_DATA image when there are no data available for the total 250 BMC ProactiveNet User Guide . graph period. an error message appears (as shown below) and the graph does not display. if two statistics are measured in percentage and two in units. This problem happens mostly when adding a graph to a view and seems to occur only when using Internet Explorer 6. keep the following limitations in mind: ■ No more than twelve attributes can be displayed on a graph. ■ For example. and the other being measured in time. Indicator cannot relate to more than one measurement. if you have three statistics. one being measured in percentage.

The list lets you choose from 1 hour up to 3 months. 8 Select appropriate values in the Filter Area. For an Individual Graph. or Area Graph option graph. 6 Click Next to open the Monitor Instance area. Choosing a filter limits your graph choices to the selected group and provides a means of organizing your data. select graph options for the graphs. To show the parent instance for the selected monitor instance on page 255 and To show the child instances for the selected monitor instance on page 255 To create a line or area graph 1 In the navigation pane in the Operations Console. The Custom Graph screen is displayed. 5 Select a Monitor Type. Select the desired group. Choosing No Filter lets you generate a graph from all resources in the system. To view parent and child instances for the selected monitor instance see. 7 Select the resource instances to monitor. and click Apply. However.Creating custom graphs Creating a line or area graph Line graphs are the most common type of graphs that plot linear relationships. and indicators are not applicable to Area Graphs. 2 In the Views & Graphs drawer. In the Custom Graphs screen. click Views & Graphs. ■ Show Graph for the last .Choose the amount of time you want to show on the . choose more than one Monitor Type. select the Line Graph . For Multiple Monitor Graphs. they can plot only single instance and single attribute selections. click the Custom Graphs icon 3 In the Custom Graphs screen. 4 Select a Group Filter. Area graphs are specialized line graphs. choose only one Monitor Type. Chapter 5 Customizing graphs 251 . regardless of whether they are in a group or not. A list of resource instances available under the Monitor Type you selected is displayed.

The statistics selections (attributes) vary based on the monitored entity. Choose the attributes you want to graph for each instance. see the BMC ProactiveNet Monitor Guide. such as the last four hours. Daily Baseline. Weekly Baseline. Baseline High represents the point at which 95% of the weighted average of the historical values fall below this value for that hour. You can select device or application-dependent elements for viewing. These values can be used only if multiple attributes have not been selected. — Hourly Baseline. ■ Indicators provide options for dynamically changing the charting of data. or week fall above this line.Creating custom graphs ■ Time Range . or hour to compare measurements.Time Range option allows the Start and End Time selections to reflect either a particular day and hour or a particular duration of time. day. Figure 13: Attributes Area 10 Select appropriate options in the Indicators area. For more information on attribute statistics and their function. Baseline indicators 252 BMC ProactiveNet User Guide . You can change the time and date when you want to view resource data for the previous day. The attributes available vary depending on the monitor chosen. When choosing any indicator. or week. Thresholds and a Config attribute may also be graphed. # and ms). 9 Select appropriate options in the Attributes area. or Hourly & Daily Baseline: There are two baselines: Baseline High and Baseline Low. You can chart up to 12 attributes per graph. Baseline Low represents the point at which 90% of the weighted average of historical values for that hour. however you are limited to 2 units of measure (that is. day. The Attributes Area lets you dynamically change statistical data displayed in the graph you are viewing. week. A colored box around an attribute indicates there is at least one open event of the severity indicated by the color of the box. only one statistic (attribute) is viewable at a time because the Indicator cannot relate to more than one measurement.

— Minor. threshold. — Hourly Min: Lowest values of data found for the specified graph period. The baseline indicator is recalibrated for each hourly point per week.Creating custom graphs always use the current week as baseline data. Critical Absolute Thresholds: If thresholds have been set for — Minor Signature Threshold: Composite values of signature minor — Major Signature Threshold: Composite values of signature major threshold. Similarly. and applied PAD factor. the shading may use a color different from that shown in the legend. There will be two different icons for open and closed intelligent events. same will be displayed as an icon. These indicators show you what the event settings are relative to the performance of the data you are viewing. — Critical Signature Threshold: Composite values of signature critical threshold. a few data points may appear inside the shaded downtime. same will be displayed as an icon. — Abnormality Threshold: Composite values of abnormality threshold. and weekly baseline values. Chapter 5 Customizing graphs 253 . in case of overlapping scheduled downtime. Major. the graph will show the data points already collected. — Show Abnormality: If there are any events on the selected attributes and for — Show External Events: If there are any events raised by change entry. SNMP trap. baseline. baseline associated to threshold. the same will be displayed as an icon. Peak indicator can be selected only when viewing data older than 24 hours. Due to the lag in start of a scheduled downtime event. the selected duration. check boxes are displayed. and applied PAD factor. baseline associated to threshold. the data type you are viewing. — All Baselines: Select this option to show condensed Baseline High and Baseline Low for hourly. In case the Scheduled downtime is created after the start time and before the end time for the day. or external events. Low indicator can be selected only when viewing data older than 24 hours. daily. baseline associated to threshold. — Hourly Max: Highest values of data found for the specified graph period. which is associated to threshold. and applied PAD factor. — Show Intelligent Events: If there are any intelligent events on the selected attributes and for the selected duration. and applied PAD factor. — Scheduled Downtime: To view the scheduled downtime for the monitor on the graph.

— Period Max: Displays highest attribute value on Y-axis. ■ Show each monitor instance on a separate graph . ■ Show each attribute on a separate graph . 13 Select Device Name. ■ Click New to define a new schedule. ■ Show all attributes on a single graph . — Period Min: Displays lowest attribute value on Y-axis. the new attributes will also be added to the same graph. There will be two different icons for open and closed violations. For complete definition of configuration attributes and their functionality. this is not available if Scheduled Downtime indicator is selected. — Config Attributes: These attributes are displayed only if configuration attributes are available on the monitor. Note 11 (optional) Select Schedule from the list. However. each is charted separately on separate graphs.If you chose more than one instance. ■ Click Edit to change the selected schedule. Instance Name or Attribute Name. 14 Select the Data Type to be used. 12 Select an appropriate Graph Option.If you select more than one attribute. see the BMC ProactiveNet Monitor Guide. SLO indicator will only be available for upgrade setups with existing views. each instance is charted on a separate graph. to show the same in the legend. same will be displayed as an icon. 254 BMC ProactiveNet User Guide .All attributes you choose are charted on one graph. If you select some more attributes for the existing graph.Creating custom graphs — Show Violations: If there are any violations on the selected attributes and for the selected duration. ■ Show selected attributes on the corresponding graph – This will preserve the existing graph settings. — Shaded Baseline: Select this option to highlight the area corresponding to the previous baseline selection. — Period Avg: Displays average attribute value of all points of Period Min and Period Max attribute values.

If this instance does not have stats attributes. all graphs will be automatically scaled. To show the child instances for the selected monitor instance 1 Click Show Children in the graph display screen to display a menu of all the child instances of the selected monitor instance. You can change the parameters on the displayed screen. the Show Parent link displays the super parent which has stats attributes. rate data will be used. or use the icons located on the side of the graph to perform other functions. To show the parent instance for the selected monitor instance 1 Click Show Parent in the graph display screen to display the immediate parent instances or the complete hierarchy of parent instances. For more information. A submenu of the child instances is displayed with all the instances that have stats attributes. This option can be selected only if relative time range option is selected from the filter area. You Chapter 5 Customizing graphs 255 . Unless this option is unchecked. The individual or multiple monitor graph displays attributes selected. 15 Select Auto Scale if you need auto-scaling for the graph.Creating custom graphs Note When raw data is selected and if raw data is not available for the entire time range. see Additional information for changing graph display on page 271 for information about these icons. 16 Select Refresh this page for every “n” minutes to refresh the page for the specified time. 17 Click Generate Graph. 2 Select any child instance to create a graph for that instance.

A good example for online stores may be to correlate a business metric (like $s per hour) with Web server performance. The system populates the corresponding monitor instances in the Monitor Instance area. 256 BMC ProactiveNet User Guide . This option displays only the instances that have stats attributes. 6 Click Next. 5 Select Monitor Types. 2 In the Views & Graphs drawer. To create a x-y graph 1 In the navigation pane in the Operations Console.Creating custom graphs can also choose to display the first 50 child instances using the All option. Displaying this graph over a period of time can give you a visual representation of the relationship. Figure 14: Show children Creating a x-y graph X-Y graphs are used to show a correlated view of two metrics. click Views & Graphs. select the X-Y Graph option 4 Select a Group Filter. This graphing is especially useful for related metrics where the dependency is not very clearly known. . This allows IT groups to justify performance improvements on IT hardware or software. are appropriate for X-Y graphs. . where the relationship between two metrics needs to be qualified. All such scenarios. click the Custom Graphs icon 3 In the Custom Graphs screen.

■ Click Edit to change the selected schedule. see Additional information for changing graph display on page 271 for information on these icons. 9 Select appropriate values in the Filter Area. 12 Click Generate Graph(s). You can change the time and date when you want to view resource data for the previous day.Creating custom graphs 7 Select Monitor Instances for X and Y axis. 10 Select attribute for X and Y axis. The number of bars (N) is limited to 15 items per thumbnail. Top N graphs can be created from both the Operations Console and the Administration Console. For more information. Creating a Top N graph Top N Graph is a Pareto bar graph comparing Top N resources. 11 Select the Schedule. Chapter 5 Customizing graphs 257 . BMC ProactiveNet administrator sets the number of bars in the graph. You can change the parameters on Graph Display screen. On the Custom Graphs (X-Y Graph) screen. such as the last four hours. The Pareto bar chart includes resources with the highest average (based on the common measurement). or use the icons located on the side of the graph to perform other functions. You can create either a Top N or a Bottom N graph. ■ Click New to define a new schedule. The list lets you choose from 1 hour up to 3 months. 8 Click Apply. week. ■ Show Graph for the last: Choose the time period you want to show on the graph. Top N graphs compare monitored resources based on a common measurement. ■ Time Range: Time Range option allows the Start and End Time selections to reflect either a particular day and hour or a particular duration of time. or hour to compare measurements.

13 Select the Graph Preference: 2 Dimensional or 3 Dimensional 14 Select the Schedule. . click the Custom Graphs icon. in the Top 10 Interface in Utilization graph. The system populates the corresponding attributes in the lower pane of the screen. 3 In the Custom Graphs screen. 2 In the Views & Graphs drawer. Example. The 3 Dimensional option is available only through the Operations Console. 6 Click Next. Note 258 BMC ProactiveNet User Guide . 11 Specify the duration. 3-dimensional graphs configured through the Operations Console retain the option during editing through the Administration Console. 12 Select the Values to be displayed: Average and High or Average and Low. 9 On the Customs Graphs screen.Creating custom graphs Computation of Top N graphs provides an order to the individual elements within each graph. 5 Select the Monitor Type. However. click Views & Graphs. the number one graph shows the highest average for all interfaces. 15 Click Generate Graph. and select the units (Days or Hours) from the adjacent list. To create a Top N graph 1 In the navigation pane in the Operations Console. 10 Select the number of bars from the list. ■ Click New to define a new schedule. ■ Click Edit to change the selected schedule. You can select only one monitor type here. 7 Select an Attribute. select the Graph Type: Top N or Bottom N. 8 Click Apply. select the Top N Graph option 4 Select the Group Filter.

such as Availability and Utilization. Minor. since only a single instance and attribute selection is plotted. and Critical thresholds. Pie graphs are available only on attributes that have set thresholds. data is reported based on the context of a specific threshold and the break down of data points into 5 different discreet ranges is determined by the threshold value. If the selected threshold does not exist for the attribute to graph.xml. Pie graphs are best suited for getting a high-level overview of the performance of a specific attribute.Creating custom graphs Note The Forward and Backward buttons that help you view graphs corresponding to the succeeding and preceding time ranges. The Description table located below the graph lists data resources of the Top N graph. Chapter 5 Customizing graphs 259 . see Creating a line or area graph on page 251. a NO Data image appears for the pie chart even if there is data in the database. Listing all button Most monitored categories. To view a stacked graph for any of the listed instances 1 Select the check box corresponding to the monitor instance. To modify the statistics. the system prompts you to create or choose another threshold. Clicking List All at the bottom of the Top N table expands the table to list all resources that comprise the selected category. Creating a pie graph Pie graphs show the distribution of points for specified time ranges in individual pie slices and show the distribution of values over time. You can also generate Individual graphs from each of these items. A list of sources used to compile the chart is displayed. Reason being. The Num column provides a link to open the Individual graph for the resource. Different slices are available for Major. Indicators are not applicable to Pie graphs. 2 Click Generate graph. respectively are not available for Top N Graphs. interfaces. contain numerous devices. The List All feature allows you to generate a maximum number of 100 items per page. Description of slices is available in a file for each threshold or SLO at the following path: installDirectory /usr/pw/pronto/conf/ piebuckets. If the threshold is unavailable after graph creation. and services.

and can be added to a view. This kind of graph makes most sense in a view that updates automatically (on a daily basis). will be shown in terms of the unit that it is collected. Note ■ The Forward and Backward buttons that help you view graphs corresponding to the succeeding and preceding time range respectively are not available for Pie Graphs. ■ Although the breakdown is described in terms of % ranges. 7 Select a single Attribute. select Pie Graph option .Creating custom graphs Pie graphs offer a 3D option (available only through the Operations Console). You can change the parameters here. To create a pie graph 1 In the navigation pane in the Operations Console. 6 Click Next. click the Custom Graphs icon. For more information see Additional information for changing graph display on page 271 for information on these icons. and simultaneously see the percentage time where data is falling into each range of values. click Views & Graphs. The system populates the corresponding attributes in the lower pane. You cannot select more than one monitor type here. and click Apply. 4 Select the Group Filter. 8 Make your selections on the Custom Graph screen. 9 Click Generate Graph. values in the graph 260 BMC ProactiveNet User Guide . 2 In the Views & Graphs drawer. or use the icons located on the side of the graph to perform other functions. Pie graphs allow users to see compliance to threshold over a period. 3 In the Custom Graphs screen. 5 Select the Monitor Type.

Creating custom graphs

Creating a dial gauge graph
The Dial Gauge feature enables you to see monitor data graphically in a semicircular gauge with a dynamic needle that fluctuates between the last three data poll values for the specified attribute. Dial Gauges are used to show a real-time feed of the latest data points, which is best suited for very important attributes that require close attention. Views containing Dial Gauges do not update every two minutes like other views. The gauge fluctuates between the last three data poll values, simulating real-time movement. Displayed color zones are as per threshold settings of the specified monitor and show red for critical, orange for major, yellow for minor thresholds, and green for normal behavior. Like other graph options, when you click the thumbnail, the Graph Display screen appears and you can modify the graph as needed. The dial gauge applet polls the server for data according to the predefined poll interval (this can be configured). The gauge displays the current value at the bottom. The needle pauses for a longer duration at the CURRENT data point highlighting the most current value. If there is No Response or No Data from the monitor, the needle points to zero and the system displays an appropriate message at the bottom.

Note
■ This feature requires the Java plug-in. ■ The latest Sun Java VM must be installed on the computer that hosts the BMC

ProactiveNet Server.

To create a dial gauge graph
1 In the navigation pane in the Operations Console, click Views & Graphs. 2 In the Views & Graphs drawer, click the Custom Graphs icon 3 In the Custom Graphs screen, select the Dial Gauge option 4 Select a Group Filter. 5 Select a Monitor Type, and click Next. The system populates the corresponding instances in the lower pane. 6 Select a Monitor Instance, and click Apply. . .

Chapter 5 Customizing graphs 261

Creating custom graphs

7 On the Custom Graphs screen, choose a Single Attribute. 8 Under Display Options, select the display options from the list. You can choose to show either Intelligent Event or SLO threshold zones on the gauge. The dial gauge will display major, minor, critical, or SLO thresholds and show the actual value of the attribute on the gauge. 9 In the Add this Graph to View section (Dial Gauges can only be configured to be seen from a View), specify the Graph Name (name for the Dial Gauge). 10 Choose to create a new view or add the graph to an existing view. 11 Click Add to View. For add to new view selection, specify the View name. For add to existing view selection, the graph is available under the selected View. Any other graph you add to the View will also be visible. From here, you can Add, Edit, and Delete the view by choosing the corresponding buttons.

Note Fast poll frequency is not available for the dial gauge. For below type thresholds, the colors displayed will show in the opposite direction as compared to above thresholds. Although the gauge appears to update every second, it is important to realize that the data feed is still only as quick as the monitor that is polling for the data.
The gauge repeats the last 3 values over and over again until a new data point is received from the monitor, at which point the oldest data point in the gauge is discarded. That is, every time the needle changes position on the Gauge, it does not mean the gauge is displaying a new data point. The latest 3 data values for that attribute, which gives an indication of the latest trend and most up to date values are displayed. The last data value is always shown for the longest period to make it clear that it is the most current value. Adding too many dial gauges to a single view may take a long time to load. The ideal number of dial gauges in a view is 4 or less. However, we suggest that if more gauges must be added to a view, do not exceed 12.

Tip

Limitations of dial gauge graphs
■ Dial Gauges can ONLY be added to a view. ■ Dial Gauge administration can be done only through the Operations Console.

262 BMC ProactiveNet User Guide

Creating custom graphs

■ Dial Gauge display requires a supported version of Java Plug-in. If the plug-in is

not available, then a grey box is displayed. For information on supported Java Plugin versions, see the BMC ProactiveNet Release Notes. example, yahoo response time minor > 100ms and major < 50 ms (this should not happen but in case its configured this way), the below type threshold is ignored. thresholds) i.e. minor < major < critical, if this is not so, then the larger zone overlaps the smaller one. for the first time, the delay is more compared to subsequent accesses.

■ For instance or attribute where thresholds are defined both above and below,

■ It is assumed that thresholds are defined in an increasing order (for above type

■ Initial loading of the applet takes some time. So, when the user accesses the page

■ Due to the increased loading time for applets, too many dial gauges in a single

view have performance implications. It is recommended that a maximum of 12 dial gauges be used in a single view.

■ If threshold is not defined, the system displays a normal gauge (i.e., full green). ■ Tool tip is not displayed for dial gauges on the View page. However, tool tip is

available for the link below.

■ If the difference between threshold values is very less, the user may not be able to

notice the color defined for the zone in the dial gauge.

■ Dial gauge displays zero for negative data values. ■ Very large numbers (11 or more digits) may not appear clearly on the gauge.

However, there is no implication on the accuracy of data displayed below the gauge.

■ For large values, the value may overlap with the zone separator line. ■ For very small values i.e. values below 0.001, the needle will be displayed very

close to zero.

■ If the proxy server used requires authentication, the user is prompted for the user

name and password while accessing a view containing dial gauges. gauge and can be ignored.

■ Exceptions on the plug-in console do not interfere with the functioning of the

The following exceptions may be seen in the plug-in console:
■ On some Internet Explorer versions, if the dash board contains a dial gauge in the

second row, some times the dial gauge in the second row appears as overlapped with the All Events page below. Scrolling the dashboard will clear this.

Chapter 5 Customizing graphs 263

Customizing monitor graphs

■ Exceptions that may be observed in plug-in console:
java.lang.ArrayIndexOutOfBoundsException: 0 >= 0 at java.util.Vector.elementAt(Unknown Source) at com.elegantj.gauges.dial.Circle.calValueAngle(Circle) at com.elegantj.gauges.dial.Circle.drawNeedle(Circle) at com.elegantj.gauges.dial.Dial.renderDial(Dial) at com.elegantj.gauges.dial.Dial.paint(Dial) at com.elegantj.gauges.dial.Dial.update(Dial) at sun.awt.RepaintArea.paint(Unknown Source) at sun.awt.windows.WComponentPeer.handleEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) -----------------------------------------------------------------------------java.lang.NullPointerException at com.elegantj.gauges.dial.Circle.totalDiv1(Circle) at com.elegantj.gauges.dial.Circle.drawZone(Circle) at com.elegantj.gauges.dial.Dial.renderDial(Dial) at com.elegantj.gauges.dial.Dial.paint(Dial) at com.elegantj.gauges.dial.Dial.update(Dial) at sun.awt.RepaintArea.paint(Unknown Source) at sun.awt.windows.WComponentPeer.handleEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source)

Customizing monitor graphs
An Individual Graph is a line graph giving a real-time view of the data collected on a specific item. When you click an Individual graph thumbnail, its full-scale version opens in the Graph Display window, along with dialog boxes. You can globally change the line sizes in your graphs by changing the property in pronet.graphs.indGraph.lineWidth=<2>. This does not affect images already created. Related Topics Graph tab on page 265 Attributes and indicators tab on page 266 Monitor information tab on page 268 Button options on page 268
264 BMC ProactiveNet User Guide

Customizing monitor graphs

Creating an individual/multiple monitor graphs on page 270

Graph tab
Once the larger graph appears in the Graph Display window, there are three tabs where you can interact with and customize the graph. This enables you to change the data view in any particular instance by changing the attributes, indicators, or the start and end time of the current graph. These options allow viewing of data that is not currently part of the display or allows one to focus on a specific type of data to analyze and isolate a problem. Data is available for the last 90 days. The Graph tab shows the larger graph seen as a thumbnail in the View area. Additional options are available on the right side of the graph. The available icons change depending on the type and status of the graph. For details on available options, see Additional information for changing graph display on page 271. Figure 15: Graph Tab

Chapter 5 Customizing graphs 265

Customizing monitor graphs

Attributes and indicators tab
The Attributes and Indicators tab lets you dynamically change statistical data displayed in the graph you are viewing. The statistics selections (attributes) vary based on the monitored entity. A colored box around an attribute indicates there is at least one open event of the severity indicated by the color of the box. You can select device or application-dependent elements for viewing. Choose the attributes you want to graph for each instance. The attributes available vary depending on the monitor chosen. You can chart up to 12 attributes per graph,

266 BMC ProactiveNet User Guide

Customizing monitor graphs

however you are limited to 2 units of measure (i.e., # and ms). For more information on attribute statistics and their function, see the BMC ProactiveNet Monitor Guide. Figure 16: Attributes and Indicators tab

For more details on Attributes and Indicators Tab, see Creating a line or area graph on page 251.

Chapter 5 Customizing graphs 267

Customizing monitor graphs

Monitor information tab
The Description table is located at the top of the Monitor Information tab. The table contains the item targeted for the graph and information collected from the SNMP data where applicable as well as specific monitored items such as disk location, Web site URL, and instance name. The table does not have default headings but lists pertinent information for the selected resource. Figure 17: Description Table

Button options
There are four button options from which to choose:
■ Generate Graph(s) - Generates graphs once you have defined your choices. ■ Add Graph - Adds another graph to the set of graphs already plotted.

268 BMC ProactiveNet User Guide

Customizing monitor graphs

■ Add All to View - Adds all graphs to the view.

Figure 18: Add this graph(s) to View – for single graph

If there is more than one graph, you can select the graph to set the graph as thumbnail. Figure 19: Add graph(s) to View – for multiple graphs

Use the Set thumbnail graph list to set the graph as thumbnail.
■ Printer Friendly - Provides a view of graphs and their description tables without

printing the additional options available on the screen.

Chapter 5 Customizing graphs 269

Customizing monitor graphs

Creating an individual/multiple monitor graphs
You can dynamically change the attributes or indicators using the graphing options available below the graph or use the icons located on the right side of the graph to perform other graphing functions. For more information, see Additional information for changing graph display on page 271 Generating a multi-monitor graph:
■ Provides the same options available for an Individual graph. ■ Allows you to select the option for Show instance names in legend for multi-

instance graphs to include instance names in the graph legend.

■ If two monitor instances with different raw retention periods are plotted in a

single graph, where one instance graphs rate data and the other instance graphs raw data, then the Condensed data string is not displayed on the y-axis of the graph. If both instances use rate data for plotting the graph, then this string is displayed. data and the other may fetch raw data, for the same time range selected. In this case, the Condensed data string is not displayed. set of graphs together but still want to add it into a view. After a multi-graph is added to a view, the thumbnail displays a small MG icon next to it

■ Due to the difference in the raw retention periods, one monitor may fetch rate

■ Multi-graphs can be added to a view. This is useful if you want to always see this

If an intelligent event is active for a given attribute or indicator on the graph, the outline is highlighted with the intelligent event color.
■ Red - Critical ■ Orange - Major ■ Yellow - Minor

You can globally change the line sizes in your graphs by changing the property in pronet.graphs.indGraph.lineWidth=<2>. This does not affect images already created.

270 BMC ProactiveNet User Guide

Additional information for changing graph display

Additional information for changing graph display
When a graph is generated, you will notice a series of icons located to the right of the graph. These are additional options you can choose from:
■ Zoom In or Out ■ Export to Excel ■ Add New Monitors to this Graph ■ More Info ■ Add this Graph to View ■ All Abnormalities ■ Device At A Glance ■ Delete ■ Resource Pool ■ Go to Probable Cause ■ MAIL this Page ■ Share this Page ■ PDF

In addition to these functions, the exact value at any point in the graph is also available. To check the exact value at any point on the graph, place the mouse pointer on the point. BMC ProactiveNet displays the value as tool tip. Related Topics Adjusting graph axes on page 272 Exporting graph data to Excel on page 273 Adding new monitors to a graph on page 273 Obtaining more information on page 273
Chapter 5 Customizing graphs 271

Additional information for changing graph display

Adding a graph to a view on page 273 Displaying all abnormalities for a graph on page 275 Navigating the graph page on page 275 Deleting a graph from a multi-graph view on page 275 Displaying graphs for a resource pool on page 275 Analyzing probable cause on page 276 Mailing the graph page on page 276 Sharing the graph page on page 276 Generating PDF on page 277

Adjusting graph axes
Use the Zoom function to adjust the vertical axis of the graph for viewing data more closely or from a higher level. The left axis is Y1 and the right axis is Y2.

To adjust the graph
1 Click the Zoom icon to display a separate window.

2 Based on the values used to plot the graph, enter the maximum and minimum values to be used to zoom the graph and by default the graphs are auto-scaled. 3 Click the Zoom icon to view results. You can only view one axis change at a time and this option does not permanently change the graph. The browser instance may, at times, cache the zoomed view of a graph. Using the browser navigation buttons may result in display of the cached pages. To avoid this, use the navigation options provided within the Operations Console.

272 BMC ProactiveNet User Guide

Additional information for changing graph display

Exporting graph data to Excel
Use the Export to Excel icon to export all data to a excel file for viewing outside BMC ProactiveNet. This icon launches the excel application and displays all data in the .csv file.

Adding new monitors to a graph
Use the Add New Monitors to this Graph icon to add new monitors to a graph.

When you click this icon, the Custom Graph screen appears. Follow the same procedure as creating a Custom Graph.

Obtaining more information
When a monitor has more information attached, you can use the More Info icon to find out if errors have occurred, and to display other pertinent information such as matched patterns being monitored by a Log File monitor or the reason behind a Web URL not responding. This icon launches the More Info for Graph table, which provides information about the graph and the possible error. If there are more than 25, click Next to bring up additional items. The More Info feature is available for Applications only; it is not available for SNMP information, such as interface or DLCI details.

Adding a graph to a view
Use the Add this Graph to View icon category. to add a particular graph to a view

This icon launches the Add This Monitor to View pop-up window. 1 Specify the graph name, duration, and name of the view to which you want to add the graph. 2 Click Add to View to activate this graph in the View. Once a graph is added to a view, its parameters no longer need to be determined each time you want to view data in that manner. Simply click the named graph in its View group. The Domain Knowledge field is displayed whenever you add a graph to a view. In the Domain Knowledge field, you can enter specific domain knowledge that other users may benefit from when looking at the graph. This information is also used by the Event Details page when events are generated against the same monitor

Chapter 5 Customizing graphs 273

Additional information for changing graph display . ■ The Change Domain Knowledge screen is displayed. Domain knowledge Domain Knowledge information can be added whenever you add a graph to a view. Domain Knowledge information acts as a repository of graph information. users can easily trace the event the next time a similar event occurs. This information is also used by the Event Details page when events are generated against the same monitor . The Domain Knowledge field is displayed on the Add this graph(s) to View page. Figure 20: Domain Knowledge field To edit the Domain Knowledge information from the Graph Display page 1 Click Edit next to the Domain Knowledge field. 2 Make changes to the information displayed. as required. 274 BMC ProactiveNet User Guide . 3 Click Update.links to the Domain Knowledge graph are automatically provided to aid users in troubleshooting. if the relationship between an event and an event is recorded as domain knowledge. For instance. Use this field to enter specific domain knowledge that other users may benefit from by looking at the graph.links to the Domain Knowledge graph is automatically provided to aid users in troubleshooting.

Additional information for changing graph display A message indicating that the information has been updated is displayed. 4 In the Graph Description window. This option is available only for graphs with a single monitor instance and can also be accessed from the Tools menu on the Device Matrix page and from the Graph page. When generated. Area. Chapter 5 Customizing graphs 275 . When displayed from the Device Matrix page. The All Abnormalities icon is not displayed if a graph is plotted using attributes of multiple monitor types. the graph displays the last four hours. click Close. X-Y. Deleting a graph from a multi-graph view The Delete icon is tied to the Multi-graph feature and is displayed only when there are two or more graphs. the Device At a Glance page shows a stacked line graph for all monitors on the device. Use this icon to delete a graph from a multi-graph view. and Pie graphs. Displaying graphs for a resource pool The Resource Pool icon launches the Graph Display page displaying graphs for each of the individual monitor instances forming the Resource Pool. Navigating the graph page allows easy navigation from the graph to other The Device at a Glance icon related attributes graphed below without having to re-implement graph selections. Click the icon to access the All Abnormalities page that displays abnormalities for: ■ The same group on which the Abnormality Index Monitor is based ■ The same duration for which the graph has been plotted This icon is available for Line. Displaying all abnormalities for a graph is displayed as an additional graphing function only The All Abnormalities icon for graphs plotted using attributes of the same Abnormality Index monitor instance.

so that it can be used by others. This opens the BMC ProactiveNet Login screen if you have not logged in. Mailing the graph page To send the graph via e-mail 1 Click the Mail this Page icon . This link is available in the following locations: ■ Custom Graph (all the graph formats) ■ Drill-Downs from Views ■ Drill-Downs from RCA 276 BMC ProactiveNet User Guide . 4 Select HTML or Plain text to send the description in plain text format and click Send. Sharing the graph page To share the page 1 Right-click the Share link. To view this graph: 1 Copy and paste the link in the browser address location and click Enter. Copy Link Location in Mozilla Firefox. 2 Specify the From and E-mail Address in the displayed window. 2 Enter the User Name and Password and click Log On.Additional information for changing graph display Analyzing probable cause Click the Go to Probable Cause icon to access the Event History page. 2 Click Copy Shortcut in IE. This link can be sent to others via E-Mail or can be pasted in a shared location. 3 A brief description can be sent via e-mail either in HTML or plain text format.BMC ProactiveNet navigates to the specified screen.

Additional information for changing graph display ■ Drill-Downs from Event Details ■ All Abnormalities ■ DD outputs Generating PDF Click the PDF icon to view the graphs and the configuration attributes table. in PDF format without the additional options available on the screen. Chapter 5 Customizing graphs 277 .

Additional information for changing graph display 278 BMC ProactiveNet User Guide .

Chapter 6 Managing Views 279 . View management privileges allow you to manage the following views: ■ Graph-based views that include graphs ■ Report-based views that include associated reports ■ Folder views that include other views Navigating the Views & Graphs drawer Use the Views & Graphs drawer in the navigation pane in the Operations Console to create and edit views. and display graphs based on the assigned access rights.6 Managing Views What is a view? A view is a placeholder for graphs that allows you to view the graph at any time with the new data value plotted. A view enables you to store graphs and reports. To create views. a BMC ProactiveNet administrator must assign appropriate view management privileges.

update frequency. The source of the monitored data always appears within the description column of the graph tables. 280 BMC ProactiveNet User Guide . The graph labels are based on monitored attributes. Figure 21: Views ■ The title bar contains icons for customizing the display and managing views. or delete the graph. You must select the Show View details at top of the page option when creating a view to display the details. Thumbnails display data from the last update. the highlight color returns to blue. and the date and time the view was last updated above the graph thumbnail. you can Note The graph border colors act as visual notifications when data collection pertaining to that graph is in an alarming condition. By default. data source. and the date and time the graph was generated. enlarge the view. ■ View display shows the graph thumbnails. These options are available only for the graph-based view. ■ View details displays the owner. the View details are not displayed. Thumbnails provide a high-level view of all graphs that exist in the view. Using the graph thumbnails. rename. ■ Critical = Red ■ Major = Orange ■ Minor = Yellow When an event is closed. The highlight color indicates the event severity.Navigating the Views & Graphs drawer Figure 21 on page 280 displays a single view and identifies the major areas within the Views screen. and may not always represent the most current data.

Table 61 on page 281 lists the icons available on the View screen. Figure 22: Inverted triangle symbol The thumbnail appears blank if the monitored resource provides a minimum amount of data during the polling period.Managing views An inverted triangle symbol is used as a placeholder and is displayed in the following conditions: ■ Data for the entire period is not available for creating a graph ■ Rate data computation for the hour is not complete for the top 10 graphs. Related topics: Managing graph thumbnails for a view on page 287 “Customizing graphs” on page 249 Managing view templates on page 289 Managing views Through the Views tab you can create. For more information see Managing view templates on page 289. or delete any number of views. Views can also be created using view templates. View settings that are configured when creating or editing a view differ for different types of views. see Managing graph thumbnails for a view on page 287. this happens with newly created instances. For detailed information on thumbnails. Table 61: Icons on View screen Icon Icon name View Template Administration Description Creates a view using a view template and dynamically updates the view Chapter 6 Managing Views 281 . Generally. edit.

Table 62: Inputs for the Graph-based Add View screen Fields Add View View Title View Type 2. provide the necessary information to create a view and add a graph to the view as described in Table 62 on page 282. click Add View. Any view name containing special characters is displayed in hexadecimal format on the Operations Console. '. with all options Description Note Layout Type 282 BMC ProactiveNet User Guide . The Operations Console does not support special characters such as \. The layout type can be one of the following: ■ Four columns: Displays a small size view. and > in the view name. 2 In the Add View screen. <.a Specifies the view name Indicates the type of view. \. select Graph Based to create a graph-based view Sets the preferences of the thumbnail. with all options ■ One column: Displays a large size view.Managing views Icon Icon name None Show/Hide View Details Add View Edit View Update View Delete View Description Displays the names of the available views Displays hides the view details Adds a view Edits a view Refreshes the graphs and displays updated thumbnails Deletes a view To create or edit a graph-based view 1 In the View Display screen. ". with fewer options ■ Two columns: Displays a medium size view.

By default. 5 Click Finish. To edit an existing view. provide the necessary information to create a view and add a report to the view as described in Table 63 on page 284. Chapter 6 Managing Views 283 .Managing views Fields Update Description Sets the update frequency of the view as follows: ■ Daily ■ Hourly ■ Manually Update the View for every xx minutes Updates the view for a time specified in minutes Show View details at top of the page Displays the details in the View screen. 4 Click Add to View. a You cannot configure the view type when editing an existing view. Tip To create or edit a report-based view 1 In the View screen. see Creating custom graphs on page 249. View Create Option Indicates how the view is created: ■ Manual: Creates a view manually ■ Template: Enables selection and application of a view template to a view Graphs in View Add Graph Adds a graph to the view. click Edit View on the View screen and follow the steps listed in To create or edit a graph-based view on page 282. For detailed instructions. 3 Specify a name for the graph. click Add View. 2 In the Add View screen. the details are not displayed. You can toggle the display of view details using the Show/ Hide View icon.

By default. The layout type can be one of the following: ■ Four columns: Displays a small size view. see Creating or editing a report on page 294. You can toggle the display of view details using the Show/ Hide View icon. Table 63: Inputs for the Report-based Add View screen Fields View Title View Type Add Report as Thumbnail or Complete Report as Entire View Description Specifies the view name Indicates the type of view. ■ The Order button sets the order of graphs or reports in the view. with all options Show View details at top of the page Displays the details in the View screen. This option is available when you create multiple graphs or reports.a Reports in View 2. the details are not displayed. select Report Based to create a report-based view Sets the preferences of the thumbnail. 3 In the Reports screen. 2. generated reports are added to the view if they are not generated. For detailed instructions. and then click Add To View. a By default. 284 BMC ProactiveNet User Guide .b Add Reports Adds a report to the view. select the default report(s) to add to the view. the bar graph thumbnail may not display all the indices in Y-axis. The thumbnail can be set using the following choices: ■ Add Report as Thumbnail: Sets the report as a thumbnail ■ Select Complete Report as Entire View: Displays a single large report on the View screen Layout Type Sets the preferences of the thumbnail. with fewer options ■ Two columns: Displays a medium size view.Managing views Note ■ Users with access to a view have unrestricted access to all the reports. with all options ■ One column: Displays a large size view. b For Capacity Trend Reports.

■ A view can be a child of only one folder view. Access rights to folder view applies to all child views in the folder. To edit an existing view. the Available Top Level Views shows only top level views. the view to the top level first. Table 64: Inputs for the Folder-based Add View screen Fields View Title View Type Description Specifies the view name Indicates the type of view. without moving ■ If a folder view is deleted. 2 In the Add View screen. click Add View. ■ When adding a folder. provide the necessary information to create a view and add a folder to the view as described in Table 64 on page 285. the children in the folder are not deleted. This is different in Group behavior. Related topics: To show the child instances for the selected monitor instance on page 255 To create or edit a folder view on page 285 To delete a view on page 286 Managing view templates on page 289 Tip To create or edit a folder view 1 In the View screen. where one group can be a sub-group of many other groups. all the immediate children are moved to the top level. Instead. ■ Individual views cannot be moved from one folder to another. click Edit View on the View screen and follow the steps listed in To show the child instances for the selected monitor instance on page 255. Note ■ Folder view administration is available from the Operations Console only. select Folder to create a folder-based view Chapter 6 Managing Views 285 .Managing views 4 Click Finish.

click Edit View on the View screen and follow the steps listed in To create or edit a folder view on page 285. 2 Click Delete View. You can toggle the display of view details using the Show/ Hide View icon. the details are not displayed. Related topics To create or edit a graph-based view on page 282 To show the child instances for the selected monitor instance on page 255 To delete a view on page 286 Managing view templates on page 289 Tip To delete a view 1 Select the view that you wish to delete. Related topics Customizing monitor graphs on page 264 Creating or editing a report on page 294 286 BMC ProactiveNet User Guide . By default. click OK. 3 In the Confirmation dialog box. Default Sort Select Child View Available Top Level Views/ Selected Child Views Select the view to add to the folder from Available Top Level Views. and move it using the arrow key to Selected Child Views Sorts the selected child views in an ascending by default 3 Click Finish.Managing views Fields Description Show View details at top of the page Displays the details in the View screen. To edit an existing view.

3 Click Apply. modify the following settings. Note To rename a thumbnail 1 In the Views & Graphs drawer in the navigation pane. Table 65: Basic configuration for View display Setting Show Dashboard View Description Enables selection of the dashboard view that must be displayed as a thumbnail whenever you access the Views drawer in the navigation pane.Managing graph thumbnails for a view Customizing the basic screen layout on the Views tab To customize the View display 1 In the top right of the Operations Console. 2 In the Operations tab. 2 Right-click a graph thumbnail. Thumbnails of any graphs associated with the view are displayed in the right view pane. You can only set graph-based views as dashboard views. and then click Large View. You cannot view the large view for a single layout type of graph. select a view from the navigation tree. Show Home View Enables selection of a view that must be displayed as the default whenever you access the Views tab. as necessary. select a view from the navigation tree. under Layout Preferences. You cannot set folderbased views as dashboards. Managing graph thumbnails for a view To switch to large view 1 In the Views & Graphs drawer in the navigation pane. click Options. Chapter 6 Managing Views 287 .

select a view from the navigation tree. and then click Rename. To delete a thumbnail 1 In the Views & Graphs drawer in the navigation pane. 4 In the Add this graph(s) to Viewscreen. you can view a large view for the same.Managing graph thumbnails for a view Thumbnails of any graphs associated with the view are displayed in the right view pane. 3 In the confirmation dialog box. 2 Double-click a graph thumbnail to be added to an existing view. enter a name for the graph. and then click Delete. However. select a view from the navigation tree. provide the necessary information as described in Table 66 on page 288. 288 BMC ProactiveNet User Guide . click OK. click Add this Graph to View . 3 In the Custom Graphs screen. and then click Apply. Table 66: Fields in the Add this graph(s) to View screen Field Graph Name Graph Duration Add to View Domain Knowledge Procedure Enter the graph name Select the time duration for which to generate the graph Select the view to which you want to add the graph or create a new view to add the graph Type the domain information 5 Click Add to View. 2 Right-click a graph thumbnail. You cannot delete or rename a graph that is created using a view template. 3 In the Rename Graph dialog box. Note To add graph(s) to a new or exiting view 1 In the Views & Graphs drawer in the navigation pane. 2 Right-click a graph thumbnail.

Related topics: “Customizing graphs” on page 249 Managing view templates on page 289 Note Managing view templates View templates are reusable components that are place holders for details such as graph type. You can apply a view template to groups or services to create a view. To create a view template 1 In the Views & Graphs drawer in the navigation pane. and then the applicable monitor type(s). A view that is created using a view template is automatically updated when a new instance is added or removed from the group. associated views are also deleted. enter a name for the view template. monitor type. 7 Select the Group filter. Chapter 6 Managing Views 289 . click Add. see To create or edit a graph-based view on page 282. 3 In the View Template Administration screen. if a view is deleted from the view template. 4 In the Create View Template screen. The Add to View screen does not consider views created using a view template. 8 Click Next. attributes. When you add a graph to a view template all the associated views are updated. click the View Template Administration button. and then click Finish. 2 In the right view pane. select a view from the navigation tree. and indicators. 5 Click Add Graph. select the graph type. 9 Select the attributes applicable to the graph. 6 In the Custom Graphs screen.Managing view templates ■ For detailed instructions. Similarly.

or edit the graph in that template. 290 BMC ProactiveNet User Guide . and therefore. select the view template that you wish to delete. 1 In the View Template Administration screen. Creating views for Report or Folder based views does not display the count in the view template wizard. Tip In the View Template Administration screen. 3 In the confirmation dialog box. Note The Order button is used to set the order of graphs in the View Template. click Finish. 2 Click Delete Selected. see Creating custom graphs on page 249. but in view template creation. For further information. 10 In the Create View Template screen. 3 Click Finish. To delete a view template On deletion of a view template. delete. under the Select column. only monitor types are considered. you can add. ■ View template supports and displays the count only for Graph based view. you can choose monitor instances. no dynamic updates to the monitor instances take place. 1 In the View Template Administration screen. all the views created from that template are listed. 2 Make the necessary modifications. This option is available when multiple graphs are added. under the Edit column. click Edit in the view template row that you wish to edit. ■ Based on the selected graph type the corresponding screen opens. ■ The View Template Administration screen displays the newly created template. the views created using the template become normal (manual) views. click OK. when you mouse over on the views count. To edit a view template When you edit a view template.Managing view templates Note ■ In manual view creation.

By default. 2 In the Add View screen. select Graph Based to create a graph-based view. click the Add View button in the row for the view template that you want to use. with all options ■ One column: Displays a large size view. You can toggle the display of view details using the Show/ Hide View icon. with fewer options ■ Two columns: Displays a medium size view. under the Add View column. Displays a list of available view templates that you can apply to a view . Sets the preferences of the thumbnail. Table 67: Inputs for the Add View screen using a view template Fields Add View View Title View Type Layout Type Specifies the view name Indicates the type of view. View Create Option Select View Template Template Details Groups Provides a link to the Groups Filter dialog box that allows you to specify the groups to which this view template must be applied Chapter 6 Managing Views 291 Indicates how the view is created. provide the necessary information to create a view using a view template as described in Table 67 on page 291. select Template to create a view using a view template. the details are not displayed.Managing view templates To create a view using a view template 1 In the View Template Administration screen. The layout type can be one of the following: ■ Four columns: Displays a small size view. with all options Update Sets the update frequency of the view as follows: ■ Daily ■ Hourly ■ Manually Update the View for every xx minutes Updates the view for a time specified in minutes Description Show View details at top of the page Displays the details in the View screen.

There is a configurable entry in pronet. In such views.maxMonitorInsCount = 50) that defines the maximum number of monitor instances that can be plotted in a view created using a view template. The Update View operation for such views is restricted to existing monitor instances in that view in case the number of monitor instances in the selected group exceeds the above mentioned maximum count. Under such circumstances a message is displayed. if the number of thumbnails exceed 200.Managing view templates 3 Click Finish.conf (pronet.viewTemplates. it may take more than a minute to create the view. Note 292 BMC ProactiveNet User Guide .

the schedule is displayed as Mixed. When the schedule is not applicable. Each SLO can have a different schedule. General. Some of the report types also have default reports. For example. Administrative. copying. Weekly. Table 68: Views of report information on the Report tab View Report Type Frequency Schedule Description Reports are generated based on the selected report type. the defined reports are listed in tabular form. a hyphen is shown. For example. and changing the email based on the assigned access privileges for various report types. In the initial display on the Reports tab. for example. editing. The schedule displayed in the report listing depends on the individual schedules of the components that make up the report. You can query the reports using filter options to view the applicable reports. if a report based on Service Level Objectives (SLOs) is made up of more than one SLO. and Monthly at which the report is generated Displays a list of schedules. schedule 24x7 considers data collected throughout the day for the entire week (including Saturday and Sunday). deleting.7 Generating Reports Overview The Reports tab in the Operations Console presents extensive information about creating. Daily. Table 68 on page 293 lists the columns of report attributes that appear for each report. Name of the report owner Title of the report Report category Owner Report Title Category Related Topics Creating or editing a report on page 294 Chapter 7 Generating Reports 293 . Business Hours and 24x7 based on which the report is generated. or SLO Displays a list of report generation frequencies.

Select this check box to enable report generation for the report. depending on the report type. simply make changes to the attributes.Enter Report Details screen specify the following basic report attributes listed in Table 69 on page 294. 1 On the Reports screen. 3 Click Next. you need not specify attributes. 4 On the Add (Step 2 of 3) .Enter Report Details screen. If you are editing a report.Overview Deleting a report on page 298 Copying an existing report on page 298 Changing email settings in a report on page 299 Creating or editing a report This section consists of common steps and attributes required for report creation. set the attributes and contents for the specific report type. Table 70 on page 295 lists the attributes common to all report types. click Add for a new report or select a report and click Edit to edit an existing report. Table 69: Report detail attributes Field Name Contact Information Report Type Enable Report Generation Description Enter a unique report name Enter report owner’s phone number Select a report type from the list. 294 BMC ProactiveNet User Guide . see Report types available in BMC ProactiveNet on page 300. You cannot change the report type when editing an existing report. 2 On the Add Step (1 of 3) . For a list of all the available report types and a complete list of reportspecific settings for each report type. this check box is selected. By default. The settings at this point differ.

To add a filter. Use this filter to report only those events associated to the attribute being considered. click Finish. Select one or more attributes and click Next. Use this filter to limit the report to only those instances that are present in the selected group. When the Add Attribute screen opens. Use the No Filter option to consider all available devices. select a monitor type and click Apply. On the Select Group screen. select a group and click Apply. The attribute set is a collection of attributes that are used for generating a report. Select Device Search for Generate Report to Monitor Type Sub Report Title Delete Sub Report Single Attribute Select a device from the list. When the Select Monitor Type screen opens. A successful completion message is displayed. select a monitor type and click Apply. A successful completion message is displayed. Enter the title for Sub Report. click New.Overview Table 70: Common report attributes Attributes Select Group Description By default the No Filter option is displayed. Select a sub report in the Added Sub Report Section. When the Add Attribute Set screen opens. Enter a device name to search a specific device Select the appropriate option to show configuration or monitor details Click the Agent Status link. To edit an attribute select an attribute from the list and click Edit. When the Edit Attribute Set screen opens. click the No Filters link. Chapter 7 Generating Reports 295 . Attribute Set Select an attribute set from the list to limit the report to those attributes present in the attribute set. Select an attribute from the list. Use this filter to limit the report to a single attribute of a monitor type. Use the default option to consider all available monitors. Select one or more monitor types and click Next. and click Delete Sub Report to delete the selected sub report. When the Select Monitor Type screen opens. Attributes associated to the monitor types are displayed. enter a name for the new attribute and select attribute(s) and click Finish. select the attribute set type from the list and select the monitor types. To define a new attribute set. Click the attribute link.

Overview Attributes Schedule Description The period corresponding to which the data will be considered for Report generation.Select this option to calculate granular data for reports. For example. Select one of the following options: ■ Condensed Data . and then click Finish to generate the report. schedule 24x7 will consider data collected through out the day for the entire week (including Saturday and Sunday). Condensed data is selected. For example. 296 BMC ProactiveNet User Guide . High.Enter Report Details screen set the report details summarized in Table 71 on page 297. 6 On the Add (Step 3 of 3) . By default. Each SLO can have a different schedule. or Low rate values can be calculated and applicable for only condensed data. a hyphen is shown. 5 Click Next.Select this option to calculate data on hourly bases for faster calculation. During a scheduled down time BMC ProactiveNet performs the following actions depending on the configuration: ■ Stops data collection ■ Stops Event or Event Generation ■ Stops Event related Notification or Actions ■ Calculate Baseline Do not consider data during Schedule DownTime Add Sub Report Select attributes in Selected Attributes and click Add Sub Report to append sub reports to the Added Sub Report section. Avg. Select this option to reject misleading events and notifications during a scheduled down time. To add multiple attributes Press Shift and select the attributes. Follow similar steps to delete a sub-report and click Delete Sub Report. and click Edit Sub Report. Data to be used for calculation Note To edit sub-report. the schedule is displayed as Mixed. select a sub report in Added Sub Report Section. When the schedule is not applicable. if a report based on Service Level Objectives (SLOs) is made up of more than one SLO. ■ Raw Data . The schedule displayed in the Report listing depends on the individual schedules of the components that make up the report.

then the selections made on the Report Instance Comments window are automatically applied here. Display the device name with the monitor information. Also. Global comments always precede report instance comments. which are part of comments. If you select the Show Comments at option. If you add text to the Global Comments field. The available options differ based on the report type. By default the Monitor Information column is displayed even if you have not selected the Device name with Monitor Information check box. Table 71: Report display options Options Graph Type No. Global Comments Chapter 7 Generating Reports 297 . If you do not select this option while creating a report but specify comments for a report instance. This creates hyperlinks for URLs in report comments. Example for Global comments: Consider an Element Distribution Summary report created to denote availability of Solaris processes on a server. Also. Click URL Tag to enclose URLs. of rows per page (applicable for tables) Show Device name with Monitor Information Show Source Agent with Monitor Information Show report details at Show comments at Description The graph type. Display the report details. specify the location (top or bottom of the page) to display the report details. Global comments can be added to indicate that instances of this report are to be generated daily and the server is considered to be in good state if the availability is >=99. The number of rows to be displayed on a single page. this option is selected automatically. By default the Monitor Information column is displayed even if you have not selected the Show Source Agent with Monitor Information check box. Choose the font size for display of comments. E-mail Options Enter E-mail Address E-mail used to send the report by email. Also. Based on these settings report is displayed. comments that you enter here are displayed on all instances of the report. Select this check box to view Global comments and Report Instance Comments on the report. Display the source agent with the monitor information. Information or other content that you want to associate with the report. specify the location (top or bottom of the page) to display comments. in tags. Some of the display attributes are common to all the reports.Overview Note This step is common to all the report types. select the format (in which the report needs to be sent) from the list.99%.

Asset. Generate report based on the inputs. or Monthly. SLO Application Compliance and SLO Compliance History are listed based on the granularity selected for these reports. Weekly. Table 70 on page 295. Select the check box if required. This option is not available for SLO Capacity Trends. group. 298 BMC ProactiveNet User Guide . Sets the report generation frequency to Daily. 3 Click Delete. Then edit the new report to make specific changes if required. For more information see. All applicable email IDs and the associated formats are listed in the email Addresses box. Report Frequency Sharing Generate this report immediately after adding to the schedule Deleting a report Perform the following steps to delete a report: To delete a report 1 Click the Reports tab. SLO Compliance Matrix and Capacity Trends report types. 2 In the Select column of the Report screen. select the check box corresponding to the report. Number of days selected from the list to be included in the report. Repeat the procedure to add more email IDs and preferences. Copying an existing report To quickly create similar reports. Remove the email ID from the Email Addresses list. A confirmation dialog box opens. Sets report sharing parameters with everybody. click OK to delete.Overview Options Add Description Insert the email id and format into the email Address box. Report periods for Event History. Use the copy option to replicate an existing report's properties and create new reports. the copy option can be used. Threshold. or not to share. Delete Schedule Options Scheduled On Demand Schedule Report Period Save the report in the system and generate it based on the frequency.

select Modify. Perform the following steps. select the check box corresponding to the report. select the check box corresponding to the report. 3 Enter the email ID to be replaced with the new or modified email ID. 3 Select Email Type from the list. 4 Click Apply. 2 In the Select column of the Report screen. To change email settings in a report 1 Click the Reports tab. click Done. Changing email settings in a report Use this option to add. click OK to copy. If the email ID exists then the newly entered email ID is appended to the existing list of Email IDs.Overview To copy an existing report 1 Click the Reports tab. select Add option to add email IDs for all the selected reports. modify. To add a new email ID 1 On the Change Email page. 2 In the Select column of the Report screen. To modify an existing email ID 1 On the Change Email Summary page. 2 Enter the email ID to be added to the selected reports. A confirmation dialog box opens. Chapter 7 Generating Reports 299 . or delete email for the selected reports. 3 Click Change Email. 3 Click Copy. 5 On the Change Email Summary page. 2 Enter the existing email.

4 Click Apply to replace the existing email ID with a new email ID. see Asset on page 301 Threshold on page 302 User on page 303 Aggregate Performance on page 303 Availability Summary on page 305 Capacity Trends on page 307 Custom Graph on page 309 Element Distribution Summary on page 310 Event on page 312 Health Summary on page 315 Top Bottom Performers on page 317 Virtual Inventory on page 318 300 BMC ProactiveNet User Guide . To delete a new email ID 1 On the Change Email page. 2 Click Apply.Report types available in BMC ProactiveNet Note When modifying the email ID. Table 7 presents the types of reports in each category and points you to further information about each report type. you cannot modify the email Type. and Service Level Objective (SLO). Report types available in BMC ProactiveNet BMC ProactiveNet reports are divided into three categories—Administrative. select Delete option to delete the existing email ID from the selected reports. Table 72: Report types available in BMC ProactiveNet Category Administrative Report types Asset Threshold User General Aggregate Performance Availability Summary Capacity Trends Custom Graph Element Distribution Summary Event Health Summary Top/Bottom Performers Virtual Inventory Further information. General. 3 On the Change Email Summary page. click Done.

Report types available in BMC ProactiveNet Category SLO Report types Further information. see SLO Application Compliance SLO Application Compliance Report on page 319 SLO Capacity Trends SLO Compliance History SLO Compliance Matrix SLO Executive Summary SLO Health Summary SLO Capacity Trends Report on page 320 SLO Compliance History on page 321 SLO Compliance Matrix on page 321 SLO Executive Summary on page 323 SLO Health Summary on page 324 Note BMC Software recommends users to disable those default reports that are not applicable. The default reports of BMC ProactiveNet do not have filters and therefore may consume more resources on loaded setups. for the selected configuration parameters. ■ The Show Monitor Details option displays the details of various monitor instances of the selected group and device. Sort Key Chapter 7 Generating Reports 301 . This option is displayed only if you have selected Show Config Details. Select a sort key from the list. Table 70 on page 295 For further information see. Table 73: Asset report attributes Attributes Select Group Select Device Generate Report To Description For further information see. Displays configuration attributes corresponding to the selected monitor type. over a specified time period. Table 70 on page 295 ■ The Show Config Details option displays the configuration attribute details of monitor instances for the selected monitor type. Asset The Asset report displays all monitor instances of a particular monitor type in a specific group. Table 70 on page 295 Include control attributes in the Available Config Attributes list. Table 73 on page 301 lists attributes specific to Asset reports that need to be entered along with the common attributes. Monitor Type Include Control attributes Available Config Attributes For further information see.

Table 75 on page 302 lists attributes specific to Threshold reports that need to be entered along with common attributes. device. This report is an administrative type of report. Table 74: Configured Instance and Global Thresholds organized by Monitor Type Default Threshold Report Type Report Type Report Frequency Sub-Reports Included Description Threshold Weekly 1) Absolute Event Thresholds (Global Only) organized by Monitor Type. 2) Absolute Event Thresholds (Instance Only) organized by Monitor Type. Table 70 on page 295 For further information see. Table 75: Threshold report attributes Attributes Consider Description Select the threshold type based on which to generate the report. From the Default Sort Column list. For further information see. select No Filter. To consider all monitor types. Organize By 302 BMC ProactiveNet User Guide . Select the monitor type based on which the report must be generated. 4) Signature Event Thresholds (Instance Only) organized by Monitor Type. Also indicate whether instance or global thresholds or both instance and global thresholds must be considered to generate the report. Monitor Type Threshold Type Default Sort Column Select the columns for the report. Select Flat List to lists all monitor types in a table. or monitor type. Table 70 on page 295 Threshold The Threshold report allows you to quickly view the threshold values configured.Report types available in BMC ProactiveNet Attributes Show Config DD Sub Report Title Add Sub Report Description Select this option to view configuration DD. Select the criterion on which the threshold values must be organized in the report. Report thresholds are not considered for the Threshold report. The threshold values can be sorted by group. Table 74 on page 302 lists the default Threshold report types. 3) Signature Absolute Event Thresholds (Global Only) organized by Monitor Type. choose the column that must be displayed first in the report.

User Class User Status Select Attributes Sub Report Title Add Sub Report Aggregate Performance The Aggregate Performance report runs an aggregation function on selected attributes of monitor instances belonging to the specified group. Sum. Chapter 7 Generating Reports 303 . Choose No Filter option to list all the user states (Active or Inactive) or appropriate user status to be reported. average. Choose No Filter option to list all the user groups or choose the appropriate user group to be reported. Each graph reflects the aggregation result of attributes having same unit of measurement. The aggregation function can be Average. Median. See Table 70 on page 295. Select the attributes to be reported. Minimum. see User Management of BMC ProactiveNet Administrator Guide. If Table Display is enabled. and Standard Deviation. over a specified time period. This report displays the user details in a tabular format and the frequency of the report period is monthly. the report is displayed in tab format where the first tab consists of all the line graphs and the second tab shows a complete list of all instances of the selected group in table format along with the minimum. Maximum.Report types available in BMC ProactiveNet Attributes Add Sub Report Description See Table 70 on page 295. Percentile. The result of aggregation is displayed as multiple summary line graphs (stacked line graphs). Table 76: User default report types Default User Report Type Report Type Report Frequency Description User Monthly Table 77 on page 303 lists attributes specific to User reports that need to be entered along with common attributes. and maximum values for the specified attribute. user class. and user status. User The User report filters user group. For more information. Drill down from any of the instances to view the corresponding independent line graph for that instance. See Table 70 on page 295. Table 77: User report attributes Attributes Name User Group Description Specify partial or full login name of the user to be reported. Choose appropriate user class to be reported.

Aggregate Performance report can be made using multiple sub-reports. and the second tab displays different tables corresponding to each graph. where each sub-report is a combination of different group-attribute-set and aggregate function. The following default reports of the Aggregate Performance type are provided out-ofthe-box by BMC ProactiveNet: ■ Web Transaction Availability and Response Time . Alternatively. 304 BMC ProactiveNet User Guide . use the search box to locate a specific attribute.a weekly aggregation of data with the following sub-reports: — Transaction Availability — Transaction Response Time ■ Server Capacity . the first tab displays graphs corresponding to each sub-report.Report types available in BMC ProactiveNet Individual graphs for each instance or attribute are displayed (for the selected report period) when the Show graphs for each Instance or Attribute option is selected. Select Attributes (to be part of the sub report) from Available attributes and transfer to Selected Attributes. Use Ctrl and Shift keys to make multiple selections. — Server Memory Capacity Table 78 on page 304 lists attributes specific to Aggregate Performance report that needs to entered along with common attributes.a weekly aggregation of data with the following sub-reports: — Server CPU Capacity (includes sub-reports). The summary graph will be larger than the individual graphs. If Show detail table option is enabled for such reports. Table 78: Aggregate Performance report attributes Attributes Select Group Select Attributes Description See Table 70 on page 295.

■ Percentile . Select this option to display individual graphs for each instance or attribute for the selected report period. Select this option to view tables in separate tabs.5 ■ When the report has too much data. (0 – being the min. 100 – being the max. Select this option to hide the attribute column from being displayed in the report. ■ Max .It is the standard deviation across all the underlying instances.(Minimum) Sort the data points from the various instances and take the lowest value. Enter title for graph.Sort the data points from the various instances and take the middle value.all data points for each instance-attribute. ■ Sum .(Average) Sum of all data points for each instance-attribute and divided by the total number of instances. This option is enabled only when the Show Tables in separate Tab option is selected.Sort the data points from the various instances and take the highest value. ■ Median . ■ Standard Deviation . ■ Min .Value that X% of the monitors and below are reporting. Show Graphs for each Instance/ Attribute Note The report display can get distorted in the following scenarios: ■ When report is viewed using IE 5. then the Weightage combo box is enabled for the user to select the appropriate nth weightage factor. See Table 70 on page 295. Do not consider data during Schedule DownTime Sub Report Title Graph Title Add Sub Report Show Tables in separate Tab Hide Attribute Column Name See Table 70 on page 295. It Chapter 7 Generating Reports 305 . See Table 70 on page 295.Report types available in BMC ProactiveNet Attributes Select Aggregate Function Description ■ Avg . 50 – being the median) If percentile is selected.(Maximum) . Availability Summary The Availability Summary report displays Availability of a monitored element in the form of a pie graph. The report also displays information such as Total Downtime.

Table 80: Availability Summary report attributes Attributes Select Group Select Device Type Attribute Set Consider Sub Transactions if any Description Click the list to select a group or no filter option to consider all the monitors. The report also can include information about Mean Time To Recovery (MTTR). 306 BMC ProactiveNet User Guide . See Table 70 on page 295. The Availability Summary report can consist of multiple sub-reports. so Attribute Sets that have the string “Availability” in them are only considered by the report. Table 79: Availability Summary default report type Default Availability Summary Report Type Web Transaction Availability Description ■ Report Type: Availability Summary ■ Report Frequency: Weekly ■ Report Duration: Week ■ Sub-Reports Included: Transaction Availability Table 80 on page 306 lists attributes specific to Availability Summary report that needs to entered along with common attributes. Select this option for the report to be generated considering dynamic attributes associated with the monitors of the Attribute set. Note If the report period is greater than the instance creation time. Table 79 on page 306 lists the default report type for Availability Summary. the availability attribute does not show the accurate value. See Table 70 on page 295. and MTTR information. range sets.Report types available in BMC ProactiveNet is assumed that attributes displayed will be of type “Availability”. You can select or define the range set for the availability distribution. If the MTTR option is selected. device type. the report displays an additional pie graph that shows the MTTR distribution for each sub-report. This is taken care when the report is generated again. where each subreport may be a combination of different group-attributes. for which you can select a predefined range set or can define a new one.

■ Drill down on the monitor instance in the table displays a line graph for the The report displays Line graph as follows: Chapter 7 Generating Reports 307 . Select this option to view related tables. ■ The duration to violation (in days) is displayed on X axis. ■ The table is sorted with instances. select MTTR Custom Range set to define and assign values to the custom range set. Show Table containing the list of Instances Schedule Do not consider data during Schedule DownTime Sub Report Title Report Options Capacity Trends The Capacity Trends report lists all monitor instances–attribute pairs that are predicted to violate event thresholds in the specified time period. The report displays Bar graph as follows: ■ The instance-attribute pair is displayed on the Y axis.Report types available in BMC ProactiveNet Attributes Available attributes Description Select the attributes (to be part of the sub report) and transfer to Selected Attributes. Data collected is validated against the custom range specified here. When the option is selected. ■ Select the Availability Custom Range Set option to specify and define the distribution range dynamically. The maximum number of bars can be specified during report creation. Range sets define the Maximum-Minimum value of the stack in the graph. which are predicted to violate earliest (in any violated instance are present. selected attribute along with the threshold line. they would appear first). See Table 70 on page 295. See Table 70 on page 295. use the search box to locate a specific attribute. two additional options are displayed. Use Ctrl and Shift keys to make multiple selections. Alternatively. Alternatively. The report contains a bar graph at the top that shows each instance–attribute pair predicted to violate event threshold in the specified time period. See Table 70 on page 295. ■ Select the Availability Distribution range to use a pre-defined range set. Select MTTR Distribution range set to use a pre-defined range set to calculate the Mean time to recovery. Availability Range Set Include Mean Time Recovery Information Select the Include MTTR information option to display the Mean Time to Recovery information in the report. See Table 70 on page 295.

Minor. Highest Severity. Do not consider data during Schedule DownTime Enter a value to assign downtime. or Minor event thresholds are selected. Major. Table 81 on page 308 lists Capacity Trend default report. When All or highest severity threshold type is selected. When Critical. Table 81: Capacity Trend default report Default Capacity Report Type Infrastructure Capacity Trends Description ■ Report Type: Capacity Trends ■ Report Frequency. ■ A dotted line from the intersection point to the X axis will also be present. Weekly ■ Duration: One Month Table 82 on page 308 lists attributes specific to Capacity Trend sub-reports and report attributes that needs to be entered along with common attributes. then severity column is hidden and a table title is added displaying severity type of each instance. then severity column is displayed and a table title is added displaying severity of each instance.Report types available in BMC ProactiveNet ■ The line graph is projected using a dotted line from the last data point to the threshold line and the intersection point is at the predicted violation time. Major. Critical. Select this option to consider all the instances in the system Select this option to select the attribute groups from the Available Groups box and transfer to Selected Groups box Descriptions 308 BMC ProactiveNet User Guide . Table 82: Capacity Trend report attributes Report Type Sub-report section No Filter Selected Groups Report Attributes Single Attribute Attribute Set Consider Sub Transactions if any Hide Attribute name Column Use Event Thresholds as Capacity Limit See Table 70 on page 295 See Table 70 on page 295 Select this option for the report to be generated considering dynamic attributes associated with the monitors of the Attribute set Select this option for the attribute column not to be listed with the report Select this option to use Event capacity as thresholds. or All event thresholds can be selected.

Selected attributes are displayed in Selected Attributes.This option governs the data points to be used for forecasting. Default value is 14 days. Default is 7 days. By default. The inputs for Graph-based reports are collected through a reports input wizard. Click Add. See Table 70 on page 295. The Monitor Instance to be graphed option opens. Condensed data is selected. Default value is 20. Any instance that is predicted to violate event thresholds in this time period appears in the report. Any violations outside this forecast period will not be considered. ■ Data to be used – Specifies whether Condensed (Rate) or Raw (Granular) data is to be used. Maximum number of bars cannot exceed 20. Table 83 on page 309 lists attributes specific to Custom Graph report that need to be entered along with the common attributes. Schedule See Table 70 on page 295. X – Y correlation. The Select Instances for Line Graph screen opens. Select a Group Filter. ■ Show instance which will violate in the next . Select an instance and click Apply. Avg. click Next. Custom group thresholds can be set for either a single attribute or group or multiple attributes or groups. or Low rate values can be calculated and applicable for only condensed data.This is the forecast period.Report types available in BMC ProactiveNet Report Type Use Custom Group Threshold Descriptions Select this option to set custom group thresholds. and Area. ■ Use Data for the last . Click Clear to discard the selected attribute. Schedule Sub Report Title Report Options Custom Graph The Graph-based report provides an option to create a report equivalent to the current custom graph generator. Pie. High. See Table 70 on page 295. This can be used only when the Groups/Services filter is selected. Table 83: Custom Graph report attributes Attributes Graph Type Add Attributes Description See Table 70 on page 295. Choose the respective groups and click New to set new thresholds. and Monitor Type. ■ Maximum number of bars in graph – Specifies the maximum number of bars to be displayed in the bar graph. The graph types supported are Line. Selected Attributes Chapter 7 Generating Reports 309 .

This table is a list of all the elements for that distribution range sorted on their average values. Table 85: Element Distribution Summary report attributes Attributes Select Group Single Attribute Attribute Set Consider Sub Transaction if any Description See Table 70 on page 295. See Table 70 on page 295. See Table 70 on page 295. Element Distribution Summary The Element Distribution Summary report displays either the actual (with respect to custom ranges) or percentage (with respect to specified event thresholds) distribution of instance-attribute values in the form of stacked bar graphs. 310 BMC ProactiveNet User Guide . Select this option to generate reports considering dynamic attributes associated with monitors of the Attribute set. Table 84: Application Infrastructure Element Summary default report Default Element Distribution Summary Report Type Application Infrastructure Element Summary Description ■ Report Type: Element Distribution Summary ■ Report Frequency: Weekly ■ Duration: Week Table 85 on page 310 lists attributes specific to Element Distribution Summary report that needs to be entered along with common attributes.Report types available in BMC ProactiveNet Attributes Show More Info Data to be used Sub Report Title Add Sub Report Description Select this option to display more information on the graph. See Table 70 on page 295.Enter Element Distribution Details screen. See Table 70 on page 295. See Table 70 on page 295. Further drill down on each of the elements in the table leads to the individual graph for that element for the specified time period. Custom ranges can be defined in the Create (Step 2 of 3) . Drill down on any bar in the stacked bar graph displays a table based on the distribution ranges. Default ranges for percentage distribution in the stacked bar can be specified in the configuration file. Table 84 on page 310 lists Element Distribution Summary default report.

It defines the maximum and minimum values of the stacks in the graph. Select this option to dynamically define the distribution range. The available options differ based on the report type. See Table 70 on page 295. Select one of the following custom ranges: ■ Bad ■ Poor ■ Fair ■ Good ■ Excellent Threshold Severity Custom Distribution Range Distribution Details Show data broken down by Select this option to set the graph display either as 2D or 3D. See Table 70 on page 295. Select one of the following options: ■ Hour ■ Day ■ Week ■ Month ■ Quarter Do not consider data during schedule down time Sub Report Title Add Sub Report See Table 70 on page 295. Data is validated against the specified custom range.Report types available in BMC ProactiveNet Attributes Hide Attribute Name and Column Distribution range based on Threshold Description Select this option to hide attribute name and column during report display. Data to be used for calculation See Table 70 on page 295. Chapter 7 Generating Reports 311 . Select this option to break down the report display. This option is displayed only if the distribution range is based on thresholds. Select this option to consider specified event thresholds with percentage distribution of instance attribute values. On selecting this option distribution range is displayed and you can select the range from the list. Select this option to generate report for a specific event severity. Report displays instance attribute values for the specified custom range in the form of multiple stacked bar graphs.

The graph lists all events consolidated. Table 86: Event default report types Default Event Report Types Critical Events for Previous Day Description ■ Report Type: Event ■ Report Frequency Daily ■ Duration: Day Critical Events for Previous Week Note ■ Report Type: Event ■ Report Frequency Weekly ■ Duration: Week Table 87 on page 313 lists attributes specific to Event report that should be specified along with the common attributes. Drilldown from the bars of the graph shows events in that time interval block.5. The Event Report shows events that occurred during a specified time period. The report consists of a stacked bar graph indicating the number of events on the Y-axis and time period on the X-axis based on the inputs. see Acknowledging events on page 122.Report types available in BMC ProactiveNet Event Events are of two types. BMC recommends that you use BMC ProactiveNet Performance Management Reporting Studio to generate Event Reports.1 of BMC ProactiveNet to version 8. The Event Report is available only if you are a BMC ProactiveNet user upgrading from version 8. External events coming from a device known to the BMC ProactiveNet server will be automatically associated to that device. If you are a new BMC ProactiveNet version 8. irrespective of their multiple occurrences in the bars of the graph.5 user. External events are those that are received from third party device and Intelligent events are those that are generated from the BMC ProactiveNet server. External and Intelligent events. To see the severity and status history when you drill-down from the status.0 or 8. Drilldown from a multiple options bar graph shows the list of events of the respective options. 312 BMC ProactiveNet User Guide .

■ Intelligent Events: Lists the BMC ProactiveNet events only. Attributes to report on ■ No Filter—includes all the events on all monitored instances during generation of the report ■ Single Attribute—see Table 70 on page 295. ■ Devices—see Table 70 on page 295.Report types available in BMC ProactiveNet Table 87: Event report attributes Attributes Event Selection Description ■ All Events: Lists both BMC ProactiveNet and external events. Filter Options ■ Intelligent Events ■ All Events — Events Associated with Device—includes only events associated with a device known to BMC ProactiveNet server — Events Not Associated with a Device—includes events that are not associated with a device which are generated from a third party ■ No Filter—includes all events during generation of the report ■ Groups/Services—see Table 70 on page 295. ■ Attribute Set—see Table 70 on page 295. External events refer to device-associated events and events received from external event adapters. ■ Consider Dynamic Attributes if any (applicable only to select monitors)—includes events on all Dynamic attributes for the selected monitors ■ Priority—includes the events with the selected priority ■ Consider Events with Duration Greater Than:—includes all the events that are open for more than the time duration specified Chapter 7 Generating Reports 313 .

Hence. Select any of the following severities to be considered for the report: — Critical — Major — Minor — Warning — Information — OK ■ Graph Options — Show only Graph—only displays the graph — Show only Table—only displays the table ■ Granularity—controls the number of time intervals that the report is divided into — By Hour—one bar of the graph will represent the number of events that occur within an hour — By Day—one bar of the graph will represent the number of events that occur within a day The PDF option for event reports is disabled. the PDF option in E-mail Options (page 3 of 3) while creating or editing a report will not work. Note 314 BMC ProactiveNet User Guide .Report types available in BMC ProactiveNet Attributes Display Options Description ■ Status — Open: Lists only the events which are not closed — Assigned: Lists only the events that are assigned — Acknowledged: Lists only those events that are acknowledged — Closed: Lists only those events that are closed — Blackout: Lists only those events that are blackout ■ Severity—determines the severity level of the report.

The Health Summary report consists of multiple sub-reports (if multiple groups – attribute sets – severity combinations have been specified). Performance is based on the total violation time for that instance.Report types available in BMC ProactiveNet Health Summary The Health Summary report shows all monitor instances for a specified group (in order of worst at the top to least worst at the bottom) in terms of violation of threshold over a specified time period. Table 88: Health Summary default report types Default Health Summary Report Types Application Infrastructure Health Description ■ Report type—Health Summary ■ Report frequency—Weekly ■ Duration—Week ■ Sub-reports (apply to all instances) — Health Summary for End User Availability — Health Summary for End User Response Time — Health Summary for Application Infrastructure Availability — Health Summary for Application Infrastructure Response Time — Health Summary for Application Infrastructure Performance — Health Summary for Infrastructure Availability — Health Summary for Infrastructure Performance Chapter 7 Generating Reports 315 . Table 88 on page 315 lists Health Summary default report types. In this case. a summary bar graph at the top (if selected for display) of the Top N violator is available for each sub report.

Consider Dynamic Attributes only Select this option to include dynamic attributes. 316 BMC ProactiveNet User Guide .Report types available in BMC ProactiveNet Default Health Summary Report Types Application Infrastructure Hot Spots Description ■ Report type—Health Summary ■ Report frequency—Daily ■ Duration—Day ■ Sub-reports — Health Summary for End User Availability (Critical and Above) — Health Summary for End User Response Time (Minor and Above) — Health Summary for Application Infrastructure Availability (Critical and Above) — Health Summary for Application Infrastructure Response Time (Minor and Above) — Health Summary for Application Infrastructure Performance (Minor and Above) — Health Summary for Infrastructure Availability (Critical and Above) — Health Summary for Infrastructure Performance (Minor and Above) Table 89 on page 316 lists attributes specific to Health Summary report that needs to be entered along with common attributes. If the check box is not selected. Intelligent Event Threshold Select this option to restrict report generation to a specific severity level. Table 89: Health Summary report attributes Attributes Select Group Single Attribute Attribute Set Description See Table 70 on page 295. Custom Threshold Show All Instances Select this option to restrict instance violation. See Table 70 on page 295. See Table 70 on page 295. Select this option to view all instances matching the input criteria. When All severity threshold type is selected the severity column is displayed and a table title is added displaying severity of each instance. then only violated instances are displayed.

Select one of the values to be displayed on the graph. See Table 70 on page 295. See Table 70 on page 295. See Table 70 on page 295. See Table 70 on page 295. in terms of the average value over a specified time period. Top Bottom Performers The Top/Bottom Performers report displays all attribute or monitor instances of a specific monitor type of a group. as a bar graph. See Table 70 on page 295. Table 90 on page 317 lists attributes specific to Top Bottom Performers report that need to be entered along with common attributes. Select this option to filter and view violations that meet the criterion in terms of absolute time or percentage of report period time violated. See Table 70 on page 295. See Table 70 on page 295. Table 90: Top Bottom Performers report attributes Attributes Select Group Attributes to Report on Graph Type No of Bars Values to be Displayed Show Table containing the list of instances Do not consider data during Schedule DownTime Sub Report Title Data to be used for calculation Description See Table 70 on page 295. See Table 70 on page 295.Report types available in BMC ProactiveNet Attributes Show Graph along with the Table Do not consider data during Schedule DownTime Select columns for the table Sub Report Title Add Sub Report Data to be used for calculation Show only rows with duration greater than Description Select this option to indicate the presence of a summary bar graph in the sub-section of the report. Flag rows with duration greater than Maximum number of entries to be displayed in the table Select this option to flag rows corresponding to violations that meet the criterion in terms of absolute time or percentage of report period time violated. Select this option to filter the maximum number (top N) of rows in the table. See Table 70 on page 295. This option is applicable only for sub reports added without selecting the Show all instances option. Select the number of bars from the list to be displayed on the graph. Chapter 7 Generating Reports 317 . Select this option to view a list of related tables. Select the column options to be displayed in the table.

on a periodic basis. resource pools and their relationships. the sub report generated with that option will be empty. 318 BMC ProactiveNet User Guide . This report also lists the various configuration attributes and supports drill down to individual line graph. Table 91 on page 319 lists attributes specific to Virtual Inventory report that should be specified along with the common attributes.Report types available in BMC ProactiveNet Virtual Inventory The BMC adapter for VMWare remotely monitors the Virtual Center (VC) or ESX server (host) using web services and discovers the VMWare entities such as ESX servers. The Virtual Inventory Report lists the virtual entities such as ESX Hosts or VMs. clusters. ■ Resource Pool and VMs for a given VC(s) group and will display the logical view ■ Cluster and ESX Hosts for a given VC(s) group and will show the logical view of the devices. of the devices. Virtual Machines (VMs). If an ESX Host exists without VMs underneath it. Clusters or ESX Hosts and ResourcePools/VMs. The report will list ■ ESX Hosts and VMs belonging to the Hosts for a given VC(s) group and will Note display the physical view of the devices. along with their performance attributes. The ESX in clusters have a drill down to the VMS underneath it.

which shows the compliance distribution of the SLO Instances over the report period. Daily or Weekly baselines for generating the report. Select either Hourly. The baseline data is used for computation. You can search for the available attributes in the Search for field. ■ Bar Graph. ■ Show Virtual Entities—displays the entities you select. which shows the compliance distribution of the SLO Instances for the granularity selected. Drill down on the pie graph displays a summary table based on the distribution ranges over the entire report period. By default common attributes for the entities selected are in the Selected Attributes box and the Available Attributes box lists all the uncommon attributes of the entity pair. ■ ESX Hosts/VMs ■ Resource Pools/VMs ■ Clusters/ESX Hosts ■ Select Attributes—add or delete attributes to be included in the report. See Table 70 on page 295. This report displays the following for each SLO type selected: ■ Pie Graph. SLO Application Compliance Report The SLO Application Compliance Report displays SLO Compliance information of an application. Drill down on any bar in the stacked bar graph displays a table based on the distribution ranges over the granularity. This table is a list of all the SLO instances for that distribution range sorted on their compliance values. This table is a list of all the SLO instances for that distribution range sorted on their compliance values over the entire report period. ■ Sub Report Title—specify the title for the sub report Add Sub Report Report Options Consider Baseline See Table 70 on page 295.Report types available in BMC ProactiveNet Table 91: Virtual Inventory report attributes Attributes Sub Report Selection Description ■ Available Groups—shows a list of all groups. Each SLO Type for the SLO is displayed in a sub section. The common attributes for a given pair of entities change when you specify a different entity. However auto-created groups by VMware group has the type of group listed in parenthesis against each group. Chapter 7 Generating Reports 319 . Select the group that will be considered to generate the report. The Attribute set is depends on the entity pair selected for the Virtual Inventory report (ESX Hosts/VMs or Resource Pools/VMs or Clusters/ESX Hosts).

Specify the granularity for bars displayed in the graph. A dotted line from the intersection point to the X axis will also be present. Enter attributes list in Table 93 on page 320. use the Search For box to locate a specific SLO. The X axis shows the duration to violation (in days). Specify the SLOs to be considered while generating the report. 320 BMC ProactiveNet User Guide . Drill down on the monitor instance in the table displays a line graph for the selected attribute along with the threshold line. which are predicted to violate earliest (in any violated instance are present. Table 93: SLO Capacity Trends attributes Attributes Select SLO Description Select an SLO from the list or select All to consider the entire SLO. This filter is available only when All SLOs are being considered for the report. See Table 70 on page 295. For All SLOs. use SLO Type filter to select the SLO Types. Use Ctrl and Shift keys to make multiple selections. A table which shows the time when each attribute (in the selected SLO Type) for each monitor instance will violate SLO Threshold along with other details appears below the bar graph. Each instance–attribute pair predicted to violate the SLO Threshold in the specified time period are displayed as a bar on the Y axis. This filter is available only when All SLOs are being considered for the report. A single SLO name or multiple SLO names can be selected. The report contains a bar graph. For All SLOs. Available SLO Select the SLO to be considered from the Available SLOs box and transfer to the Selected SLOs box. The table is sorted with instances. Alternatively. Sub Report Title Add Sub Report Delete Sub Report Show data broken down SLO Capacity Trends Report SLO Capacity Trends report lists all monitor instance–attribute pairs that are predicted to violate the SLO threshold in the specified time period. they would appear first). use SLO Type filter to select the SLO Types. A single SLO name or multiple SLO names can be selected. See Table 70 on page 295. Attribute that are not expected to violate the SLO Threshold will not appear in the bar graph or the table. See Table 70 on page 295. The line graph is projected using a dotted line from the last data point to the threshold line and the intersection point is at the predicted violation time.Report types available in BMC ProactiveNet Table 92: SLO Application Compliance attributes Attributes Select SLO Description Select an SLO from the list or select All to consider the entire SLO. Specify the SLOs to be considered while generating the report.

This filter is available only when All SLOs are being considered for the report. A single SLO name or multiple SLO names can be selected. (Link will be provided at the time of document collation). ordered bar graphs. Available SLO Select the SLO to be considered from the Available SLOs box and transfer to the Selected SLOs box. Enter the attributes listed in Table 94 on page 321. Show data broken down SLO Compliance Matrix The SLO Compliance Matrix report displays the compliance summary of selected SLOs. The report contain multiple. Use Ctrl and Shift keys to make multiple selections. which will show the SLO compliance values corresponding to a particular day. one for each SLO. Any instance predicted to violate SLO Threshold in this time period appears in the report. Hide Resource Column Do not consider data during Schedule DownTime Show instance which will violate in next Use Data for the last Maximum number of bars in graph Specify the maximum number of bars that are to be displayed in the bar graph. Any violations outside this forecast period are not considered. This is the forecast period. use the Search For box to locate a specific SLO. month. Specify the granularity for bars displayed in the graph. Specify the time period for which data points are to be used for forecasting.Report types available in BMC ProactiveNet Attributes Available SLO Description Select the SLO to be considered from the Available SLOs box and transfer to the Selected SLOs box. use SLO Type filter to select the SLO Types. For All SLOs. Drill-down to SLO Health Summary report for the corresponding time period is available for from each bar in the bar graph. Use Ctrl and Shift keys to make multiple selections. Select this option if you do not want the Resource column to displayed in the report. Administrator Guide. SLO Compliance History SLO Compliance History report lists compliance values for specified set of SLOs for the specified time period. Specify the SLOs to be considered while generating the report. Alternatively. Chapter 7 Generating Reports 321 . Table 94: SLO Compliance History attributes Attributes Select SLO Description Select an SLO from the list or select All to consider the entire SLO. week. The graph also displays a line corresponding to the compliance objective of the SLO. At least one time period must be selected to generate this report. Alternatively. use the Search For box to locate a specific SLO. or quarter within the specified time period for a particular SLO. The report mainly displays SLO details and the recorded compliance levels for different periods chosen. For further information see.

322 BMC ProactiveNet User Guide . Table 95: SLO Compliance Matrix attributes Attributes Select SLO Description Select an SLO from the list or select All to consider the entire SLO. This filter is available only when All SLOs are being considered for the report. Enter the attributes listed in Table 95 on page 322. use the Search For box to locate a specific SLO. Clicking the SLO name in the summary table displays its instance compliance details in a separate page. SLO instances having array-type attributes are displayed in separate tables (a table for each instance) with the instance name displayed as the table title. Use Ctrl and Shift keys to make multiple selections. Available SLO Select the SLO to be considered from the Available SLOs box and transfer to the Selected SLOs box. Web transactions have dynamic or array-type attributes and sub transactions. use SLO Type filter to select the SLO Types. Click the Show Compliance Matrix Report icon to view the Compliance Matrix report. Only the SLO compliance details summary table is displayed in the report page.Report types available in BMC ProactiveNet The report also displays compliance details of instances of the SLOs listed. on the Compliance Matrix page Hide SLO Type Column Show icons instead of numbers for Select this option to display icons instead of numbers to depict SLO the SLO Compliance values compliance values. For All SLOs. A single SLO name or multiple SLO names can be selected. Select this option if you do not want the SLO Type column to be listed in the report. Clicking the History column in the report displays the SLO Compliance History report for the SLO. Alternatively. Clicking the Graph column displays the line graph for the SLO. So. Specify the SLOs to be considered while generating the report.

■ Previous Month . ■ Month to Date . ■ Previous Week .Select this option to create the report based on SLO compliance values of the previous week. Performance is based on the absolute percentage compliance or the delta from desired percentage compliance.Select this option to create the report based on data collected during the previous quarter.Select this option to create the report based SLO compliance values of the last seven days.Select this option to create the report based on data collected during the previous year. Chapter 7 Generating Reports 323 . ■ Quarter to Date . excluding the current day. Drill-down to get more details in terms of a breakdown over the specified time period (see the SLO Compliance History report).Select this option to create the report based on SLO compliance values of the previous month. excluding the current day. The SLO names are present in the report instance details keyed to the serial number that appears in the X-axis of the graph.Report types available in BMC ProactiveNet Attributes Select history periods to be displayed in the table Description ■ Previous Day . excluding the current day.Select this option to create the report based on data collected over the past one year. The sort order and the performance criterion can be specified during report creation.Select this option to create the report based on SLO compliance values of the previous day.Select this option to create the report based on SLO compliance values of the past three months. SLO Executive Summary SLO Executive Summary report lists all SLOs (or the selected set of SLOs) sorted based on their performance for the specified time period. ■ Year to Date . ■ Previous Year . The report contains a graph which shows each SLO's percentage compliance and compliance objective. ■ Previous Quarter .Select this option to create the report based on SLO compliance values collected over the past thirty days. ■ Week to Date . Table 96 on page 324 lists SLO executive summary default report type Worst Performing SLOs.

Based on this selection. Alternatively. Delta implies that the difference between the compliance objective and the compliance value for the SLO over the specified time period will be used for reporting. If the check box is clear. Absolute implies that the actual compliance values for the SLO over the specified time period will be used for reporting. A table below shows a complete list of all violated instances or a partial list of certain violated instances (if filters have been specified to limit the entries). A single SLO name or multiple SLO names can be selected. each of which may contain a summary bar graph at the top (if selected for display) which shows the top N violators. Specify the sort criterion (absolute or delta) to be used when calculating the SLO performance. either the top performing SLOs or the bottom performing SLOs (among the selected SLOs) will be graphed from left to right.Report types available in BMC ProactiveNet Table 96: Worst Performing SLOs default report type Default Worst Performing SLO Report Types Report Type Report Frequency Duration Description SLO Executive Summary Weekly Week Enter the attributes listed in Table 97 on page 324. This table may have selected instances highlighted 324 BMC ProactiveNet User Guide . then only details of SLOs present in the graph are displayed in the table. Use Ctrl and Shift keys to make multiple selections. use SLO Type filter to select the SLO Types. Maximum supported number is 20. Table 97: SLO Executive Summary attributes Attributes Select SLO Description Select an SLO from the list or select All to consider the entire SLO. Select or clear the check box to enable or disable the option to show all SLOs in the table. This filter is available only when All SLOs are being considered for the report. Sort Criterion Sort Based On Max No of SLOs Show all SLOs in the table SLO Health Summary The SLO Health Summary report shows all SLO instances (in order of worst at the left to least worst at the right) in terms of violation over a specified time period (with respect to SLO Thresholds). This is a consolidated list per instance–attribute and not a list of individual violations for every instance–attribute pair. For All SLOs. Specify the SLOs to be considered while generating the report. Specify the sort (top or bottom) criteria. use the Search For box to locate a specific SLO. The SLO Health Summary report consists of multiple sub-reports (if multiple SLOs have been specified). Available SLO Select the SLO to be considered from the Available SLOs box and transfer to the Selected SLOs box. This is the maximum number of SLOs that will be displayed in the graph.

Select Do not consider data during For further information see. Report Scheduler The Report Scheduler is responsible for triggering report generation at pre-set time intervals (Daily. Select this option to specify the presence of a summary bar graph in this sub-section of the report.hour – The hour of the day that the Daily Report should be Chapter 7 Generating Reports 325 . Administrator Guide.daily. This option is applicable only for sub reports added without selecting the Show all instances option. Flag rows with violation time greater than Maximum number of entries to be displayed in the table Select the columns to be displayed in the report. or Monthly). You can drill-down from any of the entries to the independent line graph. Default is 4. Raw data or Condensed (Rate) data is used for calculating the output values. Use this filter to flag rows in the generated report table based on the specified criteria.minute – The minutes of the hour (defined above) that the Daily Report should triggered. Use this filter to view only those violations greater than the specified time period. Select the column for the Table Hide Attribute Column Name Sub Report Title Add Sub Report Select Data to be used for calculation Show only rows with violation time greater than. Enter the attributes listed in Table 98 on page 325.Report Scheduler flagged based on input criteria. ■ pronet. Select this option to include all instances. See Table 70 on page 295. Select this option if you do not want the Attribute column to be listed in the report. Based on the selection. Specify the maximum number of instances to be displayed in the table. triggered. Default is 30. See Table 70 on page 295.daily. The following properties need to be set in the pronet. (Link will be Schedule DownTime provided at the time of document collation). Table 98: SLO Health Summary attributes Attributes Select SLO Show all instances Show Graph along with the Table Description Select an SLO from the list to be considered while generating the report.report.report. Weekly.conf file for the scheduler module to work: ■ pronet. The table has a limited list of entries based on the input criteria.

Additional options BMC ProactiveNet displays a series of icons on the header of each report.The day of the week (values from 1-7) that the Weekly ■ pronet.day .report. ■ pronet.report.report. Availability of these additional options are based on the report type (Scheduled Report and Preview Report.monthly.The day of the month that the Monthly Report should be triggered (valid number or a keyword ‘last’ for end of month).minute .hour .report.monthly. ■ pronet. Default is 1.report. Default is 0.day . Related Topics Show/Hide report header on page 327 Date drop-down on page 327 Deleting instances on page 327 Disable generation on page 327 Adding comments to a report on page 328 Scheduling on page 329 Adding a report to a view on page 329 Generating a report on page 329 Editing a report on page 330 Exporting to Portable Document Format (PDF) on page 330 326 BMC ProactiveNet User Guide .hour .minute . Default is 4.weekly.The minutes of the hour (defined above) that the Monthly Report should be triggered.monthly. Report should be triggered. Default is 1. ■ pronet.report.The minutes of the hour (defined above) that the Weekly Report should be triggered. Default is 45 ■ pronet.The hour of the day (the day is defined above) that the Weekly Report should be triggered. refer to Report Creation).weekly.Additional options ■ pronet. Default is 5.weekly.The hour of the day (the day is defined above) that the Monthly Report should be triggered.

Disable generation Use the Disable Generation icon to disable the generation of reports. by the Delete Instances option in the Reports screen. To delete Report Instances 1 Select the Date. click OK. Deleting instances This option is used to delete report instances. the second option is not displayed. there was an option to delete a report but not its instances individually. Chapter 7 Generating Reports 327 . Earlier to 7.1 version. 4 Click OK. 3 Select one of the following options: ■ Delete the selected report instance ■ Delete all previous occurrences for the report Note In case the report has only one instance. Date drop-down Select the Report period from the list. 5 On the Confirm dialog. 2 Click Delete Instances icon .Additional options Exporting to CSV on page 330 Mailing a report on page 331 Printing a report on page 332 Show/Hide report header Use the Show/Hide Report header icons to view or hide the header display. This is taken care in this release.

is displayed. the same is updated for the report and the Show Comments at option is not displayed for the report instance. 3 Click OK. To add a comment 1 Click the Add Comment icon . Add comments you want to associate with the report instance generated.99%. On a particular day. then the Report Instance Comments window displays the option. For example. due to power outage Availability falls below 99% and the server is considered to be in Bad state. Report Instance comments are always displayed after Global comments of the report. This creates hyperlinks for URLs in report comments. Click URL Tag to enclose URLs. indicating that the comment has been updated successfully. 2 Type in your comments and click OK. 328 BMC ProactiveNet User Guide .Additional options Adding comments to a report Use the Add Comment icon to access the Report Instance Comments window. A message. which are part of comments. consider an Element Distribution Summary report created to denote Availability of Solaris Processes on a server. The Report Instance Comments window is displayed. Use the Report Instance Comments window to indicate to other users that the overall health of the server is good and due to an unforeseen condition the server's condition was Bad for a day. If the Show Comments at option was not selected for a report. Report instances are to be generated Daily and the server is considered to be in Good state if the Availability is >=99. You can enter specific information that other users may benefit from by looking at that particular instance of the report. change the font size. If you select the option here and specify the location of comments. in tags. If required.

Once a report is added to a view. acknowledged. This icon is only available for reports where the On Demand option is selected during report creation. an event that is currently closed appears as open in the Status column of the generated because the event was open during the report generation period. to show the report as a single large report. Make changes as required in the Report Creation page.Additional options Scheduling Click the Schedule icon to schedule the report. 3 Select Show Detailed Report. Generating a report Use the Generate Report icon to generate a report. 2 Specify the view to which you want to add the report. Simply click the report in its View group. if the event is acknowledged and assigned before being closed during the report generation period. its parameters no longer need to be determined each time you want to view data in that manner. the Status column displays corresponding entries for the open. assigned. all these statuses show up in the selected Status column. If the event life cycle (opened. and closed) is contained within the report generation period. You can add the report to an existing view or a new view. Adding a report to a view Use the Add to View icon to add a report to a view. Similarly. acknowledged. Note Chapter 7 Generating Reports 329 . 5 Click Add to View. assigned. For example. and closed statuses. To add a report to a view 1 Click the icon to launch the Add this Report to View pop-up window. This is disabled when you select Show Detailed Report. 4 Select the Layout Type.

3 Click Save to save the report in CSV format. If reports with instance names containing commas are exported to CSV. 330 BMC ProactiveNet User Guide .pdf extension for further action. For operational steps to edit report. 4 Click Cancel to abort action. 2 On the message screen.Additional options Editing a report Use the Edit Report icon to edit the report. Exporting to Portable Document Format (PDF) Use the PDF icon to save the report in PDF. 2 Save the report with the.0 to use the Export to PDF function effectively. BMC Software recommends Windows 2000 Service Pack 3 and Adobe Reader 6. disabled for new customers. Note ■ Sometimes the Export to PDF function may not work properly on a system running Windows 2000 Service Pack 4. the PDF option is available only for upgrade customers and is Exporting to CSV Use the CSV icon to export report data to a excel sheet. ■ In Event reports. To export report to CSV 1 Click the CSV icon. click Open to view the report in CSV format. To save report in PDF 1 Click PDF icon. refer to the Report Administration topic. the values are shifted to the next column.

Copy the pronet.conf file is enabled. ■ If the mail size is too large the mail will not be delivered. Chapter 7 Generating Reports 331 .Additional options Mailing a report To mail a report 1 Click the Mail this Page icon to display the Mail Details for Snapshot window.manageAllReports. 4 Email address: The receivers' email address. This is a Microsoft Managing all reports The Administrator/Admin class users can now manage all the available reports (including private reports) that is. and on the menu click Other Actions. 5 Message: A brief message description sent via mail either in HTML or Plain text format. To manage a report 1 Click the Manage All tab to display the Manage all Reports window. click Tools => Options => Security and click Change Automatic Download Settings. limitation. disable and delete these reports. Select View in browser option to view the mail in Internet Explorer in HTML format.option=false property from the Pw \pronto\conf\pronet.conf file to pw\custom\conf\pronet. enable. The Manage All tab is visible only when the conf entry in the pronet. ■ In Outlook 2007 double-click the message. ■ In Outlook 2003 to view a report in email. All reports (except SLA reports if the license is not valid) are displayed. reportType reportName is displayed as the subject of the email. 3 Subject: The subject line of the email. By default the value is set to "false" .conf and set the value to "true". Deselect Don’t download pictures or other content automatically in HTML email. Note Change the following settings for Outlook 2003 and 2007 only if the report is not properly displayed in the mail. 2 From: The report sender's e-mail address. By default. The Automatic Download Settings screen is displayed.report.

In case attributes associated with a monitor created through Monitor Wizard are changed after Asset Report creation. BMC ProactiveNet recommends that default reports should not deleted from the system. Pruning a report The prune period for reports is as follows: ■ 1 month: for daily reports ■ 6 months: for weekly reports ■ 2 years: for monthly reports The prune period for events is set to 7 days by default. Points to Remember ■ Default reports cannot be restored once deleted. For Upgrades. The options will only be for 2d and 3d bar. all line and scatter plots will be displayed as 3D bars. Asset report continues to report on the original attributes. click the Print icon . still be valid when the attribute was modified in the VAM monitor type. ■ BMC ProactiveNet 7. disable or delete the reports. ■ Asset Reports do not track changes made to the Monitor Wizard based monitors. hence the Admin user will not be able to navigate through the reports. There will be no hyperlinks for the reports. To retain a report for more than 7 days.Points to Remember 2 Select the check boxes against the reports to enable. change the prune period using pw commands. Line and Scatter plot is not used for displaying objective and values. Note Printing a report To print the report. See the BMC ProactiveNet Administrator Guide for more information about CLI commands.0 uses stacked bars for displaying objective and value. ■ The old attribute references from a VAM monitor type added to Asset report will 332 BMC ProactiveNet User Guide .

Please note. ■ BMC ProactiveNet does not support use of special characters for sub-transaction For non-restricted users. change the archive settings using pw commands (pw log period). names. To generate reports based RAW data for longer periods. In case. report is not generated. increasing the archive period has performance impacts. any of the report includes web transaction monitors with special characters in the sub-transaction names. and is not recommended. the Operations Console displays the following reports in the Reports list page: ■ All public reports (irrespective of who created the report) ■ All reports that are shared with the user group (irrespective of who created the report) ■ Any private reports created by this user. Chapter 7 Generating Reports 333 .Points to Remember ■ RAW data is archived after 8 days. BMC ProactiveNet recommends using RATE data for generating reports for longer periods.

Points to Remember 334 BMC ProactiveNet User Guide .

SLOs measure the performance of the service provider and are outlined to avert disputes between the two parties on misunderstanding. Predefined and custom-defined indicators (SLO types. Seamless integration with Violation Summary and Probable Cause Chapter 8 Managing service levels 335 . SLO views complement existing infrastructure-centric application management solutions. Service level view enables you to take a proactive approach to meeting SLOs. With new business views. The SLO Management Console The SLO Management Console provides an integrated view of all SLOs.8 Managing service levels What is an SLO? A service level objective (SLO) is a key component used to evaluate. This view provides valuable information on performance status from an end users’ perspective for each business unit and SLO compliance. SLO administration is the first step in integrating the SLO with the BMC ProactiveNet system. and maintain acceptable service levels and compliance with service level agreements (SLAs). grouping of required attributes and metrics) present a relational view of objectives and the actual status of SLO compliance. and track SLOs. The views represent application performance metrics in a way that relates the IT and line of business teams as a close working unit on which the company depends. SLO business views help define. business structures are available in a top-down hierarchical view that delivers near real-time service level views of application and service metrics. SLO views also represent application performance levels and service levels committed to within the organization. BMC ProactiveNet monitors and reports on the various aspects of SLOs. monitor. BMC ProactiveNet enables you to define SLOs in the BMC ProactiveNet system. measure.

The SLO Management Console Analysis within SLO views help extend the IT capability to troubleshoot and pinpoint problems quickly as SLO violations occur. see To recalculate an SLO on page 349. For more information. there is a provision to select a Dashboard View from Options in the SLO Mgmt console. you can add the following pages as tabs Reports Enables you to view the reports for an individual SLO Enables you to view the details of SLO violations Displays SLO records with computed delta values (difference between the compliance objective and its value for the time unit) Viewing a graphical history of SLO compliance and violations on page 360 Viewing violation details for an SLO on page 355 Comparing compliance objectives with actual results on page 358 Violation Details Watch List Also. For example. Table 99: Navigation tabs in the SLO Management Console Navigation tab Current Status Description Provides the latest view of the performance of various SLOs configured in the system Provides a hierarchical tree presentation of SLOs for a user-defined time duration Provides various options for the administration of SLOs in BMC ProactiveNet Summarizes details for all top-level SLOs created in the system Further information Viewing the current status of SLOs on page 351 Viewing SLOs in a hierarchical tree on page 361 Managing SLOs on page 337 Tree SLO Administration Compliance Matrix Viewing SLO compliance details and history on page 352 Also. Product Short computes SLO compliance at the end of each day. 336 BMC ProactiveNet User Guide . 2009. 2009 is available only on September 11. computation of compliance for September 10. Customizing basic settings for SLO data display Using the Options screen. you can customize various aspects of SLO data display. Table 99 on page 336 presents the default tabs that are available in the SLO Management Console and additional tabs that you can define. and discusses their functions.

d Optionally. However. 4 Click Apply. move. you can manage all the SLOs monitored by BMC ProactiveNet. Note You can add multiple tabs only for Current Status. SLO Details. Table 100 on page 337 summarizes the available settings. b Click Add Tab. to delete a tab. c Optionally. and then click Delete Tab(s). select the tab in the Selected Tabs box. a Select an item from the General. Related Topics Creating or editing an SLO on page 338 Deleting SLOs on page 341 Chapter 8 Managing service levels 337 . Table 100: Basic configuration for SLO data display Setting Show Device name with Monitor Description To view device names on all Service Management screens Show icons instead of numbers for the To view a compliance icon instead of percentage in numbers SLO Compliance Values 3 Under Tab Selection. to change the order of tabs in the console. modify the settings as necessary. perform the following substeps to add. Managing SLOs Through the SLO Administration tab on the SLO Management console. 2 In the SLO Mgmt tab. under Display Preferences. use the arrows to the right of the Selected Tabs box. you must specify a different name for each tab. or Views box. and delete the items to be displayed as tabs in the SLO Mgmt console.Managing SLOs To customize SLO data display 1 Click the Options link at the top right of the Operation Console.

and then click Next. Table 101: Attributes for defining an SLO SLO attribute Name Owner Contact Information Description A unique name for the SLO Name of the user who owns the SLO Phone number or email address of the SLO owner 338 BMC ProactiveNet User Guide . For all other SLO attributes. you can accept the default settings. click the SLO Administration tab.Managing SLOs Managing SLO types during SLO configuration on page 341 Managing schedules during SLO configuration on page 342 Managing range sets during SLO configuration on page 344 Requesting guidance for setting SLO thresholds on page 345 Recalculating SLO data for modified time periods on page 348 Resetting SLO compliance data on page 350 Creating or editing an SLO A special wizard on the SLO Administration tab guides you through the task of defining a new SLO or editing an existing SLO. click Add. specify or modify the SLO attributes summarized in Table 71 on page 297. click Edit. 2 Click the relevant option: ■ For a new SLO. ■ To edit an existing SLO. To create or edit an SLO 1 On the SLO Management console. Note Only the fields indicated by a red asterisk are mandatory. 3 On the first screen (Step 1) of the SLO wizard.

Select the schedule to apply to SLO monitoring. See Managing SLO types during SLO configuration on page 341. 5 Select the Monitor Instances to add to the SLO. See Managing schedules during SLO configuration on page 342. This allows you to set threshold values for different time periods. If required. Create corresponding Response Time SLO Schedule Select this check box if you chose Availability as the SLO type and want a corresponding Response Time SLO created. 6 On the third screen (Step 3) of the SLO wizard. and System Performance.Managing SLOs SLO attribute SLO Contents Description Type of objects that comprise the SLO. If you choose SLOs. and not to calculate Aggregate Compliance values option. You can add other types or edit the attributes of the SLO types at this point. You can add other schedules or edit the attributes of the schedules at this point. you can modify any of the SLO values summarized in Table 71 on page 297. The grouping can include SLOs based on instances and other nested SLOs. you can create an SLO only for classification by selecting the Use this SLO for grouping only. or if you chose Response Time as the SLO type and want a corresponding Availability SLO created. Response Time. See Managing range sets during SLO configuration on page 344. Basic schedules are 24X7 and Business Hours. Response time threshold values may not be the same during business and non-business hours.Range Set Percentage of compliance or non-compliance (as indicated and based on the SLO type) that the SLO must obtain You can add other range sets or edit the settings of the user-defined ranges at this point.Objective SLO Compliance . and then click Next. Copy from Services/Groups SLO Type Check this option and select between services or groups to copy from the existing services or groups. select one or more Group Filter and at least one Monitor Type to associate with the SLO. SLOs or Instances ■ SLOs based on instances form base-level SLOs ■ SLOs based on SLOs provide a consolidated view of related SLOs. and then click Next. 4 On the second screen (Step 2) of the SLO wizard. The type of SLO based on the groups to which it is associated Basic SLO types are Availability. For example. This option is static and acts as a filter. you can select multiple schedules. Chapter 8 Managing service levels 339 . SLO Compliance .

8 If you are defining Transaction Monitors. select the relevant sub-transactions and click Delete Sub-Transactions. if Attributes A. enter values in the fields below the table as described in Table 102 on page 340 and then click Apply. For guidance on setting values based on compliance values recommended by Product Short for the selected monitor instances. 10. and B is twice as important as A. and then click OK in the confirmation message.Managing SLOs ■ To modify a specific SLO. Table 102: Configurable SLO values Setting Service Level Objective: Condition Service Level Objective: Value Minimum Duration Description Condition using which SLOs are compared with actual measurements. click SLO Guidance. Only after the SLO value has continued to stay in the violation range for a period greater than the minimum duration it is reported as a violation. and then specify the severity and duration for the event. such as a Web Transaction. select sub-transactions from the displayed list and click Apply. select the Set corresponding Instance Intelligent Event Threshold option. and 15 (respectively). Financial Impact Amount of financial loss (per hour) caused if the SLO condition is not met Tip Weight 7 If you want intelligent event thresholds created for all the listed SLO. either Greater than or equal or Less than or equal SLO value (a percentage) for the instance or attribute Time period for validating the SLO violation. For more information. then Attribute C is thrice as important as A. For example. enter values directly in the displayed table. 340 BMC ProactiveNet User Guide . you can now add (and subsequently delete) sub-transactions on the displayed list. Weight associated with the SLO attribute. B. 9 To add a sub-transaction. specify a weight of zero. click Add Sub-Transactions. 10 To delete sub-transactions. see Requesting guidance for setting SLO thresholds on page 345. and C have associated weights of 5. ■ To modify multiple SLOs. a whole number greater than zero Associated Weights define the relative importance of an attribute within the SLO (for computation requirements). To ignore SLO violations during computation.

and then click Next. add new monitor types and attributes to any existing SLO Type. and System Performance. select the attributes to associate with the SLO Type. Chapter 8 Managing service levels 341 . BMC ProactiveNet provides three default SLO Types: Availability. Deleting SLOs To delete a SLO 1 Select the check box under the Select column corresponding to the SLO that you wish to delete. 6 In the confirmation dialog box. 3 From the list of attributes corresponding to the selected Monitor Type(s). The new SLO is created and displayed in the SLO list on the SLO Administration screen. You can create new SLO Types during the configuration of an SLO as described in Creating or editing an SLO on page 3383. Managing SLO types during SLO configuration An SLO Type is a grouping of related attributes across different monitor types registered with Product Short. To define a new SLO Type 1 On the first screen (Step 1) of the SLO wizard during SLO configuration. 3 In the confirmation dialog box. click OK. 4 Specify a name for the attribute set. click OK. 2 Click Delete. 2 Select the Monitor Type(s) to associate with the SLO Type.Managing SLOs 11 Click Finish. Response Time. 5 Click Finish. that is. You can also edit existing SLO Types. click New beside the SLO Type field. Each SLO has one associated SLO Type. and then click Next. An SLO Type defines the attributes to include in compliance calculations.

and then click Next. to 5 P. e Click OK. click OK. 3 Optionally.M. perform the following substeps to delete attributes associated with the selected SLO Type: a Select all relevant attributes. and then click Next. 342 BMC ProactiveNet User Guide . c From the list of attributes corresponding to the selected Monitor Type(s).M. d Click Finish.Managing SLOs To edit an existing SLO type 1 On the first screen (Step 1) of the SLO wizard during SLO configuration.M. A schedule can include multiple time periods for inclusion or exclusion. an SLO with the 24x7 schedule will consider all recorded monitored attribute values for SLO computation.M. d Click Finish. b Select the Monitor Type(s) to associate with the SLO Type. for 5 days a week (Monday to Friday) will consider the monitored attribute values recorded between 9 A. c In the confirmation dialog box. select the attributes to associate with the SLO Type. and 5 P. another SLO with a schedule of 9 A. Managing schedules during SLO configuration A schedule is a defined period of time used by BMC ProactiveNet to consider recorded monitored attribute values for SLO computations. and then click Edit. Schedules help put SLO compliance computation in the right perspective without distorting the values by including invalid periods. For example. in the Edit AttributeSet screen. 2 In the Edit AttributeSet screen. However. e Click OK. perform the following substeps to add attributes: a Click Add Attributes to add new attributes to the selected SLO Type. Monday to Friday only. select the SLO Type from the list. b Click Delete..

select the relevant option: ■ To create a new schedule. e Click Close. click OK. You can create new schedules or edit existing schedules during the configuration of an SLO as described in Creating or editing an SLO on page 338. select a schedule that you wish to delete from the list. click New beside the Schedule field. To delete a time period included in the schedule. 3 Perform the following substeps to define time periods for inclusion or exclusion: a For inclusion. select the schedule in the list. ■ To edit an existing schedule. 2 Specify (or modify) a name for the schedule. 3 In the confirmation box. Exclusion periods take precedence over inclusion periods. 4 Click OK. Chapter 8 Managing service levels 343 . for exclusion. or a monthly recurrence of days and times to be excluded. b Optionally. select it in the list and click Delete. click Done. d After adding all relevant time periods. 2 Click Delete Schedule. define the start time and end time of the period during one or more days of the week. and then click Edit. To define a new schedule or edit an existing schedule 1 On the first screen (Step 1) of the SLO wizard during SLO configuration. and then click Edit. define either a one-time exclusion time period by specifying the start date and time and end date and time.Managing SLOs BMC ProactiveNet provides two default schedules: 24x7 and Business Hours. c Click Add to add the period to the list of time periods within the schedule. Note Tip To delete a schedule 1 On the first screen (Step 1) of the SLO wizard during SLO configuration.

click New beside the Range Set field. select the relevant option: ■ To create a new range set. The From Range field is auto-populated. 344 BMC ProactiveNet User Guide . select the range set in the list. 3 Select the severity and specify the upper limit of the range in the To Range field. To delete a range from the list of defined compliance ranges (starting with the last defined range). 5 Repeat List item. 4 Click Add Compliance Range to add the range to the list of defined compliance ranges on the right. 2 Specify (or modify) a name for the range set. See Creating or editing an SLO on page 338. on page 287 for all other relevant ranges in the range set. select the range set in the list.Managing SLOs Managing range sets during SLO configuration You can create new range sets or edit existing range sets during the configuration of an SLO. ■ To edit an existing range set. and then click Edit. click OK. 2 Click Delete Range Set. click Remove Compliance Range. Note To delete a range set 1 On the first screen (Step 1) of the SLO wizard during SLO configuration. and then click Edit. on page 287 and List item. 6 Click Done. 3 In the confirmation dialog box. To create a new range set or edit an existing range set 1 On the first screen (Step 1) of the SLO wizard during SLO configuration.

Managing SLOs Requesting guidance for setting SLO thresholds During SLO configuration. 2 Select the Suggest Thresholds for SLOs option. 3 Select the thresholds that you want to apply to your SLO. the value is highlighted in red. Chapter 8 Managing service levels 345 . Threshold values are recommended based on raw data points collected for each monitor instance (by default. and then click OK. you can request guidance from in setting thresholds and defining compliance objectives based on past performance. and then click Apply. If the suggested value is inaccurate due to NO_RESPONSE data points. If a threshold was not suggested. You can choose between the following options: ■ Obtain automatic suggestions for SLO thresholds based on past performance and the overall SLO objective ■ Preview past compliance values for all instances ■ Display performance graphs for all instances To obtain automatic suggestions for thresholds 1 On the third screen (Step 3) of the SLO wizard during SLO configuration. from the last eight days). A list of suggested thresholds is displayed for the relevant monitor instances and attributes. click SLO Guidance. the value is highlighted in yellow. The thresholds that you chose to apply are highlighted in green.

By default. All compliance values are as of the end of the previous day.skipND property is set to true and SLO ignores NO_DATA points. see Creating custom graphs on page 249. 2 Select the Preview Past Compliance option. the recommended SLO value for the attribute is always 100%. and then click OK. ■ Changes in SLO compliance or threshold do not affect previously calculated values.businessview.Managing SLOs Note ■ Threshold values cannot be suggested for instances without any past data points. ■ Since data points of the Availability attribute are either 0 or 100%. ■ BMC ProactiveNet considers NO_DATA and NO_RESPONSE data points ■ By default. and then click OK. Compliance values are displayed for each monitor instance and the SLO as a whole. click SLO Guidance. when calculating the SLO compliance. SLO treats NO_DATA points as violations. but only new calculations. ■ Suggested threshold values may not be accurate if data points are repeated. 346 BMC ProactiveNet User Guide . Individual graphs are displayed in the Graph Display window for each monitor instance based on data collected over the last eight days. If you set pronet. the pronet. To preview past compliance values 1 On the third screen (Step 3) of the SLO wizard during SLO configuration. raw data points collected for the monitor over the past eight days are considered. The new values are displayed throughout the product even though the calculations are based on older values.skipND to false. 2 Select the Show Past Performance option. 3 Click Close. 3 Click Close. For more information. click SLO Guidance. To display graphs of past performance 1 On the third screen (Step 3) of the SLO wizard during SLO configuration.businessview.

■ All old compliance values are invalidated if the start of the week or quarter is ■ The corresponding default pronet.conf file. current date. the number of violated points in violation details may not ■ Problem not resolved only considers violation records corresponding to the ■ If the SLO uses any schedule other than a full day schedule. month-to-date compliance ■ Irrespective of the exact time of creation of the SLO.conf file. considers the days for which the SLO has been calculated only. ■ If an SLO is added in the middle of the month. Product Short requires the raw data of all the 24 hours for accurate calculation. As generation or computation happens the next day. the number of violated points in calculation and the number of violated points in violation details. valid entries are 0 to 11 (Jan to Dec). changed.Managing SLOs Key SLO Computation ■ Retention for stats data should be at least two days. violation records (if any) are available immediately on SLO creation.businessview. ■ Any change in Service Level Threshold values may result in a mismatch between ■ In case of server restart.conf entries are as follows: pronet. be accurate and may not match the number of violated points in calculation. ■ Any change to the start of week or quarter configuration after SLO creation may ■ When calculating Quarter to Date compliance and Week to Date compliance. Calculation begins on the next day after SLO addition. Product Short considers all data points for the day during computation. the starting month of the quarter and the starting day of the week is configured in the pronet.firstmonthofquarter=0 The above entry represents the first month of the quarter. Chapter 8 Managing service levels 347 . the number of violated points from calculation may not match the number of violated points in violations details. ■ Columns displayed in the Compliance Matrix are configured in the pronet. result in abnormal values for the current week or quarter. However. This abnormality is corrected from the subsequent week or quarter.

Managing SLOs ■ The corresponding default pronet.businessview. if a child SLO is recalculated. 348 BMC ProactiveNet User Guide .WTD. starting from the day when you changed the entry. ■ When you recalculate a parent SLO.conf entries are as follows: pronet.MTD. Similarly. its compliance values are reflected in the parent SLO also.firstdayofweek entry to begin the week on any other day (by default. Valid entries are: — Previous Day: PD — Previous Week: PW — Previous Month: PM — Previous Quarter: P — Previous Year: PY — Month to Date: MTD — Year to Date: YTD — Week to Date: WTD — Quarter to Date: QTD ■ Previous Quarter and Previous Year computations are started afresh from the date of upgrade to BMC ProactiveNet 7.QTD. all its child SLOs are also recalculated.1. Recalculating SLO data for modified time periods Use the Recalculate SLO option to: ■ Remove or add data collected during specific periods to SLOs ■ Calculate SLO values anew for multiple SLOs Note ■ SLO violation details are not regenerated after SLO recalculation.businessview. ■ If you change the pronet.YTD The above entry represents the periods to be displayed in the compliance matrix page on the Operations Console.showperiods=PD. Sunday is the first day of the week). do not recalculate SLOs for the week.

SLOs that you selected on the SLO Administration screen are displayed in the Selected SLOs field. if the external time range is to include data collected from 4 PM to 8 PM. 2 Click Recalculate. select the days for which you want to recalculate the SLO values. 5 Click Recalculate. If you click Recalculate without defining any external time ranges. The SLO will report data collected from 9 AM to 10 AM and 2 PM to 5 PM. the tool tip displays the SLO type and associated schedule. Note Chapter 8 Managing service levels 349 . Tip 4 If you want to include or exclude certain time ranges during the specified time period. When you mouse over the selected SLO. the data exclusion clause overrides the inclusion clause. for the same associated schedule. The external time range overrides the associated schedule of the SLO. if the associated schedule is to include data collected from 9 AM to 5 PM. Similarly. the SLO is recalculated based on the existing schedule associated with it. perform the following substeps: a Select either Inclusion or Exclusion. When you define a time range and apply it while recalculating an SLO. 3 In the SLO Recalculation screen. compliance values are recalculated using the external time range and the associated schedule. select the SLOs that you want to recalculate. the SLO will report data collected between 9 AM and 8 PM. For example. ■ BMC ProactiveNet allows you to recalculate data for a period of eight days. In the SLO Recalculation screen. and the external time range is to exclude data collected from 10 AM to 2 PM.Managing SLOs To recalculate an SLO 1 On the SLO Administration screen. b Set one of the following type of time ranges: ■ One-time Setting: A time range applicable for a period of days ■ Every Day: A time range applied to the individual days c Click Add to add the time range that you specified.

Compliance values of the server between May 9.Managing SLOs Example 'Chk Availability' is an SLO defined to check the availability of a server. select the time range that you want to delete.M. To exclude the server downtime and recalculate the SLO compliance values anew for the week.M. 2005 ■ Select External Inclusion or Exclusion Time Ranges: Exclusion. and 3 P.13.2005: 93% 05. and server compliance values fell below 90 on both days.2005: 94% 05.10.12.2005: 75% 05. 2005 are as follow: 05. On resetting SLO(s).M.M. 2 Click Delete.11. 350 BMC ProactiveNet User Guide . for some unscheduled maintenance tasks. all compliance values are lost.M. and End Time 3 P.2005: 95% The server was made unavailable on May 11 and May 12 between 12 P. This action is irreversible.09. to 5 P. the following values are used: ■ Select Days: From May 11. Every Day. 2 Click Reset SLO. select the relevant SLOs in the table. To delete a time range 1 In the SLO Recalculation screen. Resetting SLO compliance data Resetting an SLO clears all the compliance history that has been collected for the SLO since it was created. 2005 and May 13. 2005 to May 12. WARNING To reset the existing SLO(s) 1 On the SLO Administration screen.M. Start Time 12 P. The server is expected to be available (Compliance: >= 90%) during business hours (Schedule: 8 A.).2005: 76% 05.

On clicking Cancel. At an attribute level. Represents graphically the longest open violation (if any). the selected SLO is reset and not its referenced SLO(s). see Viewing a graphical history of SLO compliance and violations on page 360. ■ If you try to reset an SLO. You can use the Set Current Status Preferences option to customize the contents of the current status screen. you are prompted to reset all the references. Based on the user access level. you can create multiple versions of the SLO current status page. as summarized in Table 103 on page 351.Viewing the current status of SLOs Note ■ Reset SLO is not applicable to an SLO that is created for grouping alone. the current status screen displays all the SLOs (configurable) in the system against the SLO Name. For more information. Chapter 8 Managing service levels 351 . If you have selected more than one SLO. 3 In the confirmation dialog box. On clicking Continue. See Customizing the display of SLO status information on page 352. In case of an existing violation. Each version shows up as a separate tab in the SLO Management console (based on selection). click OK. Table 103: Columns of SLO status information on the Current Status tab Column Name Description Provides a link to the SLO Details page. You can select one SLO at a time or all the SLOs configured in the system. you are prompted to reset the child SLO attached to the parent SLO. and Response Time. Each SLO can be expanded further to view the instances linked to them. Viewing the current status of SLOs The Current Status tab on the SLO Management console provides the latest view of the performance of various SLOs configured in the system. By default. click the icon to view the violation details. Availability. which is referred by other SLO(s). Availability and Response Time for each SLO Current Status Problem Not Resolved Displays the current violation status for the SLO. click the hyperlink to view the Instance Details page. You can expand a nested SLO to view its associated SLOs. SLO status details are displayed in a table with several columns of information. all the SLO(s) are reset.

2 Select the SLOs for which you want to display status information. and Year to date. 3 Select the SLO Types for which you want to display status information. The Compliance Matrix tab summarizes SLO details in a tabular format as described in Table 104 on page 353. To customize the display of SLO status information 1 Click the Set Current Status Preferences icon. Month to date.Viewing SLO compliance details and history Column Previous Week Compliance Description Previous week compliance of the SLO. and the recorded compliance levels. Week to date. status. Previous week. 352 BMC ProactiveNet User Guide . Viewing SLO compliance details and history The Compliance Matrix tab on the SLO Management Console presents a summary of SLO data for all top-level SLOs created in the system. including SLO details. Customizing the display of SLO status information The Preference screen helps in configuring the current status display. the compliance is displayed as an icon or a number. 5 In the Other Options box. select the time periods for which to display status information. choose from the following options: ■ Show Trend for SLO Compliance: Displays trend analysis ■ Show Financial Impact: Includes a financial impact for measurement 6 Click Apply. 4 In the Time Period box. Depending on the Global setting. This option is at a user level and differs for each version of SLO current status. It can be configured to display any one of the following: Previous month. Quarter to date.

send an email. Displays the SLO compliance for the previous day Week to Date Month to Date Quarter to Date Year to Date Displays the SLO compliance for the previous week Displays the SLO compliance for the previous month Displays the SLO compliance for the current month Displays the SLO compliance for the current year Details Current Status History Objective Tip ■ To generate a printer-friendly version of the Compliance Matrix screen. Table 104: Columns of SLO information on the Compliance Matrix tab Column SLO Type Description Displays the name assigned to the SLO.Viewing SLO compliance details and history Note Compliance values for time periods do not include the data from the current date. Provides a link to the SLO Compliance History Report screen. Provides a link to the Violation Details screen in case of an open violation. It reflects the real-time Service Level Threshold violations at any level. schedule a report. Valid Statuses are: open (red icon) and closed (green dot). save the page as a PDF or CSV. Displays the compliance objective associated with the SLO. click . . click . click ■ To view the Compliance Matrix report. and graphical representations of the compliance levels across different periods (depending on data collected to date) and the SLO Violation history Displays the current status of SLO compliance. Related Topics Chapter 8 Managing service levels 353 . The icons on the top right of this screen let you view the report header. Provides a link to the Compliance Matrix screen that lists the components of that SLO. ■ To save the contents of this screen in CSV format. The SLO Type is a grouping of related attributes across Monitor Types. Colors and ranges are configurable from the first screen (Step 1) of the SLO wizard during SLO configuration. Provides a link to the SLO Details screen that gives complete information about the individual SLO. This column does not apply to Nested SLOs (SLO based on SLOs). All compliance values below the compliance objective are treated as a bad range and the cell is highlighted in red. Displays the SLO Type associated with the SLO. The system compares the actual compliance value against this value. or print the page.

you can click an individual SLO link to display a detailed matrix corresponding to that SLO. and corresponding attributes depending on the type of the SLO. see Viewing a graphical history of SLO compliance and violations on page 360. The matrix lists childlevel SLO instances.Viewing SLO compliance details and history Viewing a summary of details and compliance metrics for an SLO on page 354 Viewing violation details for an SLO on page 355 Viewing a history graph for an SLO on page 357 Viewing a breakdown of SLO metrics for various time periods on page 357 Viewing a summary of details and compliance metrics for an SLO From the Compliance Matrix tab > SLO column. Instance Details Tab is only available in the case of drill-down from instance level. and violations. For more information. Table 105: Columns of SLO information after drilling down into an individual SLO Column SLO Instance Attribute Details Description Displays the SLO instance name Displays the monitored attribute name Provides a link to the Instance Details screen that provides complete information about the individual instance. a graphic representation of the compliance levels across different periods (depending on data collected to date). ■ SLO Details tab provides complete information about the individual SLO. Table 105 on page 354 summarizes the columns that are displayed on drilling down into an individual SLO. ■ Instance Details tab provides complete information about the individual instance. and a graphic representation of the compliance levels across different periods (depending on data collected to date). and a graphic representation of the compliance levels across different periods (depending on data collected to date). 354 BMC ProactiveNet User Guide .

It reflects the real-time Service Level Threshold violations at any level. The Violation Details page provides the Service Level Threshold violation summary and allows the user to sort columns. you can click an individual SLO link to display the Violations Details page corresponding to that SLO. Provides a link to the Graph Display page. Colors can be set for compliance values only and not for the current status. this screen lists all the violations in the last 24 hours. By default. and the icon display in all the subsections depends on the corresponding range set definitions. The Violation Details screen links the SLO with Probable cause Analysis (PCA) and associates Service Level Violation Events and Infrastructure Events. Icon display depends on the compliance value of the instance. Valid Statuses are: open (red icon) and closed (green dot). The default value is 31 days.Viewing SLO compliance details and history Column Current Status Description Displays the current status of SLO compliance. Table 106 on page 355 summarizes the columns that are displayed on drilling down into the current status of an individual SLO. Service Level Threshold violation records are purged at regular intervals. Provides a link to the Violation Details screen in case of an open violation. Table 106: Columns of Violation Details current status information after drilling down into an individual SLO Column Time SLO Name SLO Type Description Date and time when the violation was recorded Name of the SLO Name of the SLO type Chapter 8 Managing service levels 355 . Icons are tied to compliance values during range set definition. which in turn has a Custom Graph Generator link Lists the weights associated with the attribute Displays the SLO compliance for the previous day Displays the SLO compliance for the current week Displays the SLO compliance for the current month Displays the SLO compliance for the current quarter Displays the SLO compliance for the current year Graph Weight Previous Day Week to Date Month to Date Quarter to Date Year to Date Viewing violation details for an SLO From the Compliance Matrix tab Current Status column.

For more information. To filter the list of violations 1 In the query fields above the list of violations. the Violations Details page lists all the violations recorded in the last 24 hours. and a graphic representation of the compliance levels across different periods (depending on data collected to date). Description of the violation The icon in this column provides a link to the Probable Cause Analysis page Filtering violations By default. the default is Open ■ Time period: either a predefined interval or a custom time range defined by the From and To times 356 BMC ProactiveNet User Guide . set the filtering criteria for the violation from the following criteria: ■ Selected SLO ■ Duration of the violation: the maximum amount of time for which the violation has been open. You can use the query fields to filter the list by various criteria. and violations. Min. Max: 1 day ■ Status of the violation record: either Open or Closed. SLO Details tab provides complete information about the individual SLO. see Viewing a graphical history of SLO compliance and violations on page 360. and a graphic representation of the compliance levels across different periods (depending on data collected to date).Viewing SLO compliance details and history Column SLO Details Description This column provides a link to the SLO Details screen that provides complete information about the individual instance. Instance Details Tab is only available in the case of drill-down from instance level. Device Information Status Duration Violated Points SLO Violation Description Analyze Details of the instance from which the violation is generated Current status of the violation Duration for which the violation was open Number of violated points for closed violations. ■ Instance Details tab provides complete information about the individual instance. a graphic representation of the compliance levels across different periods (depending on data collected to date). Violated points are not displayed for open violations.: 15 minutes.

which provides options to generate a graph for different predefined time ranges Associated weight Chapter 8 Managing service levels 357 . Instance Details Tab is only available in case of drill-down from the instance level. Quarter to Date. ■ Instance Details tab provides complete information about the individual instance. you can click the graph icon for an individual SLO to display a graphical representation of the SLO compliance over a specified duration. Viewing a breakdown of SLO metrics for various time periods From the Compliance Matrix tab > time period columns (Previous Day. Graph Weight This column provides a link to the Graph Displays page. Viewing a history graph for an SLO From the Compliance Matrix tab > History column. Table 107: Columns of SLO metrics for a defined time period Column SLO Instance Attribute Details Description Name of the SLO Instance Name of the associated attribute This column provides a link to the SLO and Instance Details.Viewing SLO compliance details and history 2 Click Apply. The list of violations is refreshed according to the specified criteria. SLO Details tab provides complete information about the individual SLO. you can click the time period for an individual SLO to display a detailed view of the various data points collected for the time period. Week to Date. For more information. The screen provides options to generate the graph for different predefined time ranges. and Year to Date). see Viewing a graphical history of SLO compliance and violations on page 360. and a graphic representation of the compliance levels across different periods (depending on data collected to date). and a graphic representation of the compliance levels across different periods (depending on data collected to date). Table 86 on page 312 summarizes the columns that are displayed on drilling down into the time period of an individual SLO. Month to Date.

Compliance Objective Month to Date Delta The compliance value associated with the SLO. only one of them is displayed. The compliance computation does not consider the current date. Link on the name listing directs to the Watch list page specific to that individual SLO SLO Type associated with the SLO. This column provides a link to the SLO Details page.Comparing compliance objectives with actual results Column Violated/Total Points Description Number of violated points based on the Service Level Threshold for the instance or attribute and the total number of data points recorded for the time range. For more information. The SLO Type is a grouping of related attributes across Monitor Types. you can sort the compliance percent value for the Month To Date column from worst to best. The compliance computation does not consider the current date. Default SLO Types are Availability and Performance. Details 358 BMC ProactiveNet User Guide . For example. which is the difference between the compliance objective and its value for the time unit. Table 108: Columns of information on the Watch List screen Column SLO Type Description Name assigned to the SLO. Table 108 on page 358 summarizes the columns that are displayed on the Watch List screen. see Viewing a graphical history of SLO compliance and violations on page 360. SLO compliance for the current month. The system compares the actual compliance value against this objective. Calculation of total points and violated points is based on the schedule of the SLO SLO’s compliance objective Instance level compliance Compliance Objective Compliance Value Comparing compliance objectives with actual results The Watch List screen displays SLO records and computed delta values. The difference between the compliance value and objective for the specified time period. which provides complete information about the individual SLO. This screen also provides filters to view specific records. You can sort by any column. If the same SLO is displayed in two or more multi-tier SLOs. and a graphic representation of the compliance levels across different periods (depending on data collected to date).

The available values are: Previous Day. Quarter to Date. Previous Week. and Year to Date. Week to Date. under Tab Selection. The Watch List screen has two sections: ■ Filters ■ Watch List table Filtering SLO records in the Watch List The default display includes all top-level SLOs with a compliance below 100% set for the Month to Date time period. To filter SLOs in the Watch List 1 Use any combination of the following query fields to set the filter criteria: ■ Time Period: Select the time period from the list to view corresponding compliances for that period. Month to Date. Note To view the Watch List 1 From the Options => SLO Mgmt tab. 2 Click the Watch List tab. ■ Show the following SLOs: Select the SLO grouping to view. you must have the Watch List tab added on the Operations Console. Previous Month. select Watch List. You can use the query fields to filter the list.Comparing compliance objectives with actual results Related Topics Accessing the Watch List on page 359 Filtering SLO records in the Watch List on page 359 Drilling down to an individual SLO in the Watch List on page 360 Accessing the Watch List To access the watch list. Chapter 8 Managing service levels 359 .

that provides complete information about the individual SLO. a graphic representation of the compliance levels across different periods (depending on data collected to date). and SLO violations. and SLOs which violate their compliance goals. Default SLO types are Availability and Performance. The icon in this column provides a link to the Instance Details page. A link on the SLO name directs you to the Watch List page specific to that individual SLO. Associated weight for the attribute Viewing a graphical history of SLO compliance and violations 360 BMC ProactiveNet User Guide . SLO Details Month to Date Compliance SLO compliance for the selected time period. Delta Weight Difference between the compliance value and objective for the specified time period.Viewing a graphical history of SLO compliance and violations The available values are: All SLOs. Drilling down to an individual SLO in the Watch List The drill-down from the SLO column displays details of the particular SLO. SLOs with compliance below 100%. The compliance computation does not consider the current date. Table 109: Columns of information on the Watch List Column SLO Name SLO Type Description SLO name. The system compares the actual compliance value against this objective. For more information. ■ Show Top level SLOs Only: Select this check box if you want to include only top level SLOs in the listing. 2 Click Apply. SLO type associated with the SLO. see Viewing a graphical history of SLO compliance and violations on page 360. Device Info Attribute Compliance Objective Details of the instance from where the violation is generated Attribute for which the Service Level threshold has been set Compliance value associated with the SLO. The compliance computation does not consider the current date. The SLO Type is a grouping of related attributes across monitor types.

click the link in the Thresholds Conditions column on the SLO Details screen. see Health Summary on page 315. The SLO Details page displays the following information: ■ SLO Information: Displays general information about the SLO. a weight. Viewing SLOs in a hierarchical tree The Tree tab in the SLO Management Console provides a real-time. displays a line graph (default) and violations (if any) for the selected instance based on data collected over the last 24 hours. click the link in the Name column to view a graphical representation of an individual SLO. Watch List tab. click Generate SLO Health Summary Report . For more information on the health report.Viewing SLOs in a hierarchical tree From the Compliance Matrix tab. ■ To add this SLO Details page as a tab in the Service Management Console. click Promote as Tab on the top right of this page. From the SLO Details screen. Viewing instance details To access the Instance Details screen. The SLO hierarchy and IT Groups are visible on a hyperbolic plane mapped to a circular display region. and Violation Details tab. interactive visualization of the SLO violation status. The Instance Details screen provides complete information about an individual instance. and a graphical representation of the violation history. ■ To generate an SLO Health Summary report. a graphical indication of the current status. you can click the SLO Details icon for an individual SLO to view information about an SLO. ■ SLO Violation History: Displays the various SLO instances with a description of the threshold condition. you can perform the following tasks: ■ In SLO Information. Chapter 8 Managing service levels 361 . ■ Compliance Summary: Displays a graphical representation of the compliance levels within the last 24 hours. Tip On the Current Status tab. click Edit to add comments.

the tree might not be displayed properly in Firefox 1. drag any point on the tree. For example. perform the following steps on Windows 2000 or XP: To ensure proper display of the tree on Firefox 1. ■ To focus on the SLO. select the time from the Time list.5 browser 1 In the Control Panel. click Show Legend or Hide Legend. ■ To promote the page as an independent tab. right-click the SLO icon and choose Set As Root to set the selected SLO as root. ■ To filter SLOs by maximum violation duration. you can perform the following tasks: ■ To change the focus point on the tree.Viewing SLOs in a hierarchical tree SLOs displayed are based on the Access Control level of the user. Use browser settings to Direct connection. click Network Settings. To ensure proper display of the tree. specify a name for the new tab. double-click the Java icon. and then click Apply.5. To control the display on the tree. Related Topics Controlling the display in the SLO Tree on page 362 Accessing further information from the SLO Tree on page 363 Controlling the display in the SLO Tree The following tasks guide you through the various actions that you can perform to control the display of information in the SLO Tree. and then change the default option. click Promote as Tab. Only the selected SLO and its child nodes are displayed. The SLO tree is refreshed to display only those SLOs for which violations occurred within the selected time duration. 2 In the Java Control Panel. ■ To display or hide the legend. If the BMC ProactiveNet Server is within the firewall and the Operations Console is outside the firewall. a user may be restricted to view only a subset of SLOs that exist in the system. 362 BMC ProactiveNet User Guide .

■ Access the Compliance Matrix page. and then choosing SLO Details.conf file. you can access various screens to view further information about the SLO or the SLO instance. and then choosing SLO Instance Details. see Viewing SLO compliance details and history on page 352.slatree. by right-clicking the SLO. see Determining the probable cause for an event on page 159. For more information. Accessing further information from the SLO Tree From the SLO tree. and then choosing Compliance Matrix. ■ On the SLO level. ■ Access the Probable Cause Analysis page. and then choosing Probable Cause. you can perform the following operations: — Access the SLO Details page. For more information. For more information. — On the SLO instance level. Chapter 8 Managing service levels 363 . by right-clicking the SLO instance. by right-clicking the SLO instance. see Viewing instance details on page 361.applet. see Viewing a graphical history of SLO compliance and violations on page 360.Viewing SLOs in a hierarchical tree To change the data refresh interval 1 Data refresh interval (in seconds) for the SLO Tree can be specified using the pronet. For more information. you can perform the following operations: ■ Access the SLO Instance Details page. by right-clicking the SLO.refreshRate property in the installDirectory/usr/pw/ custom/conf /pronet.

Viewing SLOs in a hierarchical tree 364 BMC ProactiveNet User Guide .

Related Topics Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 365 . or Monitor Type level: a Select the check box corresponding to the monitors to alter their data collection. 2 On the Administration tab. 3 Select the View Type (By Device. Device. or Group Name to view associated monitors. To change data collection settings 1 Click the Options link at the top right of the console.9 Controlling BMC ProactiveNet data collection and infrastructure Activating and deactivating data collection You can use the Data Collection Administration option to start or stop data collection for a monitor or groups of monitors. and By Group) for display on the Data Collection Administration screen. b Select On/Off option from the list corresponding to the monitors. Monitor Type. By Monitor Type. To use this option the BMC ProactiveNet administrator assigns the 'Allow Collect Data Management' privileges. 4 Click the Device Name. 5 Perform the following actions at individual monitor level or at the Group. under the Data Collection heading. 6 Click Apply. Click Edit link of Data Collection.

and groups allows BMC ProactiveNet administrators to specify a time range during which the monitor. therefore. device. down-time events cannot be scheduled with finer granularity than five minutes. The Scheduled Down Time feature supports multiple schedules with different time ranges. this period is five minutes. 366 BMC ProactiveNet User Guide . By default. You can schedule down time for the following frequencies: ■ One-time ■ Daily ■ Weekly ■ Monthly The scheduler polls the database periodically for downtime events. or group stops collecting data.Scheduling downtime Scheduling downtime on page 366 Tracking changes to BMC ProactiveNet objects on page 373 Viewing BMC ProactiveNet and PATROL agent statuses on page 374 Managing attribute sets on page 377 Managing baselines on page 380 Knowledge patterns on page 163 Managing relationships on page 397 Managing schedules on page 410 Importing and exporting users on page 412 Viewing BMC ProactiveNet software information on page 415 Downloads tab on page 418 Scheduling downtime The Scheduled Down Time feature for devices. monitors. In addition. if a large number of devices is scheduled.

To avoid the possibility of false events at the beginning of the maintenance window. Upgrade users have the option to turn baseline calculation off or on when Data Collection is on. upgrade users can: ■ Stop alarm or event generation ■ Stop alarm-related notifications or actions ■ Calculate baseline parameters If an upgrade user turns on the Data Collection option. the Calculate Baseline option is disabled because there is no data to calculate. number of agents. BMC ProactiveNet recommends that the downtime event be scheduled 15-20 minutes ahead of the actual maintenance period.Scheduling downtime it may take some time for the scheduler to turn off data collection for the scheduled devices. AlarmRule Action/ Notification. In Windows Day and Time Properties. Upgrade users can still access the Alarm/Event Generation. then the Calculate Baseline option is enabled. allow fair time for the device. The time taken to stop data collection and then resume data collection depends on the server load.) Usage scenario This topic depicts a typical data sample that can consists of the following test data. For example. select Automatically adjust clock for daylight saving changes. monitor. (When Data Collection is off. ■ Load on BMC ProactiveNet Server: Moderate (system load <1.5) ■ Number of agents scheduled down: 4 ■ Number of monitors scheduled down: 1200 ■ Scheduled down duration: 45 minutes Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 367 . and number of monitors scheduled for down time. This should always be selected to show the appropriate default time zone. or group to stop data collection. While scheduling downtime. and Calculate Baseline options from the Add Device for Scheduled Down Time dialog. Note Note for upgrade users New and upgrade users have different options available to them in this feature.

BMC ProactiveNet will monitor the Web server for availability and response time even during the device downtime and generate event or alarm. BMC ProactiveNet console will display the events. 2 Select the Downtime option. Once the device is up again. The advantage of this setup is that.15 minutes ■ Time taken to resume data collection: 1 . Application: In the above case. However. Data collection is on. Thus the administrator can check the system and ensure that the web server is working as expected before the time to get it online. in case of SLOs defined for availability of this device. 3 Frequency is Weekly. Alarm/Event generation is on. and 8 A. let us look at the following example: Assumptions: — BMC ProactiveNet is monitoring a web server for availability and response time. AlarmRule Action/Notification is off.M. 368 BMC ProactiveNet User Guide . any event or alarm generated during this period will not be notified.5 minutes To understand the usage of the Scheduled Down Time feature. 5 Add Time Range.Scheduling downtime ■ Time taken to stop data collection: 10 . However. BMC ProactiveNet will poll for the monitored attributes and report. the events will close. To schedule the web server downtime 1 Select the web server. data collection can be switched off to avoid inconsistent SLO compliance calculation. — During downtime. both availability and response time will not return data and alarms may be generated.M. 4 Specify the Time and Date as applicable. for maintenance. — These alarms will automatically close after the web server is online again. Operations: — During regular monitoring. — The web server is brought down on Sunday between 4 A.

Select the Downtime option. New users can skip to step 3. select Tools => Schedule Device Downtime. In the BMC ProactiveNet Administration Console. Next. you specify the duration of the down time. the list can be quite extensive.Scheduling downtime Adding a downtime schedule To add a downtime schedule 1 In the BMC ProactiveNet Operations Console. You can narrow your device search if Groups have been set up for your devices. 2 Choose a Filter. You can choose to filter the list by Device or by Group. The exact display of time (for each entry in the Devices Already Scheduled for Down Time section) may vary depending on the Administration Console (Windows and Solaris). 3 Click Add to open the Scheduler. Choose Options => Administration => Data Collection => Scheduled Down Time => Edit. You have the following options: ■ One-time setting ■ Daily ■ Weekly ■ Monthly To specify the duration of the down time On the Add Device for Scheduled Down Time screen. All devices or groups that are currently down are highlighted in Red. and are monitoring numerous devices. 2 Upgrade users only. The Scheduled Downtime Administration window is displayed. launch the Scheduled Down Time Administration window. These settings govern BMC ProactiveNet behavior during the scheduled downtime. 1 Select the Device to be scheduled. If you choose to filter by Device. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 369 .

Daily and weekly baseline values are recalculated based on the hourly baseline. The downtime is scheduled to occur monthly on the specified day and time. It is not a recurring setting. By default. Alternatively click the calendar link and select from the pop-up calendar. 4 Under Time Pattern field. The downtime is scheduled weekly at the specified day and time. Manually specify the dates in mm/dd/yyyy format. BMC ProactiveNet checks for the pause period corresponding to the current time. In case data collection is On. select the Time Zone. In case Alarm/Event Generation is On. only old values are used. 3 Select the Frequency: Frequency One Time Setting Daily Weekly Monthly Description The downtime is scheduled to run once. 6 From the list. the Start Time and End Time change accordingly. At the time of baseline calculation. If you change the Time Zone and the corresponding time falls either in the previous day or the next day. In case Calculate Baseline is Off. the Start Date changes accordingly. the server time zone is displayed here. During this period. The downtime is scheduled run daily at the specified time. ■ Alarm Rule Action/Notification: Specify if BMC ProactiveNet should send alarm notification for the alarms generated during this period. By default. ■ Alarm/Event Generation: Specify if BMC ProactiveNet should generate Events/ Alarms against the data collected. select the Start and End Date. previously calculated baseline is used. During the pause period. When you change the time zone. 370 BMC ProactiveNet User Guide . 5 Select the Start Time and End Time. The baseline stays unaffected by new data. the server time is displayed here. Outside the pause period baseline calculation is performed using current data. Hourly baseline is not recalculated and previous values are used. Calculate Baseline is a scheduled downtime for baseline calculations.Scheduling downtime ■ Data Collection: Select On or Off to continue collecting data or stop data collection respectively.

11 In the Added Successfully dialog box. After specifying the required time and date combination. 10 Click Yes to confirm the schedule. 7 Click Add Time Range . open it from Tools menu on the Administration Console.Scheduling downtime Note The Time Zone field displays GMT + Time Zone difference in hours. click Close. The system presents various alerts or confirmatory messages. 12 After defining the required Device Downtime. BMC ProactiveNet adds the schedule to the device. together with location. From 7. ■ To change the specified time and date combinations. — Click Remove Time Range. Selection is displayed in red if opened during its own scheduled time.1. ■ The Scheduler presents the Devices Scheduled selection. Edit/Delete downtime schedule Once a schedule is set.0. click Delete. and click OK. 8 Click Yes to confirm. — Select the entry under Time Range Entry. On confirmation. click OK . Time Zone for Indiana-Starke displays GMT – 05:00 US/Indiana-Starke instead of GMT – 5:00 as in 7. you can view and edit it by following the procedure given below: To edit/delete downtime schedule 1 If the Scheduler is closed. (If you want to delete the schedule. 9 Click Add.) 3 Modify the schedule as required. 2 Highlight the device whose schedule you want to change and click Edit. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 371 .

schedule downtime has no affect on the device ■ From Release 6.. Special notes ■ Do not perform any operations (monitor creation. Example: Consider the following schedules: Weekly: down at 9:00 A. (though the daily downtime is from 9:30 A.1.up at 10:30 A. . Daily: down at 9:30 A. In this case. data collection resumes after the higher schedule is completed. Related Topics Activating and deactivating data collection on page 365 Tracking changes to BMC ProactiveNet objects on page 373 Viewing BMC ProactiveNet and PATROL agent statuses on page 374 Managing attribute sets on page 377 Managing baselines on page 380 Knowledge patterns on page 163 372 BMC ProactiveNet User Guide . ■ If the devices data collection is off. Day Light Savings settings have been taken care of. to 10:30 A. To delete a schedule.M. ■ In case of overlapping downtime. to 10:00 A. etc) on devices during their scheduled downtime. data collection resumes only after 10:30 A.M.up at 10:00 A.M.M.M. .M. ■ In 7. select the schedule from the list and click Delete.5.M. editing multiple schedules is not allowed. flash check.M.M. This can result in unexpected behavior and display of invalid data.). we have an overlapping weekly downtime from 9 A. Time settings for the previously scheduled downtime might get effected. ■ A schedule cannot be edited while it is active (during downtime).Scheduling downtime Note BMC ProactiveNet does not allow editing of multiple schedules at a time. data collection.

■ All Groups (Grid View) => Tools. and provide information on the possible impact to your Web environment. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 373 . software and hardware requirements change constantly and need modification on the fly. List includes all devices in the system. 2 Inputs for Add Change Entry screen.Tracking changes to BMC ProactiveNet objects Managing relationships on page 397 Managing schedules on page 410 Importing and exporting users on page 412 Viewing BMC ProactiveNet software information on page 415 Downloads tab on page 418 Tracking changes to BMC ProactiveNet objects In production environments. By default. This feature is also accessible from the following flows: ■ All Devices (Grid View) => Tools. To track changes in your environment 1 Go to Options => Administration => Configuration Changes => Add/View. To add a new entry 1 Click Add. This regular change necessitates a high degree of change management. This displays the Add Configuration Change Event screen. the login name of the current user is displayed. BMC ProactiveNet can store and track configuration data. ■ The screen displays all the available entries related to the selected device. Default is the current time 3 Select the Device from the list. ■ All Devices (Grid View) => Monitor list => Tools. ■ User: Name of the user. 2 Set the Time Filter.

The BMC ProactiveNet Agent Status screen also displays an event summary of the agent’s monitors. PATROL Agents are connected to the BMC ProactiveNet server through PATROL Proxy Server(s) which are hosted on PATROL Proxy Agents. collecting their data. Go to Options => Administration => Agent Status. 374 BMC ProactiveNet User Guide . Remote agents are those agents that reside on machines outside the BMC ProactiveNet server. The Agent Status screen lists the current operating status of both the BMC ProactiveNet and PATROL agents. The local agent or BMC ProactiveNet server agent resides on the BMC ProactiveNet server.Viewing BMC ProactiveNet and PATROL agent statuses ■ Day: Day of change ■ Device: List of all devices in the system ■ Hour: Hour of change ■ Group: List of all groups in the System ■ Contact: Contact details (Text field limited to 50 chars) ■ Summary: Summary of the action (Text field limited to 120 chars) ■ Long Description: Comprehensive description of the Configuration Change Event (Text area limited to 1024 chars) 3 Click Apply to add a new entry. and delivering the data to the BMC ProactiveNet server for storage in the database. Related Topics “Controlling the display in the All Services Tree View ” on page 106 “Managing configuration changes” on page 125 “Viewing further information for a specific event from the Tools Menu” on page 38 Viewing BMC ProactiveNet and PATROL agent statuses The BMC ProactiveNet agent controls all service monitors (non-SNMP monitors) and is responsible for spawning the creation of monitors.

Viewing BMC ProactiveNet and PATROL agent statuses The BMC ProactiveNet agent status columns are listed in Table 110 on page 375. Monitors Drill-down Provides access to all the monitors on that device or resource. Name This column lists the name of the PATROL agent as defined by BMC ProactiveNet administrator. Valid states are: ■ Connection Active. This column lists the IP Address of the system hosting the BMC ProactiveNet agent. indicated by the green plugged icon ■ Agent Unreachable. indicated by the red unplugged icon ■ No Agent. and the red unplugged icon indicates the agent is disconnected. This column lists the Name and version of the operating system on the system hosting the BMC ProactiveNet agent. This will be shown as two different icons in three different scenarios as explained in “PATROL agent status icon and tooltip” on page 376. indicated by N/A. This column lists BMC ProactiveNet version and build number of the agent. This column is sorted by default. Table 111: Options for BMC PATROL agents Agent Status Description Connection status of the PATROL agent is displayed. This column lists the type of connection in use by the BMC ProactiveNet agent. Green plugged icon indicates the agent is connected. Table 110: Options for BMC ProactiveNet agents Agent Status Description The Agent column indicates if there is an agent attached to the device. Agent Name Agent Version IP Address OS Name Last Connected Running Since Tunnel ID Connection Type Agent Status This column lists the name of the Agent as defined by BMC ProactiveNet administrator. This column lists the date and time from which the agent is running. There will be a tooltip on the PATROL agent status icon which displays the connection status of PATROL agent as well as PATROL Proxy Agent. This column lists the latest date and time when the agent connected to BMC ProactiveNet server. and the connection status of the agent (connected or disconnected). Use the Monitors hyperlink to view event summary by Monitor Type (of all the monitors associated with a specific device). This column displays the current operating status of the agent. This screen displays events and provides tools for managing them. The BMC PATROL agent status columns are listed in Table 111 on page 375. This column lists the Tunnel ID in the case of TunnelAgent. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 375 .

the machine. Lists the port number on which the PATROL Proxy agent is running. but PATROL Proxy agent is up and running.Viewing BMC ProactiveNet and PATROL agent statuses Agent Status Port Proxy Agent Hostname/IP Proxy Agent Port Status Description This column lists the port number on which the PATROL agent is running. that is. and PATROL agent status when you select the Patrol Agents tab.Disconnected Patrol Proxy Agent .Connection Active Patrol Agent . 376 BMC ProactiveNet User Guide . Proxy agent name. Table 112: PATROL agent status icon and tooltip Scenario PATROL and PATROL Proxy agent are up and running.Connection Active Drill down from the agent status table To drill down from the agent status table 1 Click Monitors under the Monitors column. Status icon Tooltip Patrol Agent . ■ The Patrol Agents tab is available only if at least one PATROL adapter exists in PATROL agent status icon and tooltip The agent status icons and the tooltip are displayed as follows in three different scenarios. This column lists the hostname or IP address of the PATROL Proxy agent (ProactiveNet Agent) on which the PATROL agent is configured. PATROL agent is down.Disconnected Patrol Agent . PATROL and PATROL Proxy agent are down or disconnected. This column displays the current operating status of the agent. the Agent Status screen displays such PATROL agents on multiple rows. Note ■ If the same PATROL agent is configured on multiple PATROL Proxy servers.Disconnected Patrol Proxy Agent . one for each PATROL Proxy server. You can filter the agents on the PATROL agent name.

■ The Event List screen displays all open events corresponding to the monitor. Related Topics Activating and deactivating data collection on page 365 Scheduling downtime on page 366 Tracking changes to BMC ProactiveNet objects on page 373 Managing attribute sets on page 377 Managing baselines on page 380 Knowledge patterns on page 163 Managing relationships on page 397 Managing schedules on page 410 Importing and exporting users on page 412 Viewing BMC ProactiveNet software information on page 415 Downloads tab on page 418 Managing attribute sets An Attribute Set is a list of related performance attributes (metrics) that. Custom Attribute Sets are required for creating advanced relationships. taken together. Once these functional groupings are established. Drill down from the event list screen Click the Probable Cause icon (under Analyze column) to view all abnormalities. Use the Tools menu to access other functions. 2 Click the Severity Event icon to view Event List screen. represent a more abstract functional grouping of those individual attributes.Managing attribute sets ■ BMC ProactiveNet displays all Monitors associated with the Agent. they can be used to leverage relationships between various elements in the infrastructure. The product is delivered with a Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 377 .

3 On the Add Attribute Set screen. click Add on the AttributeSet Administration screen. you can create an Attribute Set containing Windows System CPU usage. Solaris System CPU usage. These include. 378 BMC ProactiveNet User Guide . During upgrade. you can create an Attribute Set for all CPU usage performance attributes across all platforms. and SLO type. for example. 5 Click Next. click Edit. Managing relationships on page 397 for more information on how Attribute Groups can be used. ■ To edit an existing attribute. we can do away with creating different relationships for each system monitor type. To locate a specific monitor. Select all monitors types corresponding to the attributes to be grouped. etc. and does not check for deletions. Click Add Attributes to add more attributes. BMC ProactiveNet recommends not editing default Attribute Sets (with the exception of adding new custom monitors). use the Search For field. Relationship. By creating an attribute set as discussed in the above example. to create a relationship between Web Servers and CPU usage. 4 Select the Monitor Type. In this case. 2 Click the relevant option: ■ For a new attribute. This feature is recommended only for advanced users who are trained and familiar with the Probable Cause capabilities of BMC ProactiveNet. To create or edit a new attribute set from the Operations Console 1 Go to Options => Administration => Attribute Sets => Edit. ■ Use the Shift and Ctrl keys to make multiple selections. Options are Global. 6 Select the Attributes to be grouped from under each of the Monitor Types in the Attributes section. AIX System CPU usage. Report. the system only carries forward the new attributes (added). See. It is conceptually similar to how many monitor instances can be put together in a 'Group' and relationships are then defined in terms of the 'Group' rather than from the individual monitor instance.Managing attribute sets group of out-of-the-box attribute sets. select the Attribute Set Type from the list.

10 Click Finish. To locate a specific attribute. ■ Default Attribute Sets cannot be deleted. 9 Select the Attributes to be included by selecting the corresponding check boxes under the Select column. To delete an attribute set 1 Open the Attribute Set Administration screen. use the Search For box. 8 Specify a name for the Attribute Set. Related Topics Activating and deactivating data collection on page 365 Scheduling downtime on page 366 Tracking changes to BMC ProactiveNet objects on page 373 Viewing BMC ProactiveNet and PATROL agent statuses on page 374 Managing baselines on page 380 Knowledge patterns on page 163 Managing relationships on page 397 Managing schedules on page 410 Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 379 . 5 Click OK to return to Attribute Set Administration screen. 2 Select the check box under Select corresponding to the Attribute Set to delete. 7 Click Next. ■ BMC ProactiveNet confirms and deletes the Attribute Set. 4 Click OK in the confirmation screen. ■ The new Attribute Set is available for use. 3 Click Delete.Managing attribute sets ■ Use the Shift and Ctrl keys to make multiple selections.

These two days share the same 24-hour baseline. All these ■ Weekend Pattern . different patterns are required.Saturday 380 BMC ProactiveNet User Guide . The baseline is calculated by collecting the values for a monitor’s attributes and metrics over a specified time period and establishing a low baseline value (consisting of the 10th percentile of all the values for a given time period) and a high baseline value (consisting of the 90th percentile of all the values for a given time period). for attributes that change frequently.Baseline is calculated separately for the weekend . BMC ProactiveNet captures the following baseline patterns: ■ Hourly baseline . a pattern captured at hourly intervals may be best. For example. ■ Daily baseline .Each hour of the day has a high or low value that is tracked. days share the same 24-hour baseline.Baseline is calculated daily from Monday to Friday.A high or low value is derived from the moving average of each ■ Weekday Pattern . A higher weight is given to the latest data being factored into the baseline average. and Sunday. A daily baseline is initialized after the monitor instance is created and 24 hours of data collection has occurred. Hourly interval ranges represent a smaller number of data points and will have a tighter range. To track the anomalies in behavior for different attribute types. A weekly baseline is initialized after the monitor instance is created and 168 hours of data collection has occurred. An hourly baseline is initialized after the monitor instance is created and 24 hours of data collection has occurred. This high or low range is taken from a larger number of data values and consequently will be a wider range than the hourly.Managing baselines Importing and exporting users on page 412 Viewing BMC ProactiveNet software information on page 415 Downloads tab on page 418 Managing baselines The baseline is the expected normal operating range for a metric or attribute of a monitor. which is best suited for capturing frequent changes. The accuracy of the baseline improves over time. and is repeated for each day. taking a weighted average of these values over time. This tracks the pattern for that metric on an hourly basis. consecutive day.

you can specify freeze points to discard values corresponding to specific period. Requirements for baseline generation For baselines to be generated for an attribute. Because this is an isolated case and not a regular pattern. the previously calculated baseline is used. if the baseline is not correct. Hourly baseline is not recalculated and previous values are used. it can be easily reset. For example. Baseline Administration provides a better control over baseline calculations. Absolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements. if the Key Performance Indicator (KPI) mode is active. artificially will raise or lower the baseline. At the time of baseline calculation. You can also create baselines for special or seasonal dates. During the pause period. Outside the pause period baseline calculation is performed using current data. you might want to set a pause period for the holiday season when Web traffic is expected to peak. only old values are used. that attribute must have an active abnormality threshold. BMC ProactiveNet checks for the pause period corresponding to the current time. For example. Daily and weekly baseline values are recalculated based on the hourly baseline. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 381 .Baseline is calculated separately for pre-determined days when your business experiences out of the ordinary workloads or other special behavior. as well as edit or delete previously defined baseline calculation periods. The baseline stays unaffected by new data. you might want to discard this data for the overall baseline. if calculated into the baseline.Managing baselines ■ Seasonal baseline . During this period. These days. Similarly. Additionally. only those attributes that have an active abnormality threshold and are also KPI attributes will have baselines generated for them. An active abnormality threshold means that the threshold exists and is not suppressed. Pausing baseline calculation Pausing baseline calculation allows you to schedule downtime for baseline calculations. Through the Options screen you can add new baseline calculation periods. causing unnecessary abnormalities.

Select SLO Group to include all instances from the SLO group. Select Indefinite to stop a particular baseline calculation. subsequent operations performed (such as create. click Add under Pause Baseline Note Calculation. To delete a Pause Baseline Calculation Period 1 Go to => Options => Administration tab. ■ Monitor Instance . 4 Specify the Pause Baseline period. After making the required changes.Specify the start time for the pause period. ■ To edit an existing Pause Baseline Calculation Period.Managing baselines To define or edit a Pause Baseline Calculation Period When a Pause Baseline Calculation Period is edited for the first time. ■ Device . ■ Monitor Type . 2 Click the relevant options: ■ For a new Pause Baseline Calculation Period. Select the Monitor Instance. a From time . edit. or delete) on Baseline Pause Periods are not effective until the Rate process is restarted. 5 Click Add. 1 Go to Options => Administration => Advanced => Baseline => Edit. ■ SLO .Select the Monitor Type to include all instances of the monitor type.Select the monitor instance to add a single monitor instance. 2 Click Edit corresponding to Baseline Administration. b To time . The system updates the Pause Baseline Calculation Period and returns to the Baseline Freeze Point Administration screen. ■ Group . 382 BMC ProactiveNet User Guide .Select Group to include all the instances in the group. 3 In the Pause Baseline Calculation Period screen. click Edit.Specify the end time for the pause period.Select Device to include all the instances associated with the device. click Update.

select the check box (corresponding to the Pause Period to delete) under Select column. On Reset. the baseline data is reinitialized based on previous data generated from the same instances. Resetting a baseline Baseline can be reset to re-compute the baseline. ■ Device . To reset a baseline 1 Click Reset Baseline on the baseline Administration screen.Select the Device to include all the instances associated with the device. ■ SLO . ■ Number of days for considering data. ■ Monitor Type . ■ Group . 3 Click Delete.Managing baselines On the Pause Baseline Calculation screen. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 383 . ■ Monitor Instance . All historic baseline information is deleted and the new baseline is initially just an estimate (based on the performance of the old data in the specified period).Select the Group to include all the instances in the group. 2 Select the Monitor Instances. 3 Specify the period for calculating the new baseline using one of the following options: ■ From Time and To Time .Specify the start and end time of the period for considering data for baseline calculations.Select the Monitor Instance to include the single monitor instance.Select SLO to include all instances from the SLO. 4 Click OK in the confirmation screen. Baseline values are refined over time as the pattern is relearned. The system deletes the Baseline Pause Period and returns to Administration screen.Select the Monitor Type to include all instances of the monitor type. Confirmation is displayed on the Administration screen.

5 Click Reset. causing unnecessary abnormalities. such as weekly or monthly payroll and backups In the Operations console. 2 On the Options page. 3 In the Advanced area of the Administration page. If you select a single attribute. There are two types of dates that you can account for using the baseline seasonality functionality: ■ specific seasonality dates—planned. next to Baseline. It modifies only baseline values computed for future use. or weekly). if calculated into the baseline. 384 BMC ProactiveNet User Guide . ■ If you select All Attributes as the Monitor Attribute Selector. there may be pre-determined days when your business experiences out of the ordinary workloads or other special behavior. single days with exceptional behavior. You can use the baseline seasonality functionality to calculate specialized baselines for these unusual days that are separate from the baseline for normal business days. daily. choose Options. choose the Administration tab. Note ■ Baseline reset at the attribute level does not change historic values. ■ The Baseline Administration page is displayed. click Edit. These days.Managing baselines 4 Select the baseline types to be reset. such as special sales and holidays ■ recurring seasonality dates—events that repeat on a regular basis with exact frequency. The seasonal baseline can be applied to all groups and services or to specified groups and services. artificially will raise or lower the baseline. then the attribute baseline value of the current hour is reset. To access the Baseline Seasonality Administration page 1 From the Operations Console. Creating a separate baseline for seasonal or special dates In your organization. then all baseline values of the current day are reset. Specify at least one of available baseline types (hourly. you control the baseline seasonality feature using the Baseline Seasonality Administration page.

Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 385 . see the pw log period CLI section in the BMC ProactiveNet Administration Guide. ■ The Baseline Seasonality Administration page is displayed. For baseline seasonality to work. if the default retention period for a device is 90 days and you schedule a baseline seasonality schedule for every six months. if the seasonality schedule is one year apart. The data retention period for the device should be at least as long as the baseline seasonality schedule. If the retention period is insufficient. Use the Baseline Seasonality Administration page for ■ Creating a baseline seasonality instance on page 385 ■ Editing or deleting a baseline seasonality instance on page 389 Creating a baseline seasonality instance Before you begin ■ Ensure that your system is configured to have a long enough data retention period to accommodate the baseline seasonality schedule that you select. click the Baseline Seasonality link. a warning message is displayed on the Baseline Seasonality Administration page. then the longest span of time between days in the schedule is one year. For example. In that case. For information about listing and setting the data retention period. For example. the rate and baseline tables must be able to hold data for one year. the data retention period is too short and the Baseline Seasonality Administration page will display a warning message that there insufficient data retention.Managing baselines 4 On the Baseline Administration page. the rate and baseline data must cover the longest span of time between seasonality days that is in any seasonality schedule.

2 On the Baseline Seasonality Administration page. a specific group will take precedence over a global instance. a warning message is displayed on the Baseline Seasonality Administration page. If duplicate schedules are created. choose the group that will be affected by the dates you are adding. specific seasonality dates 1 Access the Baseline Administration page as described in To access the Baseline Seasonality Administration page on page 384. click Add. For example. 3 In the Baseline Seasonality Name field. choose All Instances. ■ If the special dates only affect one or more of your systems and services. Sale Days. ■ If the special dates will affect all of your systems and services. seasonality A takes precedence. choose Group and follow these steps: a Click the linked text next to Group. c Click Apply to accept your selection and close the dialog box. ■ The Select/Group dialog box is displayed. not the group name. 4 In the Monitor Instance Selector area. then A still takes precedence. or all instances. If there are duplicate schedules.Managing baselines ■ Plan your baseline seasonality schedules so that there are no duplicate schedules for any instance. For example. If seasonality A is for group Z and seasonality B is for group Y. b From the Select/Group dialog box. 386 BMC ProactiveNet User Guide . choose the monitor instances that will be affected by these special dates. 5 Choose the Set Specific Seasonality Dates radio button. If both schedules are for specific groups. Related Topics: To create a seasonality baseline for single. if seasonality A is for group Z and seasonality B is for all instances. specific seasonality dates on page 386 To create a seasonality baseline for events that occur on a regular basis on page 387 To create a seasonality baseline for single. enter a general name to identify the specific dates that you will be entering. precedence is determined alphabetically by the baseline seasonality name. group.

choose Group and follow these steps: a Click the linked text next to Group. and year from the drop lists or you can click the calendar icon and double-click the desired date. 5 Choose the Set Seasonality Recurrence Pattern radio button. and year of the special date for which you want to create a seasonality baseline. You can either select the month. Weekly Backups. The date is displayed in the Included Dates list. select the month.Managing baselines 6 In the Pick Date field. The start date can be a past. enter a general name to identify the specific dates that you will be entering. day. ■ If the special dates will affect all of your systems and services. 4 In the Monitor Instance Selector area. choose the date from you want to start the first occurrence of the seasonality baseline. click Add. b From the Select/Group dialog box. The Select/Group dialog box is displayed. 2 On the Baseline Seasonality Administration page. The date or group of dates that you added appears in the list of dates on the Baseline Seasonality Administration page. ■ If the special dates only affect one or more of your systems and services. on page 387 and List item. choose the monitor instances that will be affected by these special dates. on page 387 to add additional dates. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 387 . 6 In the Start From field. 3 In the Baseline Seasonality Name field. choose All Instances.Click Apply to accept your selection and close the dialog box. For example. 8 [Optional] Repeat List item. click Add. or future date. choose the group that will be affected by the dates you are adding. 7 Click Add Date. day. To create a seasonality baseline for events that occur on a regular basis 1 Access the Baseline Administration page as described in To access the Baseline Seasonality Administration page on page 384. current. 9 When you have finished adding dates.

you would enter 1 in the Recur every __ weeks on field. ■ If the special event occurs each month or every few months. — Specify the monthly frequency of the special event: If the special event occurs on the same day each month or every few months. follow these steps: — Choose the Monthly radio button. such as payroll or inventory. select the Sunday check box. If the backup procedure occurs every week. such as a weekly or twice per week backup procedure. choose the The __ __ of every __ month(s) radio button and select the monthly occurrence of the day of the week. Example If the backup procedure always takes place on Sunday. Example If your organization has a backup procedure every two weeks. 388 BMC ProactiveNet User Guide . the day of the week. and the monthly frequency for the special event. choose the Day __ of every __ month(s) radio button and enter the day of the month and the monthly frequency for the special event. If the special event occurs on the same day of the week at the same frequency each month. you would enter The _ Last _ _ Friday _ of every _ 3 _ month(s). If the special event always occurs on the 30th day of the month. — Select the check box for the day of the week on which the event occurs.Managing baselines 7 Specify the occurrence frequency of the special event that you are adding: ■ If the special event occurs every week or every few weeks. 8 Click Add. Example Example If the special event occurs on the last Friday of every third month. you would enter Day _ 30 _ of every _ 1 _ month(s). — Enter the number of weeks between occurrences of the special event in the Recur every __ weeks on field. enter 2 in the Recur every __ weeks on field. follow these steps: — Choose the Weekly radio button.

4 Click Update. To delete a baseline seasonality instance 1 Access the Baseline Administration page as described in To access the Baseline Seasonality Administration page on page 384. click Edit to the right of the baseline seasonality instance that you want to edit. ■ The Edit Baseline Seasonality dialog box is displayed. the data for that the period that the seasonality baseline existed will remain and the normal baseline will be applied in the future during the time period that was previously specified by the baseline seasonality instance. make the required changes to the baseline seasonality instance. select the check box of the seasonality baseline instance that you want to delete. click OK. To edit an existing baseline seasonality instance 1 Access the Baseline Administration page as described in To access the Baseline Seasonality Administration page on page 384. Example: Configuring seasonality baselines for a retail organization Your retail organization has planned special sales for the following dates this year: ■ May 31 ■ November 29 Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 389 . 2 On the Baseline Seasonality Administration page. 4 In the confirmation dialog box. you can edit or delete it. 3 Click Delete. Editing or deleting a baseline seasonality instance Once you have created a baseline seasonality instance.Managing baselines The recurrence pattern that you added appears in the list of dates on the Baseline Seasonality Administration page. 3 In the Edit Baseline Seasonality dialog box. If you delete a baseline seasonality instance that you have created. 2 On the Baseline Seasonality Administration page.

Your organization pays its employees every two weeks on Fridays and performs inventory quarterly. January 1 ■ Groundhog Day. 390 BMC ProactiveNet User Guide . September 19 ■ World Teachers’ Day. so you need to create a seasonality baseline to avoid triggering abnormalities due to the decreased load on the days that your organization is closed for business. November 17 When your organization is closed. your organization should set seasonality baselines as follows. the load on your systems and services drops considerably.Managing baselines ■ July 4 ■ December 22 ■ September 7 ■ December 23 ■ November 27 ■ December 26 ■ November 28 ■ December 27 The increased business on these special sale days increases the load on your systems. October 5 ■ World Peace Day. February 2 ■ International Earth Day. June 18 ■ International Talk Like a Pirate Day. Based on these facts. May 8 ■ International Picnic Day. Your organization is closed on Sundays and on the following holidays: ■ New Year’s Day. March 20 ■ International Tuba Day. so you need to create a seasonality baseline for these sale days to avoid triggering abnormalities due to the increased load on these days.

4 Because these sales increase the load on all your systems and services. 3 In the Baseline Seasonality Name field. on page 387 to add the additional sale dates. choose All Instances.Managing baselines To create a seasonality baseline for days on which your store has special sales: 1 Access the Baseline Administration page as described in To access the Baseline Seasonality Administration page on page 384. click Add. enter Sale Days. 8 Repeat List item. in the Monitor Instance Selector area. on page 387 and List item. 5 Choose the Set Specific Seasonality Dates radio button. select May 31 of the current year. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 391 . 2 On the Baseline Seasonality Administration page. 6 In the Pick Date field. 7 Click Add Date. The date is displayed in the Included Dates list.

2 On the Baseline Seasonality Administration page. Therefore. choose All Instances. in the Monitor Instance Selector area. click Add. 392 BMC ProactiveNet User Guide . this decreases the load on all your systems and services. 3 In the Baseline Seasonality Name field. To create a seasonality baseline for Sundays (the day of the week that your business is closed): 1 Access the Baseline Administration page as described in To access the Baseline Seasonality Administration page on page 384. enter Sundays. 4 Because your business is closed. Figure 23: Baseline Seasonality for Sales Days 9 Click Add. The group of special sale dates that you added appears in the list of dates on the Baseline Seasonality Administration page.Managing baselines ■ Figure 24 on page 393 shows the Add Baseline Seasonality page after the data has been entered.

Figure 24: Baseline Seasonality for Sundays 10 Click Add.Managing baselines 5 Choose the Set Seasonality Recurrence Pattern radio button. 8 In the Recur every __ weeks on field. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 393 . 9 Select the Sunday check box. enter 1. ■ Figure 24 on page 393 shows the Add Baseline Seasonality page after the data has been entered. 7 Choose the Weekly radio button. 6 In the Start From field. choose the first Sunday in January.

6 In the Pick Date field. 394 BMC ProactiveNet User Guide . choose Group. on page 387 to add the additional holiday dates. in the Monitor Instance Selector area. 5 Choose the Set Specific Seasonality Dates radio button. The group of holidays on which your business is closed appears in the list of dates on the Baseline Seasonality Administration page. The date is displayed in the Included Dates list. click Add. 8 Repeat List item. 2 On the Baseline Seasonality Administration page. enter Holidays. 4 Because these holidays decrease the load on all your systems and services. 4 Because payroll activities increase the load only on the server used by your accounting department. 3 In the Baseline Seasonality Name field.Managing baselines Every Sunday is added as a recurring pattern for a new seasonality baseline on the Baseline Seasonality Administration page. ■ The Select Group dialog box is displayed. To create a seasonality baseline for payroll days: 1 Access the Baseline Administration page as described in To access the Baseline Seasonality Administration page on page 384. in the Monitor Instance Selector area. 3 In the Baseline Seasonality Name field. 7 Click Add Date. 5 Click the linked blue text to the right of the Group radio button (This text reflects the Group that currently is selected). on page 387 and List item. choose All Instances. 2 On the Baseline Seasonality Administration page. 9 Click Add. click Add. To create a seasonality baseline for holidays on which your business is closed: 1 Access the Baseline Administration page as described in To access the Baseline Seasonality Administration page on page 384. select January 1 of the current year. enter Payroll Activity.

Figure 25: Baseline Seasonality for Payroll activity 13 Click Add. 11 In the Recur every __ weeks on field. 7 Select the check box for the group that represents your accounting department and click Apply.Managing baselines 6 In the Select Group dialog box. For example. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 395 . ■ The Select Group dialog box closes and the group that you selected is displayed to the right of the Group radio button. ■ Figure 25 on page 395 shows the Add Baseline Seasonality page after the data has been entered. (Although your employees receive their checks every two weeks on Friday. enter 2.) 10 Choose the Weekly radio button. it might be a service named Accounting. choose the first Thursday in January of the current year. 8 Choose the Set Seasonality Recurrence Pattern radio button. the bulk of payroll activity occurs on the Thursday before the checks are received. 9 In the Start From field. browse to the group that you have defined that represents your accounting department. Every other Thursday is added as a recurring pattern for a new seasonality baseline on the Baseline Seasonality Administration page. 12 Select the Thursday check box.

September 30. 3 In the Baseline Seasonality Name field. 6 In the Select Group dialog box. choose in the Monitor Instance Selector area. in the Monitor Instance Selector area. on page 387 and List item. click Add. 11 Repeat List item. on page 387 to add the inventory dates for each quarter (June 30. ■ The Select Group dialog box is displayed. ■ The Select Group dialog box closes and the group that you selected is displayed to the right of the Group radio button. choose Group. 2 On the Baseline Seasonality Administration page. The group of days on which your business conducts quarterly inventory appears in the list of dates on the Baseline Seasonality Administration page. enter Quarterly Inventory. 9 In the Pick Date field. 10 Click Add Date. For example. 4 Because quarterly inventory increases the load on your database. The date is displayed in the Included Dates list. 8 Choose the Set Specific Seasonality Dates radio button. and December 31). 396 BMC ProactiveNet User Guide .Managing baselines To create a seasonality baseline for quarterly inventory: 1 Access the Baseline Administration page as described in To access the Baseline Seasonality Administration page on page 384. 5 Click the linked blue text to the right of the Group radio button (This text reflects the Group that currently is selected). select March 31of the current year. browse to the group that you have defined that represents your inventory database. 12 Click Add. it might be a service named Inventory. 7 Select the check box for the group that represents your inventory database and click Apply.

Managing relationships Managing relationships Relationships allow you to specify how elements within the infrastructure are related. User-defined relationships work together with static relationships to filter events. By defining a relationship between application and the host system. By managing relationships. Relationships define dependencies between various monitored elements in the system and are used for Probable Cause Analysis. Only the system availability alert will be sent out. BMC ProactiveNet will not send out an alert for the application availability. not related to the queried event. due to the defined relationship. Static Relationships relate different monitor types (not specific to any instances). see “Adding or editing an Intelligent Event Suppression relationship” on page 403. For details about defining Intelligent Event Suppression Relationships. Now. Intelligent Event Suppression Relationships are NOT static relationships.an important factor for maximizing the power behind the Probable Cause feature. If the event instance does NOT belong to any instance relationship. Instead of leveraging 'out-of-the-box' knowledge about how various monitor instances relate to one another. Generally. If it does. As explained in the above example. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 397 . Such relationships are easy to manage and all instances added to the group will inherit the relationship. it uses the static relationship rules. then the algorithm applies those relationship filters. BMC ProactiveNet recommends use of group-level relationships. and event suppression. Probable Cause Analysis Relationships are static relationships (in the probable cause smart filter) based on static rules. For example. BMC ProactiveNet recommends using separate relationships for event suppression and probable cause analysis. the Probable Cause algorithm can leverage very specific user domain knowledge . available events related to system A are suppressed by available events of System B. higher level of validity can be achieved for both Probable Cause Analysis and events. Relationships for both probable cause and Intelligent Event Suppression are called Common relationships. algorithms first check to see if the event instance belongs to any instance relationships. if the system goes offline. impact prediction. relationships go a along way in customizing BMC ProactiveNet behavior. Probable cause and Business Impact features use this information to filter out events and violations. Although common relationships (applicable to both Intelligent Event Suppression and Probable Cause Analysis) can be created. both the system and the application will not be available. However. we can monitor an application and the host system. and guide Probable Cause and Business Impact algorithms.

3 BMC ProactiveNet includes default. if you upgraded from a version of BMC ProactiveNet older than 8. If more granular relationships are needed.00. 398 BMC ProactiveNet User Guide . Focus on creating relationships that are specific to your infrastructure. Defining Intelligent Event Suppression relationships Because of changes to the service model. 2 Think through the relationships before creating them. Plan the relationships well. Take advantage of this out-of-the-box functionality. Generally a scalable and well thought-out plan of related groups works best. BMC ProactiveNet recommends defining the broader relationships first. However.Managing relationships This preserves all built in rules even in environments where the instances are constantly being changed. consider these best practices: 1 Define broad rather than narrow relationships. this functionality has been preserved as Intelligent Event Suppression.5. you will not see the Intelligent Event Suppression functionality. relationship administration was deprecated starting with BMC ProactiveNet version 8. Relationships are used to ascertain the potential probable causes and related events.5. Think of elements in your infrastructure in abstract groupings and create relationships based on these groupings as opposed to using the device or instance level.5. you can always define additional relationships. Global relationships. If this is your first installation of BMC ProactiveNet. Best practices for defining Intelligent Event Suppression relationships Before you begin defining Intelligent Event Suppression relationships. Narrow relationships may inadvertently filter out potential abnormalities by forcing BMC ProactiveNet to give them lower scores. or you did not use the relationship administration feature in previous releases. This functionality has been absorbed into the changes made to the service model in BMC ProactiveNet version 8.

Once these relationships are established. but also depends on a pool of Application servers (Appserver Pool A) and on database A. you want to convey the above information into the BMC ProactiveNet system so it can be leveraged by Probable Cause Analysis algorithms. This is a required. Scenario Consider that you have an online store that sells widgets A. and C. thus taking advantage of the domain knowledge injected into the system via the relationship mechanism. In this scenario. Each type of widget is served by distinct WebServer pools. thus limiting the conclusions it can draw about the potential causes of an event. This information is known as domain knowledge. the Probable Cause algorithm must rely strictly on out-of-the-box relationships. B. Without this information. as you drill down on the event through the Probable Cause pages. 1 Online Store A consists of one pool of Web servers (WebServer Pool A) dedicated to selling widget A items. Using the Relationships folder located in the Administration Console. but also depends on a pool of Application servers (Appserver Pool B) and on database B. 3 Online Store C consists of a similar third configuration set up for selling widget C items. Establishing relationships The following shows how you would want to create relationships that represent the specific scenario described earlier in this example: WebTranxMonitors A => WebServerPool A => AppServerPool A => Database A Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 399 .Managing relationships Relationship example Assumptions Before attempting to establish relationships. BMC ProactiveNet will guide you to the most accurate Probable Cause event that is related to the event. essential step since all relationships are defined in terms of monitor instances. 2 Online Store B consists of another pool of Web servers (Webserver Pool B) dedicated to selling widget B items. if there is a problem with any of these online stores and an event is triggered. you can input this relationship information into the system so that it can be used whenever a problem crops up with a transaction on any of the three online stores. as well as by different Application servers and/or databases behind the Webservers. a monitor for each relevant element in the Web infrastructure has already been created.

Each relationship has a unidirectional dependency. and delete Intelligent Event Suppression rules. Related topics Managing relationships on page 397 Adding or editing an Intelligent Event Suppression relationship on page 403 Overview of the Intelligent Event Suppression screen From the Intelligent Event Suppression screen. The four pools for online store A would form one relationship tree. as well as access the dialog box that allows you to create Intelligent Event Suppression rules. disable. you can enable. and the same for online store C. relationships can easily be formed by creating a Relationship for each of these Groups. The Intelligent Event Suppression 400 BMC ProactiveNet User Guide . the four pools for online store B would form another relationship. After these Groups are established.Managing relationships WebTranxMonitors B => WebServerPool B => AppServerPool B => Database B WebTranxMonitors C => WebServerPool C => AppServerPool C => Database C Each of the 'pools' above can be represented by creating a standard 'Group' in the BMC ProactiveNet Administration Console.

These out-of-the-box relationships are not editable. You can obtain more information about the relationship by hovering your cursor over the more information icon . The Name column displays the name of the Intelligent Event Suppression relationship. device or monitor separated by an arrow to indicate the direction of the relationship. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 401 . Only the Ping/ Availability=>Device SameDevice. Default Global relationships are shipped with BMC ProactiveNet and are immediately visible when you access the Intelligent Event Suppression screen. . This is indicated by the lock icon in the Edit column for each of the default relationships. Figure 26: Intelligent Event Suppression screen The Select column allows you to select the check box of the Intelligent Event Suppression relationship that you want to delete. clicking the Edit link to the right of Intelligent Event Suppression. Relationship names are formed from the primary group.SameSourceAgent relationship is enabled by default. or monitor (the event that suppresses the events from the secondary event) and the secondary group. device.Managing relationships Administration screen is accessed by selecting Options=>Administration and in the Advanced area.

click Edit. to the right of Intelligent Event Suppression. select the checkbox. see “Adding or editing an Intelligent Event Suppression relationship” on page 403. the Enabled check box for that relationship is selected. The Add button allows you to add a new Intelligent Event Suppression relationship. For more information. 4 On the Intelligent Event Suppression screen. The Precedence column displays the order in which the relationships are processed if multiple primary events exist for the same secondary event. 402 BMC ProactiveNet User Guide . For more information see. Enabling or disabling Intelligent Event Suppression relationships Use the following procedure to enable or disable Intelligent Event Suppression relationships. 3 In the Advanced area. “Enabling or disabling Intelligent Event Suppression relationships” on page 402. The Edit column allows you to edit the scope and other attributes of the associated relationship. The Delete button allows you to delete any Intelligent Event Suppression relationship that is selected in the Select column. perform one of the following actions: ■ To enable the Intelligent Event Suppression relationship. The Enabled column allows you to enable and disable relationships. To enable/disable an Intelligent Event Suppression relationship 1 Click the Options menu at the top right of the console. Events are suppressed by the primary event that passes the rule which has highest precedence. 2 Choose the Administration tab. the primary event with the highest severity is processed. see “Adding or editing an Intelligent Event Suppression relationship” on page 403. If a relationship is enabled. For more information. For more information about providing a description. in the Enabled column for the the Intelligent Event Suppression relationship rule that you want to enable or disable. If there is a tie with rule precedence. see “Adding or editing an Intelligent Event Suppression relationship” on page 403. 1 is the highest precedence.Managing relationships The information displayed by the more information icon is provided by the Description box available when you create an Intelligent Event Suppression relationship.

and so on. Adding or editing an Intelligent Event Suppression relationship Intelligent Event Suppression relationships are only supported for users who are upgrading from versions of BMC ProactiveNet older than version 8. If you have installed BMC ProactiveNet for the first time. Before attempting to establish any relationships. this functionality is not supported.0. Before you add Intelligent Event Suppression relationships. ensure that a monitor for each relevant element in your infrastructure has already been created.the Intelligent Event Suppression relationship Note Tip is applied to the monitors within a group or device. or monitor-based . You can create any of the following types of Intelligent Event Suppression relationships: ■ Global . Intelligent Event Suppression relationships can be either applied globally or to a specific monitor or monitors that you specify. To define any relationship between elements in your infrastructure. device. 5 Click Apply. The status of the relationship is displayed in the Enable column. or to a specific monitor or monitors that you specify Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 403 . Web servers. you should: 1 Define a monitor for each element in your environment. Using a group to define a relationship makes it more practical to maintain relationships. first define a monitor for each element. applications. All relationships are defined in terms of monitor instances. create groups for any pools of servers. 2 Define groups for any set of related instances: For example.Managing relationships ■ To disable the Intelligent Event Suppression relationship.the Intelligent Event Suppression relationship is applied to all monitors ■ Group. deselect the checkbox. and then use the actual monitor to define the relationship.

To specify a single attribute: a Choose the Single Attribute option. the first monitor type in the monitor type list is selected.an event on a single attribute for a specified monitor type will suppress events on the secondary monitor. 404 BMC ProactiveNet User Guide . Choose from the following: ■ All Attributes . b Click the link to the right of the Single Attribute option. use the check boxes to select whether the primary and secondary monitor instances in the relationship must reside on the same device. 4 In the Primary Attribute Selector area. choose Global. c Choose the monitor type for the attribute and click Apply. (By default. 1 Click the Options menu at the top right of the console. choose the attributes of the primary monitor that will trigger suppression for the selected attributes on the secondary monitor.Managing relationships Access the Add Intelligent Event Suppression Relationship dialog box and then follow the procedure appropriate for the type of Intelligent Event Suppression relationship that you want to create. 2 Choose the Administration tab.) The Select Monitor Type dialog box is displayed. you must first access the Add Intelligent Event Suppression Relationship dialog box. The Add Intelligent Event Suppression Relationship dialog box is displayed. click Edit. to the right of Intelligent Event Suppression.an event on any attribute of the primary monitor will suppress events on the secondary monitor ■ Single Attribute . 2 In the Scope area. To add a Global Intelligent Event Suppression relationship 1 Access the Add Intelligent Event Suppression Relationship dialog box. 4 On the Intelligent Event Suppression screen. click Add. or both. on the same source Agent. 3 In the Advanced area. Accessing the Add Intelligent Event Suppression Relationship dialog box To define any type of Intelligent Event Suppression relationship. 3 In the Global Scope: Qualifiers area.

5 In the Secondary Attribute Selector area. The list of attributes available depends on the monitor type you selected.an event on any attribute in the selected attribute set will suppress events on the secondary monitor. the less likely it is that BMC ProactiveNet will suppress the events on the secondary monitor. Notification wait time affects secondary monitor event suppression as follows: Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 405 . choose the attribute set to which you want to apply the relationship. select the attribute for that monitor that will trigger events to be suppressed on the secondary monitor. Choose from the following: ■ All Attributes . b From the drop list. however. enter a description of the relationship. and <body> tags are not supported. The default wait time is 120 seconds. HTML is supported.an event on the selected attributes of the primary monitor will suppress events on any attribute in the selected attribute set on the secondary monitor 6 (Optional. <head>.)In the Notification Wait Time field enter the time in seconds for BMC ProactiveNet to wait for an event on the primary monitor to occur before processing the event that has occurred on the secondary monitor.) In the Description text box. choose the attributes for which events will be suppressed when the specified events occur on the primary monitor. The shorter the notification wait time.an event on the selected attributes of the primary monitor will suppress events for a single attribute for a specified monitor type on the secondary monitor ■ Attribute Set . To specify an attribute set: a Choose the Attribute Set option.Managing relationships The Select Monitor Type dialog box closes and the name of the monitor you selected is displayed to the right of the Single Attribute option. d From the drop list beneath the name of the monitor you selected. ■ Attribute Set . the <html>.an event on the selected attributes of the primary monitor will suppress events on all attributes for the secondary monitor ■ Single Attribute . This description is displayed when you hover your cursor over the more information icon next to a relationship on the Intelligent Event Suppression screen. 7 (Optional.

use regular expressions to type a pattern for the groups or devices that you want to be primary monitor instances for the relationship. choose the group or device to be the primary monitor instance for the relationship. Click Add. choose Group or Device as the primary monitor instance. choose Group or Device as the primary monitor instance. Define a relationship based on multiple 1 From the drop list. device. You can filter the list of groups or devices by entering search criteria in the Search for text box and pressing Enter. 2 From the drop list under the Group or Device selection. 2 From the drop list to the right of the Group selection. 3 In the text box beneath the Regexp selection. The new relationship is enabled and listed.Managing relationships ■ If there is no event on the primary monitor at the end of the notification wait time. 2 In the Primary Monitor Instance Selector area. choose Specific Monitors. ■ If there is an event on the primary monitor at the end of the notification wait time. choose Regexp. To add a group. BMC ProactiveNet suppresses the event on the secondary monitor and sends the notification for the event on the primary monitor. 4 Press the Enter key. perform one of the following actions: Define a relationship based on a single group or device: 1 From the drop list. The resulting list will be based on your search criteria. making it easier for you to find the desired group or device in a large list. BMC ProactiveNet sends notification for the event on the secondary monitor event as per the notification setting. 8 After completing the add relationship screen. or monitor-based Intelligent Event Suppression relationship 1 In the Scope area. The system returns to Intelligent Event Suppression screen. 406 BMC ProactiveNet User Guide .

choose Regexp. choose the monitor that you want to be the primary monitor instance for the relationship. Agent*. The drop list below the selected monitor displays the list of devices that have that monitor. Click the number of matches found link to review the resulting list to verify that this list is composed of the groups or devices that you want to be the primary monitor instances for the relationship. If the selected monitor is added to other devices. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 407 . choose Monitor as the primary monitor instance. All matches in the list will be primary monitor instances in the relationship. Define a relationship based on a single monitor Define a relationship based on multiple monitors 1 From the drop list. use regular expressions to type a pattern for the monitors that you want to be primary monitor instances for the relationship. All matches in the list will be primary monitor instances in the relationship. those devices will be included as the primary monitor instance. 4 Press the Enter key. 2 From the drop list under the Monitor selection. BMC ProactiveNet searches for groups or devices based on the pattern you entered and displays the number of matches found.Managing relationships groups or devices BMC ProactiveNet searches for groups or devices based on the pattern you entered and displays the number of matches found. 1 From the drop list. 2 From the drop list to the right of the Monitor selection. For example. Click the number of matches found link to review the resulting list to verify that this list is composed of the monitors that you want to be the primary monitor instances for the relationship. 3 In the text box beneath the Regexp selection. choose Monitor as the primary monitor instance. The primary monitor instance in the relationship will be based on the selected monitor for all the listed devices.

Choose from the following: ■ All Attributes . or monitor(s) to be the secondary monitor instance 6 (Optional. Device. choose the attributes of the primary monitor that will trigger suppression for the selected attributes on the secondary monitor. enter a description of the relationship. 408 BMC ProactiveNet User Guide . c Choose the monitor type for the attribute and click Apply. select the attribute for that monitor that will trigger events to be suppressed on the secondary monitor. (By default. 5 Using the same steps that you used for defining the primary monitor instance. and <body> tags are not supported.Managing relationships 3 In the Primary Attribute Selector area. choose the attribute set to which you want to apply the relationship. d From the drop list beneath the name of the monitor you selected. however. select group(s).) In the Description text box. select Group. This description is displayed when you hover your cursor over the more information icon next to a relationship on the Intelligent Event Suppression screen. b Click the link to the right of the Single Attribute option. To specify a single attribute: a Choose the Single Attribute option. To specify an attribute set: a Choose the Attribute Set option.an event on a single attribute for a specified monitor type will suppress events on the secondary monitor. the first monitor type in the monitor type list is selected. the <html>.) The Select Monitor Type dialog box is displayed. 4 In the Secondary Monitor Instance Selector area. device(s). or Monitor as the secondary monitor instance. b From the drop list. The Select Monitor Type dialog box closes and the name of the monitor you selected is displayed to the right of the Single Attribute option. The list of attributes available depends on the monitor type you selected. HTML is supported. <head>.an event on any attribute of the primary monitor will suppress events on the secondary monitor ■ Single Attribute . ■ Attribute Set .an event on any attribute in the selected attribute set will suppress events on the secondary monitor.

To edit an existing Intelligent Event Suppression relationship 1 On the Intelligent Event Suppression screen. Notification wait time affects secondary monitor event suppression as follows: ■ If there is no event on the primary monitor at the end of the notification wait time. click Edit. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 409 . click the Edit link for the relationship that you want to edit. 2 Make the desired changes to the relationship. The default wait time is 120 seconds.)In the Notification Wait Time field enter the time in seconds for BMC ProactiveNet to wait for an event on the primary monitor to occur before processing the event that has occurred on the secondary monitor. the less likely it is that BMC ProactiveNet will suppress the events on the secondary monitor. The system returns to Intelligent Event Suppression screen. The Add Intelligent Event Suppression Relationship dialog box is displayed. click Add. 3 Click Add. to the left of Intelligent Event Suppression. The relationship is enabled and updated. The system returns to Intelligent Event Suppression screen. The shorter the notification wait time. ■ If there is an event on the primary monitor at the end of the notification wait time. 8 After completing the add relationship screen. The new relationship is enabled and listed. 2 Choose the Administration tab. BMC ProactiveNet suppresses the event on the secondary monitor and sends the notification for the event on the primary monitor. 3 In the Advanced area. Deleting a relationship To delete a relationship 1 Click the Options menu at the top right of the console.Managing relationships 7 (Optional. BMC ProactiveNet sends notification for the event on the secondary monitor event as per the notification setting.

However. 5 Click Delete. another SLO with schedule of 9 A. 2 Click the relevant option: ■ For a new schedule. you can define new schedules.M. Through the option screen.. ■ Related topics Managing relationships on page 397 Adding or editing an Intelligent Event Suppression relationship on page 403 Managing schedules A schedule is a defined period which includes hours of the day. Schedules help put SLO compliance computation in the right perspective without distorting the values by including invalid periods. for 5 days a week (Monday to Friday) will only consider monitored attribute values recorded between 9 A. The Edit Schedule screen opens. to 5 P. 6 Click OK to confirm that you want to delete the relationship. Monday to Friday. change the values in the Days. The Add New Schedule screen opens.M. BMC ProactiveNet uses schedules to consider recorded monitored attribute values for SLO computations. 410 BMC ProactiveNet User Guide . ■ To edit an existing schedule. as well as edit or delete previously defined schedules. To add or edit a schedule 1 Navigate to Add SLO (Step 1 of 4) screen.M. 3 Specify a Name for the schedule. days of the week. click New. SLO with schedule 24x7 will consider all recorded monitored attribute values for SLO computation. To add more days to the existing schedule.Managing schedules 4 On the Intelligent Event Suppression screen. select the check box next to the relationship that you want to delete. Start Time. against the Schedule field. click Edit. and 5 P. The system deletes the relationship definition and returns to Intelligent Event Suppression screen. and End Time fields and click Add.M. and so forth. Example.

b Select the Start Time and End Time from the list. The BMC ProactiveNet Server’s time zone is selected by default. The new schedule is available in the list. click Done. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 411 .Managing schedules 4 Choose an applicable Time zone from the list of time zones provided. Start and End time relate to the each of the days. d Select check boxes against the Days to include. ■ The system updates the new time range in the table below. click Done. a Select the check box against the Day to include. To delete a schedule 1 Click Delete Schedule. f Click Add. ■ To define time range for a single day. The system updates the entries and returns to the Create SLO Wizard screen 1 of 4. 5 After adding the computation timings for all days to be part of the Schedule. Exclusion period takes precedence over inclusion period. ■ The system updates the database and returns to the SLO Creation Wizard screen 4 of 4. c Click Add. ■ The system displays a confirmatory message. 2 After making the required changes. ■ To define same time range for multiple days. e Select the Start Time and End Time from the list. ■ The system updates the new time range in the table below. Specify both inclusion and exclusion period. 6 Click Close. Use the list to change the time zone.

and roles. . Using this option. ■ Do not open the exported XML file before importing it on another machine.Use text editor. user accounts from testing environment can be exported and imported to the production setup. If user want to open the exported XML file for any security reasons. Note ■ First export the users and then import them. to maintain the user accounts across all the BMC ProactiveNet server’s Enterprise environment. 412 BMC ProactiveNet User Guide . The following scenarios help you understand the steps you will need to perform while importing users. Table 113: Scenarios while importing users Import User(s) Exists User Group(s) Exists All Some Procedure Only user Only user Only user Yes No No Do not create the user as the user with this name already exists in the system.Importing and exporting users Importing and exporting users Users (Export or Import) enables to export and import the users from one BMC ProactiveNet Server to the other.There is no need for the user to open the exported XML file before importing on a different machine . Create users and map only to the user groups which already exists. ■ Ensure that the users you import are the same as you export. Create users and map to all the existing user groups. If you want to view the exported XML file in a browser copy the file to <PN_PATH>\pw\pronto\web on the BMC ProactiveNet server to locate the DTD. user groups. Use text editor if you want to open the exported XML file.

User Groups. and Roles Users. 2 Click Export link corresponding to Users. To export users 1 Click Options => Administration => Advanced => Users . User Groups. 2 Create a Read Only user group and assign the Read Only role.Importing and exporting users Import User(s) Exists User Group(s) Exists None Procedure Only user No If Read Only user group exists 1 Create a user and assign it to the Read Only user group. to open Export User Data screen. 2 Create a user and map it to all the user groups (newly created as well as existing). and Roles No None 1 Create all user groups present in the XML file (if required create roles if the roles on which these user groups are dependent on do not exist). Users. User Groups. 3 Create a user and assign the Read Only group created above. No Some 1 Create user groups which do not exist from the XML file (if required. Users. User Groups. 2 Create a user and assign it to all the above newly created user groups. users can be selected based on the following options: Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 413 . and Roles Users. and Roles Yes Skip No All Create user and map it to all the existing user groups. 3 Use the Filter options to select the users. Else 1 Create a Read Only role if it does not exist. create roles if the roles on which this user groups are dependent do not exist).

9 Click Close in the Download Complete window. 6 Click Export. 8 Click Save in the Save As window. 2 Click Import link corresponding to the Users. to open Save As window.Importing and exporting users ■ User Class ■ Status ■ User Name ■ User Group or Role 4 Specify a User Name and User Group or Role. Select Import User Groups and Roles if you want to import the user(s) along with the user groups and roles. and the default location is desktop.xml. The default file name is userdata. 3 Specify the Import File name or use the Browse option to locate the file. This screen gives the status of the import and the user details table. to open the Import User(s) screen. 10 Click Back to Administration link to return to Administration Tab. to display the User Import Summary screen. 414 BMC ProactiveNet User Guide . 5 Click Cancel in the Import User(s) screen to return to Administration Tab without importing the user. 5 Select the User form the table. Select Export User Groups and Roles if you want to also export user groups as well as the roles associated with the users. to open File Download window. To import users 1 Click Options => Administration => Advanced => Users. select Select All to export all the users. This will import all the user groups and roles and associate them to the appropriate users. 7 Click Save in the File Download window. to open Download Complete window. 4 Click Import.

4 The Performance Diagnostics Details screen displays the following details as described in Table 114 on page 416. Click View link of Installation Rules.Viewing BMC ProactiveNet software information Viewing BMC ProactiveNet software information This section provides links to view installation history. and Performance Diagnostic Details. 2 The BMC ProactiveNet Server Performance screen displays the options Performance Graphs. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 415 . Viewing BMC ProactiveNet performance diagnostics BMC ProactiveNet offers both pre-configured and user-defined diagnostic tools to help monitor your system. The Options screen opens. It provides information of various patches. To view installation history 1 Click the Options link at the top right of the console. under the BMC ProactiveNet heading. 4 Use the filter to search for specific information. 2 On the Administration tab. 3 Click View link of Details to view performance diagnostic details. under the BMC ProactiveNet heading. Click View link of Performance Diagnostics. Installation history The Installation history provides an audit trail of BMC ProactiveNet installation. performance diagnostics and license usage information. To view performance diagnostic details 1 On the Administration tab. 3 The View History File screen opens. and hotfixes applied on BMC ProactiveNet Server.

Scroll down to the Event Details heading to see the number of open and closed events of all types. poll period in second. number of active poll period in seconds. number of instances. displays a list of all views including those that were not created by you.Viewing BMC ProactiveNet software information Table 114: Diagnostic details Performance diagnostic types General Details Cell metrics Remote Agent Device Monitor instance Monitor type Attribute User Data details Graph View Report SLO Event Description displays the server sizing details. total number of attributes. describes the cell-based event activity and lists the event classes that are sending the events displays the type of operating system on which BMC ProactiveNet is installed and Agent counts. displays the monitor type. Click View next to Performance Diagnostic Details to see a list of detailed statistics. displays a list of all reports including those that were not created by you. attribute id and total number of events. displays if monitor instances are turned off by the device flag or device instance flag. However. monitor instances count. number of attributes per monitor type. 416 BMC ProactiveNet User Guide . This also gives the details about the monitor type. ■ External events . and total instance attributes. displays the monitor type. displays SLO details. displays a list of all graphs including those that were not created by you. These details can be displayed or hidden using the Show and Hide option. you are restricted to view only those events that are created by you. displays the following event details: ■ Signature Events .This gives the number of open and closed absolute events. displays the device type and count. displays the minimum and maximum value of raw data retention period in hours.This give the number of open and closed signature events. both device-associated and non-device-associated. and instances per second.This gives the number of open and closed external events. ■ Absolute events . Report details can either be hidden using the Show or Hide options. User detail screen is categorized in to two types namely: configured users and logged in users. and custom API instances per second. and minimum and maximum value of rate data retention period in hours.

Viewing BMC ProactiveNet license usage BMC ProactiveNet License Usage screen displays information on the licensed features of BMC ProactiveNet. and so forth Routing TCP connection displays routing details. BIOS. displays the TCP connection details. 2 The License Usage screen displays the license details. 3 Click Show Details to view details of default monitors. physical memory. 3 Click Send. processor. number of licenses being used. under the BMC ProactiveNet heading. The Email Details Snapshot screen opens. 2 Enter the required email information. To view license usage details 1 On the Administration tab. System information displays details about the physical system: its name. Note Performance Diagnostic page takes much longer duration to load (6 minutes) on WIndows. and number of licenses available at present. Chapter 9 Controlling BMC ProactiveNet data collection and infrastructure 417 . To send and view mails 1 On the License Usage screen at the right hand corner. click View link of License Usage. exact number of licenses available for each BMC ProactiveNet feature or monitor. click the mail icon. It can vary depending on the operating system of the server. OS.Viewing BMC ProactiveNet software information Performance diagnostic types System specific Description displays the system specific details of the server.

See the BMC ProactiveNet Getting Started Guide for exact steps to install BMC ProactiveNet Agent and BMC ProactiveNet Administration Console.Downloads tab Downloads tab Links to various files required for installing the BMC ProactiveNet Agent and BMC ProactiveNet Administration Console are available here. 418 BMC ProactiveNet User Guide .

Integrating BMC ProactiveNet with BMC BladeLogic provides BladeLogic job history information to probable cause analysis. The probable cause analysis results page indicates if there has been a BladeLogic job executed on the device before 24 hours and after 30 minutes from the current time stamp of the primary event. For more information about probable cause analysis. the job name. see Determining the probable cause for an event on page 159 The following BMC BladeLogic job types are considered during probable cause analysis: ■ Deploy Job (30) ■ Deploy Job Attempt (205) ■ File Deploy Job (40) Chapter 10 Integrating with BMC BladeLogic 419 . If a BladeLogic job has been executed on the device. Benefits of BMC BladeLogic integration A BladeLogic job might make a configuration change to a device which causes its behavior to change. This snapshot job will be able to detect better the configuration changes made to the device. certain events that are generated on BMC ProactiveNet will trigger the execution of a pre-defined snapshot job on BMC BladeLogic. job type. When you access probable cause analysis for a service degradation event. the probable cause analysis results page flags devices which have had BladeLogic jobs execute in the same time frame as the event that you are trouble-shooting.10 Integrating with BMC BladeLogic This chapter provides details on how to import BMC BladeLogic information into BMC ProactiveNet so that you can factor BladeLogic job history into probable cause analysis. In addition. the probable cause analysis filters and ranks the events from most probable cause to least. so that when you invoke probable cause analysis for an event. and start and end time of the job is displayed next to the device.

such as a deploy job or an Network Shell Script job. unless the batch job contains any of the supported job types. These changes will be displayed. The following job types are not supported or displayed in probable cause analysis device history: ■ ACL Push Job (1009) ■ Batch Job (200) ■ Atrium Import Job (5190) ■ Audit Job (31) ■ Compliance Job (5106) ■ Component Discovery Job (405) ■ Patch Analysis Job (45) ■ Provision Job (5029) ■ Update Service Properties Job (1017) ■ Patch Subscription (220) ■ Download Job (46) 420 BMC ProactiveNet User Guide .Benefits of BMC BladeLogic integration ■ Network Shell Script Job (111) ■ Sync Job (190) ■ Deploy Apply Job (203) ■ Deploy Undo Job (204) ■ Snapshot Job Note Snapshot job executions are listed in the probable cause analysis device history only if the snapshot job detects any changes. Batch jobs also are not listed in the probable cause analysis device history.

3 From the BMC BladeLogic Application Server Administration utility. run the following command: set AppServer EnableTomcatService true Chapter 10 Integrating with BMC BladeLogic 421 . access the /opt/bmc/BladeLogic/8. This is required only for pw blade create packages command. No other roles should be assigned to this user. From the command line. To enable Web services on the BMC BladeLogic Application Server 1 Log in to the BMC BladeLogic Application Server. ■ For UNIX. serve as the BladeLogic administrator account ■ create a dedicated user account for the BMC BladeLogic Application Server to ■ enable Web services on the BMC BladeLogic Application server ■ set up the credentials on the BMC ProactiveNet Server for accessing BMC BladeLogic from BMC ProactiveNet ■ test the credentials on the BMC ProactiveNet Server that you have set up to ensure that a connection is being made To create a dedicated BladeLogic administrator user account for the BMC BladeLogic Application Server 1 Create a new user for the BMC BladeLogic Application Server. choose Start => Programs => BMC Software BladeLogic => Utilities => Application Server Administration.Setting up the integration between BMC BladeLogic and BMC ProactiveNet Setting up the integration between BMC BladeLogic and BMC ProactiveNet To integrate BMC BladeLogic with BMC ProactiveNet you must ■ install and license the BMC BladeLogic Agent on the BMC ProactiveNet Server (for instructions. 2 Assign that user the single role of BLAdmins. see the BMC BladeLogic documentation). 2 Start the BMC BladeLogic Application Server Administration utility as appropriate for your operating system: ■ For Windows. enter blasadmin. using the BLAdmins account.1/NSH/br directory.

5 Restart the BMC BladeLogic Application Server. and CLITunnelService. To set up credentials with the UDDI registry on the BMC ProactiveNet Server for accessing BMC BladeLogic from BMC ProactiveNet 1 Log in to the BMC ProactiveNet Server as administrator. These will be registered with the specified web services properties when you start the BladeLogic server. 2 Access a command line and enter: pw blade setup -use_uddi -uddiuser uddiUserName -uddipass uddiPassword host hostName [-port portNumber] -user userName -pass password 422 BMC ProactiveNet User Guide . The Blade Logic Application Server log indicates if the web services registration was successful for LoginService.Setting up the integration between BMC BladeLogic and BMC ProactiveNet 4 [optional] To configure the registration of web services in the BMC Atrium UDDI Server. by giving the following commands: ■ You can remove the web services registration in the BMC Atrium UDDI Server — set WebServices RegistryServer "" — set WebServices RegistryServerPort "" — set WebServices RegistryServerUserName "" — set WebServices RegistryServerPassword "" The web services registered in the BMC Atrium UDDI server will be removed when the BladeLogic server is shutdown. AssumeRoleService. enter the following commands: ■ set WebServices RegistryServer registryServerHostName set WebServices RegistryServerPort registryServerPort set WebServices RegistryServerUserName registryServerUserName set WebServices RegistryServerPassword registryServerPassword The default Registry Server port is 8080. No other roles should be associated with this user account or the integration will fail. WARNING ■ You must create a dedicated user account with only a BLAdmins role.

Setting up the integration between BMC BladeLogic and BMC ProactiveNet Table 115: pw blade setup with UDDI registry command option descriptions Option -use_uddi -uddiuser uddiUserName -uddipass uddiPassword -host hostName -port portNumber -user userName -pass password Description specifies to use the UDDI registry to obtain BMC BladeLogic web services host and port information user name to connect to UDDI server password to connect to UDDI server host name or IP address of the UDDI server port number of the UDDI server user name to connect to the BladeLogic Application Server Note: This should be the user account created for the BLAdmins role. ■ If the command returns 1. You can now To change the time correlation filter on page 172. a message Info: Connection to BladeLogic server succeeded. the credentials were created successfully.domain. Re-enter the pw blade setup command correctly. an execution error has occurred. 2 Access a command line and enter: pw blade setup -host hostName [-port portNumber] -user userName -pass password Chapter 10 Integrating with BMC BladeLogic 423 .com –port 8080 –user pronet –pass opensesame If the connection is successful. To set up credentials without the UDDI registry on the BMC ProactiveNet Server for accessing BMC BladeLogic from BMC ProactiveNet 1 Log in to the BMC ProactiveNet Server as administrator. password to connect to BladeLogic Application Server For example. 3 Follow the appropriate instructions based on the return code that you receive: ■ If the command returns 0. ■ If the command returns a number other than 0 or 1. is displayed. there is a syntax error. pw blade setup –use_uddi -uddiuser udaman -uddipass uopensesame –host server. An error message is displayed indicating which error occurred.

3 Follow the appropriate instructions based on the return code that you receive: ■ If the command returns 0.domain. ■ If the command returns 1. password to connect to BladeLogic Application Server For example. 3 Follow the appropriate instructions based on the return code that you receive: ■ If the command returns 0. a message Info: Connection to BladeLogic server succeeded. If the connection is successful. is displayed. An error message is displayed indicating which error occurred. 2 Access a command line and enter the command pw blade test. To test your credentials on the BMC ProactiveNet Server for accessing BMC BladeLogic 1 Log in to the BMC ProactiveNet Server as administrator. an execution error has occurred. Re-enter the pw blade setup connection command correctly. a message Info: Connection to BladeLogic server succeeded. then the credentials that you set up are working correctly. You can now To change the time correlation filter on page 172. is displayed.com –port 9843 –user pronet – pass opensesame If the connection is successful. you can now To install the BMC ProactiveNet provided content on BMC BladeLogic on page 427.Setting up the integration between BMC BladeLogic and BMC ProactiveNet Table 116: pw blade setup without UDDI registry command option descriptions Option -host hostName -port portNumber -user userName -pass password Description host name or IP address of BladeLogic Web Services port number of BladeLogic Web Services user name to connect to the BladeLogic Application Server Note: This should be the user account created for the BLAdmins role. ■ If the command returns a number other than 0 or 1. is displayed. If desired. Error: BladeLogic connection information has not been setup. there is a syntax error. 424 BMC ProactiveNet User Guide . the credentials were created successfully. If the connection is unsuccessful a message. pw blade setup –host server.

Re-enter the pw blade clear ■ If the command returns a number other than 0 or 1.Additional change information using snapshot job execution ■ If the command returns 1. 2 Access a command line and enter: pw blade clear connection If the connection is successful. there is a syntax error. If desired. you may need to To clear the connection to BMC BladeLogic that you created on the BMC ProactiveNet Server on page 425 and To set up credentials with the UDDI registry on the BMC ProactiveNet Server for accessing BMC BladeLogic from BMC ProactiveNet on page 422 again. An error message is displayed indicating which error occurred. you can To set up credentials with the UDDI registry on the BMC ProactiveNet Server for accessing BMC BladeLogic from BMC ProactiveNet on page 422 from a different user. ■ If the command returns 1. Additional change information using snapshot job execution Chapter 10 Integrating with BMC BladeLogic 425 . is displayed. Re-enter the pw blade test connection command correctly. Warning: BladeLogic connection information has not been setup. is displayed. an execution error has occurred. If the connection is unsuccessful a message. a message Info: Connection to BladeLogic server succeeded. connection command correctly. an execution error has occurred. An error message is displayed indicating which error occurred. the credentials that you set up are no longer available. there is a syntax error. To clear the connection to BMC BladeLogic that you created on the BMC ProactiveNet Server 1 Log in to the BMC ProactiveNet Server as administrator. ■ If the command returns a number other than 0 or 1. Depending on the error message displayed. 3 Follow the appropriate instructions based on the return code that you receive: ■ If the command returns 0. Warning: Clearing of BladeLogic connection information failed.

Also. Limitations ■ BMC BladeLogic can run only a single instance of a snapshot job at a time. When events matching the criteria mentioned above are received/generated. This snapshot job will be able to better detect the configuration changes made to that device. the snapshot job is executed. so that when you invoke probable cause analysis for an event. a mapping file called <<install_dir>/pronto/conf/ supportedDeviceTypesAndOSForBlade. 426 BMC ProactiveNet User Guide . integration to work. Hence. For more information. This information can be viewed from the BMC BladeLogic Device History results screen. This may lead to some events on BMC ProactiveNet not triggering snapshot jobs on BMC BladeLogic (since earlier snapshot jobs may not have completed). You can create content that is more tuned to your environment by customizing the BMC ProactiveNet provided content or by creating new content. ■ The BMC ProactiveNet agent is required on the target machine for BladeLogic Installing the BMC ProactiveNet content BMC ProactiveNet provides pre-defined content by means of a content installer that helps load BMC ProactiveNet content into the BladeLogic server. Integrating BMC ProactiveNet with BMC BladeLogic provides BladeLogic job history information to probable cause analysis. a default throttling logic time period of 10 minutes(can be altered in pronet. if a particular snapshot job is triggered on BMC BladeLogic. the probable cause analysis results page flags devices which have had BladeLogic jobs execute in the same time frame as the event that you are trouble-shooting.conf) needs to elapse before the same snapshot job is executed again.Installing the BMC ProactiveNet content A BladeLogic job might make a configuration change to a device which causes its behavior to change. This snapshot job captures change information on the device associated with the generated/received event provided a BMC BladeLogic RSCD agent is also running on that device. certain events that are generated on BMC ProactiveNet will trigger the execution of a pre-defined snapshot job on BMC BladeLogic for that device (provided the BMC ProactiveNet pre-defined content has been installed on BMC BladeLogic). This content helps collect relevant configuration change information which helps probable cause analysis. Certain events (critical or major events that are associated with devices that have a BMC ProactiveNet agent installed) generated/received on BMC ProactiveNet can cause a BMC ProactiveNet provided snapshot job to be executed on the BMC BladeLogic server. the snapshot job must finish execution before it can run again. In addition.conf> is looked up to check which snapshot job to run on BMC BladeLogic. If a match is found. see “Viewing BMC BladeLogic device history information” on page 431.

The component discovery job must run at least once on all targets so that components. 5 Edit all three snapshot jobs (PPM-SolarisOS-Snapshot. can be discovered. This step is mandatory. This step is mandatory. PPM-WeblogicSolaris-Snapshot) to assign the proper targets and create an appropriate schedule for the snapshot jobs. Run all three snapshot jobs once.bin PPM-linux-8_1-nnn.Installing the BMC ProactiveNet content BMC ProactiveNet provided content consists of three component templates.bin 2 Copy the content installer to the machine where BMC BladeLogic server is installed.jsp. three associated snapshot jobs and three associated component discovery jobs.bmc. Run all three component discovery jobs once. To install the BMC ProactiveNet provided content on BMC BladeLogic 1 Download the BMC ProactiveNet content installer from https:// webapps. PPM-ApacheSolarisSnapshot. Chapter 10 Integrating with BMC BladeLogic 427 . PPM-WeblogicComponentDiscovery) to assign the proper targets and create an appropriate schedule for the component discovery jobs. 3 Run the content installer which will import the BMC ProactiveNet provided content into the BMC BladeLogic server. if any. PPM-ApacheSolaris-ComponentDiscovery. BMC ProactiveNet provides content that is appropriate for capturing configuration change for Solaris OS. Apache Web server on Solaris OS and for WebLogic application server on Solaris OS. Snapshot jobs run on the same targets will not work unless components have been discovered. The filenames of the content installer for BladeLogic server are as follows: OS Windows Solaris Linux Filename PPM-8_1-nnn. 4 Edit all three component discovery jobs (PPM-SolarisOS-ComponentDiscovery.com/epd/faces/licensedProd.exe PPM-solaris-8_1-nnn.

428 BMC ProactiveNet User Guide . d Select the PPM folder and right-click. Browse.Creating new BladeLogic content Creating new BladeLogic content You can create content that is more tuned to your environment. f Select this newly created component template from the Folder and right-click to select the Open option. The component template will open in edit mode. To create new content 1 Create component template PPM-ApacheLinux-Template on BladeLogic server. Browse and Snapshot from the Allowed Operations section and click Next three times. add the parts that make up this component by clicking on the + sign which shows the Select Parts dialog. g Select the Parts. e Select Discover. You can parameterize the name using properties (both local properties and global properties). Click Finish to create the bare bones component template. Properties can be entered in the form ?? APACHE_CONF_DIR??. Click Ok twice to create the part. Select the type of the part with the first drop down (File. Add more parts if necessary. Click Add New button to display the New Component Template Part dialog. select the Component Template folder and rightclick to get the context menu. The following procedure gives an example of how to create content for Apache on Linux which is not a pre-defined sample starter content given by BMC ProactiveNet. h In the Parts tab. etc. Snapshot and Local Properties tab to edit section. Discover.) and then add the name. Directory. c If PPM folder does not exist. From the context menu select New => Component Template to create a component template and provide the template name as PPM-ApacheLinuxTemplate. a Log into BladeLogic Server Automation Console. expand the Component Templates folder. Select New => Component Template Folder to create a new folder called PPM. b Under the Folders tab.

SnapshotJobName. ■ ComponentTemplateName . WebServer). ■ SnapShotJobName .Linux.Name of the snapshot job that should be triggered. Chapter 10 Integrating with BMC BladeLogic 429 . 2 Create corresponding component discovery job PPM-ApacheLinuxComponentDiscovery on BladeLogic server and specify the PPM-ApacheLinuxTemplate as the template. add a new entry "WebServer.ComponentTemplateName ■ DeviceType . The discovery rule is used by the component discovery job to discover components on specified targets.The fields are BMC ProactiveNet Device type (for example. Assign proper targets and create a schedule for the snapshot job. Snapshot jobs will not run on targets unless components have been discovered. The map file is in a CSV format with one line per device type. 4 To map the snapshot jobs created on BladeLogic server (PPM-ApacheLinuxSnapshot) onto the BMC ProactiveNet configuration file. PPM-ApacheLinuxSnapshot. add an entry to <install directory> /pw/pronto/conf/supportedDeviceTypesAndOSForBlade. For example. ■ SnapShotPath . ■ OS .OS. Server. Assign proper targets and create a schedule for the component discovery job. 3 Create a corresponding snapshot job PPM-ApacheLinux-Snapshot on BladeLogic server and specify the PPM-ApacheLinux-Template as the template./PPM. Local properties and global properties can be used.conf.Operating System type. click on the Show the Test Signature Screen button in the Discover tab.SnapShotPath. The component discovery job must run at least once on all targets so that components. if any. The format in the CSV file is DeviceType.Name of the component template that is associated with the snapshot job. can be discovered. PPM-ApacheLinux-Template ".Group name where BMC ProactiveNet provided snapshot job is present.Creating new BladeLogic content i To add a Rule Definition.

there is a syntax error. Info: Creation of BladeLogic packages for ProactiveNet agents succeeded. 430 BMC ProactiveNet User Guide . you can create packages so that BladeLogic can deploy ProactiveNet Agents to BladeLogic managed systems.Creating packages to deploy ProactiveNet Agents to BMC BladeLogic managed systems Creating packages to deploy ProactiveNet Agents to BMC BladeLogic managed systems After you have set up and tested the credentials necessary to connect the ProactiveServer to the BMC BladeLogic managed system. ■ If the command returns a number other than 0 or 1.. ■ The machine on which the BMC ProactiveNet Server is installed must be reachable from the machine where BMC BladeLogic Server is installed. Re-enter the pw blade create packages command correctly.. 3 Follow the appropriate instructions based on the return code that you receive: ■ If the command returns 0. The ProactiveNet Agent software is loaded into the BladeLogic depot in the / Software/BMC/ProactiveNet directory as BMC_PN_Agent version_build_platform. an execution error has occurred. Creating BladeLogic packages for ProactiveNet agents This may take a long time. An error message is displayed indicating which error occurred. To create packages to deploy BMC ProactiveNet Agents from the BMC ProactiveNet Server to BMC BladeLogic managed systems 1 Log in to the BMC ProactiveNet Server as administrator. Before you begin ■ You must have Administrator privileges to create these packages. ■ If the command returns 1. 2 Access a command line and enter: pw blade create packages If the command succeeds the following message is displayed. ■ A BMC BladeLogic Agent must be installed on the BMC ProactiveNet Server and it must be running. execution was successful.

■ Before executing the pw blade create packages command you should delete the existing software and packages on the BMC BladeLogic Server.Viewing BMC BladeLogic device history information The packages are created in the BladeLogic depot in the /Packages/BMC/ ProactiveNet directory as BMC_PN_Agent_ platform. use BMC BladeLogic to create and run a deployment job to deploy the packages to BMC BladeLogic managed systems. Go to the BladeLogic depot and delete the software BMC_PN_Agent version_build_platform in the directory /Software/BMC/ProactiveNet. Note ■ BMC recommends that the BMC BladeLogic server and the BMC ProactiveNet Server are in the same LAN. Creating packages across a slow WAN is not recommended because the pw blade create packagescommand may time out while copying the agent packages from the BMC ProactiveNet Server to the BMC BladeLogic server. Also. Viewing BMC BladeLogic device history information BMC BladeLogic device history information is available from the Tools menu in the Operations Console or from the Probable Cause Analysis dialog box. delete the packages BMC_PN_Agent_ platform in the directory /Packages/BMC/ ProactiveNet. Once the packages are created. Chapter 10 Integrating with BMC BladeLogic 431 .

History Filters allows you to filter out the BladeLogic jobs from the BladeLogic Device History page. Setting the Relative time filters the events that occurred during the specified time until the system time. Figure 27: BMC BladeLogic Device History screen The Time filter displays 24 hours before and 30 minutes after the timestamp of the event.M. are displayed. To add history filters. For example.. The Edit Time option allows you to edit the Relative and Absolute time.Viewing BMC BladeLogic device history information Figure 27 on page 432 shows the BMC BladeLogic Device History results screen. Table 117 on page 432 lists the columns in the BMC BLadeLogic Device History results screen and describes the information that is contained in each column. refer to “To add history filters” on page 434. if you do not want to view them from the current page as well as from all the BladeLogic pages. Table 117: Description of BladeLogic Device History screen Column Host Name Description Name of the device for which BladeLogic changes have occurred Name of the BladeLogic job that contributed the change 432 BMC ProactiveNet User Guide .M. Absolute time allows you to specify the time range for displaying the events that occurred during the specified time period. the events that occurred from 09:55 to 10:00 A. if you specify 5 minutes and the system time is 10:00 A.

For example. select BladeLogic Device History. select the event for which you want to obtain BMC BladeLogic device history. select an event that occurred on the device with a timestamp on or near 10:30AM on the current date. 2 Click the Tools menu icon for that event.Viewing BMC BladeLogic device history information Column Type Description Icon representing the type of job: ■ ■ ■ : Deploy jobs : Nsh jobs or scripts : Snapshot jobs Start End Status User Template Part Changed Timestamp for when the job began Timestamp for when the job ended End result of the job User name of the account who ran the job Details the changes to BladeLogic templates captured by snapshot jobs To view BMC BladeLogic device history from the Tools menu 1 From the Events Console. 2 Click the probable cause analysis icon . The BladeLogic Device History screen displays the BMC BladeLogic device history for 24 hours before and 30 minutes after the timestamp of the event that you selected. BMC BladeLogic device history is displayed for 24 hours before and 30 minutes after the event's timestamp. to see the BladeLogic history for the previous 24 hours up until 10:30AM on the current day. To view BMC BladeLogic device history from the Probable Cause Analysis results page 1 From the Events Console. By default. 3 From the Tools menu. Chapter 10 Integrating with BMC BladeLogic 433 . select an event which occurred 24 hours before and 30 minutes after the event's timestamp for which you want to obtain BMC BladeLogic device history.

click the delete filter icon next to the filter you have defined. 2 Click on Add Exclusion Filter from the Device History Exclusion Filters screen that is displayed. Note To delete a filter. 434 BMC ProactiveNet User Guide . For more information about probable cause analysis. click the Tools menu icon for the event and choose BladeLogic Device History. as well as the time of the last change. 5 Click on the Preferences icon to specify the filter for all BladeLogic pages. For more detailed BladeLogic device history. Restore Defaults option will remove all the specified filters. 3 Select the job type from the drop down list. see the BMC BladeLogic documentation. 4 Specify a pattern match in the Job Name contains field and click OK. The jobs that match the pattern name are excluded from the current page.Viewing BMC BladeLogic device history information A summary of the BMC BladeLogic device history is included in the BladeLogic History column in the probable cause analysis results page for the selected event. The BMC BladeLogic Device History screen will be displayed. To add history filters 1 Click on the link against History Filters to edit the filter. This column includes the icon for the job type. see Determining the probable cause for an event on page 159 For more detailed information about BMC BladeLogic.

Table 118: Event classes not considered during probable cause analysis ■ MC_CELL_UNDEFINED_CLASS ■ MC_CELL_PARSE_ERROR ■ MC_SMC_EVENT ■ MC_CELL_PROCESS_ERROR ■ MC_SM_SHADOW_REQUEST ■ MC_SM_IMPACTS_REPORT ■ MC_SM_SHADOW_REQUEST_ERROR ■ MC_SM_SHADOW_UPDATE ■ MC_SM_SHADOW_DELETE ■ MC_SM_LOOP_DETECTED ■ SIM_NOTIFICATION_EVENT ■ SIM_COMPONENT_OVERWRITE ■ SIM_COMPONENT_CHANGE ■ SIM_COMPONENT_DELETE Appendix A Event information used in probable cause analysis 435 .A Event information used in probable cause analysis Event classes not used by probable cause analysis Administrative events include all events within the following event classes which are children of the EVENT class.

Event classes not used by probable cause analysis ■ SIM_RELATIONSHIP_CHANGE ■ SIM_RELATIONSHIP_DELETE ■ SMC_MAINTENANCE ■ MC_SLM_EVENT ■ MC_SLM_ASSOCIATE ■ MC_SLM_STATUS_UPDATE ■ MC_SLM_REMOVE_SLA_FREQUENCY ■ MC_SLM_DELETE_SLA ■ MC_UPDATE_EVENT ■ ADMIN_EVENT ■ ADMIN_CONFIG_INFO ■ ADMIN_UNREGISTER ■ ADMIN_UNREGISTER_PRODUCT ■ ADMIN_CLEAR_BLOCK ■ ADMIN_ACTIVITY_STATE ■ ADMIN_SECONDARY_INFO ■ IAS_STOP IAS_SYNC_EVENT ■ IAS_EVENT IAS_START ■ IAS_SYNC_BACKUP IAS_REINIT ■ IAS_SYNC_PRIMARY ■ IAS_LOGIN IAS_ERROR ■ BIP_EVENT BIP_START ■ BIP_STOP IPS_EVENT ■ IPS_CONTROL IPS_START ■ IPS_CONFIG IPS_STOP ■ IPS_CNX IPS_CONNECT ■ IPS_IM_CONNECT IPS_ERROR ■ IPS_REQUEST IPS_PUBLISH ■ IPS_CELL_PUBLISH ■ IPS_CLASSINFO IPS_ENV ■ IPS_CLASSINFO IPS_ENV ■ IBRSD_ADMIN_EVENT 436 BMC ProactiveNet User Guide .

Event classes not used by probable cause analysis ■ IBRSD_START IBRSD_STOP ■ MC_CLIENT_BASE ■ MC_CLIENT_CONTROL ■ MC_CLIENT_START ■ MC_CLIENT_STOP ■ MC_CLIENT_PAUSE ■ MC_CLIENT_UNPAUSE ■ MC_CLIENT_HEARTBEAT ■ MC_CLIENT_ERROR ■ MC_ADAPTER_BASE ■ MC_ADAPTER_CONTROL ■ MC_ADAPTER_ERROR ■ MC_ADAPTER_START ■ MC_ADAPTER_STOP ■ PORTAL_PARAMETER_STATE_CHANGE ■ PORTAL_RSM_STATE_CHANGE ■ SMC_STATE_CHANGE ■ IBRSD_ERROR ■ IBRSD_RETRY_EVENT ■ IBRSD_EVENT ■ IBRSD_SM_INCIDENT ■ IBRSD_REMOTE_ACTION ■ IBRSD_SM_INCIDENT ■ IBRSD_REMOTE_ACTION ■ IBRSD_SM_INCIDENT_CLOSE ■ CI_INCIDENT_INFO ■ MC_CELL_CONTROL ■ MC_CELL_START ■ MC_CELL_STOP ■ MC_CELL_TICK ■ MC_CELL_STATBLD_START ■ MC_CELL_STATBLD_STOP Appendix A Event information used in probable cause analysis 437 .

Slots used during probable cause analysis ■ MC_CELL_ACTIVITY_CHANGED ■ MC_CELL_DB_CLEANUP ■ MC_CELL_LOG_CHANGED ■ MC_CELL_LOG_MSG ■ MC_CELL_CONNECT ■ MC_CELL_CONNECT_RESOURCES_EXP ANDED ■ MC_CELL_CONNECT_SUSPENDED ■ MC_CELL_CONNECT_RESUMED ■ MC_CELL_CLIENT ■ MC_CELL_UNALLOWED_CONNECT ■ MC_CELL_ALLOWED_CONNECT ■ MC_CELL_DISCONNECT ■ MC_CELL_MODIFIED_EVENT ■ MC_CELL_DESTINATION_UNREACHA BLE ■ MC_CELL_HEARTBEAT_EVT ■ MC_CELL_HEARTBEAT_ON ■ MC_CELL_HEARTBEAT_FAILURE ■ MC_CELL_DUPLICATE_EVT ■ MC_CELL_DUPLICATE_ON ■ MC_CELL_DUPLICATE_FAILURE ■ MC_CELL_RESOURCE ■ MC_CELL_RESOURCE_OVERFLOW ■ MC_CELL_RESOURCE_EXPANSION ■ MC_CELL_RESOURCE_REDUCTION ■ MC_CELL_ACTION_RESULT ■ MC_CELL_PUBLISH_RESULT Slots used during probable cause analysis The following core event slots provide data that is used during probable cause analysis: 438 BMC ProactiveNet User Guide .

Slots used during probable cause analysis ■ eventclass ■ date_reception ■ status ■ msg ■ severity ■ mc_ueid ■ mc_priority ■ mc_smc_id ■ mc_date_modification ■ mc_incident_time ■ mc_location ■ mc_host ■ mc_host_address ■ mc_parameter_value ■ mc_parameter_unit ■ mc_event_category ■ mc_incident_time ■ mc_object_class ■ mc_object ■ mc_tool_key ■ mc_host_id ■ mc_host ■ mc_tool_key ■ mc_long_msg More data is provided by the following slots from the ALARM and ABNORMALITY event classes: ■ pn_parameter_id ■ pn_last_time ■ pn_group_ids ■ pn_thresh_id ■ pn_thresh_type ■ pn_alarm_id ■ pn_vm_host_id ■ pn_highest_severity ■ pn_end_time ■ pn_detail_diag ■ pn_detail_diag_count ■ pn_suppress_type ■ pn_suppress_mode ■ pn_suppress_notified ■ pn_suppress_rule_id ■ pn_thresh_above ■ pn_baseline_type ■ pn_baseline_hourly_low Appendix A Event information used in probable cause analysis 439 .

Monitors related to VMware ■ pn_baseline_daily_low ■ pn_baseline_weekly_low ■ pn_baseline_hourly_high ■ pn_baseline_daily_high ■ pn_baseline_weekly_high ■ pn_thresh_duration ■ pn_pts_exceeded ■ pn_pts_total ■ pn_extremeness ■ pn_predict_to_occur_time ■ pn_object_class_id The following extended slots from the DEVICE_UPDATE_EV event class provide additional data: ■ new_parent_device_unique_name ■ parent_device_unique_name Monitors related to VMware The following monitors are related to VMware: ■ BMCVMwareResourcePool ■ BMCVMwareCPU ■ BMCVMwareVM ■ BMCVMwareVMCPU ■ BMCVMwareMemory_V2 ■ BMCVMwareCPU_Total ■ BMCVMwareHostMon ■ BMCVMwareDatastoreMon ■ BMCVMwareDiskPerfMon ■ BMCVMwareVCMon ■ BMCVMwareVnetPerfMon ■ VMwareVMSysMon ■ VMwareVMMemMon ■ VMwareHostBusAdapterMon ■ VMwareVCSysMon ■ VMwareHostSysMon ■ VMwareHostMemMon ■ VMwareVMNetMon ■ VMwareVMCPUMon ■ VMwareHostCPUMon ■ VMwareHostNetMon 440 BMC ProactiveNet User Guide .

Monitors related to VMware ■ VMwareRPSysMon ■ VMwareHostDiskMon ■ VMwareVMCPUTotMon ■ VMwareVMDiskTotMon ■ VMwareVMNetTotMon ■ VMwareHostCPUTotMon ■ VMwareHostDiskTotMon ■ VMwareHostNetTotMon ■ VMwareHostDSMon ■ VMwareMon ■ VMwareHostDatastorePathMon Appendix A Event information used in probable cause analysis 441 .

Monitors related to VMware 442 BMC ProactiveNet User Guide .

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Index A Acknowledge event icon 76 event operation 76 Acknowledged (ACK) event status icon 26 actions responding to an event 80 area graph. creating a pie graph 259 Custom graphs. creating 19 E event collectors described 25 event count affected by status 29 event list folder. creating 261 B BMC Impact Explorer Event Groups. finding 20 configuring Events tab display settings 86 creating local filter 68 current data 130 Custom Graphs 249 Index 443 . creating for remote cells 61 event operations. creating a top N graph 257 Custom graphs. creating 251 Assign To (event operation) 76 Assigned event status icon 26 Auto-baseline 183 Custom graphs. changing preferences 133 Canvas View. creating X-Y graphs 256 customizing Events tab display settings 86 Customizing_the_display_of_events 86 D Decline Ownership event operation 76 icon 76 dial gauge graphs. setting up and using 132 central ProactiveNet Server 86 child ProactiveNet Server 86 Close event icon 76 operation 76 Closed event status icon 26 collectors event count affected by status 29 color event status icon 26 configuration items. creating a line or area graph 251 Custom graphs. performing 76 event priority icons 27 setting 76 understanding 27 event severity icons 27 levels 27 event status icons 26 understanding 26 C Canvas View. creating a dial gauge graph 261 custom graphs. described 25 bookmarks.

See event priority 27 I icons Acknowledge Event 76 Close event 76 Decline Ownership 76 event priority 27 event severity 27 event status 26 Set Priority 76 Take Ownership 76 Index Term 31. performing 76 organizing events in the event list 53 F filtering events. See event operations. changing user preferences in the Canvas View 133 operations console. creating 251 M multiple ProactiveNet Server deployment 86 O Open event status icon 26 operations console.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z events acknowledging 76 assigning to an individual 76 closing 76 declining ownership 76 performing operations 76 responding with an action 80 setting the priority 76 sorting 72 sorting fields 73 taking ownership 76 events list organizing 53 refreshing 52 Events View configuring display settings 86 customizing display settings 86 Integrate BMC ProactiveNet alarms BMC Run Book Automation 237 Integrating with SLM 247 L launching originating ProactiveNet Server 86 line graphs. changing user preferences in the Graph View 150 operations console. setting up and using the Graph View 149 operations console. creating 259 priority. custom 249 P pie graphs. creating filters when searching for configuration items 20 querying SLO records in the Watch List 359 SLO violations 356 quick filters severity 64 severity quick filter 64 slot quick filter 64 BMC ProactiveNet User Guide . setting up and using the Tile View 143 operations. setting up and using the Canvas view 132 operations console. by slot name 64 events. changing user preferences in the Tile View 143 operations console. overview 64. setting up and using 149 graphs. 56 instant poll 130 444 Q queries. 54. by severity 64 events. changing preferences 150 Graph View. 159 SLO records in the Watch List 359 SLO violations 356 filters creating local 68 global 64 severity quick filter 64 slot quick filter 64 FlashCheck 130 G Graph View. setting up and using the Canvas View 132 operations console.

changing user preferences in the Graph View 150 user console. creating 257 R refreshing the event list automatically 52 remote actions accessing results of 81 responding to event 80 remote cells. creating 256 T Take Ownership event operation 76 icon 76 Index 445 . setting up and using the Graph View 149 user console. changing preferences 143 Tile View. setting up and using the Tile View 143 user preferences. setting up and using 143 top N graphs. changing for the Canvas View 133 user preferences. changing for the Tile View 143 S Set Priority event operation 76 icon 76 severity effect on event status icon 26 level indicator (Events View navigation) 27 quick filter 64 slot quick filter 64 sorting events multiple columns 73 single column 73 status affects event count for collector 29 event icons 26 X X-Y graphs. changing user preferences in the Tile View 143 user console. creating event list folder 61 Reopen Event event operation 76 results of a remote action 81 U Unacknowledge Event event operation 76 user console. changing user preferences in the Canvas View 133 user console.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Tile View. changing for the Graph View 150 user preferences.

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 446 BMC ProactiveNet User Guide .

.

49532 *166654* .