ProactiveNet User Guide 9.0

BMC ProactiveNet User Guide
April 2012
www.bmc.com
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 .....................................................................................................24 Operations Console views ..................................................................................31 Breadcrumbs .........................................................................................................33 Using the BMC ProactiveNet Operations Console to monitor BMC Cloud Lifecycle Management objects .......................................................................................................33 About the Central Console .................................................................................34 About the multiple pane view ...........................................................................36 Using the tenant filter ..........................................................................................40 Aggregate monitors for cloud objects ...............................................................42 Chapter 2 Working with events 45 Event views in the Main drawer of the navigation pane ..........................................45 Customizing the display of the event list ....................................................................46 Viewing the default event list for Event Collectors ...................................................48 Viewing further information for a specific event from the Tools Menu ................51 Behavior of popup windows for Tools Menu options ...................................54 Viewing the event list for a specific component in the navigation tree ..................54 Viewing CI-based event lists .........................................................................................56 Customizing the standard and custom event class slot display labels ...................58 Selecting the type of event list to view ........................................................................59 Intelligent Events Details template ...................................................................60 Creating a new template for event list columns .........................................................60 Editing a default or user-defined template for event list columns ..........................62 Copying an existing template for event list columns ................................................62 Deleting a user-defined template for event list columns ..........................................63 Applying a default, global, or user-defined template for event list columns ........63 Adding a column to an event list .................................................................................64 Deleting a column from an event list ...........................................................................64 Viewing the event Details Notebook ...........................................................................65 Event relationships .........................................................................................................70 Viewing event relationships ...............................................................................71
Contents
Viewing related events ...................................................................................................71 Refreshing the event list .................................................................................................72 Organizing events in the event list ...............................................................................73 Using event and component folders .................................................................73 Filtering events .....................................................................................................84 Searching events ...................................................................................................92 Sorting events .......................................................................................................93 Creating shortcuts for Tools Menu options ................................................................94 Performing event operations .........................................................................................96 Configuring the Assign to User List ...............................................................100 Dynamic help for events ..............................................................................................101 Exporting and copying event information ................................................................102 Sending manual events ................................................................................................103 Editing class and slots for sending manual events .......................................105 Working with local actions ..........................................................................................106 Guidelines for executing local actions ............................................................107 Adding or modifying local actions ..................................................................108 Executing remote actions .............................................................................................113 Ping Event mc_host_address ...........................................................................114 TraceRoute to Event mc_host_address ...........................................................114 Send EVENT as SMTP E-mail ..........................................................................114 Modify Slot Value ..............................................................................................114 Show Remote Action Environment .................................................................115 Setup Sending SMTP E-Mails - Windows Only ............................................115 Trigger Remedy Incident for Event .................................................................116 BMC Atrium Orchestrator workflows ............................................................116 Launching an originating BMC ProactiveNet Server .............................................118 Customizing the display of events ............................................................................119 Viewing the event list for remote cells ......................................................................120 Operations possible on the event list for remote cells ..................................123 High availability remote cell support in the event list .................................124 Viewing predictive events ...........................................................................................124 Viewing all abnormalities ............................................................................................126 Adding a column to an event list for an abnormality ..................................127 Deleting a column from an event list for an abnormality ............................128 Filtering event display for All Abnormalities ................................................130 Viewing further information for an abnormality ..........................................132 Viewing events and abnormalities by service ..........................................................132 Viewing further information for Services => Grid View ...........................135 Viewing monitor and device information under the Services => Grid View ....................................................................................................................................135
Viewing services in a hierarchical tree ......................................................................137 Controlling the display in the Services => Tree View ...............................138 Viewing events by group .............................................................................................139 Default groups ....................................................................................................142 Filtering event display for All Groups ............................................................142 Viewing further information for Groups => Grid View ............................143 Viewing monitor and device information under the Groups => Grid View ....................................................................................................................................144 Viewing events for groups in a hierarchical tree .....................................................146 Controlling the display in the Tree View .......................................................147 Viewing events by device ............................................................................................149 Filtering event display for All Devices ...........................................................151 Viewing further information for All Devices ................................................153 Viewing events for monitored services .....................................................................154 Viewing further information for All Monitors ..............................................155 Acknowledging events ................................................................................................155 Closing events ...............................................................................................................157 Managing configuration changes ...............................................................................158 Managing data collection .............................................................................................159 Distinction between new and upgrade users ................................................160 Pausing data collection .....................................................................................161 Resuming data collection ..................................................................................162 Diagnostics ..........................................................................................................162 Examining current data (FlashCheck) ............................................................163 About the Canvas view ................................................................................................164 Canvas view modes ...........................................................................................164 Canvas view details ...........................................................................................165 Setting up and using the Canvas view .....................................................................166 Using Edit mode to set up the Canvas view ..................................................166 Using View mode to monitor objects in the Canvas view ...........................172 About the Tile view ......................................................................................................177 Tile view modes .................................................................................................177 Tile attributes ......................................................................................................178 Tile preferences and defaults ...........................................................................179 Tile view details .................................................................................................179 Setting up and using the Tile View ...........................................................................180 Using Edit mode to change preferences in the Tile view .............................181 Saving tile preferences as defaults ..................................................................182 Using View mode to monitor objects in the Tile view .................................183 About the Graph view .................................................................................................189 Graph view modes .............................................................................................190
Contents
Graph View details ............................................................................................190 Setting up and using the Graph View ......................................................................190 Using Edit mode to change preferences in the Graph view ........................191 Using View mode to monitor objects in the Graph view .............................194 About the Heat Map View ..........................................................................................200 Heat Map View modes ......................................................................................201 Heat Map View details ......................................................................................202 Setting up and using the Heat Map View ................................................................202 Using Edit mode to change preferences in the Tree Map view ..................203 Using View mode to monitor objects in the Heat Map View ......................204 About the Chart View ..................................................................................................206 Setting up and using the Chart View ........................................................................207 Using Edit mode to change preferences in the Chart View .........................207 Using View mode to monitor objects in the Chart View .............................211 Changing chart attributes .................................................................................212 Details window .............................................................................................................213 Viewing the Details notebook .....................................................................................215 Launching the BMC Atrium Service Context application from the BMC ProactiveNet Operations Console ..............................................................................218 Chapter 3 Determining the probable cause for an event 221 What is probable cause analysis? ...............................................................................221 How BMC ProactiveNet performs probable cause analysis on events ................221 Time correlation .................................................................................................224 User-defined filters ............................................................................................225 Knowledge patterns ..........................................................................................225 Service model relationships .............................................................................226 Global relationships ...........................................................................................226 Data correlation ..................................................................................................227 Scoring .................................................................................................................227 Configuring BMC ProactiveNet to perform probable cause analysis ...................227 Configure complete monitor coverage ...........................................................227 Assign correct device types ..............................................................................228 Create monitors under the correct devices ....................................................228 Create service models for interdependent CIs ..............................................228 Associate monitors to the proper CI ...............................................................228 Set a polling interval of 5 minutes or less .......................................................229 Establish a reliable baseline ..............................................................................229 Ensure sub-categories are defined for external events .................................230 Viewing probable cause analysis for an event .........................................................230 Customizing the display of the Probable Cause Analysis list ...............................232
Filtering unrelated events to find probable cause ....................................................234 Changing the time correlation filter ................................................................234 Enabling user-defined filters ............................................................................235 Saving recurring conditions as a known probable cause ........................................236 Probable cause analysis in a scalable deployment environment ...........................237 Limitations of probable cause analysis in a scalable environment .............238 Probable cause analysis in a virtual environment ...................................................239 How probable cause analysis handles VMotion events ..............................239 Limitations of probable cause analysis in a virtual environment ...............239 Chapter 4 Event administration 241 Overview ........................................................................................................................241 For upgrade users ..............................................................................................241 Accessing the event administration options ..................................................242 Understanding event thresholds ................................................................................242 Baselines ..............................................................................................................244 Auto-baseline ......................................................................................................245 How abnormalities are generated ...................................................................245 Setting event thresholds ....................................................................................246 Managing event rules ...................................................................................................250 Default event rules .............................................................................................250 Filtering the event rule list ................................................................................252 Event rule types ..................................................................................................254 Event rules or event management policies ....................................................254 Adding a basic event rule type .......................................................................255 Adding an advanced rule type ........................................................................261 Editing a basic or an advanced rule ................................................................263 Deleting an event rule .......................................................................................264 Updating event actions .....................................................................................264 Enabling and disabling event rules .................................................................265 Supplying arguments to a server command ..................................................265 Defining email groups .......................................................................................267 Event actions: managing BMC ProactiveNet events in external environments ................................................................................................................................................268 Managing BMC ProactiveNet events through SNMP traps ........................268 Managing BMC ProactiveNet events through Run Command on Server . 278 Managing BMC ProactiveNet events through Diagnostic Commands on the BMC ProactiveNet Server .................................................................................279 Managing the AlarmPoint integration ...........................................................280 Managing BMC ProactiveNet events in the Remedy environment ...........281
Contents
Managing BMC ProactiveNet events in the BEM environment .................292 Managing BMC ProactiveNet events BMC Atrium Orchestrator (formerly known as BMC Run Book Automation) .........................................................300 Reducing events ............................................................................................................307 Customizing event text ................................................................................................309 For upgrade users ..............................................................................................310 Integrating BMC ProactiveNet with Service Level Management .........................312 Chapter 5 Customizing graphs 313 Creating custom graphs ...............................................................................................313 Limitations ..........................................................................................................314 Creating a line or area graph ............................................................................315 Creating a x-y graph ..........................................................................................320 Creating a Top N graph ....................................................................................321 Creating a pie graph ..........................................................................................323 Creating a dial gauge graph .............................................................................325 Customizing monitor graphs ......................................................................................328 Graph tab ...........................................................................................................329 Attributes and indicators tab ...........................................................................330 Monitor information tab ..................................................................................332 Button options ....................................................................................................332 Creating an individual/multiple monitor graphs ........................................334 Additional information for changing graph display ...............................................335 Adjusting graph axes .........................................................................................336 Exporting graph data to Microsoft Excel ........................................................337 Displaying all abnormalities for a graph ........................................................339 Mailing the graph page .....................................................................................340 Sharing the graph page .....................................................................................340 Generating PDF ..................................................................................................341 How setting the All Baselines option affects absolute instance thresholds .........341 Chapter 6 Managing Views 343 What is a view? .............................................................................................................343 Navigating the Views and Graphs drawer ...............................................................343 Managing views ............................................................................................................345 Customizing the basic screen layout on the Views tab ................................351 Managing graph thumbnails for a view ....................................................................351 Managing view templates ...........................................................................................353 Chapter 7 Overview Generating Reports 357 ........................................................................................................................357
Creating or editing a report ..............................................................................358 Deleting a report ................................................................................................362 Copying an existing report ...............................................................................362 Changing email settings in a report ................................................................363 Report types available in BMC ProactiveNet ...........................................................364 Asset .....................................................................................................................365 Report Scheduler ...........................................................................................................390 Additional options ........................................................................................................391 Deleting instances ..............................................................................................392 Disable generation .............................................................................................392 Adding comments to a report ..........................................................................393 Scheduling ...........................................................................................................394 Adding a report to a view .................................................................................394 Generating a report ............................................................................................394 Exporting to Portable Document Format (PDF) ............................................395 Exporting report data to Microsoft Excel .......................................................395 Mailing a report ..................................................................................................396 Managing all reports .........................................................................................396 Printing a report .................................................................................................397 Points to Remember .....................................................................................................397 Chapter 8 Managing service levels 399 What is an SLO? ............................................................................................................399 The SLO Management Console ..................................................................................399 Customizing basic settings for SLO data display .........................................400 Managing SLOs .............................................................................................................401 Creating or editing an SLO ...............................................................................402 Deleting SLOs .....................................................................................................405 Managing SLO types during SLO configuration ..........................................405 Managing schedules during SLO configuration ...........................................406 Managing range sets during SLO configuration ...........................................408 Requesting guidance for setting SLO thresholds ..........................................409 Recalculating SLO data for modified time periods ......................................412 Resetting SLO compliance data .......................................................................414 Viewing the current status of SLOs ............................................................................415 Customizing the display of SLO status information ....................................416 Viewing SLO compliance details and history ..........................................................416 Viewing a summary of details and compliance metrics for an SLO ..........418 Viewing violation details for an SLO ..............................................................419 Viewing a history graph for an SLO ...............................................................421 Viewing a breakdown of SLO metrics for various time periods ................421
Contents 9
Comparing compliance objectives with actual results ............................................422 Accessing the Watch List ..................................................................................423 Filtering SLO records in the Watch List .........................................................423 Drilling down to an individual SLO in the Watch List ................................424 Viewing a graphical history of SLO compliance and violations ...........................424 Viewing instance details ...................................................................................425 Viewing SLOs in a hierarchical tree ...........................................................................425 Controlling the display in the SLO Tree .........................................................426 Accessing further information from the SLO Tree .......................................427 Chapter 9 Managing BMC ProactiveNet data collection and infrastructure 429 Activating and deactivating data collection .............................................................429 Scheduling downtime ..................................................................................................431 Usage scenario ...................................................................................................432 Adding a downtime schedule ..........................................................................434 Edit/Delete downtime schedule .....................................................................436 Special notes .......................................................................................................437 Tracking changes to BMC ProactiveNet objects .......................................................438 Viewing BMC ProactiveNet and PATROL agent statuses .....................................439 Drill down from the agent status table ...........................................................442 Managing attribute sets ...............................................................................................443 Managing baselines ......................................................................................................445 Pausing baseline calculation ............................................................................446 Resetting a baseline ..........................................................................................448 Creating a separate baseline for seasonal or special dates ..........................449 Managing relationships ...............................................................................................462 Defining Intelligent Event Suppression relationships ..................................463 Overview of the Intelligent Event Suppression screen ................................465 Enabling or disabling Intelligent Event Suppression relationships ...........467 Adding or editing an Intelligent Event Suppression relationship .............467 Deleting a relationship ......................................................................................474 Managing schedules .....................................................................................................474 Importing and exporting users ...................................................................................476 Viewing BMC ProactiveNet software information ..................................................479 Installation history .............................................................................................480 Viewing BMC ProactiveNet performance diagnostics .................................480 Viewing and exporting the license usage report ...........................................482 Pausing auto-refresh ..........................................................................................485 Chapter 10 Integrating with BMC Server Automation 487 Benefits of BMC Server Automation integration .....................................................487
10
Setting up the integration between BMC Server Automation and BMC ProactiveNet ..................................................................................................................488 Additional change information using snapshot job execution ..............................493 Installing the BMC ProactiveNet content ..................................................................494 Creating new BMC Server Automation content ......................................................495 Creating packages to deploy BMC ProactiveNet Agents to BMC Server Automation managed systems ...................................................................................497 Viewing BMC Server Automation device history information .............................499 Provisioning BMC ProactiveNet components with BMC Server Automation ................................................................................................................................................502 Creating packages for provisioning ................................................................503 Creating a property instance in BMC Server Automation ..........................505 Creating BMC Server Automation jobs to deploy BMC ProactiveNet component packages to remote hosts .............................................................507 Uninstalling components provisioned with BMC Server Automation .....509 Chapter 11 Configuring BMC ProactiveNet Integrations 511
Appendix A Event information used in probable cause analysis 519 Event classes not used by probable cause analysis ..................................................519 Slots used during probable cause analysis ...............................................................522 Monitors related to VMware .......................................................................................524
Contents
11
12
1
Introducing the BMC ProactiveNet Operations Console
Accessing the Operations Console
The BMC ProactiveNet server is an 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. For information about supported browser versions, see the BMC ProactiveNet Installation and Configuration Guide. Avoid multiple logons using the same browser, user name, and password, and launching different tabs within the same browser, as this might result in no data or other unpredictable results. For multiple logons, see To enable multiple Firefox sessions on page 14 and To enable multiple Internet Explorer sessions on page 15.
Note
To log on to the BMC ProactiveNet Operations Console

1 Open a Web browser. 2 Enter the host name or IP address of the BMC ProactiveNet server. 3 In the BMC ProactiveNet Logon screen, enter a valid user name and password.
To log on for the first time after installation, use the following default values: user name: admin password: admin
Chapter 1 Introducing the BMC ProactiveNet Operations Console
13
Accessing the Operations Console
Note The default protocol for this connection is HTTP. To log on using a secure HTTPS connection, click the link Switch to Secure Mode on the log on page. If you use HTTPS, BMC ProactiveNet encrypts the information relay from the Web interface for additional security. Secure connection mode is indicated by the text You are using a secure connection now.
4 Click Log On.
To change your Operations Console password

1 Click the Options link at the top the Operations Console. 2 In the General tab, under User ID and Password, click Edit. 3 Enter the old password and the new password, and then click Apply. Related Topics Choosing the console type on page 15 Navigating the Operations Console on page 16
To enable multiple Firefox sessions

By default, Firefox shares one session across all browser windows that you open. To enable multiple sessions, you must create separate profiles that can be used by different sessions. For more information on setting profiles, see the Firefox help. Before performing this procedure, close any open Firefox sessions. 1 From the command line, change to the Firefox installation directory and execute the following command: firefox.exe -ProfileManager 2 In the Firefox - Choose User Profile window, select Create Profile. 3 In the Create Profile Wizard, create one profile for each Firefox session that you want to launch and then exit the Profile manager. For detailed instructions for creating profiles, see the Firefox online Help. 4 After you complete creating the new profiles, create a shortcut to Firefox.exe on your desktop or Taskbar for each profile that you created. 5 Right-click the Firefox icon for each shortcut and select Properties.
14 BMC ProactiveNet User Guide
Choosing the console type
6 In the Target field of the Properties window, specify the name of the profile to use when launching Firefox from that shortcut. For example, "F:\Program Files \Mozilla Firefox\firefox.exe -P "ProfileA". Click OK. 7 Click Start > Control Panel > System. 8 In the Advanced tab of the System window, create a new environment variable with the variable name MOZ_NO_REMOTE and a variable value of 1. 9 Click on each shortcut to open Firefox in separate sessions.
To enable multiple Internet Explorer sessions

1 Perform one of the following actions:
From Internet Explorer, choose File > New > Window. Perform the following steps:
1 Right click the Internet Explorer icon in the Windows Taskbar and choose Properties. 2 In the Launch Internet Explorer Browser Properties window, append the nomerge parameter to the Target value and click OK.
Choosing the console type

The BMC ProactiveNet Operations Console provides options to navigate through the system and view related information. Several console views are available based on assigned access rights. You can select the appropriate console type from the Change Console list at the top of the Operations Console. 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, abnormalities, services, groups, devices, and monitors The Operations Console is the default console displayed when you log on to BMC ProactiveNet. To change this setting, see To set the default logon console on page 16.
15
Navigating the Operations Console
Console Type SLO Management Console
Purpose Displays an integrated view of all Service Level Objectives (SLOs) These business views help define, measure, and track SLOs.
To set the default logon console

1 Click the Options link at the top of the Operations Console. 2 In the General tab, under Layout Preferences, select the console type that you want to set as the default when you log on to BMC ProactiveNet. 3 Click Apply. Related Topics Accessing the Operations Console on page 13 Navigating the Operations Console on page 16

Use the navigation pane's drawers and navigation trees within each drawer to group and select the objects displayed in the Operations Console. Use the view pane to view events and information related to each object. 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. Figure 1: BMC ProactiveNet Operations Console
Navigation pane
Displays a series of drawers and links that enable you to navigate through BMC ProactiveNet. You can select which drawers that you want displayed in the navigation pane by setting options in the Navigation Pane Options dialog box. For details, see Changing navigation pane options on page 18. Table 2 on page 17 describes the available drawers in the navigation pane and discusses their functions.
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 Further information Viewing the default event list for Event Collectors on page 48
Lists available remote cells connected to Viewing the event list for remote the BMC ProactiveNet Server and cells on page 120 monitored by BMC ProactiveNet Chapter 1 Introducing the BMC ProactiveNet Operations Console 17
Navigational element Reports
Description
Further information
Enables you to generate and manage Generating a report on page 394 reports based on data collected by BMC ProactiveNet Manages views and graphs in the Operations Console Managing view templates on page 353 Managing graph thumbnails for a view on page 351
Views & Graphs
Bookmarks
Enables you to view, rename, 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. Only you can view and manage the bookmarks that you create. Provides a search mechanism so that you can search for CIs that meet the specified search criteria Finding configuration items to view on page 21
Find CI
Related Topics Accessing the Operations Console on page 13 Choosing the console type on page 15 Hiding the navigation pane on page 19
Changing navigation pane options

If you have Super Admin, Event Admin, Data Collection Administrator, or Service Administrator permissions, 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.
To set navigation pane options

1 In the title bar of the navigation pane, click Navigation Pane Options .
2 In the Navigation Pane Options dialog box, select the drawers that you want to display in the navigation pane by clicking the check box next to the name of the drawer. 3 To make changes to the objects displayed in individual drawers, click on the drawer name and perform the following additional steps, depending on which drawer that you select:
a In the Main drawer, select the folders that you want to display in the navigation tree. b In the Other Cells drawer, select the cells that you want to display in the cell navigation tree. 4 Perform one of the following actions:
Click Apply to save your changes and keep the Navigation Pane Options
dialog box open. box.
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.
Hiding the navigation pane

By default, the navigation pane is displayed when you log on to the BMC ProactiveNet Operations Console. 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 .
The Navigation pane is collapsed and the title bar is displayed vertically on the left side of the Operations Console. To redisplay the Navigation pane, click on the title bar.
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.
To create bookmarks
1 In any drawer of the navigation pane, select an object in the navigation tree. 2 In the right pane, select a view for the object that you selected in the navigation tree.
19
3 From the Navigation Menu at the top of the drawer, 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. You cannot select other views of the object from the bookmark. For example, if you bookmarked a device that was displayed in Tile View, only the Tile View is available when you view the bookmark. However, if you drill down on the device tile from the bookmark, other views are available for the objects associated with the bookmarked device. The bookmark does not show the object's status or the hierarchy in the navigation tree. However, you can organize bookmarks into folders within the Bookmarks drawer and drag and drop the bookmarks among those folders. See To add a folder to the Bookmarks drawer on page 20.
Note
To remove bookmarks
1 In the Bookmarks drawer of the navigation pane, select the object that you want to remove. 2 From the Navigation Menu at the top of the Bookmarks drawer, choose Delete.
To add a folder to the Bookmarks drawer

1 From the Navigation Menu at the top of the Bookmarks drawer, choose Add Folder. 2 Click on the new folder created in the Bookmarks drawer. The name of the folder is changed to an editable field. 3 Enter the name for the new folder and press Enter. You can now drag and drop bookmarks that you create into the new folder.
To rename bookmark folders

1 In the Bookmarks drawer of the navigation pane, select the object that you want to rename.
2 From the Navigation Menu at the top of the Bookmarks drawer, choose Rename Folder. The name of the folder is changed to an editable field. 3 Enter the new name for the folder and press Enter.
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. 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. A basic search lets you search for a specific CI based on name and class type. 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, the Find CI drawer is not displayed in the navigation pane.
Note
To perform a basic search for a configuration item

1 In the Navigation pane, click Find CI. 2 In the Basic tab, enter all or part of the name of the component that you want to search for. 3 From the Class list, select a component type, such as Computer System, application service, database, and so on. If you select Base Element, all service CIs for all classes are returned. If you leave Name contains or Class blank, the search could take a long time, depending on the number of CIs. Also, the results list could be very long. You should refine the search by specifying values in one or both of these fields. 4 To find only those CIs that propagate their priority to causal components, select Propagates Priority. These CIs are considered the important components for your business. 5 Click Find.
Chapter 1 Introducing the BMC ProactiveNet Operations Console 21
Note
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. This number can be configured. For details, see the BMC ProactiveNet Administrator Guide. 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. For details about creating static folders, see Using event and component folders.
To use an existing filter to perform an advanced search for a configuration item

1 In the Navigation pane, click Find CI. 2 In the Find CI drawer, click Advanced. 3 From the Query list, select the filter that you want to use to perform the search. You can create filters in one of the following ways:
By accessing the CI Query Editor in the Find CI drawer. For details, see To
create a new filter to perform an advanced search for a configuration item on page 22. folder in the navigation tree in the Main drawer. For details, see Using event and component folders.
In the Add Component Folder dialog box when you create a new component
4 Click Find. All components matching the search criteria appear in the results list at the bottom of the Find CI pane up to a maximum 500. This number can be configured. For details, see the BMC ProactiveNet Administrator Guide. 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. For details about creating static folders, see Using event and component folders.
To create a new filter to perform an advanced search for a configuration item

1 In the Navigation pane, click Find CI. 2 In the Find CI drawer, click Advanced. 3 Perform one of the following actions:
To use an existing filter to create a new filter, select the filter from the Query list
and click Edit Queries.
If you select an existing filter that contains blank entries, the Find CI search assumes that it is a template and automatically opens the CI Query Editor dialog box.
To create a new filter, click Edit Queries.
4 In the CI Query Editor dialog box, select Create New Filter. 5 (optional) To make the filter available to all users who log on to the operations console, select Make *Global (all users). An asterisk is placed next to the name of the query to indicate that it is global. 6 From the Class list, select the type of component that you want to search for. 7 If necessary, expand the query builder options by clicking the plus button next to the Class list. 8 Begin building the parameters for your query by selecting the attributes for the class type that you selected. To display additional attributes, click the plus button next to the attribute name. Each new attribute that you add narrows and refines the search. The query will search for components with all of the attributes that you specify, indicated by the AND before the attribute names. If you use the same attribute, but specify different values, then the query will search for components with any but not all of the values that you specify, indicated by the OR before the attribute names. 9 When you have finished building the filter, perform the following actions:
To save the filter, click Save and enter a name for the filter in the Enter Query
Name dialog box.
To execute the search, click Find.
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 drag and drop a CI from the results list to a static folder that you create in the navigation tree in the Main drawer. You can use the new filter to create a static folder of CI objects or a dynamic folder in the navigation tree.
For details about creating static and dynamic folders, see Using event and component folders.
To view all existing configuration items (CIs present on the Central Server and its Child Servers)
You can add CIs that are available on the Central Server to My Folders so that you have a centralized view of all existing CIs. To do this: 1 In the Main drawer of the navigation pane, click My Folders. 2 From the Navigation Menu at the top of the drawer, choose Add Folder => Component Folder. 3 In the Add Component Folder dialog box, specify a name and description for the folder in the Folder Name and Description text boxes. 4 Select Static List of Objects from the Folder type list and CIs from Service Model from the Object type list. 5 In the Find CIs to Display in the Available CIs List Below section, click Find. All existing CIs (CIs present on the Central Server as well as its Child Servers) are displayed in the Results box. 6 Select the CIs that you want to add to My Folders and click the right arrow icon. The CIs are added under the folder you created. This folder is displayed under My Folders in the navigation tree.
Navigation tree
The navigation tree shows an at-a-glance synopsis of the events and views. Event and component folders are displayed in a hierarchical manner in the navigation tree. The folders displayed in the navigation tree are divided into the following categories:
Global: When you create a folder under this node, all BMC ProactiveNet users can
view and access that folder. access that folder.
My Folders: When you create a folder under this node, only you can view and
Note Folder and Component views are used as containers for groups, devices, and services. They are access control aware. Folders that contain monitor groups and devices are filtered based on the ACLs in the CIs that the monitors and devices are associated with.
To further organize your display, you can add event and component folders, including folders for configuration items (CIs) associated with a service model, beneath these top-level folders, depending on your permissions. A CI is any component that needs to be managed in order to deliver an IT service. CIs are under the control of change management. CIs typically include hardware, software, buildings, people, and formal documentation, such as process documentation and SLAs. For more information about CIs, see the BMC ProactiveNet Service Modeling and Publishing Guide. Also, 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; for example, if the tile represents a device, then that tile can be moved to another device folder by using drag and drop. Users traversing the navigation tree can see and perform actions and operations on only those collectors to which they are granted access, based on different roles in the .mrl file of the collectors. However, the collector-based permissions on events do not apply when you view an event list from the following locations:
Drill-downs from Groups, Services, Devices, or Monitors (Grid View and Tree
View) tree
Abnormalities, Groups, Services, Devices, or Monitors nodes in the navigation
Parent event and component folders (not individual collectors within or outside
the parent folders)
In the navigation tree, the severity icons for a collector dynamically change depending on the severity level of the events for that collector. For example, if there is a Critical event on one of the devices, then the green icon changes to a red icon, indicating a Critical event. This allows you to see the status of devices on your system immediately. By default, when you open the navigation tree, all nodes and subnodes are loaded even if a node is not expanded. If this causes performance issues, you can change how the navigation tree is loaded. For details, see the BMC ProactiveNet Administrator Guide.
Event and component folders

Event and component folders enable you to organize cells and collectors to make event displays meaningful for operators. 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. Administrators define event folders and associate them with one or more collectors. Each level of the collector is shown as a node under the event folder. An event list is associated with the lowest level nodes of an event folder. The parent level of an event folder represents all of the events or abnormalities associated with the collectors.
Event collectors
Event collectors gather events for display in an event list. They provide operators with meaningful groups of events or abnormalities and show relationship through the hierarchy of the nodes in the navigation tree. To access the event list for a collector, operators click the collector node in the navigation tree. Event collectors are dynamic or static. Nodes for dynamic collectors appear or disappear from the navigation tree based on whether or not events are present that meet the collectors criteria. Nodes for static collectors remain in the navigation tree whether events are present or not.
Component folders
A component folder is a grouping of groups, services, or devices from several different event lists (collectors) that shows the relationship of groups, services, or devices through the hierarchy of the navigation tree. Administrators define component folders and associate them with one or more groups, services, or devices. Each level of the component folder is shown as a node under the parent component folder. An event list is associated with the lowest level nodes of a component folder. The parent level of a component folder represents all of the events associated with the groups, services, or devices. Table 3 on page 27 shows the icons and describes the objects represented in the navigation tree.
Table 3: Navigation tree objects and definitions Object icon Name and definition Navigation tree top-level node (Global); the Global node contains the following default collectors: Event Collectors: Displays the entire event collector hierarchy Abnormalities: Displays all the abnormality events Services: Displays all the services Groups: Displays all the groups Devices: Displays all the devices Monitors: Displays all monitor categories Based on permissions, users can create event and component folders under this node to organize the event view. Navigation tree top-level node (My Folders); based on permissions, 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 events response activity. The BMC ProactiveNet Server assigns a status value to each event, and then you can change the status by performing event operations or other actions on the event. Also, a rule can change the status of an event automatically. Table 4 on page 28 lists the icons that are displayed in the event list to represent event status.
27
Table 4: Event status icons Icon Event status Open Closed Acknowledged Assigned Blackout
The color of the status icon is always the same. However, if you have configured the event list to use the severity color for the event line, the color of the icons background varies with the severity of the event.
Understanding event severity

Each event has a severity level associated with it that indicates the seriousness of the event. In combination with status and priority, the severity level indicates the urgency of the need to take action. For example, a high severity level for an event in the Closed status is no cause for alarm, but a high severity level for an event in the Open status and with a priority of 1 indicates an urgent need for action. Table 5 on page 28 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.
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 Icon in Event List Severity level Critical Major Minor Warning Information Ok Unknown Predictive Critical Predictive Major Predictive Minor
Color faint grey
Icon in Event List
Severity level 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. For example, if one event has a severity of Critical, the event or component folder is displayed in the navigation tree with a Critical (red) severity indicator.
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. Table 6 on page 29 lists the icons that are displayed in the event list to represent event priority.
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 events current state quickly. Each events state depends on multiple factors:
Severity, reflected in the severity icon and color of the event line (based on the
preference selected by the user)
Priority, reflected in the priority icon The last event operation performed on the event, reflected in the status icon
When you perform an event operation on an event, the state of the event changes according to Table 7 on page 30. For information about performing event operations, see Performing event operations on page 96.
29
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 30 shows how an event in any state is affected by the operations that are valid for that current state. The circles represent the event states. Each arrow represents an action, with the direction of the arrow indicating the flow of the action. For example, if the event is currently in the Acknowledge Event state, you can perform a Take Ownership, Assign To, Close Event, or Unacknowledge Event action. Conversely, for that event to be in the Acknowledge Event state, you should perform an Acknowledge Event or Decline Ownership action. 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), each event collector has two event counts. The first count is enclosed in parentheses and represents the number of unacknowledged (Open) events; this count does not include closed, blackout, assigned, and acknowledged events. This counter decreases whenever the status changes from open to closed, blackout, assigned, or acknowledged state. The second count indicates the sum of all the events. For example, 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.
Operations Console views

In the Operations Console, you can use the smart icons in the toolbar to select the following views, depending on the object that you have selected in the navigation tree:
Event View: displays information about events; 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
Heat Map View: displays a heat map of the cloud infrastructure objects or services
that you select in the navigation tree. The nested heat tiles are color-coded to show the alarm stages of the objects or services that you select.
Tree View or Graph View: the Tree View displays all service groups in a
hyperbolic tree for a user-defined period, 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. The view that is available depends on what object that you have selected in the navigation tree. The Graph View is available only for CI objects.
Chart View: allows you create graphs that show the performance of metrics over a
specified period of time
31
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.
The view stays the same until you select a different view. The only exception is if the selected view is not available for a particular object type. In this case, the operations console changes to a view that is defined for that object type. However, you can enable a configuration option that allows the view to be changed automatically. When this option is enabled, the operations console automatically switches to the default view defined for the object type that you select in the navigation tree. You can continue to use the toolbar buttons to manually change the view with this option enabled. For details about how to enable this option, see the BMC ProactiveNet Administrator Guide. The following table lists the default views defined for each node and object type.
Object type Abormalities Devices folder Devices Event Collectors folder Event collectors Groups folder Group Services folder Configuration item (CI) Component folder Default view Event View Grid View Grid View Event View Event View Grid View Grid View Tile View Graph View Tile View
If you have integrated BMC ProactiveNet with BMC Cloud Lifecycle Management (CLM), additional nodes and objects are displayed in the navigation tree of the operations console. The following table lists the default views for the cloud object types.
Object type Cloud resources Locations Network containers Compute pools Service offerings Default view multiple pane view Heat Map View Heat Map View Heat Map View Heat Map View
Using the BMC ProactiveNet Operations Console to monitor BMC Cloud Lifecycle Management objects
Note The view changes only if you select an object of a different type in the navigation tree. The view does not change if you select objects of the same type.
Breadcrumbs
As you navigate through the operations console, a trail of breadcrumbs is created at the top of the operations console window, providing a history of the areas that you have viewed. A new breadcrumb is created each time you click on a navigation item, such as a navigation pane drawer, folder, or view. The breadcrumb is labeled based on the object that you selected. You can return to an item by clicking on one of the breadcrumbs. By default, five breadcrumbs are shown in the breadcrumb string. If you click more than five areas, then the first breadcrumb is dropped and the new breadcrumb is added to the end of the breadcrumb trail. The number of breadcrumbs that are displayed can be configured. For instructions, see the BMC ProactiveNet Administration Guide.
If you have integrated BMC Cloud Lifecycle Management into your BMC ProactiveNet environment, you can use the BMC ProactiveNet Operations Console to view the cloud objects and monitor their status. The cloud objects displayed in the BMC ProactiveNet Operations Console are defined in BMC Cloud Lifecycle Management. You can configure BMC ProactiveNet to retrieve the cloud topology from BMC Cloud Lifecycle Management and display the objects in the navigation tree in the BMC ProactiveNet Operations Console. You can use the various console views and tools to monitor these objects in the BMC ProactiveNet Operations Console. For more information about enabling this functionality, see BMC ProactiveNet 9.0 online technical documentation. After you perform the necessary configuration tasks, the Cloud Resources node is displayed in the Operations Console navigation tree and the following nodes are displayed under the Cloud Resources node.
33
Locations: define where the pods are located Pods: as defined in BMC Cloud Lifecycle Management, represent a physical
level-2 portion of the cloud bound by a set of physical network equipment, such as routers, firewalls, and load balancers. Pods contain one or more network containers. Onboarding pods adds capacity incrementally to a data center. virtual layer-2 segments of the cloud that are used to isolate workloads or tenants based on specific policies and rules. groupings of similar compute resources provisioned into the cloud. Compute pools are mapped to network containers.
Network containers: as defined in BMC Cloud Lifecycle management, represent
Compute Pools: as defined in BMC Cloud Lifecycle Management, logical
Under the Services node, service offerings are displayed. Service offerings, as defined in BMC Cloud Lifecyle Management, represent the way an IT organization makes a service available to its customers. You can view the service offerings by either expanding the Services node in the navigation tree, or selecting the Services node and then selecting one of the following console views: Tile View, Canvas View, or Heat Map View. You can drill down from the tiles displayed in these views to display the service offering instances associated with each service offering, or you can select a service offering in the navigation tree to display the service offering instances in the console views. Service offering instances represent specific deployments of a service offering.
About the Central Console

The Central Console in BMC ProactiveNet is used to monitor the cloud infrastructure in a cloud deployment that is being monitored on multiple child servers. There are two modes for the Central Console:
Global Console: use this mode to view the status of all cloud resources on child
servers and cross-launch to those child servers for deep dive investigation and diagnostics. The Global Console has the following drawers in the navigation pane:
Main Find CIs
The following nodes only are displayed in the navigation tree in the Main drawer:
Cloud Resources My folder
Local Server: use this mode to access the objects that are being monitored on the
central server in a multiple server deployment. The Local Server has all of the drawers and nodes in the navigation tree that are displayed in the operations console in a single server deployment. For a description of each drawer and node, see Navigation pane on page 17.
Accessing the Central Console

You access the Central Console from the computer that serves as the central server in a BMC ProactiveNet multiple server deployment.
To log on to the Central Console

1 Open a Web browser. 2 Enter the host name or IP address of the central server computer. 3 In the BMC ProactiveNet Logon screen, enter a valid user name and password.
To log on for the first time after installation, use the following default values: user name: admin password: admin
The default protocol for this connection is HTTP. To log on using a secure HTTPS connection, click the link Switch to Secure Mode on the log on page. If you use HTTPS, BMC ProactiveNet encrypts the information relay from the Web interface for additional security. Secure connection mode is indicated by the text You are using a secure connection now. 4 Click Log On.
Note
Using the Central Console

From the Central Console, you can monitor the status of the cloud resource components that are monitored on child servers from a central location. You can crosslaunch from the Central Console to the child servers to perform actions on the resource, infrastructure, and service components and set thresholds.
To cross-launch to the BMC ProactiveNet Operations Console on child servers

1 In the title bar of the Central Console, click the down arrow next to the Launch to Child Server icon .
35
A list of child servers associated with the central server is displayed. 2 Select the child server on which you want to launch the operations console. If Single Sign-on has been implemented, the operations console launches in a separate window with the Events view displayed. If Single Sign-on has not been implemented, you will be prompted to enter a user name and password. 3 If prompted, enter the user name and password for the operations console on the child server. The operations console launches in a separate window with the Events view displayed.
About the multiple pane view

The multiple pane view in the BMC ProactiveNet Operations Console displays hierarchy, relationships, and health status of cloud resources in a single view. The multiple pane view gives you aggregated performance visibility into your entire cloud environment to help you quickly identify and prioritize any potential performance issues. The multiple pane view is divided into the following panes:
Heat Map View on the left side of the pane, which displays the network resource
structure defined in BMC Cloud Lifecycle Management as nested heat tiles in BMC Cloud Lifecycle Management, sorted by status, from worst to best.
Tile View on the right side of the pane, which displays the Resource pools defined
You can use the details pop up window to get further information about an object's status and its possible cause. If you have deployed BMC ProactiveNet in a multiple server environment, you can cross launch from the objects in the multiple pane view in the Central Console to the child server where the objects are monitored.
Accessing the multiple pane view

Use the multiple pane view to monitor the overall status of the BMC Cloud Lifecycle Management objects that you are monitoring in BMC ProactiveNet.
To access the multiple pane view in the BMC ProactiveNet Operations Console
1 Click on the Cloud Resources node in the navigation tree of the operations console. The following figure shows an example of the multiple pane view.
If you access the view in a single server environment or from a child server in a multiple server environment, you can perform actions on the objects in each view by using the Tools menu . If you access the view in a multiple server environment and from the BMC ProactiveNet Central Console, then you must crosslaunch to the child servers where the objects are stored to perform actions on them. For information, see Using the multiple pane view on page 37.
Using the multiple pane view

The multiple pane view in the BMC ProactiveNet Operations Console provides a holistic view of how your cloud resources are performing. The multiple pane view displays the status of your cloud resources in multiple dimensions so that you can identify and address any potential issues that might affect the performance of your cloud infrastructure. The multiple pane view displays the following information:
37
network resource structure grouped by location and displayed in the Heat Map
View, with the pods defined for each location and the network containers associated with each pod shown as nested heat tiles, color-coded by status.
For details about the Heat Map View, seeAbout the Heat Map View on page 200.
status of resource pools displayed in the Tile View.
For details about the Tile View, see About the Tile view on page 177.
To access details for objects displayed in each view

When a cloud resource in the view shows an abnormal status, you can use the Details window to gather further information to determine the possible cause. 1 Mouse over the resource that shows the abnormal status, and click the Details button . The details window is displayed with the following tabs: Summary, Events, Resource Pools, Tenants, SOIs, and Network Containers. The following figure shows an example of the details window.
Note The Resource Pools and Network Containers tabs might not be displayed for certain object types. If you display the details window for a Network Container, the Zones tab is displayed instead of the Network Containers tab.
The top of the Summary tab displays encapsulated performance data color-coded to show any thresholds that have been violated. The Events tab shows any impacting events that might be causing the abnormal status. The Network Containers tab, Resource Pools tab, Tenants tab, and SOIs tab show any of those objects that are defined for a given pod that might be affected by the impacting event. For more information about this window, see Details window on page 213. The Tile View shows the status of the compute pools. To further analyze the cause of the event, you can drill down to view the child objects from the multiple pane view. If you access the multiple pane view in a multiple server environment, you can cross-launch from the Heat Map View or Tile View to the child server where the thresholds are defined for the cloud resources by clicking the Menu icon and selecting Launch > viewName - Child Console. From the Heat Map View, you can launch to the Graph View on the child server. From the Tile View, you can launch to either the Event View or the Graph View on the child server. The BMC ProactiveNet Operations Console on the child server is launched with the appropriate view displayed. You can use the views in the operations console and probable cause analysis to further determine the cause of the impacting event that is causing the abnormal status. If you are accessing the multiple pane view in a single server environment, you can use the Menu commands to perform the same tasks as you could if you were accessing the views separately from the multiple pane view. If you are accessing the multiple pane view from the Central Console in a multiple server deployment, then you must cross-launch to the child servers where the objects are stored to perform actions on them.
To display the toolbar in the Heat Map and Tile Views

If you are viewing the multiple pane view in a single server environment or on a child server in a multiple server environment, you can display a toolbar to change the settings for the Heat Map view or to perform tasks on the objects in the Tile View. 1 In the Heat Map or Tile View, click Show Toolbar The toolbar opens at the top of the view. In the Heat Map View, you can change the following options:
the number of levels of heat tiles to display, up to three what the size of the tiles indicates
Priority
The priority of an object based on either its own priority or on the priority of another impacted object that propagates its
39
priority to it. The objects with the highest priority have the largest tiles in the Heat Map. Number of children The number of child nodes associated with an object. The objects with a higher number of child objects associated with them have the largest tiles in the Heat Map. The status of the worst SLA defined for the object. The objects with the worst SLAs defined have the largest tiles in the Heat Map. The number of virtual machines associated with an object. The objects with a higher number of VMs associated with them have the largest tiles in the Heat Map.
SLA
Number of VMs
The color of the tiles represents the object's status. This option cannot be changed in the multiple pane view. You can change these options in the Heat Map View that is accessed separately from the multiple pane view by using the Heat Map View Preferences dialog box. For more information, see Using Edit mode to change preferences in the Tree Map viewWhen the Tree Map View is in Edit mode, you use the options in the Tree Map View Preferences dialog box to determine how you want the nested tiles to look. . In the Tile View, you can change the following options:
sort the tiles alphabetically by name or by severity, from highest to lowest filter the tiles based on severity search for compute pools based on the criteria that you enter in the Find Name
field
adjust the size of the tiles
For more information about using the Tile View separately from the multiple pane view, see Setting up and using the Tile View on page 180.
Using the tenant filter

The tenant filter in the BMC ProactiveNet Operations Console lets you sort events and objects in the BMC ProactiveNet Operations Console based on the tenants that are defined in BMC Cloud Lifecycle Management.
The tenant filter is displayed in the toolbar in the BMC ProactiveNet Operations Console. A tenant is displayed in the tenant list if it has at least one configuration item (CI) associated with it. All tenants that are accessible for the user account that you use to log on to the operations console are displayed in the tenant list. If you are logged on with the Administrator account, you can see all tenants that are defined. For more information about tenant-aware support in the BMC ProactiveNet Operations Console, see the BMC ProactiveNet online technical documentation.
To create a list of favorites for tenants

You can create a Favorites list for tenants in your cloud environment so that you can sort events and objects based the tenants that you view most often. 1 In the toolbar of the BMC ProactiveNet Operations Console, click Tenant Selector - Favorites .
2 From the drop-down list, select Edit Favorites Tenant List. 3 In the Edit Favorite Tenants List dialog box, select a tenant under Available Tenants and click the right arrow button to move the tenant to the Favorite Tenants list. To search for a particular tenant, enter the search string next to Available Tenants. The list of tenants is filtered based on the criteria that you enter. 4 Click OK to close the Edit Favorites Tenant List dialog box. The tenants that you select are added to the Tenant Selector - Favorites list. Click the Tenant Selector - Favorites icon to access the list.
To filter objects based on tenant

1 In the toolbar of the BMC ProactiveNet Operations Console, click Tenant Selector - Search .
2 Enter the name of the tenant that you want to search for in the search field. The Tenants are filtered based on the search criteria that you enter. 3 Select a tenant from the list. Events and objects are sorted and displayed in the operations console views based on the tenant that you select.
41
Aggregate monitors for cloud objects

You can view utilization metrics for aggregate monitors for the cloud resources that you are monitoring in BMC ProactiveNet. These monitors process performance data for a specific cloud object type (Tenants, Pods, Network Containers, or Compute Pools) into consolidated metrics that are displayed in the Tile View. The consolidated metrics help you to understand how your provisioned cloud resources are being utilized. You can view the metrics in the BMC ProactiveNet Operations Console by selecting the cloud object in the navigation tree and displaying the Tile View, or by viewing the Details window of that object from any supported view. Each tile in the Tile View displays the utilization metrics for the aggregate monitors associated with the cloud objects. The status of a cloud object is determined based on thresholds set for the aggregate monitors. When aggregate utilization of these monitors crosses the set threshold, an minor, major, or critical alarm gets generated and the status of the object is updated in the Tile View and navigation tree. The following metrics for the aggregate monitors are displayed for the cloud objects that are defined in BMC Cloud Lifecycle Management and monitored in BMC ProactiveNet.
CPU utilization: monitors the total CPU consumption, computed as a percentage Memory Utilization: monitors the total memory consumption, computed as a
percentage
Network Utilization: monitors the average network input and output, computed
in kilobits per second (KBps) megabits per second (MBps)
Storage utilization: monitors the total disk input and output, computed in
Availability utilization: monitors the total availability, computed as a percentage Status Aggregate: displays the Status composition of child objects, computed as
percentages. This metric can help you to determine if certain child objects are operating outside of normal thresholds even though the parent object shows that its status is within normal thresholds. The Status Aggregate monitor displays threshold values only when a threshold is violated. You can view threshold values by holding the mouse pointer over the information oval to display a tooltip window. When thresholds are within normal ranges, the monitor displays a status icon that shows that the status is OK. When a threshold is violated, the icon changes to reflect the severity of the threshold violation.
By default, the CPU utilization, Memory utilization, Network utilization, and Status Aggregate metrics are displayed in the Tile View. You can add Storage utilization, Availability, and custom metrics to a tile by using the Tile View Preferences dialog box. You can set thresholds for the aggregate monitors in the BMC ProactiveNet Operations Console. If you have a multiple server deployment, you must set the thresholds on the child servers. If you are viewing the cloud objects from the Central Console, you can cross launch to the child servers to set the thresholds. For details about thresholds and setting threshold values, see Understanding event thresholds on page 242 and Setting event thresholds on page 246. You can mouse over the information ovals in the Tile View to view the current value of a metric and the minor, major, and critical thresholds that are set for each metric. You can edit the tiles to select the metrics that you want to display in the Tile View. For details, see Using Edit mode to change preferences in the Tile view on page 181.
43
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, based on the assigned access rights. The event information and statuses are updated every two minutes. Table 8 on page 45 summarizes the basic characteristics of each type of event view. Each view is displayed as a separate node in the navigation tree in the Main drawer.
Table 8: Views of event information in the Main drawer View Event Collectors Description Displays a list of events for services and devices monitored by BMC ProactiveNet Further information Viewing the default event list for Event Collectors on page 48
Abnormalities
Displays a list of abnormality type events. Abnormality Viewing all abnormalities on type events are events that are automatically detected page 126 from statistically significant abnormal trends. 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 139 Viewing events by device on page 149 Viewing events for monitored services on page 154
Services Groups Devices Monitors
Chapter 2 Working with events 45
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, click Preferences .
2 In the Event List Preferences dialog box, use the information in Table 9 on page 46 to determine the appropriate settings. Table 9: Event list preference settings
Field Auto-Refresh Description Enables automatic refresh of the event list after a periodic interval. The default refresh interval is 2 minutes. This can be configured by changing the pronet.alarmStatusView.refreshRate property in the installDirectory\ pw\pronto\conf\pronet.conf file. By default, AutoRefresh 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. To view the event list pop-up window, right-click a configuration item under Services => Graph View, and select View Events. Number of Events to Download Per Page Enables specification of the number of events to be downloaded per page. The recommended setting is 200. The higher the value, the more time required to refresh the events.
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, a user can enter operation notes using confirmation dialog boxes. By default, 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. If cleared, tooltips display the same event attributes as displayed in the header row of the event list and labels in the Details Notebook. This setting is not applicable to slots related to Baseline and Threshold for Intelligent events, in both, the header row of the event list and labels in the Details Notebook.
Filling Row with Severity Color Displays the severity color for the following options: Entire event row Only the first column (after the Status, Tools Menu, Priority, 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, Tools Menu, Priority, 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. 4 In the Event List Preferences dialog box, click OK.
Viewing the default event list for Event Collectors
Note The preference settings are applied to browser windows for a particular user logon on the same computer. All pop-up boxes reflect this change with a delay of a maximum of one minute.

The Event Collectors screen lists all the events for services and devices monitored by BMC ProactiveNet. Events on the Event Collectors screen are displayed in a tabular form as summarized in Table 10 on page 48.
The default event list does not display events based on permissions of devices. It displays all events based on the permissions of event collectors.
Table 10: Event information columns on the 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. Status Provides basic information about the events response activity, that is, displays the current status of the event. The status of an event can be one of the following event: Open Assigned Acknowledged Blackout Closed
Note
Column Tools Menu
Description For events originating from BMC Impact Manager (cell), this menu enables you to perform operations on an event, execute remote actions/diagnostics, perform probable cause analysis for the event, retrieve BMC 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 event requires action before the other Indicates the seriousness of the event, 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. This can be configured by changing the bmc.proactivenet.defaultSeverity property in the installDirectory\pw\pronto\conf \pronet.conf file. 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.
Occurred
Displays the date and time when the event occurred
Column Message
Description Displays a short description of the reason for the event. It also displays clickable hyperlinks to external websites. The supported hyperlinks are http://, https://, ftp:// and www. The following slots support the hyperlink feature: Message Monitoring Tool Device Name Host Object URI It might also display the following icons: Action Result(s)
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, by default, the first event in the list is selected. Occasionally, no event is selected and highlighted in the event list. Related Topics Viewing the event list for remote cells on page 120
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.
Table 11: Further information options from the Tools Menu on the All Events screen Option Operations Remote Actions/Diagnostics Action Results Probable Cause Analysis Description Enable you to perform event operations such as open, close, and so on. For more information, see Performing event operations on page 96. Enable you to execute a remote action on a selected event. For more information, see Executing remote actions on page 113. Enables you to view the results that are generated when you perform a local or remote action on an event. Enables you to perform probable cause analysis on the selected event. For more information, see How BMC ProactiveNet performs probable cause analysis on events on page 221. Enables you to store and track configuration data. For more information, see Managing configuration changes on page 158. Enables you to export information about all or only visible slots in a BAROC, XML, or CSV file. For more information, see Exporting and copying event information on page 102. Enables you to send information of a selected event quickly. For more information, see Sending manual events on page 103 .
Add Configuration Change Export
Send Manual Event(s)
Additional options for an Intelligent Event Intelligent Event History Diagnostics Displays event history details. For more information, see Table 12 on page 53. Enables you to use pre-configured and user-defined diagnostic tools to help monitor your system. For more information, see Diagnostics on page 162. Displays a graph and provides additional options to modify the graph. For more information, see Customizing monitor graphs on page 328. Displays the parent groups and subgroups, if available. Displays the related event associated with the main event.
Show Graph(s) Show Parent Groups Related Events
Option Threshold + Data Collection
Description Enables you to set event thresholds and managed data collection. For more information, see Understanding event thresholds on page 242, Managing data collection on page 159, and Resetting a baseline on page 448. Note: The Reset Baseline and Manage Data Collection options are displayed only to users who have administrator privileges and to unrestricted users who have permissions for baseline administration and manage data collection. These options are not available to restricted users.
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. 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, see Launching an originating BMC ProactiveNet Server on page 118. This option is available only when you have a multiple server deployment environment. Both these options are available in a multiple server deployment environment where devices are sourced from the CMDB. If you have configured BMC Service Level Management with BMC ProactiveNet, you can view BMC Service Level Management options for CMDB-published CIs. Note: The Launch options are available for events associated with the CI and the CI itself, only if the CIs are sourced from the Configuration Management Database (CMDB).
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. 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 Namename of an event rule that triggered the action Action Typetype 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 126 Viewing events by device on page 149
Viewing the event list for a specific component in the navigation tree
Viewing events by group on page 139 Viewing events for groups in a hierarchical tree on page 146 Acknowledging events on page 155 Viewing events and abnormalities by service on page 132 Viewing services in a hierarchical tree on page 137 Searching events on page 92 Behavior of popup windows for Tools Menu options on page 54
Behavior of popup windows for Tools Menu options

When you navigate through various BMC ProactiveNet screens, you observe the following behavior for various options selected from the Tools Menu:
Operations such as Intelligent Event History, Probable Cause Analysis, Show
Graph(s), and Show Parent Groups open in a popup window. All further navigation that you perform from this popup window is limited to this popup window only. Threshold, Absolute Instance Threshold, Signature Global Threshold, Signature Instance Threshold, Reset Baseline, and Manage Data Collection, open in a second popup window. These operations do not reuse the popup window opened by operations listed in the first bullet point. the same operation, otherwise, opens in a new window.
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, no matter from where they are launched.
The procedures for viewing events for an event collector, a group, a service, a device, and a monitor are almost alike. BMC ProactiveNet displays the events for the selected object in the event list pane.
When No filter is selected in Groups filter, all non-device-associated external events and events on the devices or monitors to which you have access are displayed. Only events executed on accessible monitors are listed. The Tools menu options depend on your permissions. If you have Write access, Thresholds and Data Collection options are available (only on a monitor).
Note
To view the event list for a collector

1 In the navigation tree, expand the Global folder . whose
2 Expand the hierarchy under Event Collectors to locate the collector events you want to display. 3 Click the collector.
To view the event list for all abnormalities

1 In the navigation tree, expand the Global folder. 2 Click Abnormalities.
Tip You can also view the event list for abnormalities by performing the following steps:
1 In the navigation tree, expand the Global folder. 2 Click Event Collectors => All Events. 3 Apply one of the following out-of-the box advanced filters:
All Abnormalities Active Abnormalities Inactive Abnormalities
For more information, see Applying a default, global, or user-defined template for event list columns on page 63.
To view the event list for a group

1 In the navigation tree, expand the Global folder. 2 Click Groups.
Viewing CI-based event lists
3 Expand the hierarchy to locate the group 4 Click the group.
whose events you want to display.
To view the event list for a service

1 In the navigation tree, expand the Global folder. 2 Click Services. 3 Expand the hierarchy to locate the service 4 Click the service. whose events you want to display.
To view the event list for all devices

1 In the navigation tree, expand the Global folder. 2 Click Devices.
To view the event list for all monitors

1 In the navigation tree, expand the Global folder. 2 Click Monitors.

Because BMC ProactiveNet provides impact analysis, the Services node in the navigation tree includes business services nodes. This allows you to display a CIbased event list that displays the events associated with consumers and providers for all services. You can select Services or any service node level to view the corresponding event list data in the Event View. The Additional Filter for Event Scope drop list has also been introduced for a CIbased event list. This list is visible only for CI-based events.
Viewing events for all services

If you select Services, direct events for all the root-level services available are displayed in the Event View. You have the option of changing the Event View to display impacting events or all events.
Viewing events for a single service component node in the Event View
If you select a service component node (CI node) from the navigation tree, direct events for the selected component are displayed. You can filter the events based on scope (Impacting (Direct or Providers) (displays both consumer and provider events), or Direct ) using the Events Scope drop list located above the event list. If you choose Impacting (Direct or Providers), the event list based on this filtering criteria does not get refreshed. However, a snapshot of the time that the event was last fetched is displayed.
Refreshing the event list

You can only refresh CI-based event lists for direct events. For Impacting (Direct or Providers) and Events Scope, a snapshot of the time that the event was last fetched is displayed, and the refresh option is not available.
Informing users of event occurrence

If no events occur for a CI-based event list, a message indicating the same is displayed.
Viewing events for a single service component node in the Graph, Tile, or Canvas View
If you select a service component node (CI node) in the Graph, Tile, or Canvas View, you can choose from the following options for viewing the events:
All (Direct and Providers) Change (Direct) Direct Impacting (Direct and Providers) Predictions (Direct and Providers)
If you choose any of these options, a snapshot of the specified event list for the selected node is displayed, and the refresh option is not available.
Customizing the standard and custom event class slot display labels
Customizing the standard and custom event class slot display labels
Slots identify information within an event class. Each event class has defined slots. Some slots are common to all event classes, while others are unique to an event class. The default slots in the event list provide basic information about an event. By changing the slots presented in the event list, you can view additional pertinent information or change the order in which event data is presented. You can also customize the standard and custom event class slot display labels in the event list.
To configure custom and standard event class slots to be displayed in the event list
1 In a text editor, open the pw\pronto\conf\resources\en_<lang>\kbinfo \kb_core_resource.properties file. 2 Add the new custom event slot and associated display name. You can specify either the class and slot name or just the slot name, as shown below.
3 Log off and log on again for the change to be effective. You do not need to restart the BMC ProactiveNet Server.
Selecting the type of event list to view
Selecting the type of event list to view

The Quick Columns Selector in the toolbar panel allows you to select the columns that are displayed in the event list. BMC ProactiveNet provides the following out-of-the-box or default templates.
Table 13: Out-of-the box event list templates Template Abnormality Information Columns displayed in the event list Status, tools menu, priority, severity, score, date and time the abnormality occurred, message produced by the abnormality, host name on which the abnormality occurred, and object (monitor) on which the abnormality occurred Status, tools menu, priority, severity, action count (number of occurrences), host name on which the intelligent event occurred, date and time the intelligent event occurred, message produced by the intelligent event, and IP address of the host on which the intelligent event occurred Status, tools menu, priority, severity, date and time the event occurred, message produced by the event, and host name on which the event occurred Tools menu, incident priority, incident status, incident assignee, incident ID, date time, and message produced by the event Status, tools menu, priority, severity, date and time the event occurred, message produced by the event, host name on which the event occurred, object (monitor) on which the event occurred and its class Status, tools menu, priority, severity, date and time the event occurred, predicted severity, predicted time, message produced by the event, host name on which the event occurred, and object (monitor) on which the event occurred Status, tools menu, priority, severity, date and time the event occurred, host name on which the event occurred, object (monitor) on which the event occurred, message produced by the event, ID, internal ID, and propagations Status, tools menu, priority, severity, date and time the event occurred, owner of the event, and message produced by the event
Alarm Information
Basic Information
Event Incident Information Intelligent Events Information
Predicted Events Information
Remote Cell Events Information
Supervisor Information
Creating a new template for event list columns
Template Intelligent Events Details
Columns displayed in the event list Status, tools menu, priority, severity, tool, date and time the intelligent event occurred, metric, message, device, and score. If you do not have access to a device, the Tools menu is not available in the Device matrix page. When viewing a device, the event counts take into account only the events from accessible monitors. Only monitors accessible to the user are displayed. Note that Intelligent event matrix pages are authorization aware; Groups, devices and monitors in these pages and any actions available from the Tools menu reflect your access privileges and permissions. For more information, see Intelligent Events Details template on page 60.
Intelligent Events Details template

Administrator and other users cannot edit, delete, or copy the Intelligent Events Details (default or out-of the box) template. This template is available from the following drill-down options:
Event View => Abnormalities, Groups, Services, Devices, and Monitors Event View => All components folders created by a user under the Global and
My Folders folders
Tree View => Groups and Services and then right-clicking to select the All
Events or Abnormalities options
Grid View => Abnormalities, Groups, Services, Devices, and Monitors, and
then clicking the event counts displayed on these pages
Related topics: Creating a new template for event list columns on page 60

An administrator can create a customized template so that the event list displays only those columns that are present in this newly created template.
To create a new template for event list columns

1 Click Quick Columns Selector. 2 In the Quick Columns Selector dialog box, click Editor. 3 In the Event List Column Editor dialog box, select the Templates tab, and then, on the left, click New Template . 4 Specify a Name for the new template. 5 Select Make Global so that all users can view this template. A global template is prefixed with an asterisk (*). Only an administrator user can delete a global template. User-defined templates are not prefixed with an asterisk. 6 Select Default for New Event Folders to use this template as a default for newly created event folders. 7 Select Show in Quick Columns Selector so that this template appears in the Quick Columns Selector dialog box. 8 Under Available Columns, perform the following steps: a Click Event Class Selector .
Tip
b Select an event class, and then click OK. c Select a column name. d Click the right arrow. e Click the Up or Down arrows to change the order in which the columns will be displayed. 9 Click Save. Related topics: Editing a default or user-defined template for event list columns on page 62 Copying an existing template for event list columns on page 62 Deleting a user-defined template for event list columns on page 63
Editing a default or user-defined template for event list columns
Applying a default, global, or user-defined template for event list columns on page 63 Adding a column to an event list on page 64 Deleting a column from an event list on page 64 Adding a column to an event list for an abnormality on page 127 Deleting a column from an event list for an abnormality on page 128
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, click Editor. 3 In the Event List Column Editor dialog box, select the Templates tab, and then, on the left, click a default or user-defined template. 4 Modify the information that you want to edit. 5 Click Save.
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.
To copy a default or user-defined template

1 Click Quick Columns Selector. 2 In the Quick Columns Selector dialog box, click Editor.
Deleting a user-defined template for event list columns
3 In the Event List Column Editor dialog box, select the Templates tab, and then, on the left, click a user-defined or default template. 4 Click Copy .
A template Copy of copiedTemplate appears on the left, under the list of availabletemplates.
Deleting a user-defined template for event list columns

Administrators and other users can delete user-defined templates created by them.
To delete a user-defined template

1 Click Quick Columns Selector. 2 In the Quick Columns Selector dialog box, click Editor. 3 In the Event List Column Editor dialog box, select the Templates tab, and then, on the left, click a user-defined template. 4 Click .
Applying a default, global, or user-defined template for event list columns

All users can apply default, global, or user-defined templates to an event list to view the columns present in these templates.
To apply a default, global, or user-defined template

1 Click Quick Columns Selector. 2 In the Quick Columns Selector dialog box, click Editor. 3 In the Event List Column Editor dialog box, select the Templates tab, and then, on the left, click a default, global, or user-defined template. 4 Click .
Adding a column to an event list
The event list displays only those columns that are present in the selected template.
Adding a column to an event list

All users can add a single column from any event class to the event list.
To add a column to an event list

1 Click Quick Columns Selector. 2 In the Quick Columns Selector dialog box, click Editor. 3 In the Event List Column Editor dialog box, select the Single Columns Selector tab. 4 Under Available Columns, click Event Class Selector 5 Select an event class, and then click OK. 6 From the Event List Column Editor dialog box, 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. BMC recommends that you add a maximum of 30 columns to the event list to optimize the performance of refresh. .
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. 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

1 Click Quick Columns Selector. 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.
Viewing the event Details Notebook

The Details Notebook pane displayed below the event list provides all of the recorded information about an event. 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, Show Graph(s), and Detailed Diagnostics Basic information about the event, such as status, severity, priority, date and time of occurrence, object class, object name, host, owner, message, and detailed message Event Metric Event metric information such as metric and its value, class, category, monitor category, repeated, and SO For an intelligent event, this field includes additional information such as threshold, average value, baseline, baseline type, comparison, duration, minimum sampling window, absolute deviation, deviation, score, predict, and auto close
Column name Logs and Notes
Sections in subtab Historical Attributes
Description of contents Historical attributes of the event, such as date and time of occurrence, repeated, original severity and priority, origin time, reported by source, arrived, received, modified, last modifier, time to close, 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. The Logs and Notes table displays notes added by the user, event notification history, event rule history, history of any rule or policy applied, and event operation history.
Object
Object Monitored
Hyperlinks to launch Show Graph(s) and Tools Menu Information about the monitored object, such as its name, class, owner, and URL For an intelligent event, this field includes additional information about groups.
Host of Object
Information about the host of the monitored object, such as its name, address, class, location, and service For an intelligent event, this field includes additional information, such as VMware host and ID
Parameter Related Component
Monitor metric and its value; parameter unit and its threshold Device name, component alias, ID, and type
Column name Source
Sections in subtab Origin
Description of contents Information about the origin of the event, including class, key, and severity Information about the adapter or gateway from which the event originated, including the tool name, tool ID, monitoring tool name, tool suggestion, adapter host, client address, tool class, rule, tool key, tool severity, tool address, and tool time (time when the event originated) By default, this card is not visible. For more information, see To select the cards to be displayed in the Details notebook pane on page 69.
Reporter
Internals
Tracking
Tracking information, such as the ID, internal ID, account, timeout, collectors, propagations, history, modification history, Access Control List (ACL), and Common Event Model (SEM.) version Alarm ID is displayed in this section if the event selected is of ALARM type. By default, this card is not visible. For more information, see To select the cards to be displayed in the Details notebook pane on page 69.
Relationships
Information about events abstracted from this one, abstractions, causes and effects, associations, relation source, and event relations A list of undefined attributes and values
Undefined Attributes
Column name Others
Sections in subtab dependOnTheSelectedEvent
Description of contents Information in this card changes according to the type of event selected. The event type is displayed before the slots present for that event type, provided the event type has slots that are not present in the remaining cards. For example, attributes of a core event that are not displayed in other cards, such as ITSM category, company, item, location, manufacturer, model, version, and operation category 1, 2, and 3, product name, type, Service Model Component (SMC) impact, and priority might be displayed in this card.
To view and hide the Details Notebook

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.
To view the total number of filtered events that are displayed

1 Select a collector from the All Event Collectors folder. 2 Apply the necessary filters for the events. For more information on applying filters, see Filtering event display for All Abnormalities on page 130. The Event(s): label on the right side of the event list notebook header displays the number of events for which the filters have been applied. The format in which it is displayed is Event(s): <Number of filtered events>. For example, Event(s): 200, where 200 is the total number of filtered events. Event count is not displayed for the event list for which the Details Notebook pane is not present. For example, event count will not display for the latest 10 events and maximized event list on Tile and Canvas views. Event count is also not displayed if the number of events for a particular filter is zero.
Note
To select the cards to be displayed in the Details notebook pane

1 Select an event from the event list. 2 Click Edit Notebook Preferences .
3 Select the cards to be displayed in the Details Notebook pane. 4 Click Close .
If you select more cards than can be displayed, use the tiny right and left arrows to the right and left of the Details Notebook to navigate through the cards.
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 In any of the cards listed in Table 14 on page 65 of the Details Notebook pane, . click Edit Preferences 3 Select the event information that must be displayed in the selected card. The attributes available for selection depend on the type of event selected. The permissions that a user has determine whether the user can perform an action on a hyperlink. 4 Click Close. In the Summary card, when you click Edit Preferences, 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.
Note
To view additional information about a card in the Details Notebook pane

1 In any of the cards listed in Table 14 on page 65 of the Details Notebook pane, . click More Info 2 Click Minimize .
To add notes or annotate an event

1 From the event list, select an event.
Event relationships
2 In the Logs and Notes card of the Details Notebook pane, click More Info 3 Scroll down to the Logs and Notes section and enter the annotated text. Do not include nonprinting characters such as FS (0x1c) and RS (0x1e), and printing characters such as <, >, , and in the notes. These characters are not supported. 4 Click Save. A Notes icon is displayed in the selected event message.
Note
Event relationships
You can establish a relationship between two CIs or events by defining rules and policies. For example, consider the following scenarios: Scenario 1: Create a correlation policy between the following two cause and effect events.
Cause event could be a CPU reaching 80% usage for a device. Effect event could be response time of web URL hosted on that device is slow.
When you select the web URL event and view the event relationship, the Event Relationship window displays the cause event. By viewing and resolving the cause event, the effect event gets automatically resolved. In this example, by resolving the CPU issue the response time of the web URL improves. Scenario 2: Create an Abstraction rule to generate an event when an application server and web server services of an online shopping portal is down with a message "Online shopping portal is down". If both these events are generated and you have taken no action, an abstraction event is generated with the message "Online shopping portal is down". You can view and take relevant action on these events. For more information on creating and using user-defined policies, see to the BMC ProactiveNet Administrator Guide and for more information about rules for policy types and how to create them, see the BMC Knowledge Base Development Reference Guide. For information on how to view event relationships, see Viewing event relationships on page 71.
Viewing related events
Viewing event relationships

You can view the event relationships from the BMC ProactiveNet Operations Console.
To view event relationships

1 The Event Relationships icons are displayed in the Message column if an event has a relationship. represents the main event to which a new event is associated. represents an event that is associated with a main event. Click the icons to open the Event Relationship window with details of the selected event in the Selected Event: pane. 2 Select a relationship from the Relationships pane and the tabs displayed below vary based on the relationship selected. The tabs display the Event Condition Formula (ECF) name that you have defined in the policy you created. 3 Select a tab to view the details in the Details pane. For more information on viewing the details in the Details pane, refer to Viewing the event Details Notebook on page 65. 4 Click to refresh the data/screen.
Note
If you have upgraded from a previous version of BMC ProactiveNet
Performance Management and you have related events, the displayed in the Message column.
icon is
You can view the remote action results when you click on
in the Message column. This feature is available only from this release. For more information on remote actions, refer to Executing remote actions on page 113.
For more information about event relationships, go to Event relationships on page 70.
Viewing related events

To view events that are associated with another event, in an event list row, click in the Message column to view the original event, or click in the Message column to view the new associated event. When you click the Event Relationships icon, the Event Relationship dialog box is displayed. This dialog box displays the details of the selected event.
BMC ProactiveNet includes .mrl files in which event relationships are defined. The BMC ProactiveNet cell processes events as per the rules in the .mrl files. The Relationship Type and Rule or Policy columns are populated with data as per these files. For more details about .mrl files and rules, see the BMC Knowledge Base Development Reference Guide. Figure 3: Event Relationship dialog box

All of the event sources in the BMC ProactiveNet system can generate thousands of events. You can choose whether to view all of those events as they occur. You can configure refresh of the event list to occur automatically or manually, and even if you use the automatic refresh, you can manually refresh at any time to be sure that you have the most recent data. When you manually refresh the event list, the BMC ProactiveNet Server is queried for any changes in events. The console updates the event list if changes are present.
Organizing events in the event list
On the Internet browser, the F5 and Refresh buttons are not supported. Also, on some UI screens, the Back, Forward, and Close buttons are also not supported.
Note
To automatically refresh the event list

1 From the navigation bar, click Preferences .
2 In the Event List Preferences dialog box, select Auto-Refresh. If Auto-Refresh is not enabled and an event is modified externally from the console, the event is not updated until you manually refresh the event list by clicking Refresh in the navigation bar.
Note If the BMC ProactiveNet Server is extremely busy, the event list might not be refreshed until the BMC ProactiveNet Server completes the current eventprocessing load.

You can use various techniques to organize events and view information about them:
Use event and component folders to arrange events from different sources. Filter events to see only the ones of interest. Search events to see only the ones of interest. Change the sorting of the event list.
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. With these folders, you can display events in a single tree node in the navigation tree, grouping events in your own ways.
Note Folders are a prerequisite for image views. You must first create an event or component folder to which you can add an image view.
For more information about creating event folders, see Creating event folders on page 74. For more information about creating component folders, see Creating component folders on page 76. For more information about creating remote cell event folders, see Creating remote cell event folders on page 81.
Creating event folders

The following procedures explain how to add, delete, and modify event folders, and how to move them within their hierarchy.
To add an event folder node

1 In the Main drawer of the navigation pane, click Global or My Folders . 2 From the Navigation Menu at the top of the drawer, choose Add Folder => Event Folder. 3 In the Add Event Folder dialog box, enter a name for the new event folder and optionally enter a description. 4 Under Available Event Collectors, select a collector or subcollector to add to the new event folder. 5 Click the right arrow to add the selected collector to This Folders Event Collectors .
Tip You can also drag a collector or subcollector from Available Event Collectors and drop it into This Folders Event Collectors .
The selected collector appears beneath the new event folder in This Folders Event Collectors . To remove the selected collector from This Folders Event Collectors , click the left arrow . 6 To add another collector or subcollector, repeat the previous steps.
7 Scroll down on the dialog box and underEvent List View , perform the following actions:
From Event List Columns, select a template to use to determine which columns
to display in event list.
From Event List Filter, select how you want to filter the events in the event list.
8 (optional) To add a subfolder, perform the following additional steps: a Under This Folders Event Collectors, select the newly created event folder. b Click Add Subfolder .
c Specify a name for the newly created event subfolder. d Repeat the previous steps to add more event subfolder. e Add event collectors to each subfolder as specified in step 4 through step 6. 9 Click OK.
To delete an event folder node

1 In the Main drawer of the navigation pane, click Global or My Folders. 2 Select a folder in the navigation tree. 3 From the Navigation Menu at the top of the drawer, choose Delete.
4 In the Delete Folder confirmation dialog box, click Yes. Deleting a parent event folder deletes the event folder and all its descendants.
WARNING
To move an event folder subnode within its parent folder node

1 In the Main drawer of the navigation pane, click Global or My Folders . 2 Select a folder in the navigation tree. 3 From the Navigation Menu at the top of the drawer, choose Edit Folder.
4 In the Edit Event Folder dialog box, select the event folder subnode or collector that you want to move.
5 Click the Move Up or Move Down arrow button to move the event folder or collector subnode within the parent folder node hierarchy. 6 Click OK.
To edit an event folder node

1 In Main drawer of the navigation pane, click Global or My Folders . 2 Select a folder in the navigation tree. 3 From the Navigation Menu at the top of the drawer, choose Edit Folder.
4 In the Edit Event Folder dialog box, perform any of the following actions:
Modify the name of the existing event folder Add or modify the description Add, delete, or move event folder subnodes or collectors, if any Change the template for the event list Change the filter for the event list
5 Click OK.
Creating component folders

The following procedures explain how to add, delete, and modify component folders, and how to move them within their hierarchy.
To add a component folder node

1 In the Main drawer of the navigation pane, click Global or My Folders. 2 From the Navigation Menu Component Folder. at the top of the drawer, choose Add Folder =>
3 In the Add Component Folder dialog box, specify a name for the new component folder and optionally enter a description. 4 Under Folder Contents, select one of the following options to determine what components are displayed in the folder that you are creating:
Static List of Objects - search for components and select the components that
you want to include in the folder from the list returned in the search results.
Dynamic- Contents Change - search for components based on the filter criteria
that you specify. The list of components changes over time based on the filter criteria.
The maximum number of CIs that a static or dynamic folder can hold is 500. You can configure this number in the pronet.conf file. For details, see the BMC ProactiveNet Administrator Guide. To avoid performance issues when the navigation tree loads, 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. High level or general search criteria could return too many results. When you create a dynamic folder, use Test Filter to verify approximately how many CIs match the search criteria that you enter. If the search results in too many CIs, enter additional attributes in the search criteria to narrow the search.
Continue with the following procedures, depending on what type of folder you are creating. To add a static folder node on page 77 To add a dynamic folder node on page 79
To add a static folder node

1 If you selected Static List of Objects, select one of the following types of components to include in the new folder:
Groups and Devices: proceed to step 2. CIs from Service Model: proceed to step 3.
2 If you selected Groups and Devices, perform the following additional steps: a Under Available Components, select to search for Groups or Devices or All. b Enter the search criteria for the name of the group or device that you want to search for. The Groups and Devices list is automatically filtered based on the search criteria that you entered.
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.
Tip You can also drag a group or device from Available Components and drop it into This Folders Components.
d To add another group, service, or device, repeat these steps. 3 If you selected CIs from Service Model, 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. b (optional) If you want all users that log on to the BMC ProactiveNet Operations Console to access the query that you are creating, select Make *Global (all users). An asterisk is placed next to the query name to indicate that it is global and is available to all users. c From the Class list, select the type of component that you want to search for. d If necessary, expand the query builder options by clicking the plus button next to the Class list.
e Begin building the parameters for your query by selecting the attributes for the class type that you selected. To display additional attributes, click the plus button
next to the attribute name. Each new attribute that you add narrows and refines the search. The query will search for components with all of the attributes that you specify, indicated by the AND before the attribute names. If you use the same attribute, but specify different values, then the query will search for components with any but not all of the values that you specify, indicated by the OR before the attribute names. f When you have finished specifying the query attributes, click Find. g Under Results, select the CI to add to the new component folder.
h Click the right arrow to add the selected CI to This Folder's CIs. You can also drag a component or subcomponent from Results and drop it into This Folder's CIs. The selected item appears beneath the new component folder in This Folder's CIs. Click the left arrow to remove the selected item. A device added to a CI folder node or subnode is not visible in the navigation tree but is useful in the Tile view. i To save the query to use again, click Save, enter the Query Name, and click OK. The saved query can also be used to search for CIs in the Find CI drawer in the navigation pane. 4 (optional) To add a subfolder, perform the following additional steps: a Under This Folders CIs, select the newly created component folder. b Click Add Subfolder .
Tip
Note
c Specify a name for the newly created component subfolder. d Repeat the previous steps to add more component subfolders. 5 On the Add Component Folder dialog box, click OK.
To add a dynamic folder node

1 If you selected Dynamic - Contents Change, 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. b (optional) If you want all users that log on to the BMC ProactiveNet Operations Console to access the query that you are creating, select Make *Global (all users). An asterisk is placed next to the query name to indicate that it is global and is available to all users.
c From the Class list, select the type of component that you want to search for. d If necessary, expand the query builder options by clicking the plus button next to the Class list.
e Begin building the parameters for your query by selecting the attributes for the class type that you selected. To display additional attributes, click the plus button
next to the attribute name. Each new attribute that you add narrows and refines the search. The query will search for components with all of the attributes that you specify, indicated by the AND before the attribute names. If you use the same attribute, but specify different values, then the query will search for components with any but not all of the values that you specify, indicated by the OR before the attribute names. f When you have finished specifying the query attributes, click Test Filter. g Under Results, the CIs that match the search criteria are displayed up to a maximum of 500. h To save the query to use again, click Save, enter the Query Name, and click OK. 2 On the Add Component Folder dialog box, click OK.
To delete a component folder node

1 In the Main drawer of the navigation pane, click Global or My Folders . 2 Select a folder in the navigation tree. 3 From the Navigation Menu at the top of the drawer, choose Delete.
4 In the Delete Folder confirmation dialog box, click Yes. Deleting a parent component folder deletes the component folder and all its descendants.
WARNING
To move a static component folder subnode within its parent folder node
4 In the Edit Component Folder dialog box, select the component folder subnode that you want to move. 5 Click the Move Up or Move Down arrow button to move the component folder or collector subnode within the parent folder node hierarchy. 6 Click OK. You can use this procedure to move a group, service, or device within its parent folder node.
Tip
To edit a component folder node

4 In the Edit Component Folder dialog box, perform any of the following actions:
Modify the name of the existing component folder Add or modify the description Add, delete, or move component folders, groups, services, or devices, if any
5 To save your changes, click OK.
Creating remote cell event folders

The following procedures explain how to add, delete, and modify remote cell event folders, and how to move them within their hierarchy.
To add a remote cell event folder node

1 In the navigation pane, click Other Cells. 2 Select a remote cell for those listed in the Other Cells navigation tree. 3 From the Navigation Menu Folder. at the top of the drawer, choose Add Event
4 In the Add Event Folder dialog box, enter a name for the new event folder and optionally enter a description. 5 Under Available Event Collectors, select a collector or subcollector to add to the new event folder. You cannot add the self collector to a remote cell event folder. The self collector is the top level collector in the Available Event Collectors list and has the same name as the remote cell. 6 Click the right arrow to add the selected collector to This Folders Event Collectors .
Note
Tip You can also drag a collector or subcollector from Available Event Collectors and drop it into This Folders Event Collectors .
The selected collector appears beneath the new event folder in This Folders Event Collectors . To remove the selected collector from This Folders Event Collectors , click the left arrow . 7 To add another collector or subcollector, repeat the previous steps. 8 Scroll down on the dialog box and underEvent List View , perform the following actions:
From Event List Columns, select a template to use to determine which columns
to display in event list.
From Event List Filter, select how you want to filter the events in the event list.
9 (optional) To add a subfolder, perform the following additional steps: a Under This Folders Event Collectors, select the newly created event folder.
b Click Add Subfolder
c Specify a name for the newly created event subfolder. d Repeat the previous steps to add more event subfolder. e Add event collectors to each subfolder as specified in step 4 through step 6. All remote cell event folders are global folders, meaning they can be seen by all users who access the operations console with the correct permissions. To view a remote cell event folder in the operations console, 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. 10 Click OK.
To delete a remote cell event folder node

1 In the navigation pane, click Other Cells . 2 Select a folder in the navigation tree. 3 From the Navigation Menu at the top of the drawer, choose Delete.
4 In the Delete Folder confirmation dialog box, click Yes. Deleting a parent event folder deletes the event folder and all its descendants.
WARNING
To move a remote cell event folder subnode within its parent folder node
1 In the navigation pane, click Other Cells . 2 Select a folder in the navigation tree. 3 From the Navigation Menu at the top of the drawer, choose Edit Folder.
4 In the Edit Event Folder dialog box, select the event folder subnode or collector that you want to move. 5 Click the Move Up or Move Down arrow button to move the event folder or collector subnode within the parent folder node hierarchy. 6 Click OK.
To edit a remote cell event folder node

1 In the navigation pane, click Other Cells . 2 Select a folder in the navigation tree. 3 From the Navigation Menu at the top of the drawer, choose Edit Folder.
4 In the Edit Event Folder dialog box, perform any of the following actions:
Modify the name of the existing event folder Add or modify the description Add, delete, or move event folder subnodes or collectors, if any Change the template for the event list Change the filter for the event list
5 Click OK.
Filtering events
Using filters available in the filters panel located above the event list, you can narrow the scope and number of events displayed. By default, the Quick filters panel is button in the navigation bar toggles the filters panel displayed. The Show Filter on and off. BMC ProactiveNet offers the following filtering methods:
quick filters, which show events based on a specific status, severity level, time,
event type, device, 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. The Quick Filter in the filters panel provides an easy way to view only those events in an event or component folder, or an event collector that satisfy a single or multiple criteria for filtering. You can also save the quick filter settings for event collectors and event collections, and go back to the last saved filter settings. Examples of event folders are:
Event Collectors and Abnormalities under the Global folder and user-defined event folders created under the My Folders or Global folder Examples of component folders are: Groups, Services, Devices, and 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, Intelligent Events, By Status, and so on
To filter events by status

1 From the navigation tree, select an event or component folder, or an event collector. 2 In the filters panel, click the down arrow next to the Status list.
A list of event statuses is displayed: All Open (includes open, assigned, and acknowledged events, 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. Select No filter from the Status list to return to the default event list view.
Note
To filter events using severity

1 From the navigation tree, select an event or component folder, or an event collector. 2 In the filters panel, click the down arrow next to the Severity 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. 3 Select the severity level that you want to use to filter the event list. 4 Click Filter.
To filter events by time

1 From the navigation tree, select an event or component folder. 2 In the filters panel, click the Edit Time (calendar) icon next to the Time field. 3 In the Quick Filter Time Selector dialog box, perform either List item. on page 86 or List item. on page 87. 4 Select Relative time and proceed with the following substeps: a Click the down arrow below Relative time.
b From the list, select the number of minutes, hours, days, weeks, or months, and skip to List item. on page 87. 5 Select Absolute time and proceed with the following substeps: a Select the From date and time. b Select the To date and time. 6 Click OK. 7 Click Filter. In the Quick Filter Time Selector dialog box, click Clear to return to the default event list view.
Note
To filter events by type

1 From the navigation tree, select an event or component folder, or an event collector. 2 In the filters panel, click the down arrow next to the Event Type list.
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. 4 Click Filter. Select No filter from the Event Type list to return to the default event list view.
Note
To filter events by device

1 From the navigation tree, select an event or component folder, or an event collector.
2 In the filters panel, enter the device name in the Device field. 3 Click Filter.
To filter events by groups

1 From the navigation tree, select a component folder, such as Devices or Monitors. 2 In the filters panel, click Groups. 3 In the Groups Filter dialog box, perform the following substeps: a From the list on the left, select the way in which you want to display the groups by selecting one of the following options:
Tree: Displays the parent group nodes, intermediate nodes, 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. c Select the groups, and then click the right arrow. d In the box on the right, select the groups that you want to use to filter the event list. Use the Ctrl or Shift key to select multiple groups. e From the list on the right, select Include or Exclude to include or exclude the groups in the filter criteria. f Click Apply. 4 Click Filter.
Tip
To save a quick filter for event collectors and event collections

1 From the navigation tree, select an event collection or an event collector. 2 Set the necessary filters for the event collection or the collector. 3 Click Save.
Note
By default, the value of bmc.proactivenet.saveQuickFilterInDB in the pronet.conf file is true. If no quick filter is set for a collector or collection, the
default severity parameter is the value of bmc.proactivenet.defaultSeverity, specified in the pronet.conf file (Information and Above), and the default status is All Open.
You cannot save a quick filter if the value of bmc.proactivenet.saveQuickFilterInDB is false. The saved quick filter is user specific.
The filters that you set for the event collection or collector will be saved.
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. Global or advanced filters are available for the Event Collectors event folder and all its subnodes. These filters are not available for the Abnormalities event folder and all the component folders: Groups, Services, Devices, and Monitors and all the drilldowns associated with all the component folders. By default, the advanced filter selected in the filters panel is applied to the event list. You can use these filters to adjust the view of the event list just as you use the quick filters.
To create a filter
1 In the filters panel, click Advanced Filters . .
2 Click Create New Filter
3 Click the down arrow next to the Class list. 4 Select an event class, and then click .
5 To filter events according to one or more event attributes, specify the following information for each attribute: a (optional) Select a left parenthesis or a NOT condition. b Select an event attribute.
c Select a comparison operator. d Enter a value against which you want the filter to compare. e (optional) Select a right parenthesis. f To add another filter condition (event attribute), click .
Tip
To remove a filter condition, click g Select a logical operator, AND or OR. h Repeat List item. on page 89 through List item. on page 90 to add as many filter conditions as you want. 6 Click Save. 7 In theEnter Filter Name dialog box, enter a name for the filter, and then click OK. 8 Click OK. The new filter is displayed in the Name list. in the corresponding filter condition row.
To apply an out-of-the-box-or user-defined filter

1 In the filters panel, click Advanced Filters. 2 Click the down arrow next to the Name list. 3 Select a filter. 4 In the Filter Change Confirmation dialog box, click Yes. The selected filter is applied to the event list.
To apply a filter without saving changes

1 In the filters panel, click Advanced Filters. 2 Click the down arrow next to the Name list. 3 Select a filter. 4 Modify one or more filter conditions.
5 Click Apply. The conditions that you change in an existing filter are not saved until you click Save.
Note
To clear a filter
1 In the filters panel, click Advanced Filters. 2 Click the down arrow next to the Name list. 3 Select a filter. 4 Modify one or more filter conditions. 5 To clear a filter condition, click Start Over. The modified filter conditions are discarded and the original filter is applied to the event list.
To cancel a filter
1 In the filters panel, click Advanced Filters. 2 Click the down arrow next to the Name list. 3 Select a filter. 4 Click Cancel. 5 In the Cancel Filter Confirmation dialog box, click Yes. The most recently applied filter is canceled and the previously selected filter is applied to the event list.
To delete a filter
1 In the filters panel, click Advanced Filters. 2 Click the down arrow next to the Name list. 3 Select a filter. 4 Click Delete.
5 In the Filter Delete Confirmation dialog box, click Yes. 6 Click OK . The selected filter is removed from the Name list. Administrator and other users can delete user-defined filters they create. However, neither an administrator nor other users can delete default or out-of-thebox filters.
Note
Searching events
Using Find Events , available in the toolbar panel located above the event list, you can narrow the scope and number of events displayed. The search functionality is available for event collectors only. Search is performed only on those slots of a CORE_EVENT class that are visible to you in the event list at that instance. Search is case sensitive and considers blank spaces. Therefore, you must enter the exact search criteria to retrieve results. Search is ineffective in the following cases:
If the search is based on the date slot If you select a component folder in the navigation tree If you select an event folder (All Event Collectors, All Abnormalities, 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, type a query to search. 3 Click Find Events.
Sorting events
The set of slots presented in the event list is called the slot order. When you change the slots presented, either by adding or removing slots or by rearranging them, you change the slot order.
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. Even if a multiple sort order has been established, you can click any column header that is not part of the designated multiple sort order to reset sorting. This action establishes single-column sorting, and the column on which you clicked is designated as the first, and only, column in the new sort order. To reverse the sort order, re-click the column header. To remove the sort order, press the Ctrl and Shift keys, and click the column header. Figure 4: 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. You can set a multiple-column sort order as shown in Figure 5 on page 94 . Multiplecolumn sorting is available for the Event Collectors event folder and all its subnodes. However, this feature is not available for the Abnormalities event folder
Creating shortcuts for Tools Menu options
and all the component folders: Groups, Services, Devices, and Monitors and all the drill-downs associated with all the component folders. Figure 5: -Multiple-column sorting indicators
In the following procedures, you can select or clear the column headers that you want to use to sort the contents of the event list.
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. 2 Press the Ctrl key and click a second column header. 3 Repeat List item. on page 94 to add more columns to the sort order for the event list. If you have established a multiple sort order in the event list, you can:
Click one of the columns to re-sort the event list based on that single column. Press the Ctrl key and click a column header contained in the sort order to
Tip
toggle that columns display between ascending and descending order. order to remove that column from the sort order.
Press the Ctrl and Shift keys, and click a column header contained in the sort

Using Edit Toolbar , available in the toolbar panel located above the event list, you can create shortcuts for performing event operations, executing commands, and actions. By default, the toolbar panel is available to all the users. However, Edit Toolbar is visible only if a user has permissions to view it. Show Toolbar navigation bar toggles the toolbar panel.
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, for example, Close, then shortcuts for all the following operations, except Close are displayed.
Acknowledge Close Take Ownership Decline Ownership View Remote Action Results Copy Export Set Priority Intelligent Event History Probable Cause Analysis Operations Menu Tools Menu
To create shortcuts for menu buttons, commands, 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, 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, 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.
Performing event operations
2 Click Close.
The shortcuts appear in the toolbar panel; they are context-sensitive. For
example, if an event is acknowledged, the Acknowledge button in the Menu Buttons section is disabled. However, if the event is not acknowledged, the Acknowledge button is enabled. Once a user changes the toolbar buttons, they are saved as user preferences and available to that user on the subsequent logon.
To remove shortcuts for menu buttons, commands, and actions

1 In the toolbar panel, click Edit Toolbar. 2 From the toolbar panel, right above the event list, select and drag one icon at a time that you want to remove, and then drop it into the Edit Toolbar dialog box. 3 Click Close.

Event operations change the status, priority, or ownership of an event. Your user role determines the event operations that you can use. You can perform these operations on a maximum of 500 events. BMC recommends that you use the toolbar to perform operations on multiple events. However, if you choose to use the Tools Menu or the Operations Menu in the Status column, press and hold the Shift key to select multiple continuous events, or the Ctrl key to select multiple non-continuous events, and ensure that you click the Tools Menu on the last selected event. Table 15: Event operation descriptions
Event operation Take Ownership Description Assigns ownership of an Open or Acknowledged event to self; puts the event in the Assigned state Assigns ownership of an Open, Acknowledged, or Assigned event to self or another person in the same account; puts the event in the Assigned state
Tip
Assign To
Event operation Decline Ownership
Description Removes ownership of an event in Assigned event; puts the event back in the Acknowledged state Recognizes the existence of on Open event; 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; ignores the event in calculating status; disables any further event operation Assigns a priority level to the event Changes the state of an event to Open. This operation is displayed only for remote event management cells.
Acknowledge Event
Unacknowledge Event Close
Set Priority Reopen Event
The following topics provide instructions for 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, an operation is performed only on the selected events whose status makes the operation valid. If the operation is not valid for some selected events, a message box reports the internal IDs of those events, and the events are not changed.
Note
To take ownership of an event

1 From the event list, select an event of which to take ownership. 2 Click one of the wrench icons, column. or , (that is available) in the Tools Menu
3 Click Operations => Take Ownership.
Note If Confirmations in the Event List Preferencesdialog box, is not set for All Event Operations, you do not receive a confirmation when you take ownership of an event. For more information, see Customizing the display of the event list on page 46.
4 In the confirmation dialog box, click OK.
To assign an event to an individual

1 From the event list, select one or more events to assign. 2 Click the wrench icon in the Tools Menu column. 3 Click Operations => Assign To. 4 In the Assign To dialog box, select the person to whom you want to assign the event, and then click OK.
Note The list of users in the Assign To dialog box contains only those users selected in the Assign to User List screen. To access this screen, on the Operations Console select the Options link, and then the Administration tab. Under Event Administration, click Edit next to Assign to User List.
To decline ownership of an event

1 From the event list, select an event that you own. 2 Click the wrench icon in the Tools Menu column. 3 Click Operations => Decline Ownership 4 In the confirmation dialog box, click OK.
To acknowledge an event
1 From the event list, select one or more open events designated with 2 Click the wrench icon in the Tools Menu column. 3 Click Operations=>Acknowledge Event. 4 In the confirmation dialog box, click OK. .
To Unacknowledge an event
1 From the event list, select an event that is acknowledged. 2 Click the wrench icon in the Tools Menu column. 3 Click Operations=>Unacknowledge Event.
To close an event
1 From the event list, select an event that is open, assigned to you, or acknowledged. 2 Click the wrench icon in the Tools Menu column. 3 Click Operations => Close Event. 4 In the confirmation dialog box, click OK.
Note
When the Close Event operation is performed on an intelligent event, it may
take some time to close the event. 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.
The Close Event operation is not available for abnormality events.
To set the priority for an event

1 From the event list, select an event. 2 Click the wrench icon in the Tools Menu column. 3 Click Operations => Set Priority. 4 In the Set Priority dialog box, select the priority level for the event. 5 (optional) Add notes. 6 Click OK. 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, the operation initiated by the user is not executed.
Note
Configuring the Assign to User List

This feature helps you configure the type of user list to appear when you select the function Assign To from the Tools menu when doing event operation in Event view. When configuring the Assign to User List feature, the user list depends on whether BMC ProactiveNet has been integrated with BMC Atrium Single Sign On (SSO) or not.
To configure the Assign to User List with SSO integration

1 In the Administration tab, click Edit against Assign to User List. The Assign to User List window displays. The available options define which users will be displayed when selecting the Assign To function from the Tools menu. 2 Select one of the options:
All Users (default)
Select this option to display all SSO users.

Any User Group
Select this option to select to display the users in an SSO user group or Self SSO user group. 3 Click Apply. For more information about SSO configuration, see the BMC ProactiveNet Installation and Configuration Guide.
To configure the Assign to User List without SSO integration

1 In the Administration tab, click Edit against Assign to User List. The Assign to User List window displays the following options:
All Users - both LDAP and BMC ProactiveNet Admin Users All Users Created in BMC ProactiveNet Admin All LDAP Users Your LDAP Users Your Group - both LDAP and BMC ProactiveNet Admin Users
2 Select one of the options and click Apply.

Dynamic help for events
Dynamic help for events

You can add information Web pages in static or dynamic format and view this information using the Information option in the Tools menu.
To edit Information Web Pages

1 In the Operations Console, click Options. 2 In the Administration tab, click Edit against Information Web Pages. 3 The Information Page window displays the following drop-down options:
No Information Page in Menus: The Information option is not displayed in the
Tools menu for any event.
Same Information Page for All Events: You can enter a static URL and this
same URL is displayed as a separate Web page for all event classes when you select the Information option in the Tools menu. to each event class. When you click Information in the Tools menu, the Web page specific to the selected event is displayed.
Different Information Page for each Event Class: You can enter a URL specific
Different Information Page Based On Event Slot Values: You can enter the
URL and also specify an event slot of an event class. These slot values may be required for the dynamic information page that resides on your Web server.
4 Select one of the options.

If you select the option Same Information Page for All Events or Different
Information Page for each Event Class, the following additional fields appear:
Information URL Backup URL
If you select the option Different Information Page Based On Event Slot
Values, the following additional fields appear:

Information URL Backup URL Event Slot Names
5 Enter the required information and click Apply.
Exporting and copying event information
Exporting and copying event information

You can export information about all or only visible slots in a BAROC, XML, or CSV file or copy information about all the slots into the clipboard. These operations enable you to send the event information to BMC Impact Manager (BMC IM or cell) using CLI commands. You can perform the export and copy operations on a maximum of 500 events.
To export event information

1 From the event list, select an event. 2 Click the wrench icon in the Tools Menu column, and then click Export. 3 In the Export Events dialog box, select the format in which you want to export the event column information. 4 Select Visible Slots to export information about the visible slots only or All Slots to export information about all the slots. When you export all the slots of an event, the generated BAROC file is not in a format that can be imported directly using the mposter command. To import the BAROC file, make minor edits to the file. For example, in those slots that have a list of strings, change the double-quotes to single quotes. 5 Click Save. 6 Select a location to save the slot information, and click Save. When you export an event, the exported CSV file is encoded in Unicode Transformation Format (UTF-8). You cannot view multi-byte characters in the CSV file encoded in UTF-8 in Microsoft Excel. Use another text editor, such as, Notepad on Windows to view the UTF-8 encoded CSV file.
Note
To copy an event to the clipboard

1 Create a shortcut for Copy Event as explained in To create shortcuts for menu buttons, commands, and actions on page 95. 2 Select one or more events to copy. 3 Click Copy Event.
Sending manual events
Tip You can also copy one or more events using the Ctrl and K keys. Copy is the only operation that you can perform using keyboard keys.
4 In the Copy to clipboard dialog box, click OK. The copied event information is available in BAROC format in the clipboard and can be pasted into a new text or Microsoft Word document.

This feature enables you to send events manually with minimal time and effort, to the BPPM cell or remote cells. The following user groups have permission to send manual events:
User Group Full Access Event Administrator Service Administrator Event Supervisor Event Operator Permission Yes Yes Yes Yes Yes
Launching the send manual events screen

1 From the event list, select an event. 2 Click the wrench icon in the Tools Menu column, and then click Send Manual Event(s). The Send Manual Event(s) dialog box is displayed with the populated values of the selected event. Alternatively, you can launch the Send Manual Events screen from the tool bar by clicking the icon. The slots will not be pre-populated with event values if you choose to launch Send Manual Events from here. By default, the Send Manual Event icon is not available in the tool bar. Click Edit Toolbar to include the icon in the tool bar. You should have one of the permissions mentioned in the table above to view the Send Manual Event(s) icon in the tool bar. For more information on creating shortcuts in the tool bar, see Creating shortcuts for Tools Menu options on page 94.
Note
The field names and their descriptions of the Send Manual Events screen are summarized in the following table.
Field Name Target Cell Description Allows you to select a cell from the list of cells. If you launch Send Manual Events screen from the Tools Menu, the default value will be the selected event's cell name. If you launch Send Manual Events screen from the tool bar, the default value of the target cell will be cell name of the event being viewed. Allows you to enter the number of events to be sent in one go. The default value is 1, and the maximum limit is 500. Allows you to choose time intervals between sending events. The default value is 0.2 seconds, and the maximum limit is 120 seconds. Allows you to set the severity of the event. If you launch Send Manual Event screen from the Tools Menu, the default value will be the severity of the selected event. Otherwise, the default value is CRITICAL. Allows you to set the priority of the event. If you launch Send Manual Event screen from the Tools Menu, the default value will be the priority of the selected event. Otherwise, the default value is 1 Highest. Allows you to enter a message for the event. If you launch Send Manual Event screen from the Tools Menu, the message will be that of the selected event. Otherwise, the field will be blank. Launches the Edit Class or Slots dialog box, which allows you to change the event class and slots associated with it. For more information on editing class and slots, see Editing class and slots for sending manual events on page 105. If you launch Send Manual Events from the Tools Menu, the default value is same as that of the selected event. Otherwise, the default value is Event. To change the class, see Editing class and slots for sending manual events on page 105. Note: You will not be able to select restricted classes such as, ALARM, ABNORMALITY, and all child classes of MC_CELL_CONTROL.
Copies to Send
Wait Between Sends
Severity
Priority
Message
Edit Class or Slot button
Class
Field Name Category
Description If you launch Send Manual Events screen from the Tools Menu, the default value is same as that of the selected event. Otherwise, the default value is blank. If you launch Send Manual Events screen from the Tools Menu, the default value is same as that of the selected event. Otherwise, the default value is blank. If you launch Send Manual Events screen from the Tools Menu, the default value is same as that of the selected event. Otherwise, the default value is blank. If you launch Send Manual Events screen from the Tools Menu, the default value is same as that of the selected event. Otherwise, the default value is blank.
Component Alias
Component ID
Host
3 Click OK to apply changes and go back, or Cancel to go back without saving changes.
Editing class and slots for sending manual events

The Edit Class or Slots dialog box enables you to change the event class or add more slots to the event.
To edit the class and slots

1 In the Send Manuals Event(s) dialog box, click the Edit Class or Slot... button. 2 In the Edit Class or Slots dialog box, you can change the class type by selecting a class from the Class drop-down list.
Note You will not be able to select restricted classes such as, ALARM, ABNORMALITY, PPM_EV, and all child classes of MC_CELL_CONTROL.
3 Use the left and right arrows to select or deselect the slots. 4 Click OK to apply changes and go back, or Cancel to go back without saving changes. The field names and their descriptions of the Edit Class or Slots dialog box are summarized in the following table:
Working with local actions
Field Name Class
Description Displays the list of classes available for the cell of the selected event. The default class displayed will be of the selected event. Classes like ABNORMALITY and ALARM will not be displayed. Displays the list of slots available for the selected class. Hidden slots, ready-only slots, and slots already selected will not be displayed. You can search for a slot from the available slots by typing the first few letters of the slot name, in the text box below Available Slots. Displays the list of slots selected by you. These slots will appear in the Optional Slots section of the Send Manual Event(s) dialog box. Searches/highlights a slot as per the text in the text box and performs a wrap search from the current position. It searches the Available Slots list or the Selected Slots list depending on where the focus is. By default, it searches the Available Slots list.
Available Slots
Selected Slots
Find/Next Slot button

This section provides information on local actions and the BMC ProactiveNet supported out-of-the-box local actions. Local actions are actions that you can execute on the computer you are working on. In earlier BMC ProactiveNet versions, you had to run a command or script to diagnose or solve an issue. Now, these commands are available on the UI in the form of local actions. To access local actions select Local Actions from the Tools menu. Local actions are based on user groups.
Out-of-the-box local actions for non-alarm and nonabnormality events

BMC ProactiveNet supports the following out-of-the-box local actions for non-alarm and non-abnormality events:
Ping Event Origin Traceroute to Event Origin Telnet to Event Origin
SSH to Event Origin VNC to Event Origin RDC to Event Origin Show Local Action Environment
Out-of-the-box local actions for alarm and abnormality events

BMC ProactiveNet supports the same out-of-the-box local actions for non-alarm and non-abnormality events as well as alarm and abnormality events. The only difference is that the slot used to execute local actions for non-alarm and nonabnormality events is mc_origin whereas for alarm and abnormality events, the slot is mc_host. For information on adding or modifying local actions, see Adding or modifying local actions on page 108 .
Guidelines for executing local actions

This section provides guidelines for executing local actions.
Before you begin

When you execute a local action for the first time, all required jar files are taken
from the BMC ProactiveNet Server. Your permission for executing these files may be requested. displayed. For example, if you select the Telnet to EVENT Origin local action, the Execute Local Action screen requires you to enter inputs for the attributes listed in the table below.
If any local action requires your input, a screen for you to enter your input is
Table 16: Execute Local Action screen attributes Attributes Suppress Feedback Batch Mode Description Local actions are executed, but the results are not displayed in an output window. If you select single or multiple events in an Event View, the event data is logged in the home directory\.econsole\webconsole\smss2k642\etc \event_op\celleventdata.xml file. This data helps you customize the local action script execution method.
Attributes Log output to file
Description To save the output and errors, to a file, browse and enter the directory/folder name. The output and error files will be created and saved in the directory/ folder you specified. You can see the content of these two files when you click on the Output and Errors tabs on the Feedback window. If you select Log output to file option, the Feedback window will not be displayed
By default, if no inputs are given, local actions are executed and the output is displayed on the output screen.
The system in which the local action is executed must have Java version 1.6.0.18 or
later installed.
Commands used to execute local actions must be entered in the PATH
environment variable.
To execute local actions

1 From the event list, select an event. 2 Click the blue wrench icon in the Tools Menu column. 3 Click Local Actions and select the out-of-the-box local actions from the list displayed. For a list of out-of-the-box local actions, refer to Working with local actions on page 106. 4 If any local action requires your input, a screen for you to enter your input is displayed. For a list of screen attributes, refer to the table Table 16 on page 107. If no inputs are given, local actions are executed and the output is displayed on the output screen.
Adding or modifying local actions

You can add or modify local actions using the LocalActions.xml file which is a part of the localactions.jar file.
To add or modify local actions

1 Back up of the contents of the pw\tomcat\webapps directory.
2 Copy the \pw\tomcat\webapps\localaction\localactions.jar file to a temporary location in a system that has JDK version 1.6.x installed. The temporary location does not have to be the system where the BMC ProactiveNet Server is installed. 3 Access the temporary directory where you copied the localactions.jar file. 4 Extract localactions.jar into the temporary directory by running the following command: jar -xvf localactions.jar 5 From the extracted directory structure, delete the META-INF directory and its contents by entering the appropriate command for your operating system:
Microsoft Windows: rmdir /S /Q META-IMF Solaris or Linux: rm -rf META-IMF
6 From the temporary directory, delete the orginal localactions.jar file. 7 To add or edit local actions, edit the following files in the temp\localactions\etc \event_op directory:
LocalActions.xml mc_actions.xml
The scripts (.cmd for Windows or without extension for Unix) which contain the code of the new local actions that are going to be added must be located in the same directory as LocalActions.xml and mc_actions.xml files. For example, if you want to add a new local action which will execute a ping command to the value from the %mc_host_address% slot rather than the %mc_host % slot and make this new local action available for all kinds of events for which EventClass is different than ALARM or ABNORMALITY, you would complete the following steps: a Into the LocalActions.xml file, insert the following lines:
<Action location="mc_actions.xml" id="mc_ping_host_address"> <EventClass>!ALARM</EventClass> <EventClass>!ABNORMALITY</EventClass> </Action>
Note
b Into the mc_actions.xml file, insert the following lines:

<ActionDef id="mc_ping_host_address" label="Ping Host Address" type="executable" target="mc_ping_host_address"> Ping the Host Address of the event. </ActionDef>
c Create a new file in same directory named mc_ping_host_address (Solaris or Linux) or mc_ping_host_address.cmd that includes the lines appropriate for your operating system:
Solaris or Linux:
#!/bin/sh if [ then echo ping else echo ping fi `uname` = "HP-UX" ] "ping $mc_host_address -n 5" $mc_host_address -n 5 "ping -c 5 $mc_host_address" -c 5 $mc_host_address
Microsoft Windows:
@ECHO off ECHO ping -n 5 %mc_host_address% ping -n 5 %mc_host_address%
8 In the temporary directory, create another localactions.jar file by executing the following command: jar -cvf localactions.jar *.* 9 Sign the jar file you created by executing the following commands: To sign the jar file, you must have a JDK 1.6 keytool and jarsigner (located in the JSSE SDK bin directory) in your environment path. a keytool -genkey -keystore localaction -alias lca to generate a new key or certificate. b jarsigner -keystore localaction localactions.jar lca to sign the new jar file using the new key or certificate. c jarsigner -verify localactions.jar to verify the signed jar file. 10 Replace the localactions.jar file in the \pw\tomcat\webapps\localaction\ directory with the localactions.jar file that you created. 11 Restart the BMC ProactiveNet Server.
Note
12 Verify if the newly created or updated local action is visible in the event list. 13 Clean up the Java cache in the browsers used to log into the BMC Operations Console. From the command prompt of each computer connecting to the BMC Operations Console, including the BMC ProactiveNet Server itself, execute the javaws -viewer command and delete the jar and jnlp files from both the Applications and Resources tab. Troubleshooting: The following information helps you troubleshoot issues that you might encounter when you use local actions.
Are you unable to see the changes you made to local actions, when you
modified the localactions.jar file?
Ensure that you execute the command javaws -viewer. Delete all occurrences of local actions from the Applications tab and delete the related local action files from the Resources tab.
Did local actions stop working after you changed the http port?
1 Open the LAC.jnlp file located under <BMC_ProactiveNet_Home>\pw \tomcat\webapps\localaction folder. 2 Change value of the property ixshost to include the port name next to the host name. For example, for a host which is on pngp4745 the line in the file will be <property name="ixshost" value="pngp4745" />. Change the line to <property name="ixshost" value="pngp4745:<NEW_PORT>" />. 3 For every jnlp file located under <BMC_ProactiveNet_Home>\pw\tomcat \webapps\localaction folder, change the code to include the port name next to the host name. For example, for a host which is on pngp4745 the line in the file will be <jnlp spec="1.0+" codebase="http://pngp4745/ localaction/">. Change the line to <jnlp spec="1.0+" codebase="http://pngp4745:<NEW_PORT>/localaction/">. 4 Execute the javaws viewer command at the dos prompt and delete all the older jar files. 5 Open the Operations Console and execute local actions.
How do local actions work on https protocol?
1 For local actions to work on https protocol, follow the above steps. 2 Edit the code in all jnlp files and change the value of http to https to change the port number.
How do you view the output logs to provide the file to BMC Customer Support?
To view the output logs, enable the Java Console at http://www.java.com/en/ download/help/javaconsole.xml.
How do you ensure that support for local actions is available in BMC
ProactiveNet and is properly installed?
1 Ensure that the localaction folder is available under <BMC_ProactiveNet_Home>\pw\tomcat\webapps\ and contains 16 jar files and 15 jnlp files. ??List them?? 2 All jnlp files where BMC ProactiveNet Performance Management is installed should have a host name value.
An exception occurred on the Operations Console when you copied local
actions from one BMC ProactiveNet server to another BMC ProactiveNet server. OR How do you run local actions (running on one BMC ProactiveNet server) after you copy them to another BMC ProactiveNet server? 1 If you have copied jnlp files change the host name and port number. 2 Run javaws -viewer and delete the related jar and jnlp local action files from the Applications and Resources tab.
How do you restrict local actions from executing on the basis of a slot (of type
CLASS) of an event?
1 Follow the procedure of adding and modifying local actions under To execute local actions on page 108. 2 To restrict a particular local action from executing, the LocalActions.xml file should contain <EventClass> as a child element of <Action> element. In the below example, local actions will be executed only for alarm and abnormality event class types.
<Action location="mc_actions.xml" id="mc_ping_host"> <EventClass>ALARM</EventClass> <EventClass>ABNORMALITY</EventClass> </Action>
How do you copy jar files that are required to execute local actions?
1 Follow the procedure of adding and modifying local actions under To execute local actions on page 108. 2 Include jar files that are required for the newly added local actions along with other cmd and xml files.
Executing remote actions
Where to go from here

For information about using the local actions, see version 7.3.0.1 of the BMC Impact Solutions Event Management Guide. This guide is available at http://webapps.bmc.com/ support/faces/prodversion.jsp?prodverseqid=173588. You need to be a member of the BMC Support website to access this document.

You can respond to a selected event by executing a remote action. These remote actions are created by an administrator as a response to specific events as required for your environment. You can perform remote actions on events that have been associated with or mapped to devices through a device alias. The device must be configured so that it allows the remote action to be executed on it. When you use a remote action, it is issued from your local console but executed on the computer where the BMC ProactiveNet Cell or the BMC ProactiveNet cell is installed. The number of remote actions that you can execute depends on the event type, core event or intelligent event.
To respond to an event by using a remote action

1 From the event list, select an event. 2 Click the blue wrench icon in the Tools Menu column. 3 Click Remote Actions/Diagnostics and then select a remote action. 4 In the Execute Action dialog box, enter the appropriate values required to run the selected remote action. 5 Click Execute.
To access the results of the remote action, in the event list row, click Action
Result(s)
in the Message column or the Tools Menu.
In the Event Remote Action Results dialog box, you can perform the following operations:
Export the information about the remote action to a file by selecting the
action information and clicking Export.
View the output, errors, and details about the remote action by clicking the
corresponding tab.
Note The remote actions Modify Slot Value, Show Remote Action Environment, and Trigger Remedy Incident for Event do not display an associated Action Result(s) or Related Events option.
Ping Event mc_host_address

This remote action executes a ping command against the target host defined by the mc_host_address slot. An exit code of 0 indicates a successful ping and a working connection between the local system and the target host. The output of a successful ping command, available from the Action Result(s) option, consists of ping statistics:
Pinging 209.97.50.10 with 32 bytes of data: Reply Reply Reply Reply Reply from from from from from 209.97.50.10: 209.97.50.10: 209.97.50.10: 209.97.50.10: 209.97.50.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.97.50.10: Packets: Sent = 5, Received = 5, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 33ms, Maximum = 35ms, Average = 34ms
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 selected event must contain a specified host name.
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. The event information that is sent includes event severity, class, status, handle Id, and the server cell name.
Modify Slot Value

This remote action allows to change the value of a specified slot for the selected event. You can view the change in the Details pane.
Note BMC recommends that you do not change the severity of an intelligent event by executing the Modify Slot Value remote action.
Show Remote Action Environment

This feature is designed to display information about the remote action environment. It does not display the action results in the GUI. Instead, the action results are captured in an output file in the installDirectory \server\tmp\ cellName path, where installDirectory by default equals Program Files\ProactiveNet\pw or /usr/pw. In the following example, the sample output file installDirectory \server\tmp\ cellName\ result.13.out displays remote environment information that includes, but is not limited to, the following data:
This is the Local Action execution environment. 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.log CommonProgramFiles=C:\Program Files\Common Files .... IBRSD_HOME=C:\PROGRA~1\PROACT~1\pw\INTEGR~1\ibrsd JAVA_HOME=C:\Program Files\ProactiveNet\pw\jre MCELL_HOME=C:\PROGRA~1\PROACT~1\pw\server NUMBER_OF_PROCESSORS=2 OS=Windows_NT Path=C:\Perl\site\bin;C:\Perl\bin;C:\WINDOWS\system32; .... RULE_NAME=Show Remote Action Environment REQUESTOR=admin CLASS=EVENT ....
Setup Sending SMTP E-Mails - Windows Only

You can use this remote action in conjunction with the Send Event as SMTP E-mail action. Here, you can define the SMTP server you want to use as the e-mail server for sending events.
Trigger Remedy Incident for Event

This remote action enables to generate BMC Remedy Service Desk incident for the selected event. You specify the destination host to which to send the event. To enable this action, you must be integrated with the BMC Remedy Service Desk application.
BMC Atrium Orchestrator workflows

These workflow actions are designed to be launched on demand or through remote action policies. This topic addresses the on-demand workflow. (Refer to the BMC ProactiveNet Administrator Guide for descriptions of the remote action policies designed to launch these workflows automatically.) Before you can launch these workflows, 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. See the BMC ProactiveNet Administrator Guide for the configuration steps.
Note
Launching a workflow on demand from the Event View

By default, each workflow applies to all event types. Follow these steps to select and launch a workflow from the Event View:
To launch a workflow on demand from the Event View

1 Identify the appropriate event for the workflow, and click the Tools icon to display the menu. 2 Choose Remote Actions => Atrium Orchestrator Actions to display the list of workflows.
Table 17: 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. When launched this workflow uses the corresponding OS command to check for disk space usage on the system where the configuration item resides. After updating related events and incidents with the disk usage metrics, the workflow undertakes a change management process to generate the change form and associate it with the incident information. It then launches the remediation task, which executes volume clean-up commands based on the operating system. Is used when a monitored host system is down. This workflow uses a series of ping and traceroute commands to verify whether the host specified in the event is actually down. It does not attempt to restart the host. It only confirms that the host is unreachable.
Triage Host Down
Note For a complete description of the workflows, see the BMC Software Triage and Remediation Solution Getting Started Guide for BMC ProactiveNet.
3 Select the workflow. An Execute Action dialog box opens containing input parameters that are specific to your workflow selection. Table 18: 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. If you choose false, the Change Request Type parameter is ignored. 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. If an incident already exists, then workflow updates the existing incident information. 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.
Launching an originating BMC ProactiveNet Server
4 Make your selections in the Execute Action dialog box, and click Execute to launch the workflow. An Action Results icon and a Related Events icon are displayed in the event row. An information event is returned indicating the action and the target host. 5 Verify the event notes in the Details pane. The event notes describe the stages of the workflows execution and indicate whether the workflow has been launched successfully.
To check the results of the workflow action

1 Click the Action Results icon to display the Event Remote Action Results dialog box. You can view output, errors, and details associated with the workflow action. The exit code 0 indicates a successful execution. Otherwise, the exit code defaults to -1.
To view related events

1 Click the Related Events icon to open the Event List window. You can view, filter, and perform actions on consequent events that are related to the workflow launch.
Launching an originating BMC ProactiveNet Server

When monitoring events from a central BMC ProactiveNet Server in a multiple BMC ProactiveNet Server deployment environment, you can launch BMC ProactiveNet Servers from which events originated. For details about configuring this kind of deployment, see the Administrator Guide .
To launch an originating BMC ProactiveNet Server

1 From the event list, select an event. 2 Click the blue wrench icon in the Tools Menu column. 3 Choose Launch => Originating BMC ProactiveNet Server. You might need to enter a user name or password, depending on your system authentication policies and procedures. All functionality is available in the Operations Console of the originating BMC ProactiveNet Server (also called a child BMC ProactiveNet Server).
Customizing the display of events
Customizing the display of events

Through the Options screen, you can customize the overall layout of the events to suit your preferences.
To customize the event display

1 In the Operations Console, click the Options link at the top right. 2 Click the Operations tab. 3 Modify the settings described in Table 19 on page 119 under Event Display Preferences as necessary. Table 19: Event Display Preferences for customizing event display
Setting Home page Events Console Groups 3.a Description Select the default view to be displayed whenever you access Event View. The default is the Events. Click Edit and then use the arrow icons to select groups and to set the order of groups. The Show all groups option on the top left enables you to display all groups dynamically, including all future groups.
Events Console Monitor Categories 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 option 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 with the actual numerical count of the events. Set the hierarchical view as the default view. Display events in the 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 Events view Event counts in the Groups => Grid View and All Devices Status-based border color in graphs Status icons in the navigation tree for All Events, All Devices, and Groups => Grid View Show Predictive Events Display a separate symbol for predictions on the Tile View and Canvas View Chapter 2 Working with events 119
Viewing the event list for remote cells
Setting
Description
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. 3 Under Layout Preferences, select the views, described in Table 20 on page 120, that you want to see: Table 20: 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.

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. Using the event list, you now can display events, collectors, and sub-collectors for remote cells (versions 7.1 or later). Before this information is displayed, you need to configure the Operations Console to access the remote cell. For information about
configuring a remote cell for viewing in the Operations Console, see the BMC ProactiveNet Getting Started Guide. Certain BMC ProactiveNet features such as show graphs and probable cause analysis are not available for remote cells. After the Operations Console has been configured, you can view the events, collectors, and sub-collectors for the remote cells by accessing the Other Cells accordion in the navigation tree.
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 Chapter 2 Working with events 121
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: 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.
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:
Example
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 .
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 123. For details about creating a remote cell event folder, see Creating event folders on page 74.
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
Viewing predictive events
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 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
High availability remote cell support in the event list

The event list now supports high-availability for remote cells. When the remote cell is in the passive mode, the event list is displayed in the read-only format. You cannot perform any actions in the passive mode. The remote cell takes about 120 seconds to switch to the active mode. Once the cell is in the active mode, you can perform event actions.
Note It is recommended to not use the Operations Console when cell switching is taking place.

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. 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 21: Columns of event information on the All Abnormalities screen Column Status Description Provides basic information about the abnormalitys 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 Tools Menu 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
Score Occurred
Column Message
Description Displays a short description of the reason for the abnormality. It might also display the following icons: Action Result Detailed Diagnostics Notes Related Events
Host Object
Displays the name of the host on which the abnormality occurred Displays the name of the object monitoring the abnormality
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 ProactiveNets 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 127 Deleting a column from an event list for an abnormality on page 128 Filtering event display for All Abnormalities on page 130 Viewing further information for an abnormality on page 132
Note
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 128
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. 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. 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 51 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.
Tip
Note
Table 22: 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'. 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

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 ProactiveNets 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 23 on page 130 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 23: Filter options on All Abnormalities screen
Filter option Status Time 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. 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 Specify the device name (already set up) to view corresponding records.
Note
Filter option Group Monitor Category Score
Description 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 131.
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
Viewing events and abnormalities by service
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.
Table 24: 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.

The Services => Grid View summarizes events and abnormalities of all service groups, and helps you visualize event and abnormality information for services. To access Services => Grid View, select the Services folder in the Navigation Pane, and click Grid View. You can filter the list of services using the fields described in Table 25 on page 133.
Table 25: 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. Severity 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 119. 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 26 on page 134 summarizes the columns of information available for events on the Services => Grid View screen.
Table 26: Columns of event information on the 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. Status 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 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 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 Additional tools for further information about data collection, change logs, adding change entry, and for setting event thresholds Displays the IT group name and event or abnormality status of the IT group categorized by monitor type Click the icon to view the service details. Description
Related Topics Viewing further information for ServicesGrid View on page 135
Viewing further information for Services => Grid View

The following table summarizes the available options for further information about a specific event on the Services => Grid View screen.
Table 27: Further information options on the Services => Grid View screen Options Event History Details Displays the name, monitor type, source agent, current status, event count, and event summary. Clicking an event or abnormality icon opens the event list screen. From the count of events you can drill down to the event list. For information on tool tips, see Viewing further information for GroupsGrid View on page 143. Displays a graphic representation of the services from the last 24 hours along with service information Displays the service name, service description, IT groups, and relationships
Event Summary Graph Service Information
Limitations
The All Services => Grid View does not support Group to Service and Group to Device relationships. The Service Details page does not include information about external events, abnormalities, and predictive events. If a service has both a dependency and a container relationship with the same subservice or device, then the container relationship takes precedence over the dependency relationship.
Viewing monitor and device information under the Services => Grid View
In the Services => Grid View screen, you can click the service name to drill down to a detailed view of the monitors and devices, both of which comprise the service. In the Monitors tab, you can view the following information described in Table 28 on page 135:
Table 28: Monitor details: Services Column Monitor Name Description String description of the monitor
Column Monitor Type Source Agent Open Closed Collect Data Tools
Description Functional category of monitor Agent to which the monitor belongs The highest severity event 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, you can view the information described in Table 29 on page 136:
Table 29: Device details: 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, such as those from external sources
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, Monitors, Devices, and Services tabs are displayed only if the relationships exist.

The Services => Tree View displays all service groups in a hyperbolic tree for a userdefined time duration, with the option of expanding the tree to display the contents of the service groups and their infrastructure groups. The Services => Tree View supports the following probable cause analysis relationships: Service to Group; Group to Group; Group to Service; Group to Device; and Service to Device. The following information is displayed in the Services => Tree View:
Categorization of the aggregate event status for each service by category (user
transactions, application, database, network, system, or other) based on the severity of the predictive event.
The Predictive icon is displayed next to the category icon. 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. its severity color based on a direct impact check.
If there are any events related to a dependent group, a dashed line is shown with
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.
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, then the Group tree might not be displayed properly in Firefox 2.0. This is due to known issues with the browser. To ensure the proper display of the Group tree correctly on Firefox 1.5, perform the following on Windows 2000 or XP: 1 In the Windows Control Panel, double-click the Java icon. 2 In the Java Control Panel, click Network Settings, and then change the default Use browser settings option to Direct connection.
Note
Related Topics Controlling the display in the Services Tree View on page 138
Controlling the display in the Services => Tree View

This topic summarizes the various actions that you can perform to control the display of information on the Services => Tree View.
Table 30: Controlling the display in the 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. Indicators are aggregated at each level and propagated upwards. Data refresh interval (in seconds) for the Group Tree can be specified using the property 'pronet.applet.grouptree.refreshRate' in installDirectory/ pw/custom/ conf/pronet.conf. Various icons indicate the severity of system objects (application, transactions, database, network, system, and other), the impact on SLOs, the impact on services, and the abnormality score (it indicates how close the event abnormality is to failure) For a full list of icons, you can display a legend by clicking Show Legend.
Viewing events by group
Objective Change the time list Filter the displayed services
Instructions The default time is None. Click the list to choose an appropriate time by which to filter the display. 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. For example, a user might be restricted to view only a subset of services that exist in the system.
Propagate dependency events
By default, dependency events are not propagated in the service tree. To enable dependency event propagation, change the value of the pronet.applet.tree.propagateDependencyEventsBasedOnDirectImpact property in the pronet.conf from false to true:
pronet.applet.tree.propagateDependencyEventsBasedOnDirectImpact= true
Limitation
If cyclic service-to-service relationships are created, then tree does not behave as expected. For example, if a relationship is created for Service A to Service B and again Service B to Service A, then the tree does not behave as expected. The service tree does not display duplicate services at the same level. Instead, it displays the first service that is encounters and ignores the other service with the same name.

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. Groups contain selected set of devices or applications, determined by your operating needs. For example, special monitoring of devices and applications
might be setup by building, department, or individual. BMC ProactiveNet administrator selects the groups available to a user in the corresponding User Profile. The All Groups table displays only top level groups that is, list of groups which are not part of any other group. The counts displayed in the Grid View include intelligent events and external events that are associated with a device (deviceassociated events). Hierarchical view is the default view only if there are groups in the system that can be displayed in hierarchy. 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. 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 46). Table 43 on page 216 summarizes the columns of information available for events on the All Groups => Grid View screen. Related Topics Default groups on page 142 Filtering event display for All Groups on page 142 Viewing further information for GroupsGrid View on page 143
Table 31: 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
Column Numbers of events by severity Critical Major Minor Predictive Warning Information Closed
Description The number of events for each severity The color indicates severity of the events.
The severities are displayed as an icon. Events by type Step 1 on page 151 User Transactions Application Network System Database Other Devices Tools Devices contain monitors that are under a group. These devices are displayed. Additional tools for further information about the event, including options to view graphs, set thresholds, and view diagnostics under Device at a Glance. Events of each type. Both the icon and the color represent event severity. When you place your mouse over this column, the numbers of events of each severity is displayed.
a Events are displayed with either number of events or severity icons, depending on user configuration
(see Viewing all abnormalities on page 85).
Default groups
The following groups are available in BMC ProactiveNet, by default. The default event rule, DefaultRule-BMC_ProactiveNet, is created for this default group, and the action type is email notification.
Table 32: Default groups available in BMC ProactiveNet Group name BMC_ProactiveNet BMC_ProactiveNetServer BMC_ProactiveNetAgent Description BMC_ProactiveNet is a parent group. This contains two child groups namely BMC_ProactiveNetServer and BMC_ProactiveNetAgent. System-related default monitors like System, File System and Process monitors are grouped under BMC_ProactiveNetServer. Default Agent status monitor is grouped under BMC_ProactiveNetAgent.
Filtering event display for All Groups

All Groups => Grid View offers filters to query and view specific records. Table 33 on page 142 describes the available filter options.
Table 33: Filter options for All Groups => Grid View Filter option Status Severity Description Choose the status of the events you want to see. The menu lets you to choose either open, acknowledged, assigned, closed, or no filter. Choose the severity level of the events you want to see. The menu lets you to choose critical, major, minor, warning, information, major and above, predictive critical, predictive major, predictive minor, or no filter. Choose the events in the specified time. Time Range option allows the Start and End Time selections to reflect either a particular day and hour or a particular duration of time, such as the last four hours. You can change the time and date when you want to view resource data for the previous day, week, or hour to compare measurements. Use this option to show the events in the specified time range. The menu lets you choose from 1 hour up to 3 months. Specify the group name to which the events that you want to view are associated
Absolute Time Range
Relative Time Group Name
Viewing further information for Groups => Grid View

The following table summarizes the available options for further information about a specific event on the Groups => Grid View screen.
Table 34: Further information options on the Groups => Grid View screen Option Drilling down to monitors associated with a group Details Click the Group Name link to navigate to the selectedGroupName screen. This screen gives the monitor details for the group. Use the Tools list to get additional information. For information on tool tips, see Limitation on page 143. The Groups => Grid View table might contain subgroup information. Click Sub Groups to view subgroup information. If you select a group, 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). View devices associated with a group Click Devices to view all devices associated with the group. Further drill-down to individual monitors is available from the Show Device screen. The Show Device screen is similar to All Devices. However, it only lists devices belonging to the selected group. In case of groups made up of subgroups, the Device drill-down displays all devices belonging to the subgroups. However, devices that are part of more than one subgroup are listed only once. Click Edit Thresholds. Note that if a user is associated to a user group with permission to manage thresholds, then the Thresholds option is available in the Tools menu for accessible monitor groups. However, the threshold suboptions are only available if the monitor group has at least one monitor accessible to the user in write mode. See also Setting event thresholds on page 246. 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. Note: The Group Details page does not display external events, abnormalities, or predictive events. Links are available to a drill-down Event List.
Drilling down to subgroups
Limitation
The Group Details page does not include information about info, warning, abnormality, and predictive events.
Tool Tip description for various adapters at instance hierarchy level. The instance hierarchy level is displayed only if there is hierarchy.
Tool Tip - 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.
Tool Tip - Native Adapters: Do a mouse-over at the instance hierarchy level on
monitor name the tool tip displays device name, instance name, and host server. monitor name the tool tip displays device name, project, location, and monitor name. monitor name the tool tip displays the device, and host name.
Tool Tip - TMART Adapters: Do a mouse-over at the instance hierarchy level on
Tool Tip - VMware Adapters: Do a mouse-over at the instance hierarchy level on
Viewing monitor and device information under the Groups => Grid View
In the Groups => Grid View screen, you can click the group name to drill down to a detailed view of the monitors and devices, both of which comprise the group. In the Monitors tab, you can view the following information described in Table 35 on page 144:
Table 35: Monitor details: 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. Number of closed events Check box that indicates whether data collection for the monitor is turned on
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 29 on page 136:
Table 36: Device details: 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
Viewing events for groups in a hierarchical tree
The functionality is similar to that described for the Services => Grid View screen under Viewing monitor and device information under the ServicesGrid View on page 135.

The Group Tree provides a real-time, interactive visualization of the event status for a user-defined time duration. The entire group hierarchy and devices are all visible on a hyperbolic pane mapped to a circular display region. In Group Tree view, all accessible Groups and Devices are displayed. When you expand the Tree view, all monitors accessible to the user are displayed. On the Device level, the Tools menu displays available options according to the permissions associated to the CI.
Group Tree is authorization aware; the Groups in the Tree view, and any actions available from the Tools menu of Group, Device and Monitor nodes reflect your access privileges and permissions. Information is displayed for Monitors that are not part of the explicitly mentioned monitor types which are listed under the 'Other' category.
Categorization of the aggregate event status for each service by category (user
Note
transactions, application, database, network, system, or other) based on the severity of the predictive event.
The Predictive icon is displayed next to the category icon. 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.
Aggregate abnormality score for each service (as a purple thermometer bar)
Note If BMC_ProactiveNetServer is within the firewall and the Operations Console is outside the firewall, then the Group tree might not be displayed properly in Firefox 1.5. This is due to known issues with the browser. To ensure the proper display of the Group tree correctly on Firefox 1.5, perform the following on Windows 2000 or XP:
1 In the Windows Control Panel, double-click the Java icon. 2 In the Java Control Panel, click Network Settings, and then change the default Use browser settings option to Direct connection.
On some Internet Explorer versions, when you right-click on a parameter from the hyperbolic pane, the options dialog box may appear behind the operations console. This is a known limitation. Related Topics Controlling the display in the Tree View on page 147
Note
Group to group dependent relationships are not represented in hierarchical fashion. Container relationships between groups are supported and depicted by connecting bold lines. Dependent relationships are indicated by dotted lines. Only IT dependent relationships are permitted between services and groups.
Note
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.
Table 37: Controlling the display on the Tree View Objective Instructions Indicators are aggregated at each level and propagated upwards. Change the data refresh interval Data refresh interval (in seconds) for the Tree View can be specified using the property 'pronet.applet.grouptree.refreshRate' in installDirectory/ pw/custom/conf/pronet.conf
Change the focus point on the tree Drag any point on the tree
Objective Display or hide the legend
Instructions Various icons indicate the severity of system objects (application, transactions, database, network, system, and other), the impact on SLOs, the impact on services, and the abnormality score (indicates how close the event is to failure) For a full list of icons, you can display a legend by clicking Show Legend.
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. For example, a user may be restricted to view only a subset of groups that exist in the system.
Filter the displayed devices
All Events All Abnormalities Device at a Glance Manage data Collection Add Change Entry Show Change Log Show Parent Groups Diagnostics
Viewing events by device
Objective Filter the displayed monitors
Instructions All Events All Abnormalities Show Graph Flash Check Manage data Collection Thresholds Show Parent Groups Add Change Entry Reset Baseline Diagnostics

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. The Event Profile consists of Event Thresholds (to generate an event) and Event Rules (to send event notifications). The BMC ProactiveNet administrator sets event profiles. Default settings are also available in BMC ProactiveNet for automatic configuration. For more information on event profiles, see, the BMC ProactiveNet Administrator Guide. The All Devices screen, the out-of-box default screen displayed on Event View, displays information about the events that were issued for all devices that BMC ProactiveNet is monitoring, providing a quick view of the overall health of the system.
The display on this screen in Grid View differs, depending on the configuration of displaywhether with counts or with severity icons (see Customizing the display of the event list on page 46). Table 38 on page 150 summarizes the available options on the All Devices screen.
Note
The counts displayed in the Grid View include intelligent events and external events that are associated with a device (device-associated events). From the All Devices screen under Event View, you can view the device hierarchy by clicking Show Hierarchy. You can expand the physical host node to see the virtual computers running in the system. Hierarchical view is the default view only if there are devices in the system that can be displayed in hierarchy. 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. You can switch between hierarchical or flat view. If no virtual solution is configured then flat view is the default view.
Table 38: Columns of event information on the All Devices screen Column Device Name Description Information about the associated device. 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. Device is marked for deletion (displayed for devices that are marked for deletion). The icon displays a cross mark next to the Device Name. Multiple IP address (displayed only for CMDB devices that have multiple IP addresses) Agent Displays the status of the agent attached to the device, either connected or disconnected. A green Plugged icon indicates that the agent is connected, and a red Unplugged icon indicates the agent is disconnected. 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, server or web server).
Column
Description
Numbers of events by severity The number of events for each severity a The color indicates the severity of the events. Critical Major Minor Predictive Warning Information Abnormal Closed The severities are displayed as an icon. Events by type Step 1 on page 151 User Transactions Application Network System Database Other Tools Additional tools for further information about the event, including options to view graphs, set thresholds, and view diagnostics under Device at a Glance. Events of each type. Both icon and color represent event severity. When you place your mouse over this column, the numbers of events of each severity is displayed.
a Events are displayed with either number of events or severity icons, depending on user configuration
(see Viewing all abnormalities on page 85).
Filtering event display for All Devices

You can filter the listed events using the criteria listed in the following table.
Table 39: Filter options for All Devices

Filter option Status Severity Description Choose the status of the events you want to see. The menu lets you to choose either open, acknowledged, assigned, closed or no filter. Choose the severity level of the events you want to see. The menu lets you to choose critical, major and above, major, minor, warning, information, predictive critical, predictive major, predictive minor, or no filter. Choose the events in the specified time. Time Range option allows the Start and End Time selections to reflect either a particular day and hour or a particular duration of time, such as the last four hours. You can change the time and date when you want to view resource data for the previous day, week, or hour to compare measurements. Use this option to show the events in the specified time range. The menu lets you choose from 1 hour up to 3 months. You can include or exclude groups to view the devices that are added to the group. Select the No Filter option to consider all devices accessible to the user. Specify the name of a device to limit the display to events associated with a specific device. Parent and child devices are displayed to make the hierarchy complete. If the filter criteria is not matching then the parent is displayed in italics.
Absolute Time Range
Relative Time Groups Device Name
To include or exclude a group

1 Click the link corresponding to the group to open the Group Filter window. Available groups are displayed either as Hierarchy or as Flat. Use hierarchy on or off to switch over to the corresponding view type. 2 Expand or collapse the groups. Select the groups. Use the arrows to move the selected groups. 3 Select No Filter, Include Selected Groups, or Exclude Selected Groups.
No Filter: To consider all the groups. You can view a list of accessible devices. Include Selected Groups: To include the selected groups. If you have access to
a monitor group that contains, for example, only monitors, then you can view the devices to which these monitors are associated. However, depending on your permissions for the actions that you can perform on the device, a restricted set of operations is displayed.
Exclude Selected Groups: To exclude the selected groups. For example,
consider a scenario in which you have access to two monitor groups and both these groups contain the same monitors. If the monitor group contains a device
that you can access and the Exclude Selected Groups filter is applied, the device is not displayed in the device grid view. Assume the Exclude Selected Groups filter is applied only to the first monitor group. Even though the same monitor is present in the excluded group as well as the included group (the second monitor group), the precedence of the Exclude Selected Groups filter is considered higher and therefore, the display of the device in the device grid view is blocked. Selected groups are displayed in the All Events screen. Included groups are displayed with the (+) sign and excluded groups are displayed with the (-) sign. 4 Click Apply.
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 40: 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. Show Monitors screen gives the monitor details for the device. Use the Tools list to get additional information. For details, see the BMC ProactiveNet User Guide. Drilling down to an event list for a The middle columns indicate triggered events (if any) on the Device. device Click the Severity icon (or the Count) link to view open events. From the Event List screen, you can click Status, Analyze, and Tools links to get additional information. If Status selected is Closed, then Closed Time will be displayed for all closed events. If Status selected is No Filter, all closed events will have Open Time and Closed Time and open events will have only Open Time. No time value is displayed in the Closed Time Column if the event is in open condition. View event history and graphs for a device Analyze probable cause This opens the Event History screen and Graph Display, which you can modify as required. 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. From this screen, you can show graphs and create rules.
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. When generated, the Device At a Glance page shows a stacked line graph for all monitors on the device. Choose Tools => Device at a Glance. This option can also be accessed from the Graph Display page. Choose Tools => Show Parent Groups. Choose Tools => View Service Impact Graph.
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 open event status, and number of closed events for each service. When you access All Monitors, BMC ProactiveNet filters and re-calibrates the displayed events based on the monitored services. Table 41 on page 154 summarizes the columns of information available for events on the All Monitors screen.
Table 41: Columns of event information on the All Monitors screen Column Monitor Category Current Status Description Application, network, system, database, user transactions, other Displays the severity of the open events. The severity icon can be critical, major or minor. Open events with highest severity are displayed. Click the severity icon to drill-down to Event List screen. If there are no open events green icon is displayed. The number of events for each severity The color indicates the severity of the events.
Numbers of events by severity Critical Major Minor Predictive Closed The severities are displayed as an icon. 154 BMC ProactiveNet User Guide
Acknowledging events
Column Monitor Types
Description Click the link to view all monitors in that category. From here, click the Monitors link to view the list of monitors by type. Monitor names are displayed hierarchically based on the relationship between the parent and child monitor instances for the selected monitor type. This column is collapsed by default. You can choose to either expand or collapse all the monitor names. You cannot drill-down from the instances that do not have stats attributes. 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.
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.
Table 42: 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. For information on tool tips, see Viewing further information for GroupsGrid View on page 143. Click the link to view all monitors in that category. From here, click the Monitors link to view the list of monitors by type. An ellipsis (three-dot) icon displayed along with the monitor name indicates that the monitor is an Aggregate Monitor. 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. Choose Tools => View Service Impact Graph. This options is available only if the monitor has a valid CI.
BMC ProactiveNet provides the option of acknowledging events and add messages to those events. This feature is helpful when you want to know who has addressed the event or who is responsible for the event. Acknowledging an event triggers the associated event rules. If acknowledging is cleared, the associated event rules are not triggered.
To limit the display of events to events that have not yet been acknowledged, see Viewing all abnormalities on page 126. Related Topics To acknowledge a specific event on page 156 To set the acknowledgement message on page 156 To view operations history on page 157
To acknowledge a specific event

Note
To acknowledge events, you must be assigned Allow Acknowledge Event privileges by the BMC ProactiveNet administrator. 1 From the All Events tab go to Tools Menu => Operations => Acknowledge Event. 2 In the Acknowledge Event Confirmation box, add a note and click Yes if you are sure you want to acknowledge the event. BMC ProactiveNet updates the event status screen advising others on the event acknowledgment. Summary views set to show counts do not display Acknowledged events. Acknowledged events are available only to the person acknowledging the event. Acknowledgment is applied only to event instances of the same severity (minor, major, or critical) as at the time of acknowledgement, and is not valid when the severity status of the event changes.
To set the acknowledgement message

1 On the All Events tab, choose Tools => Intelligent Event History . 2 On the Intelligent Event Details page, select Tools => Acknowledge Event. 3 If you want to assign the event to yourself, select the Acknowledge check box. 4 Enter the acknowledgement message text (up to 128 characters) in the Message box. 5 Click Submit. Your message is displayed together with the event on the Intelligent Event History screen.
Closing events
To view operations history

1 On the All Events tab, choose Tools => Intelligent Event History . 2 On the Intelligent Event Details page, select Tools => Operation History. The Operation History for selected Event window contains all operations or messages associated with an event, along with timestamp details.
Closing events
The Close Event feature allows you to close events manually. 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. When you close an event it can be viewed in the system for a week, but after a week it is removed from the system. Related Topics To close an event or a group of object events on page 157 To close multiple events on page 158
To close an event or a group of object events

1 From the appropriate display of events, choose Tools => Close Event on the row of the relevant object:
Service on the Services => Grid View tab. When closing events from the
service object, the system considers only container events. Dependency events are not closed. from the tool tip from the tool tip
Devices => Grid View: do a mouse over on Tools and select Close Event (s)
Groups => Grid View: do a mouse over on Tools and select Close Event (s)
Specific event on the All Events tab, the Event Details screen, or the Probable
cause analysis screen
2 Click OK on the confirmation message.
Managing configuration changes
To close multiple events

1 On the All Events tab, select the relevant events through the appropriate check box in the Select column. 2 Click Close Event above the list of events. 3 Click OK on the confirmation message.
Managing configuration changes

Add Configuration Change screen stores and tracks configuration data, and provides information on the possible impact to your Web environment. This option is available on all event screens. Add Configuration Change can also be accessed through Options => Administration tab. Related Topics To add a configuration change entry on page 158 To view and manage all configuration changes that have been submitted on page 159
Note
To add a configuration change entry

1 From the appropriate display of events, choose Tools => Add Configuration Change on the row of the relevant object:
Event on the All Events tab Abnormality on the Abnormalities tab (All View) Service on the Services => Graph View tab Group on the Groups => Grid View tab Device on the Devices => Grid View tab Monitor on the Show Monitors screen accessed from the Monitors tab CI on the Services => Tile View or Services => Graph View.
Managing data collection
2 Enter the specifications of the configuration change event: user, date and time, name of contact person, summary, and long description. 3 Click Apply.
To view and manage all configuration changes that have been submitted
From the appropriate display of events, choose Tools => Show Change Log on the row of the relevant object: 1 device on the Devices => Grid View 2 group on the Groups => Grid View 3 service on the Services => Tile View or Services => Graph View. On the Configuration Change screen, you can filter the change entries by date and time, device, and group or service. To view the configuration change event, select Show External Events option from the Custom Graphs while generating the graph. In the graph, 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. The time when the event was generated. The description given while generating the event.
Change entry events (Configuration Change Events) which were generated during the previous releases does not get migrated to the current version.
Note

The Manage Data Collection function gives you the flexibility to pause and resume data collection by a device, group, monitor, or service. This feature enables you to stop data collection by entities immediately during unforeseen situations, such as an urgent server maintenance task that must be carried out. Restricted users with permission to manage data collection have access only at a monitor level, with a prerequisite that the user must have write access on the monitor. If the user does not have write access, then data collection is not available to
the user even if the relevant permission has been granted. Users with Allow Collect Data Management privileges can use the Manage Data Collection feature to start or stop data collection for a monitor, device, or groups of monitors.
Note
Schedules set using the Schedule Device Downtime feature of the Administration
Console cannot be modified using the Operations Console.
The following configurable properties that control the Manage Data Collection
function are listed in the pronet.conf file (located in installDirectory/ pw/pronto/ conf):
pronet.server.pausepollperiod denotes the time interval that the scheduler
looks for pause or resume requests. The minimum and default value is 60 seconds. will be displayed in the Operations Console.
pronet.pause.minutes.defaultVal indicates the default pause duration that
The Manage Data Collection option is displayed only to users who have
administrator privileges and restricted access to groups.
Distinction between new and upgrade users

Just as in the Scheduled Down Time feature, new and upgrade users have different options available to them. New users can pause or resume Data Collection only from the Manage Data Collection dialog. In the Manage Data Collection dialog box, 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, monitor, or group of monitors will be temporarily inactive. You can choose to stop event generation, event notification, or data collection by the entity during this latent phase. The Pause period that you define and assign is a one-time setting and not recurring. The current time is the start time of the Pause period. The Pause feature can be configured with restrictions when maximum values are defined in the pronet.conf file. If configured without restrictions, you can pause an entity for any duration without any predefined values, 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). A pause period that you define from the Operations Console cannot overlap an upcoming downtime schedule set from the Administration Console. BMC ProactiveNet scheduler processes pause schedules prior to schedules defined from the Administration Console.
To pause data collection

1 From the appropriate display of events, choose Tools => Manage Data Collection on the row of the relevant object:
device on the Devices => Grid View tab group on the Groups => Grid View tab service on the Services => Grid View tab abnormality on the Abnormalities tab (All View) event on the All Events tab monitor on the Show Monitors screen accessed from the Monitors tab
2 On the Manage Data Collection screen, specify the duration for which the object must be paused, and choose when to start pausing (either immediately or after a delay that you specify). 3 If you want to pause data collection, choose Data Collection. (This is the only selection available to new users.) For upgrade users. Event or Event Generation, Event Rule Action or Notification, and Calculate BaseLine are available for selection (that is, for setting to On or Off) only if you select to keep data collection on.
Note
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 individual instances and manage the activity of specific instances.
If you want to stop only certain instances of the object, click the displayed link
to see the status of the instances and manage the activity of specific instances.
5 Click Apply.
Resuming data collection

The Resume feature enables you to activate an entity currently in the Pause state, without having to wait for the Pause period to complete. You can only resume entities that are currently paused. You cannot resume a device or group whose downtime schedule has been defined from the Administration Console.
To resume data collection

1 From the appropriate display of events, choose Tools => Manage Data Collection on the row of the relevant object:
device on the Devices => Grid View tab group on the Groups => Grid View tab service on the Services => Grid View tab abnormality on the 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, select the schedules to be resumed. 3 Click Resume.
Diagnostics
BMC ProactiveNet offers both pre-configured and user-defined diagnostic tools to help monitor your system. See Diagnostics Wizard section of the BMC ProactiveNet Administration Guide for detailed instructions on using these commands.
All event-related data is archived at the end of seven days. The Diagnostics option is not available on the Event Details page for any event that is open for more than seven days. The Get URL option is available for Web or Web Transaction monitors. This option performs a full download of the Web page (for Web monitors) or Web pages (for Web Transaction monitors), and shows the breakdown of all objects in those pages and their download times. Selecting this option displays results in a separate browser window. Get URL is also an integral part of Diagnostics tool. The FlashCheck option shows the current data of the the device.
Examining current data (FlashCheck)

With FlashCheck, you can quickly examine current data values from a selected monitor. FlashCheck triggers an instant poll from the agent running on the selected monitor, and displays the results in a separate browser window. You typically use FlashCheck to determine whether a previously detected condition still exists. By triggering a poll, you can also use FlashCheck to close resolved issues for an event before the next scheduled poll, and to update data for newly added or edited monitors.
To examine the current data values of a monitor

1 In the Operations Console, select an event in the Event View or Grid View. 2 Run FlashCheck according to the current view:
(Event View) Choose Tools => Diagnostics => FlashCheck. (Grid View) Choose Tools => FlashCheck.
A separate browser window opens with the current parameter values for the selected monitor. During FlashCheck, monitors do not retry polling.
About the Canvas view
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. FlashCheck triggers the Run Now feature in BMC TM ART Central, which
executes the monitor immediately. Results might take several minutes to appear in the FlashCheck window. If FlashCheck exceeds the timeout period before data is displayed, wait a few moments and run FlashCheck again. FlashCheck does not influence the statistics collected in BMC TM ART Central. updated with the next scheduled poll.
FlashCheck does not update BMC TM ART data in BMC ProactiveNet. Data is

The Canvas view in the Operations Console lets you create a graphical representation of the components that are being monitored in your environment. The components are represented by objects that can be placed on a background image. The objects can be graphics, such as images or connectors, or metrics information, represented in a tile. You can create and display a Canvas view for any event collector, group, device, 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.
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.
Edit mode: Use this mode to create the view by selecting a background, adding
objects, and selecting the display options for those objects.
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. 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, 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, impact priority, and impact cost
for the selected object
Related CIs: Displays information on status causes, possible problems, providers,
and consumers of the selected object
Schedule: displays the times when the selected component is in service Advanced: displays information on identification, creation and modification time,
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, shows information about the
To expand a card to view more information, click the More Info button Related topics: Setting up and using the Canvas view on page 166 Viewing the Details notebook on page 215
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. You can create a Canvas view for event collectors, groups, devices, and services. You can create a Canvas view for static and event folders but not dynamic folders. When you access the Canvas view initially, the page is in View mode and no objects are displayed. To create objects in the Canvas view, you must first change to Edit mode, set up the objects that you want displayed in the view, and then after you have set up the objects, return to View mode to monitor the object status.
To switch to Edit mode

1 Click the Preferences button in the toolbar.
The view is changed to Edit mode, and the Canvas View Preferences dialog box is displayed in the Canvas view pane. To return to View mode, close the Canvas View Preferences dialog box.

For more information about setting up the Canvas view, see Using Edit mode to set up the Canvas view on page 166 . For more information about using the Canvas view to monitor objects, see Using View mode to monitor objects in the Canvas view on page 172
Using Edit mode to set up the Canvas view

When the Canvas view is in Edit mode, you use the options in the Canvas View Preferences dialog box to determine how you want the Canvas view to look, and to choose which objects that you want to display and how you want to display them.
Before you begin

In the navigation tree, select the object for which you want to create a canvas view and then click the Canvas View button in the toolbar.
To create the Canvas View background

1 Click the Preferences button to change the Canvas view to Edit mode.
2 In the Background pane in the Canvas View Preferences dialog box, perform one or both of the following actions:
Select the Color option and then click on the colored squares to display the
color palette. Use the palette to select the colors that you want to display. that you want to display.
Select the Image option and then use the list to select the background image
You can select one of the default images, or you can add your own images to the BMC ProactiveNet Server and then select those images in the Chart View Properties Change dialog box to display in the Chart View background. For information about how to add background images, see the BMC ProactiveNet Administrator Guide.
To add objects to the Canvas view

1 In the Canvas View Preferences dialog box, click Monitored Objects. 2 Drag and drop an object from the list to where you want that object displayed on the background image. To sort objects in the Monitored Objects pane, click Name in the title bar. The objects are sorted in alphabetical order. To reverse the sort order, click the number 1 that appears in the title bar after the objects are sorted the first time. After you drag and drop the object onto the Canvas view background, a tile is created for that object.
To change object attributes in the Canvas view

1 Select an object in the Canvas view. 2 In the Canvas View Preferences dialog box, click Properties of Selected Object. 3 Select one of the following object types.
Editing options are displayed, depending on the object type that you select. Connector: shows a relationship between two objects in the Canvas view.
The color of the connector shows the current status of that object, for example, if the object is in OK status, then the color of the connector is green. Continue with List item. on page 168. resize the tile and change the attributes in the tile display. Continue with List item. on page 168.
Canvas: displays a tile view of the object that is being monitored. You can
Icon with severity background: displays an image of the object type on a
colored background that represents the objects current severity. Continue with List item. on page 169.
4 If you selected Connector as the object type, 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. 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, click the lower right corner of the
boundary box and drag it until the connector is the size that you want. To rotate the connector, click the circle to the right of the boundary box and move it until the connector is pointing in the direction that you want. Continue with List item. on page 170.
5 If you selected Canvas as the object type, edit the tile attributes as follows:
Tile order: Use the Bring to Front and Send to Back buttons to layer the order
of tiles in the Canvas view. For example, selecting a tile and clicking Bring to Front displays the selected tile in the front of the other tiles in the Canvas view. tiles onto the view. At the smallest size, the tile is shown as an icon of the objects current status. To see the tile details, place the mouse pointer over the tile. the tile. For example, if the object that you are monitoring is a server, a server icon is displayed before the object name. currently not being addressed.
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. on page 168. 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.
The attributes that you can select to display depend on the object type that is displayed in the tile. For example, devices have a broader list of attributes to select than services. If you select a KPI attribute, the Attribute Selection for Information Capsule dialog box is displayed. Perform the following additional steps: a Click the item at the end of the row until a list of attributes is displayed. b Select the attribute that you want to display in the tile, and click Apply Selection. Continue with List item. on page 170. If you select the Custom Text attribute, the Custom Text Value dialog box is displayed. Perform the following additional steps: a Enter the custom text that you want to display in the tile. For more information on the Custom Text attribute, see Tile attributes on page 178. b Click OK. 7 If you selected Icon with severity background as the object style, 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 Box Line Bring the image to the front of the view or send it to the back of the view.
To change the size of the image, click the lower right corner of the boundary box and drag it until the image is the size that you want. Continue with List item. on page 170. 8 Repeat List item. on page 167 through List item. on page 169 for each object that you add to the Canvas view. 9 Close the Canvas View Preferences dialog box to save your changes. The Canvas view is returned to View mode. 10 Click Refresh to display data for the new metrics.
To add labels and additional icons to the Canvas view

1 To add a label to the object that you are monitoring, in the Background pane in the Canvas View Preferences dialog box, drag and drop the Label icon onto the Canvas view and position it near the object that you want to label. 2 Click Properties of Selected Object. 3 In the Properties of Selected Object pane, 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, size, and style. 4 Click Apply. 5 To add an additional icon near a tile object that you are monitoring, in the Background pane, 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.
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 Box Line Bring the image to the front of the view or send it to the back of the view.
To change the size of the image, click the lower right corner of the boundary box and drag it until the image is the size that you want. 7 Close the Canvas View Preferences dialog box to save your changes. The Canvas view is returned to View mode.
To remove an object from the Canvas view

1 If you are in View mode, click the Preferences button to change to Edit mode. 2 Click an object and drag the object to the Thrash Can icon at the bottom of the Canvas view pane. You can also remove metrics from tile objects by clicking on the metric and dragging it to the trash can icon. 3 Close the Canvas View Preferences dialog box to save your changes.
To adjust the height and width of a tile

1 If you are in View mode, click the Preferences button to change to Edit mode. 2 Click the tile and then drag the lower right corner to adjust the height and width. 3 Close the Canvas View Preferences dialog box to save your changes.
Using View mode to monitor objects in the Canvas view

When the Canvas view is in View mode, you can monitor the event status of the objects and perform actions on those objects.
To turn on predict mode

1 Click Predict on the toolbar.
A graph, divided into increments, 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. The prediction severity is displayed only if that severity is higher than the objects current severity. For example, if the objects severity is Minor, the prediction severity is displayed if it is predicted to change to Major. If the objects severity is Critical, the prediction severity is not displayed if it is predicted to change to Minor. You must select Show Predictive Events in the Operations tab of the Options window to display the Predict button on the Tile view. For details about setting this option, see Customizing the display of events on page 119.
Note
To use the Tools menu to perform actions on objects

When you place the mouse pointer over a tile, you can access a menu of commands that let you perform actions on the selected object. 1 Place the mouse over the tile of the object on which you want to perform an action. The tile is highlighted and the Menu icon is displayed in the corner of the tile. 2 Click the Menu icon and select one of the following commands, depending on the object type that you are viewing.
Object type Devices Command Add Configuration Changes Description Enables you to store and track configuration data. For more information, see Managing configuration changes on page 158. Enables you to view and manage all configuration changes that have been submitted for the selected object. For more information, see Managing configuration changes on page 158. Enables you to view the events associated with the selected object. You can view the following types of events: All (Direct and Providers) Changes (Direct) Direct Impacting (Direct & Providers) Predictions (Direct and Providers) Go To Graph View Enables you to display a Graph view for the selected object. For more information, see About the Graph view on page 189.
Show Configuration Changes
View Events
Object type
Command Device at a Glance
Description Displays the Device At a Glance page, which shows a stacked line graph for all monitors associated with the selected CI and other related attributes. This option can also be accessed from the Graph Display.
Manage Data Collection
Enables you to stop data collection by entities immediately during unforeseen situations, such as an urgent server maintenance task that must be carried out. For more information, see Managing data collection on page 159. Enables you to view details about the monitors associated with the selected object. Displays the parent groups and subgroups of the selected object, if available. Provides the following subcommands: Diagnostics => System Configuration Diagnostics =>Top IP Traffic Diagnostics =>Top Processes CPU Diagnostics => Top Processes Memory
Show Monitors
Show Parent Groups
Remote Actions/Diagnostics
Groups
Monitors+devices
Enables you to display the subgroups, monitors, and devices associated with the selected group. Enables you to display a Tree view for the selected object. For more information, see Viewing events for groups in a hierarchical tree on page 146.
Tree View
Object type
Command Group Details
Description Enables you 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. Enables you to set and clear manual status and maintenance modes. Enables you to view details about the monitors associated with the selected object. Enables you to view the events associated with the selected object. You can view the following types of events: All (Direct and Providers) Changes (Direct) Direct Impacting (Direct & Providers) Predictions (Direct and Providers)
Cloud Topology
Operations
Show Monitors
View Events
Go To Graph View
Enables you to display a Graph view for the selected CI. For more information, see About the Graph view on page 189. Enables you to set and clear manual status and maintenance modes. Enables you to view details about the monitors associated with the selected object.
Services
Operations
Show Monitors
Object type
Command View Events
Description Enables you to view the events associated with the selected object. You can view the following types of events: All (Direct and Providers) Changes (Direct) Direct Impacting (Direct & Providers) Predictions (Direct and Providers)
Go To Graph View
Enables you to display a Graph view for the selected object. For more information, see About the Graph view on page 189.
To filter tiles
1 Click the down arrow next to the filter option in the toolbar. 2 Select to filter the tiles based on event severity type: Critical, Major, Minor, Warning, Informational, and OK. The tiles that have the severity that you select and higher are displayed in the Canvas view.
Example If you select Warning, all tiles with a status of Warning, Major, Minor, and Critical are displayed and all tiles with a status of Informational and OK are not displayed.
To display child objects

To drill down on a tile object in the Canvas view, you must create Canvas views for all objects that have dependency relationships with that tile object. 1 Place the mouse pointer over a tile and click the View children icon .
The objects that have dependency relationships with the parent object are displayed in the Canvas view.
About the Tile view
To view details on selected objects

Place the mouse pointer over a tile and click the Details icon
showing the details of the selected object is displayed.
. A window
Open the Details notebook at the bottom of the Tile view window.
For details about the information displayed in the details window and the Details notebook, see Canvas view details on page 165. Related topics: About the Canvas view on page 164 Viewing the Details notebook on page 215
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. Use the Tile view to get a dashboard summary of event activity. You can display a Tile view for any event collector, group, device, or service that you select in the navigation tree by clicking the Tile View button the right pane view of the Operations Console. 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.
Edit mode: Use this mode to customize various aspects of the tile display, such as
the background image and attributes displayed in the tiles, and optionally, to save your customizations as defaults.
About the Tile view
Tile attributes
By default, 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 - Critical Dark Orange - Major Light Orange - Minor Yellow - Warning 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, you can display the following attributes:

Key performance indicators (KPIs) - displays the health of business services. Custom text - displays static text and clickable hyperlinks to external websites.
The supported hyperlinks are http://, https://, ftp://, and www. future.
Predictive status and trend - displays where the component status might be in the
By default, tiles that represent configuration items display the following attributes:
Name of the component Icon and type of component Current status
About the Tile view
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. The Tools Menu lets you view additional information about the CI and perform certain task, such as setting manual status or maintenance mode. For more information on the CI Tools Menu, see Viewing further information for a CI from the Tools Menu.
Tile preferences and defaults

In Tile view Edit mode, you can select and change tile preferences. You can display different metrics for each tile, or you can choose to display the same metrics for all tiles. Preferences remain persistent until you change them again. After you set the tile preferences and metrics, you can optionally save those preferences and apply them to all tiles that do not have any customizations or, if you have administrative privileges, to all tiles for all users, even for those tiles that have customizations.
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. 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, the following additional cards are displayed in the Details notebook and the KPIs and Prediction cards are not displayed:
Setting up and using the Tile View
Status: Displays the applicable status levels of the selected object Priority and Cost: Displays the schedule status, impact priority, and impact cost
for the selected object
Related CIs: Displays information on status causes, possible problems, providers,
and consumers of the selected object
Schedule: displays the times when the selected component is in service Advanced: displays information on identification, creation and modification time,
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, shows information about the
To expand a card to view more information, click the More Info Related topics: Setting up and using the Tile View on page 180 Viewing the Details notebook on page 215
button.

Use the Tile View in the Operations Console to display a dashboard summary of event activity for event collectors, groups, services, and devices. By default, tiles are created for each node that your administrator or you create in Global or My Folders in the navigation tree. You can select the attributes that you want to display in each tile or use the default attributes. When you access the Tile view, the page is in View mode and tiles are displayed for the object that you select in the navigation tree. To edit the objects in the Tile view, you must first change to Edit mode, change tile preferences and metrics, and then after you have made your changes, return to View mode to monitor the object status.

1 Click the Preferences button in the toolbar.
The view is changed to Edit mode, and the Tile View Preferences dialog box is displayed in the Tile view pane.

For more information about setting up the Tile view, see Using Edit mode to change preferences in the Tile view on page 181. For more information about using the Tile view to monitor objects, see Using View mode to monitor objects in the Tile view on page 183. If you are logged on to the BMC ProactiveNet Operations Console with a user account that has Administrator privileges, 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. For more information, see Saving tile preferences as defaults on page 182.
Using Edit mode to change preferences in the Tile view

When the Tile view is in Edit mode, you use the options in the Tile View Preferences dialog box to determine how you want the tiles to look, and to choose which metrics that you want to display in the individual tiles.
Before you begin

In the navigation tree, 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.
To change tile attributes and preferences

1 If you are in View mode, click the Preferences button to change to Edit mode. 2 In the Background pane 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.
that you want to display.
3 To change the tile metrics, click a tile, and then click Metric Selection in the Tile View Preferences dialog box.
4 In Metric Selection, 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.
The attributes that you can select to display depend on the object type that is
displayed in the tile. For example, devices have a broader list of attributes to select than services. If you select a KPI attribute, the Attribute Selection for Information Capsule dialog box is displayed. Perform the following additional steps:
a Click the item at the end of the row until a list of attributes is displayed. b Select the attribute that you want to display in the tile, and click Apply Selection . If you select the <custom text> attribute, the Custom Text Value dialog box is displayed. Perform the following additional steps: a Enter the custom text that you want to display in the tile. For more information about the Custom Text attribute, see Tile attributes on page 178. b Click OK. 5 Close the Preferences dialog box to save your changes.
The Tile view is returned to View mode.
Click Refresh
to display data for the new attributes.

You can save the changes that you make to the tile preferences as defaults. For details, see Saving tile preferences as defaults on page 182.
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. Optionally, if you are logged on to the BMC ProactiveNet Operations Console with an account that has Administrator privileges, you can apply those changes for all users who have access to the BMC ProactiveNet Operations Console.
To save tile preferences as defaults

1 In the Tile View Preferences dialog box, click Defaults Selection.
2 To save preferences for your tile views only, in the My Tile Views section of the Background and Layout tab, 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), select Only Change Views That Are Using Defaults, and click Apply. the default values (customized settings), select Change ALL Views, and click Apply.
To save the changes for all tiles including those that have settings other than
Optionally, if you are an administrator, you can save tile preferences as the default values for all users. In the All Users Tile Views section of the Background and Layout tab, 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), select Only Change Views That Are Using Defaults, and click Apply.
To save the changes for all tiles including those that have settings other than
the default values (customized settings), select Change ALL Views, and click Apply.
To save tile metrics as defaults

1 In the Tile View Preferences dialog box, click Defaults Selection. 2 In the Tile Metrics tab, 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) and are the same object type as the currently selected object, in My Tile Views, click Apply.
If you are an administrator, to apply the changes for all users as the default
values for all tiles that are using default values (no customized settings) and are the same object type as the currently selected object, in All Users Tile Views, click Apply.
Using View mode to monitor objects in the Tile view

When the Tile view is in View mode, you can monitor the event status of the objects and perform actions on those objects.
To turn on predict mode

1 Click Predict on the toolbar.
A graph, divided into increments, 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. The prediction severity is displayed only if that severity is higher than the objects current severity. For example, if the objects severity is Minor, the prediction severity is displayed if it is predicted to change to Major. If the objects severity is Critical, the prediction severity is not displayed if it is predicted to change to Minor. You must select Show Predictive Events in the Operations tab of the Options window to display the Predict button on the Tile view. For details about setting this option, see Customizing the display of events on page 119.
Note
To size tiles
1 Move the slider control in the toolbar to the left and right.
At the smallest size, only icons of the object severity are displayed in the Tile view. Place the mouse pointer over the tile icons to display a pop up window that shows the tile details.

When you place the mouse pointer over a tile, you can access a menu of commands that let you perform actions on the selected object. 1 Place the mouse over the tile of the object on which you want to perform an action. The tile is highlighted and the Menu icon is displayed in the corner of the tile. 2 Click the Menu icon and select one of the following commands, depending on the object type that you are viewing.
Object type Devices
Command Add Configuration Changes
Description Enables you to store and track configuration data. For more information, see Managing configuration changes on page 158. Enables you to view and manage all configuration changes that have been submitted for the selected object. For more information, see Managing configuration changes on page 158. Enables you to view the events associated with the selected object. You can view the following types of events: All (Direct and Providers) Changes (Direct) Direct Impacting (Direct & Providers) Predictions (Direct and Providers)
Show Configuration Changes
View Events
Go To Graph View
Enables you to display a Graph view for the selected object. For more information, see About the Graph view on page 189. Displays the Device At a Glance page, which shows a stacked line graph for all monitors associated with the selected CI and other related attributes. This option can also be accessed from the Graph Display.
Device at a Glance
Object type
Command Manage Data Collection
Description Enables you to stop data collection by entities immediately during unforeseen situations, such as an urgent server maintenance task that must be carried out. For more information, see Managing data collection on page 159. Enables you to view details about the monitors associated with the selected object. Displays the parent groups and subgroups of the selected object, if available. Provides the following subcommands: Diagnostics => System Configuration Diagnostics =>Top IP Traffic Diagnostics =>Top Processes CPU Diagnostics => Top Processes Memory
Show Monitors
Show Parent Groups
Remote Actions/Diagnostics
Groups
Monitors+devices
Enables you to display the subgroups, monitors, and devices associated with the selected group. Enables you to display a Tree view for the selected object. For more information, see Viewing events for groups in a hierarchical tree on page 146. Enables you 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.
Tree View
Group Details
Object type Cloud Topology
Command Operations
Description Enables you to set and clear manual status and maintenance modes. Enables you to view details about the monitors associated with the selected object. Enables you to view the events associated with the selected object. You can view the following types of events: All (Direct and Providers) Changes (Direct) Direct Impacting (Direct & Providers) Predictions (Direct and Providers)
Show Monitors
View Events
Go To Graph View
Enables you to display a Graph view for the selected CI. For more information, see About the Graph view on page 189. Enables you to set and clear manual status and maintenance modes. Enables you to view details about the monitors associated with the selected object.
Services
Operations
Show Monitors
Object type
Command View Events
Go To Graph View
Enables you to display a Graph view for the selected object. For more information, see About the Graph view on page 189.
To search for tiles

1 In the text box in the toolbar, enter the letters or numbers that you want to search on. The tiles are filtered and sorted according to the search criteria that you enter, from highest severity to the lowest severity.
To sort tiles
1 Click the down arrow next to the sort option in the toolbar. 2 Select to sort the tiles based on the name of the monitored objects, the current severity or status, or the type of object that is being monitored.
To filter tiles
1 Click the down arrow next to the filter option in the toolbar. 2 Select to filter the tiles based on event severity type: Critical, Major, Minor, Warning, Informational, and OK. The tiles that have the severity that you select and higher are displayed.
About the Graph view
Example If you select Warning, all tiles with a status of Warning, Major, Minor, and Critical are displayed and all tiles with a status of Informational and OK are not displayed.

1 Select a tile and click the View children icon .

Place the mouse pointer over a tile and click the Details icon
showing the details of the selected object is displayed.
. A window
Open the Details notebook at the bottom of the Tile view window.
For details about the information displayed in the details window and the Details notebook, see Tile view details on page 179. Related topics: About the Tile view on page 177 Viewing the Details notebook on page 215
About the Graph view

The Graph view in the Operations Console displays a graphical representation of the objects that you select in the navigation tree and shows how those objects relate to each other. The Graph view is available for the following nodes:
Cloud Resources including pods, network containers, and compute pools Services Tenants
Use the Graph view to monitor events for the selected object and see how those events affect other objects in the hierarchy.
Setting up and using the Graph View
Graph view is available for only CI objects, and is available to the following types of users:
Users who have administrator privileges. Users who have access to all CIs and have permission for Graph view. Restricted users with access to the CI, and the required permissions.
The View Events option requires Read access. All other options require Write access. You display the Graph view for the selected object by clicking the Graph View icon in the toolbar in the right pane view of the Operations Console.
Graph view modes

The Graph view has the following modes:
Graph view.
Edit mode: Use this mode to customize various aspects of the Graph view.
Graph View details

You can view event details for the objects in the Graph view in one of the following ways:
display a details window by either selecting an object in the Graph view and
or right clicking on an object and selecting Details. For clicking the Details icon more information, see Details window on page 213
display the Details notebook pane that is located at the bottom of the Graph view
by clicking the up arrows notebook on page 215.
. For more information, see Viewing the Details

Use the Graph View in the Operations Console to display a graphical representation of the following object types:
cloud resources (pods, network containers, and compute pools) configuration items (CIs) in a service model that represent your important
business services
When you access the Graph view, the page is in View mode and objects are displayed for the node that you select in the navigation tree. Use the No Filter feature to filter the graphical display according to the status of the CIs in a service model. To edit the objects in the Graph view, you must first change to Edit mode, change options in the Graph View Preferences dialog box, and then after you have made your changes, return to View mode to monitor the object status.

1 Click Preferences in the Graph View toolbar.
The view is changed to Edit mode, and the Graph View Preferences dialog box is displayed in the Graph view pane. To return to View mode, close the Graph View Preferences dialog box.

For more information about setting up the Graph view, see Using Edit mode to change preferences in the Graph view on page 191 For more information about using the Graph View to monitor objects, see Using View mode to monitor objects in the Graph view on page 194"
Using Edit mode to change preferences in the Graph view

When the Graph view is in Edit mode, you use the options in the Graph View Preferences dialog box to select layout options and the indicator icons that you want to display for each object.
Before you begin

To display the Graph View, select any node under the Cloud Resources or Services nodes in the navigation tree, and then click Graph View Console toolbar. in the Operations
To change Graph view preferences

1 If you are in View mode, click the Preferences button to change to Edit mode. 2 In the General pane of the Graph View Preferences dialog box, set the following options: a Select one of the following layout formats as the default when the Graph View is opened:
Circular: Groups related objects into circles to help you visualize how the
groups are related.
Organic: Groups objects according to their relationships with each other,
with space between groups.
Hierarchic: Arranges objects according to their hierarchy. Orthogonal: Arranges objects in a more compact design with provider
components shown perpendicular to their consumer components.
Stacked Graph: Displays each layer of the graph hierarchy in a separate pane
so that you can more easily see all of the objects in a large scale deployment.
Optionally, select the orientation of the objects, Top to Bottom, Bottom to Top, Right to Left, or Left to Right. Orientation does not apply to the stacked graph layout format. If you click Run Layout, the vertical and horizontal scroll bars on the view sometimes become inactive. Adjust the zoom level of the image, or resize the browser window to reactivate the scroll bars. b Select how you want the label of the object to be determined, either by the object's name or its short description. 3 Click Topology Graph Options and set the following options: a Select the how many levels you want to show by selecting the number of consumer objects and provider objects that you want displayed when the Graph View is opened. You can select a specific number for both consumers and providers or have no limits on the number of levels displayed. The default for Consumers is 1, and the default for Providers is 2. If you chose a layout format other than Stacked Graph, set the following additional options.
b Select the thickness of the lines that indicate relationships between consumers and providers (Regular Lines), and a component's impact on another component (Impacted Lines). c Select to show numbers for the lines that indicate a component's impact on another component. This number indicates the impact percentage between the two components. d Select if you want to use the status color of the component for the lines that indicate relationships between the components. If this option is not selected, the color of the lines is black. e Select the indicator icons that you want to display for each component.
Spotlight: Displays a highlighted circle behind the component. You can set
the following options for the spotlight: Color
select what you want the color of the spotlight to indicate, either the status or the priority of the object based on the most recent event. The darker the color, the more severe is the status or the more important is the priority. select what you want the size of the spotlight to indicate:
Priority: the impact priority of the object based on either on its own priority or on the priority of another impacted object which propagates its priority to the parent object the status of the worst SLA SLA: defined for the object Being Worked On: the object has Not events that have not been assigned Direct Events: the object has events directly associated with it, not propagated from other objects
Size
Brightness: select what you want the brightness of the color associated with the object to indicate:
Direct Events: the object has events directly associated with it, not propagated from other objects Being Worked On: the object has Not events that have not been assigned
Status icon: the object's current status Priority Icon: the impact priority of the object based on either on its own
priority or on the priority of another impacted object which propagates its priority to the parent object
Not being worked on: the object has events that have not been assigned Direct Events From Component are Present: the object has events directly
associated with it, not propagated from other objects the object
SLAs - Status of Worst Targeted SLA: the status of the worst SLA defined for
Prediction Event is Present: the object 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 object

Click Apply to save your changes and keep the Graph View Preference dialog
box open.
Click OK to save your changes and close the Graph View Preferences dialog box. Click Cancel to close the Graph View Preferences dialog box without saving
your changes.
Click Refresh
Using View mode to monitor objects in the Graph view

When the Graph view is in View mode, you can monitor the status of the objects that are displayed in either a hierarchical tree or a stacked layout.
To toggle the Graph view layout

You can select to view the objects in the Graph view in a traditional hierarchical tree or with each layer in the hierarchy displayed in a separate pane. 1 At the top of the display pane, click the Toggle topology/stacked graph icon to select one of the following options:
topology: displays the objects in a hierarchical tree. You can also select the type
of layout (circular, organic, hierarchic, or orthogonal), and orientation (Top to Bottom, Bottom to Top, Left to Right, or Right to Left) of the nodes in the tree. For more information about this layout format, see Using the topology layout format in the Graph view on page 195.
stacked graph: displays objects in each level of the hierarchy in a separate pane
and resizes the icons representing each object so that all objects are visible in the view. If the nodes are displayed less than full size, a focus frame is displayed. Slide this frame over the nodes that you want to view full size. Use the stacked graph option if you are viewing an environment with a large number of nodes; for example, a pool with a large number of hosts. For more information about this layout format, see Using the stacked graph layout format in the Graph view on page 198.
Using the topology layout format in the Graph view

The topology layout in the Graph view displays the objects in a hierarchical tree. Use this layout format to view object relationships.
To set the topology layout format

1 Select one of the following layout formats:
Circular: Groups related objects in circles to help you visualize how the groups
are related.
Organic: Groups objects according to their relationships with each other, with
space between groups.
Hierarchic: Arranges objects according to their hierarchy. Select a Top to
Bottom, Bottom to Top, Left to Right, or Right to Left layout. This format is the default. components shown perpendicular to their consumer components.
Orthogonal: Arranges objects in a more compact design with provider
To filter objects by severity

By default, no filter is applied to the objects in the Graph view. You can use the filter menu to filter the objects based on the severity of the objects that meet the filter criteria. Objects that do not meet the selected filter criteria are grayed out, but are still viewable to maintain the context of the view. 1 From the filter drop list in the upper left side of the Graph view, select the object severities that you want to display in the graph. By default, No Filter is selected. The following options are available:
All objects are displayed in the graph. Only objects with a severity of Critical are displayed. All other objects are grayed out. Only objects with a severity of Critical or Major are displayed. All other objects are grayed out. Only objects with a severity of Critical, Major, or Minor are displayed. All other objects are grayed out. Only objects with a severity of Critical, Major, Minor, or Warn are displayed. All other objects are grayed out. Only objects with a severity of Critical, Major, Minor, Warn, or Information are displayed. All other objects are grayed out. Only objects with a severity of Critical, Major, Minor, Warn, Information, or OK are displayed. All other objects are grayed out.
To size the objects in the topology view

1 Use the zoom bar on the left side of the Graph view to resize the objects as follows:
Use the Zoom Out button
Zoom In button
to make the objects appear smaller, and the to make the objects appear larger.
Alternatively, drag the slider between the Zoom Out and Zoom In buttons, or use the scroll wheel on a mouse.
Use the Zoom Fit button
to resize the graph so that all objects and their relationships fit in the viewable area of the display pane.
Use the Show Overview button
to display an overview of the entire contents of the display pane in a box next to the zoom bar. Any changes you make to instances in the display pane are immediately reflected in this box. The Show Overview button lets you view the effect of your changes on all the instances in the display pane.
To view details on objects

Click the Details icon in the object tile Right click on the object and select Details Open the Details notebook at the bottom of the Graph view window
For more information, see Details window on page 213 and Viewing the Details notebook on page 215.
To turn the spotlight on and off

1 Click the Show Spotlight button on the Graph view toolbar .
A highlight is displayed behind the objects displayed in the Graph view. You can select the properties of the spotlight in the Graph View Preferences dialog box. For details, see Using Edit mode to change preferences in the Graph view on page 191
To turn indicator icons on and off

1 Click the Display All Indicators button on the Graph view toolbar .
The following indicator icons are displayed around the 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 objects.
If you expand and collapse the CI hierarchy several times, objects sometimes appear as yellow boxes. To see the objects again, click Refresh in the toolbar to reload the content.
To view the providers and consumers of a selected configuration item

1 Ensure that you are on the Graph view and on the navigation tree, select a CI for which you want to view the provider and consumer CIs. 2 Select the Tools Menu. The following options enable you to view the provider and consumer for that CI. Expand Provider Collapse Provider Expand Consumer Displays all the providers for the selected CI. Collapses all the displayed providers for the selected CI. Displays all the consumers for the selected CI.
Collapse Consumer Collapses all the displayed consumers for the selected CI.
Launching the Events view and Graph view for a remote configuration item
A remote CI is a CI that is present on a different BMC ProactiveNet Server than the one you are using to currently view the CI. In the context of the Central Server, all CIs that belong to BMC ProactiveNet Child Servers are remote CIs. You can launch the Events view and Graph view of a remote CI from the Central Server console. 1 To launch the Events view for a remote CI, on the CI, click the Tools Menu and select Launch => Events View - Child Console. The Events view is displayed in a new browser instance. This Events view belongs to the BMC ProactiveNet Server to which the remote CI is published. 2 To launch the Graph view for a remote CI, on the CI, click the Tools Menu, and select Launch => Graph View - Child Console. The Graph view is displayed in a new browser instance. This Graph view belongs to the BMC ProactiveNet Server to which the remote CI is published.
Using the stacked graph layout format in the Graph view

The stacked graph layout option provides an alternative to the topology view for monitoring cloud resources and in environments with a large scale BMC ProactiveNet deployment. Each layer in the graph hierarchy is displayed in a separate pane, with the panes stacked vertically within the Graph view. When you
expand an object in one level, child objects are displayed in the next level of the hierarchy in a separate pane. The size of the nodes is adjusted so that you can view all nodes in each pane without having to scroll the view. If the nodes become too small to view, a focus frame is displayed that can be moved over the nodes so that you can view them full size. . The following figure shows an example of the stacked graph layout with the focus frame displayed.
To view details on the objects

Click the Details icon in the object tile Right click the object and select Details Open the Details notebook at the bottom of the Graph view window
For more information, see Details window on page 213 and Viewing the Details notebook on page 215.
About the Heat Map View
Note When you change the status of a CI, the change is reflected in the Details notebook earlier than the change in the stacked graph view. The reflection of the change in status in the stacked graph view might be delayed.
To expand the hierarchy to view child objects

1 Click the plus buttons at the bottom of the objects.
A triangle is displayed to indicate which object is expanded as shown in the following figure.
To collapse the hierarchy

1 Click the minus buttons at the top left side of the stacked graph panes.
To use the focus frame to display objects full size

If the objects in a pane become too small to view, a focus frame is displayed. 1 Click on the focus frame and slide it left and right to view the nodes full size.

The Heat Map View in the Operations Console displays the hierarchical monitored objects in the navigation tree as nested heat tiles and is available for cloud resource objects (locations, pods, network containers, and compute pools) and services. The Heat Map View is color-coded to show the alarm stages of the nodes selected in the navigation tree and their child objects. Use the Heat Map View to get an at-a-glance view of the status of the objects to more quickly identify problems. The Heat Map View has the following characteristics:
You can configure what the size of the tiles represents. For example, it could be
based on the number of child objects associated within each node, so that the more child objects that a node has, the larger its tile is in the Heat Map View. You can set this value in the Heat Map View Preferences dialog box. You can set this value in the Heat Map View Preferences dialog box.
The color of the tile can represent the status or priority of the monitoried object.
The tile can be expanded to a full pane view by double-clicking on the tile. Tile characteristics can be changed by using the Heat Map View Preferences
dialog box.
Actions can be performed on the tiles by using the Tools menu. Additional details about the monitored object can be viewed either by selecting
the Details icon on the tile or by displaying the Details notebook pane located below the Heat Map View.
You can display the Heat Map view for the applicable objects that you select in the navigation tree by clicking the Heat Map View icon pane view of the Operations Console. in the toolbar in the right
Heat Map View modes

The Heat Map View has the following modes:
View mode: Use this mode to monitor the objects that you select in the navigation
tree.
Edit mode: Use this mode to customize various aspects of the Heat Map View
display.
Setting up and using the Heat Map View
Heat Map View details

You can view event details for the objects in the Heat Map view in one of the following ways:
display a details window by either selecting an object in the Heat Map View and
clicking the Details icon or right clicking on an object and selecting Details. For more information, see Details window on page 213
display the Details notebook pane that is located at the bottom of the Heat Map
View by clicking the up arrows notebook on page 215.
. For more information, see Viewing the Details

Use the Heat Map View in the Operations Console to display the nodes in the navigation tree as nested heat tiles to get an at-a-glance view of the status of the objects in each node. When you access the Heat Map View, the page is in View mode. To edit the objects in the Heat Map View, you must first change to Edit mode, change preferences, and then after you have made your changes, return to View mode to monitor the object status.

1 Click the Preferences button in the Heat Map View toolbar.
The view is changed to Edit mode, and the Heat Map View Preferences dialog box is displayed in the Heat Map View pane. To return to View mode, close the Heat Map View Preferences dialog box.

For more information about setting up the Heat Map View, see Using Edit mode to change preferences in the Tree Map view on page 203 For more information about using the Heat Map View to monitor objects, see Using View mode to monitor objects in the Heat Map View on page 204" .
Using Edit mode to change preferences in the Tree Map view

When the Tree Map View is in Edit mode, you use the options in the Tree Map View Preferences dialog box to determine how you want the nested tiles to look.
Before you begin

Select a node in the navigation tree, and then click the Tree Map View button in the Operations Console toolbar.
To change nested tile attributes

1 If you are in View mode, click the Preferences button to change to Edit mode and open the Tree Map View Preferences dialog box. 2 In the Layout Options pane of the Tree Map View Preferences dialog box, set the following options. a Under Blocks, select what you want the color of the tile to represent, either Status or Priority. b Select one of the following options to determine what you want the size of the tiles to represent, depending on the object that you have selected in the navigation tree.
Priority Number of children SLA Number of VMs/Computers The priority of the object based on either its own priority or on the priority of another impacted object that propagates its priority to it. The number of child nodes associated with the object. The status of the worst SLA defined for the object. The number of virtual machines or computers associated with the object.
c Under Levels to Show, select how many levels of child objects that you want displayed as nested tiles. The default and maximum number of levels that you can display is 3. 3 Perform one of the following actions:
Click Apply to save your changes and keep the Tree Map View Preference
dialog box open. box.
Click OK to save your changes and close the Tree Map View Preferences dialog
Click Cancel to close the Tree Map View Preferences dialog box without saving
your changes.
Click Refresh
Using View mode to monitor objects in the Heat Map View

When the Heat Map View is in View mode, you can monitor the status of the objects that you select in the navigation tree.

When you select a tile in the Heat Map View, you can access a menu of commands that let you perform actions on the selected object. 1 Select a nested tile in the Heat Map View. The tile is highlighted and the Menu icon is displayed in the corner of the tile. 2 Click the Menu icon and select one of the following commands, depending on the object type that you are viewing in the Heat Map View.
Object type Cloud Topology Command Operations Description Enables you to set and clear manual status and maintenance modes. Enables you to view details about the monitors associated with the selected object.
Show Monitors
Object type
Command View Events
View Service Impact Graph
Enables you to display a Graph View for the selected CI. For more information, see About the Graph view on page 189. Enables you to set and clear manual status and maintenance modes. Enables you to view details about the monitors associated with the selected object. Enables you to view the events associated with the selected object. You can view the following types of events: All (Direct and Providers) Changes (Direct) Direct Impacting (Direct & Providers) Predictions (Direct and Providers)
Services
Operations
Show Monitors
View Events
About the Chart View
Object type
Command View Service Impact Graph
Description Enables you to display a Graph View for the selected object. For more information, see About the Graph view on page 189.

1 Select a nested tile in the Heat Map View and click the View children icon .

1 Perform one of the following actions, with a nested tile selected:
Click the Details icon
. A window showing the details of the selected object is displayed. For more information, see Details window on page 213. more information, see Viewing the Details notebook on page 215.
Open the Details notebook at the bottom of the Heat Map View window. For
About the Chart View

The Chart View in the Operations Console lets you create graphs that show the performance metrics over a specified period of time. You can display the Chart View by clicking the Chart View icon in the toolbar in the right pane view of the Operations Console when you select an object in one of the following nodes in the navigation tree:
Pods Compute Pools Network Containers Devices Groups Services
The Chart View has the following modes:
Setting up and using the Chart View
Chart View. See Using View mode to monitor objects in the Chart View on page 211. the Chart View. See Using Edit mode to change preferences in the Chart View on page 207.
Edit mode: Use this mode to create new charts and customize the background of

Use the Chart View in the Operations Console to monitor the performance of key metrics over a specified period of time. When you access the Chart View, the page is in View mode. To create charts and edit Chart View preferences, you must first change to Edit mode. After you make your changes, return to View mode and use the charts that you create to monitor the object status.

1 Click the Preferences button in the Chart View toolbar.
The view is changed to Edit mode, and the Chart View Properties Change dialog box is displayed in the Chart View pane. To return to View mode, close the Chart View Properties Change dialog box.

For more information about setting up the Chart View, see Using Edit mode to change preferences in the Chart View on page 207 . For more information about using the Chart View to monitor objects, see Using View mode to monitor objects in the Chart View on page 211.
Using Edit mode to change preferences in the Chart View

When the Chart View is in Edit mode, you use the options in the Chart View Properties Change dialog box to create a new chart and set up the Chart View background.
Before you begin

Select a node in the navigation tree, and then click Chart View Operations Console toolbar. in the
To create a new chart

1 to change to Edit mode and open If you are in View mode, click Preferences the Chart View Properties Change dialog box.
2 In the Charts pane of the Chart View Properties Change dialog box, click Add Chart. The Add New Chart wizard is displayed as shown in the following figure.
3 Click on an object name in the wizard until a list of metrics is displayed as shown in the following figure.
The items displayed in the wizard depend on what object type you have selected in the navigation tree. Metrics that are designated as key performance indicators are displayed in the wizard with a key icon 4 Perform one of the following actions:
If you want only one metric displayed in the chart, select a metric and then
click Next.
If you want to choose a second metric for this object type, select the first metric
and then at the top of the Add Chart wizard, click the plus button. Repeat step 3 and then click Next.
5 Select the type of chart that you want to create, and perform one of the following actions:
If you select area chart, click Finish. The Add New Chart wizard is closed, and
the new area chart is displayed in the Chart View pane. Continue with step 7.
If you select line chart, click Next and continue with step 6.
6 If you select line as the chart type, select the threshold indicators that you want to display on the chart as follows:
Threshold Events: select this option to display lines that indicate signature or
absolute thresholds defined for the metric that you select to display in the chart, and icons that show the status of any threshold events generated for that metric for the selected time frame abnormality thresholds defined for the metric that you select to display in the
Abnormality Events: select this option to display lines that indicate
chart, and icons that show the status of abnormality events generated for that metric for the selected time frame
External Events: select this option to display icons that show the status of
events generated from external event adapters
Click Finish. The Add New Chart wizard is closed and the new line chart is displayed in the Chart View pane. Continue with step 7. 7 Click Close on the Chart View Properties Change dialog box to return to View mode. 8 Click Refresh .
To create a stacked chart for pods

If you are creating charts for the pods in your cloud deployment, you can create a stacked chart that shows the performance relationships for utilization parameters within a shared resource pool. 1 If you are in View mode, click Preferences to change to Edit mode and open the Chart View Properties Change dialog box.
2 In the Charts pane of the Chart View Properties Change dialog box, click Add Stacked Chart. 3 In the Add Stacked Chart dialog box, perform the following tasks.
Select the utilization parameter that you want to display. (optional) Edit the default title.
Click Finish. The Add Stacked Chart dialog box is closed, and the new chart is displayed in the Chart View pane. 4 Click Close on the Chart View Properties Change dialog box to return to View mode.
To change the Chart View background

2 In the Background pane in the Chart View Properties Change dialog box, perform one or both of the following actions:
Select the Color option and then click on the colored squares to display the
color palette. Use the palette to select the colors that you want to display. that you want to display.
You can select one of the default images, or you can add your own images to the BMC ProactiveNet Server and then select those images in the Chart View Properties Change dialog box to display in the Chart View background. For information about how to add background images, see the BMC ProactiveNet Administrator Guide. 3 Click Close on the Chart View Properties Change dialog box to save your changes and return to View mode.
To delete a chart
2 In the Chart View pane, select the chart that you want to delete. 3 In the Chart View Properties Change dialog box, click Delete Chart. The chart that you selected is removed from the Chart View pane. 4 Click Close on the Chart View Properties Change dialog box to save your changes and return to View mode.
Using View mode to monitor objects in the Chart View

When the Chart View is in View mode, you can monitor the status of the metrics that are defined for the objects that you select in the navigation tree for the period of time that you select.
To select a time frame

1 From the list above the chart view, select the time frame that you want to view in the charts that you create as shown in the following figure.
Time periods available are Last 1 hour, Last 4 hours, Last 8 hours, Last 12 hours, Last 24 hours, Last 2 days, Last 1 week, Last 2 weeks, Last 1 month, and Last 3 months.
To maximize charts
1 To display a chart in full view, click Maximize in the upper right corner of .
the chart. To return the chart to the default size, click Restore
Changing chart attributes

You can edit a chart to change the title and type, and add or remove threshold indicators without accessing the Chart View Change Properties dialog box. 1 Click the Show chart preferences button at the bottom of a chart.
The chart preferences dialog box is displayed over the chart. The following figure shows an example of the chart preferences dialog box displayed over the chart on the left.
2 Edit the following chart attributes.

Title: chart title that is displayed at the top of the chart Type: the type of chart displayed, either Line or Area. Select Indicators: indicators that show that events of a particular status have
been generated for the selected object. Indicators are displayed only for a single
Details window
metric in an area or line chart and only if thresholds have been defined for the indicator type. The following indicators can be displayed on charts:
Threshold Events: select this option to display lines that indicate signature or
absolute thresholds defined for the metric that you select to display in the chart, and icons that show the status of any threshold events generated for that metric for the selected time frame
Abnormality Events: select this option to display lines that indicate
abnormality thresholds defined for the metric that you select to display in the chart, and icons that show the status of abnormality events generated for that metric for the selected time frame events generated from external event adapters
External Events: select this option to display icons that show the status of
The chart legend defines each indicator type displayed on a chart. You access the chart legend by clicking the Chart Legends button . Also, you can mouse over an event indicator icon on the chart to get more details about the event. 3 Click OK to save your changes and close the chart preferences dialog box.
Details window
You can view details for cloud resources and services in the console views by clicking the details button . When you click the details button, a window is displayed that provides summary information for the object that you have selected. The Summary tab in the details window displays the information listed below. Not all details are provided for all objects:
Encapsulated performance data that displays color-coded status information to
show any thresholds that have been violated for the selected object
Class: displays the object class, which identifies what type of object is selected Subtype: displays the object subclass Status: displays the current status of the object Priority: displays the priority of the last event associated with the object Event Acknowledged: displays whether the last event associated with the object
has been assigned
Details window
Sub Status: displays the worst status propagated up from any provider Manual Status: displays whether the manual status of the component has been set SLA Compliance: displays the status of the worst SLA defined for the object Total Open Events: displays the number of open events associated with the object Predicted Status: displays the status of the object is predicted to become worse
than its current status at some point in the future for a service offering
Owner Name: when you select the Services node, displays the person responsible
Owner Contact: displays the contact information for the object owner Short Desc.: displays a brief description of the object Related POD: when you select the Compute Pools node, displays the pod that a
compute pool is associated with
Service Offering: if you select a service offering instance, displays the service
offering for which the instance is defined
If the object that you have selected is a cloud resource (pods, network containers, compute pools), the details window is divided into tabs with the previous information displayed in the Summary tab and the following additional tabs displayed, depending on the object that you have selected:
Events: displays the event list for the most recent 10 events associated with the
monitored object
Resource Pools: displays the Tools menu, status, and the name of any compute
pools associated with the object, component ID of the compute pools, the name of the person responsible for the compute pool objects, and that person's contact information ID of the tenants, the name of the person responsible for the tenant objects, and that person's contact information
Tenants: displays the name of any tenants associated with the object, component
SOIs: displays the name of any service object instances associated with the object,
component ID of the service object instances, the name of the person responsible for the service object instances, and that person's contact information network containers associated with the object, component ID of the network container, the name of the person responsible for the network container objects, and that person's contact information
Network Containers: displays the Tools menu, status, and the name of any
Viewing the Details notebook
Zones: displayes the zones that are associated with the network container on
which you are viewing details
To expand and view multiple tabs, click the plus icons
To perform actions on the objects, click the Tools menu in the details window tab next to the object on which you want to perform the action, and select one of the following commands:
Operations: Enables you to set and clear manual status and maintenance modes.
For more information, see Manually setting CI status or maintenance modeYou can set the status of a service CI manually by using a remote action. You can also put a CI in maintenance mode by using this feature. When you use the manual status feature, you must enter a comment that explains why the status was changed. To remove the manually set status or to return a CI to operation, you must use another remote action to clear the manually set status. . the selected object.
Show Monitors: Enables you to view details about the monitors associated with
View Events: Enables you to view the events associated with the selected object.
You can view the following types of events:

All (Direct and Providers) Changes (Direct) Direct Impacting (Direct and Providers) Predictions (Direct and Providers)
View Service Impact Graph: Enables you to display a Graph view for the selected
object. For more information, see Executing remote actions on page 113.

The Details notebook pane displayed below the Tile, Canvas, Heat Map, 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. The cards of the Details notebook pane organize the information, as described in Table 43 on page 216.
Table 43: Cards displayed in the Tile, Canvas, Heat Map, 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. The Details notebook event list shows the same information that is displayed in the Events List view, and provides toolbar options so that you can search and take actions on these events. Displays basic information about the object (tile) that you have selected in the Tile or Canvas view, such as object name, short description, description, object type icon, current event severity status, any actions taken on the last known event, prediction status, if applicable, and object description. Also includes hyperlinks to launch the Tools Menu. The menu commands that are available depend on what object is displayed in the selected tile as follows: description. Also Services: Operations (Set Manual Status, Clear Manual Status, Set Maintenance Mode, Clear Maintenance Mode), View Events (All, Changes, Direct, Impacting, and Predictions), View Service Impact Graph Groups: Monitors+Devices, Tree View, and Group Details commands Devices: Add Configuration Changes, Device at a Glance, Manage Data Collection, Show Configuration Changes, Show Monitors, Show Parent Groups, View Events (All, Changes, Direct, Impacting, and Predictions), View Service Impact Graph, and BladeLogic Device History Monitors associated with Devices: Show Parent Groups, Flash Check, 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 objects status will be and at what time that status will be reached. The prediction severity is displayed only if that severity is higher than the objects current severity. For example, if the objects severity is Minor, the prediction severity is displayed if it is predicted to change to Major. If the objects severity is Critical, the prediction severity is not displayed if it is predicted to change to Minor.
Summary
Prediction
If you select a CI object, additional cards are displayed as described in Table 44 on page 217.The Key Performance Indicators (KPIs) and Prediction cards are not displayed for CIs.
Table 44: Additional cards displayed in the Tile, Canvas, Heat Map, 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, impact priority, and impact cost. Description Displays the applicable status levels of the component: Service Level Agreement, manual status, maintenance mode, and computation statuses.
Summary Priority Details Time-Variable Properties
Related CIs
Displays information on status causes, possible problems, providers, and consumers of the selected component type. This subtab also lets you view other components that have relationships with the selected component.
Schedule Advanced
Displays the times when the selected component is in service Identification Time Stamps Permission Groups Displays information on identification, creation and modification time, and read/write permissions for groups for the selected object.
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.
To view the Details notebook

By default, the Details notebook is not displayed when you open the Tile, Canvas, Heat Map, or Graph view. To display the Details notebook, perform the following steps. 1 Select an object in the Tile, Canvas, Heat Map, or Graph view.
Launching the BMC Atrium Service Context application from the BMC ProactiveNet Operations Console
In the Details notebook title bar, click the Up arrows
To hide the Details notebook

1 In the Details notebook title bar, click the Down arrows .
To select the cards to be displayed in the Details notebook pane

1 Select an object in the Tile, Canvas, Heat Map, or Graph view. 2 Click Edit Notebook Preferences .
3 In the Preferences dialog box, select the cards to be displayed in the Details notebook pane. 4 Click Close .
If you select more cards than can be displayed, use the tiny right and left arrows to the right and left of the Details notebook to navigate through the cards.
Tip
To view additional information in a card in the Details notebook pane

1 In any of the cards listed in Table 43 on page 216 or Table 44 on page 217of the Details notebook, click More Info . The card is expanded and displayed in a separate window so that the additional information becomes visible.
If you have integrated BMC ProactiveNet with the BMC Atrium CMDB, you can launch the BMC Atrium Service Context application from the BMC ProactiveNet Operations Console for a selected business service configuration item (CI). Use BMC Atrium Service Context to view details about the services that support the objects in a service model to determine how those services are performing in your environment. BMC Atrium Service Context provides consistent information that can be shared across BMC products and among disciplines within your organization. You can
launch BMC Atrium Service Context from a business service defined in a service model from the Tile View, Canvas View, Graph View, and Heat Map View. If you enabled integration with the BMC Atrium CMDB after you installed the BMC ProactiveNet components, you must manually register the BMC ProactiveNet web services with the Web Services Registry (UDDI) to enable the cross-launch. For details, see #unique_204in the BMC ProactiveNet Administrator Guide.
Note
To launch the Service Context from a business service

1 Select a business service in the navigation tree of the BMC ProactiveNet Operations Console. 2 Select one of the following views in the operations console toolbar: Tile View, Canvas View, Graph View , or Heat Map View. The service model is displayed in the view that you select. 3 Right-click on a business service and select Launch > Service Context. The Service Context Summary View is displayed and shows a list of attributes associated with the selected business service. Your administrator can set the attributes that are displayed in the Summary View. For details, see the BMC Atrium CMDB Administration Guide. BMC Atrium Service Context also provides drill down functionality so that you can view additional details about service attributes. For more information, see the BMC Atrium CMDB User Guide.
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, BMC ProactiveNet can determine the most-likely causes for an event, such as an attribute that is outside the desired range. This process of gathering and filtering data to determine the cause for an event is called probable cause analysis. The probable cause analysis process analyzes data and displays the relevant events automatically. You can increase the accuracy of probable cause analysis by providing relationships between devices and monitors. The more data that is provided about an event, the more accurate probable cause analysis will be. For more information, see Configuring BMC ProactiveNet to perform probable cause analysis on page 227.
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. Therefore, the following events are not considered during probable cause analysis:
administrative eventsAdministrative events include all events that belong to
specific event classes within the MC_CELL_EVENT class. These event classes are listed in Event information used in probable cause analysis on page 519 handled differently from other events. For more information see, Probable cause analysis in a virtual environment on page 239.
VMware-related VMotion events Events related to use of a virtual machine are
Chapter 3 Determining the probable cause for an event 221
predictive eventsPredictive events are early warning events that BMC
ProactiveNet generates before a severe event occurs on an existing metric. blackout period for an adapter.
blackout eventsBlackout 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. 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. The Probable Cause Analysis(PCA) in BMC ProactiveNet computation is useful in trouble shooting performance related issues.
The Service Model is present, but the thresholds are not set on all the metrics. In
this case, PCA can be very effective by looking at relevant abnormalities, external events, and configuration change events. shown as impacting events. In this case, PCA can be used to sort the events by score computation and by looking at various factors like data correlation, time correlation, severity, and so on.
The Service Model is present in a detailed or high level, but lot of many events are
The Service model is not present. Impact computation is available only for open events. PCA is used for finding the
root causes after the occurrence of the event.
When trouble shooting system resource related issues in virtual environments and BMC adapter for VMware is used for data collection.
Probable cause analysis can be performed on internal events and external events. An internal event is an event that is generated by the BMC ProactiveNet Server. Internal events also are referred to as intelligent events or data events because these events include a large and rich amount of data. For a list of slots used by probable cause analysis to analyze events, see Event information used in probable cause analysis on page 519 External events are events that are received from an external source such as a remote cell or an event adapter. Because these events come from a source that is external to BMC ProactiveNet, these events do not have the data associated with them that an internal event does. Because internal and external events vary in the amount and type of data that they supply, internal and external events are handled differently during the probable cause analysis process.
Because internal events are rich in data, these events go through more analysis steps than external events. When BMC ProactiveNet is analyzing an internal event to determine if it could be a probable cause for another event, it applies a series of filters to the internal event, in the order shown in Figure 6 on page 223. Figure 6: Probable cause analysis process for an intelligent event
Because external events do not contain data as internal events do, probable cause analysis for external events uses fewer filters, as illustrated in Figure 7 on page 223. Figure 7: Probable cause analysis process for an external event
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, which might make it the cause of the result event. In general, the longer the period of time between the probable cause event and the result event, the less likely it is that the probable cause event is the cause of the result event.
If the probable cause event occurs within the time specified by the time correlation filter, then the probable cause event is assessed against the user-defined filters. For instructions on modifying the time specified by the time correlation filter, see Changing the time correlation filter on page 234.
User-defined filters
Once the event has passed the time correlation filter, you can filter probable cause events based on a collection of filters that you define. These following user-defined filters are applied depending on whether the event is internal or external:
Device Namefilters all internal events and external events that are associated
with a device that exists within BMC ProactiveNet
Groupfilters 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. Also filters external events that are not associated with a computer system and displays event outside the model, but with lower scores.
Event level - Filters based on the non-KPI metrics, service model, using global
For instructions on configuring these filters, see Enabling user-defined filters on page 235. If an internal event passes through the user-defined filters that have been applied, that internal event is then compared against any saved knowledge patterns. For more information about knowledge patterns, see Knowledge patterns on page 225. If an external event passes through the user-defined filters, BMC ProactiveNet examines the user-defined relationships for the external event to determine if the external event might be a probable cause event. For information about the userdefined relationships filter, see Service model relationships on page 226.
Knowledge patterns
If you have determined that a certain set of criteria usually results in the same probable cause event, 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.
If an internal event is compared to a knowledge pattern and matches, then that event is displayed immediately as the probable cause event. If an internal event does not match any of the saved knowledge patterns, BMC ProactiveNet examines the CI relationships for the internal event to determine if the event might be a probable cause event. For information about defining knowledge patterns, see Saving recurring conditions as a known probable cause on page 236.
Service model relationships

The relationships between configuration items (CIs) identify potential probable cause events. Service model relationships capture relationships between CIs. Because these relationships are unique to your environment, you must set them yourself. 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. For more information about service model relationships, see the BMC ProactiveNet Administration Guide. BMC ProactiveNet examines the relationships of the CI for the potential probable cause event. If the event belongs to any CI instance relationships, then those relationship filters are applied. If the event instance does not belong to any instance relationship, BMC ProactiveNet analyzes the event based on global relationship rules.
Global relationships
Global relationships are pre-defined, out-of-the-box domain knowledge provided for existing BMC ProactiveNet monitors. This domain knowledge cannot be modified. Global relationships are analyzed for all internal events and all external events that have a sub-category specified in the mc_event_subcategory slot. For more information about the mc_event_subcategory slot, see the BMC Knowledge Base Development Reference Guide.
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. Data correlation is applicable only to internal events.
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.

To maximize the capabilities of BMC ProactiveNet probable cause analysis, you should configure your BMC ProactiveNet system as recommended by these guidelines.
Configure complete monitor coverage

You must configure complete monitor coverage for your entire infrastructure. Complete monitor coverage is key for probable cause pinpointing to work correctly. This includes monitors at the system level, application level, and network level. If there is not enough coverage, then probable cause will show that no events are correlated. If monitors are not covering all dependencies in your infrastructure, then it is virtually impossible to get to the granular cause of a problem. For example, if you have a Web site in your environment, you must make sure to create a monitor for it using the Web URL or Web Transaction monitor, but you also need to create a monitor for all resource dependencies that support it, such as Web Server monitors, Application Server monitors, Database monitors, as well as all System Resource monitors for each of the computers these run on, such as TCP monitors, System monitors, Disk monitors, Ping monitors, Process monitors, Log File monitors, Interface monitors, and DNS monitors.
Assign correct device types

You must ensure that the correct device types are assigned to all devices in your infrastructure. BMC ProactiveNet uses device type information to isolate problems and relate them across different computers. By default, BMC ProactiveNet assigns a device type to each device; however, you should verify that the default device type is set correctly. Probable cause analysis uses the device type to attempt to identify the probable cause of an event. If the device type is not set correctly, events from that device could be incorrectly eliminated from the probable cause analysis calculations or could be incorrectly pinpointed as the probable cause because the events are associated with an incorrect device type.
Create monitors under the correct devices

Each monitor in the BMC ProactiveNet system is located under a specific device in the Administration Console. This device should be the target computer where the application being monitored is running - either virtually or physically. When creating a monitor, ensure that the monitor is created under the correct device in the Administration Console. This information is important for the probable cause analysis process to draw conclusions about the relationship of monitors with respect to one another. Probable cause analysis can use the device as a way of filtering out unrelated events. If the monitor assignment is not correct, there is a chance that an event that is correlated to the result event will not be displayed or, conversely, unrelated events may appear.
Create service models for interdependent CIs

You must create service models for CIs that have dependencies on one another. You can create service models using the Administration Console or BMC Impact Model Designer. For information see the BMC ProactiveNet Administrator Guide and the BMC ProactiveNet Service Modeling and Publishing Guide.
Associate monitors to the proper CI

When you create a service model by using the Associate Monitor feature in the Administration Console, ensure that you associate the monitor to the proper CI.
When you do not have access to a device, but require access to a specific monitor, the monitor can be associated to a high-level CI, for example, a service CI. You need to create a component, assign permissions, and associate the monitor to the component. If you do not have access to the device, the device is displayed without the tools menu. However, when you drill down on the device, the accessible monitors will display. The tools menu options depend on your assigned permissions. For information on associating the monitor to the proper CI, see the BMC ProactiveNet Administrator Guide.
Set a polling interval of 5 minutes or less

BMC ProactiveNet recommends using the default polling frequency. However, if you decide to change the polling frequency, keep in mind that polling frequency affects probable cause analysis. Probable cause analysis will not display events that are outside the specified timeframe before or after the result event. For example, 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. A greater number of data points increases the likelihood that the probable cause analysis process will be successful. Therefore, it is best to configure the smallest polling interval that does not affect the performance of the device.
Establish a reliable baseline

To ensure a reliable baseline for a monitor, the monitor should be collecting data consistently for at least a week. The longer the monitor has been collecting data, the more reliable the probable cause analysis process becomes. The following types of threshold settings impact the probable cause analysis process:
Absolute/Signature Event Thresholdsthe duration of these thresholds is critical
for correlating events that occur closely in time to the original event. 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, this event might not be displayed. For example, you create a threshold that creates a CRITICAL event when server CPU USED is above 90% (condition) for 1 hour (duration). At 10:00 AM the CPU
Viewing probable cause analysis for an event
USED is higher than 90%. However, an event will be generated only at 11:00 AM if the CPU USED percentage stays above 90% until 11:00 AM. 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, the CPU usage problem will not be displayed as a probable cause event because the duration for this event has not yet passed.
Abnormality Event ThresholdsBMC Software recommends that you keep the
default settings for these thresholds.
Ensure sub-categories are defined for external events

For external events to be analyzed based on global relationships, the mc_event_subcategory slot must be set for each external event. For information about the mc_event_subcategory slot, see the BMC Knowledge Base Development Reference Guide.

The probable cause analysis information for an event is displayed in the Probable Cause Analysis For Selected Event screen in the Operations console. This screen displays the probable cause events that remain after all the relevant filters have been applied.
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. 1 From the event list, select the event for which you want to determine probable cause. 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
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). 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. For instructions on enabling these filters, see Customizing the display of the Probable Cause Analysis list on page 232. From the Probable Cause Analysis For Selected Event screen, you can view: 1 A graph of the raw data for the selected event. 2 The attributes and indicators for the selected event. 3 Monitor information for the selected event. If you determine that particular conditions for a particular instance always indicate probable cause, you can set up a knowledge pattern that saves and recognizes those particular conditions. When that pattern is encountered again, BMC ProactiveNet will instantly identify those conditions as the probable cause for the event. For information about defining a knowledge pattern, see Saving recurring conditions as a known probable cause on page 236.
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. There are two tabs in this pane, the By Score and the By Device tabs. 1 By Score: This tab sorts the probable cause events based on the highest score. 2 Click on the Detailed Diagnostics icon to view detailed diagnostics for the event. The tools menu also is available for this event from the Probable Cause Analysis For Selected Event screen. 3 By Device: This tab sorts the probable cause events by device.
Customizing the display of the Probable Cause Analysis list
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. The BladeLogic icon depends on the latest job that is executed. The tooltip displays the time of the last run BladeLogic job with respect to the primary event. Click the Tools menu icon for the event and choose BladeLogic Device History to view BladeLogic device history page. For more information about integration with BMC BladeLogic, see Integrating with BMC Server Automation on page 487.

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, click Preferences .
2 In the Probable Cause Analysis Preferences page, use the information in the following table to determine the appropriate settings. Table 45: Probable cause analysis preferences settings
Field General Description
Field View
Description Displays the events sorted by score or by device. The default view is By Score. By Score: displays the events sorted on the score. By Device: displays the events sorted by devices of the events.
Time Events Filter
Enables the time specification based on the secondary event time out interval. The default time interval is -1 and +30. Enables the levels of event filter for the following options: Level 1 Level 2 Level 3 Level 4 By default, level1 is displayed.
Analysis
Enables you to correlate information in the following ways: Time Correlation - enables you to display the secondary events in the same timeframe as the primary event. Data Correlation - enables the computation of data using the data collected for the resulting event and the probable cause event. Data correlation is applicable only to internal events. Correlate metric data within time window - co-relates the metric data of the primary event against the metric data of each candidate event. Only the metric data within the analysis window is analyzed. For example, if you select - 1 hour and + 1 hour in the time window slider, then up to 2 hours of data are analyzed. Correlate metric data during previous abnormalities on event's metric - 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. (subject to data retention limits). This can produce more accurate data correlation results at the cost of increased processing time. However, the results may take up to 3 times longer to return.
Event Filter Levels
Filtering unrelated events to find probable cause
Field
Description
Filter levels on non-KPI metrics Select this option to filter by non-Key Performance Indicators (KPI). Show only highest scoring event per metric Filter using service model Displays event outside the model, but lower scores Select this option to display only the event with the highest score. For a given metric there could be multiple abnormalities and threshold events. Select this option to filter events based on the impact relationships defined for the CI associated with the primary event. Select this option to show the events that are not associated with the impacting CI's based on the model identified above.
Filter using global relationships Select this option to control whether the built-in global relationships are used to determine probable cause. 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. After the probable cause analysis identifies the probable cause 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.
Advanced By Score - Max Number of Events to Display By Device - Max Number of Devices to Display By Device - 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. Enables you to determine the maximum number of devices to display in the PCA results window. Enables you to determine the maximum number of events per device to display in the PCA results window.

There are many ways to filter unrelated events to find the probable cause of an event. The following topics explain how to configure these filters.
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, BMC ProactiveNet only considers events that have occurred one hour before or 30 minutes after the primary
event. If you want to increase or decrease the time correlation between the primary and the second event, you must change the time correlation filter.
To change the time correlation filter

1 Access the probable cause analysis for the selected event. 2 From the Sliding bar, drag the sliding pointer to set the time window before or after the timestamp of the primary event. This enables you to filter out the unrelated events.
Enabling user-defined filters

User-defined filters limit the events to be considered as probable cause events based on criteria that you define. These user-defined filters can be configured in the Probable Cause Analysis Events section. You may enable one or more of these filters at the same time.
To filter by device name

1 In the Device field enter the name of the device to see the associated events. This filter removes all events from the probable cause event list that are not associated with the device that you specify. If no name is specified in the Device field, then events for all devices will be displayed.
To filter by group
1 Click No Filter next to the Group field. 2 From the Group Filter dialog box,
Select Tree from the drop-down list to display the hierarchical group view. Select Flat List from the drop-down list to list all the available groups.
3 Click Apply. 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 edit the group filter, click on the filter displayed, select the group and click
Apply. Click Filter on the Probable Cause Events section.
Saving recurring conditions as a known probable cause
To remove the group filter, click on X next to the enabled group filter.
To filter by events
1 In the Events Filter list, select the desired level for the events that you want to filter and display. 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 levels can be modified in the preference page.
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, capture it by creating a knowledge pattern. Once a knowledge pattern is available, BMC ProactiveNet immediately applies this pattern to similar conditions and does not run probable cause analysis.
To create a knowledge pattern

1 Access the Probable Cause Analysis For Selected Event dialog box. 2 In the Event list, select the event that you want to use for your knowledge pattern. 3 Click Create Knowledge Pattern.
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, select the check box or check boxes to add further conditions to the knowledge pattern. The available conditions will change based on the event that you have selected.
Probable cause analysis in a scalable deployment environment
6 In the Name field, 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.
For example, if you created a knowledge pattern for a scenario where there is
an event on Application Availability and Ping Availability to the same device where the application is running you might name it Application Server Not Available.
7 In the Description field, enter details for the probable cause knowledge pattern.
Continuing the example from List item. on page 237, you could enter the action
that an operator should take if this knowledge pattern is encountered, such as Reboot server.
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. 8 Click Save. Knowledge patterns are saved in the database. After you have created one or more knowledge patterns, you can access an edit or delete dialog box for modifying or deleting your knowledge patterns.

In a scalable deployment environment events are propagated from the local BMC ProactiveNet servers to a central BMC ProactiveNet Server. If you want to perform probable cause analysis on all the events in the environment, probable cause analysis must be performed on the central BMC ProactiveNet Server.
Figure 8 on page 238 illustrates how events are propagated in a scalable environment. Figure 8: 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. This causes the propagated intelligent events to be treated as external events. 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.
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. When probable cause analysis is requested for a system resource-related event on an ESX host or a virtual machine, BMC ProactiveNet takes into account the issues with all the virtual machines running on that host, as well as issues with the ESX host server itself.
How probable cause analysis handles VMotion events

In addition to considering system resource events, probable cause analysis also displays relevant virtual machine migration events for the host of the event for which probable cause analysis is requested, if that event is on the virtual machine or ESX host. When probable cause analysis is requested for a VMotion event, BMC ProactiveNet displays all the system resource issues on the VMWare ESX Host from where the VM is moved.
Limitations of probable cause analysis in a virtual environment

By default, probable cause analysis in a virtual environment is confined to VMWare metrics. ESX host and VM relationships imported from the BMC ProactiveNet CMDB Extensions 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 you add monitor instances of the type that are part of the VirtualSystem Attribute Set to the devices imported from the BMC ProactiveNet CMDB Extensions, probable cause analysis will leverage the ESX host and/or the virtual machine relationship between these devices.
By default, monitors related to PATROL virtualization are not added to the VirtualSystem attribute set. You need to add these monitors manually. For more information on managing attribute sets, see Managing attribute sets on page 443. For a list of monitors related to VMware, see Event information used in probable cause analysis on page 519
Note
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, advanced, 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. If you have created an event rule with an associated escalation action, then after you upgrade, the escalation actions are removed from the event rule and consequently are not triggered by the event. Instead of the BMC ProactiveNet escalation feature, 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). An escalation policy raises or lowers the priority level of an event after a specified period of time. A specified number of event recurrences can also trigger escalation of an event. Along with the escalation policy, you can create a notification policy to alert users of changes to an events severity level. You can also use an AlarmPoint integration to handle event
Chapter 4 Event administration 241
Understanding event thresholds
escalations. See Managing the AlarmPoint integration on page 280 for general guidelines. Paging capability is no longer supported. Support for the TelAlert product is discontinued.
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. The features are listed on the Administration tab under the Event Administration heading. Choose the corresponding Edit button to access detailed information about each option.

Events are generated when Event Threshold values are exceeded. The approach BMC ProactiveNet takes to detect abnormal behavior is different from the traditional threshold approach. The traditional approach requires the definition of hard thresholds that need to be customized for each instance. This requires precise knowledge of the environment and is not very scalable in terms of administration. Table 46 on page 242 describes the types of event thresholds that BMC ProactiveNet offers.
Table 46: Types of event thresholds Threshold type Absolute threshold Description Absolute thresholds represent an absolute value above or below which an event is generated. In general, an absolute threshold is specified for attributes that have common accepted values beyond which performance is known to degrade. Absolute thresholds are better suited for attributes that change status. For example, if the total CPU utilization of Solaris System is above 80%, it may result in performance issues. In this case, you can specify an Absolute threshold of 80% for this attribute.
Threshold type Signature threshold
Description Signature thresholds are dynamic thresholds that use the baseline as the threshold. Users do NOT need to set a threshold value, as the baseline is autogenerated. Because of this, it is a much more scalable approach in managing thresholds Signature thresholds focus on performance metrics such as response time, utilization, errors for network devices, LANs, WANs, servers, and network application services, reporting readings above or below the baseline. Signature thresholds allow you to control the number of events generated by a monitor. 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. Signature thresholds are better suited for attributes that degrade over time. In case no signature threshold is enabled by the user, BMC ProactiveNet uses the default values to generate events.
Abnormality Event threshold BMC ProactiveNet Abnormality thresholds operate in the same way that Signature thresholds work. However, they generate abnormality events utilized by Probable cause Analysis correlation rather than generate events. Abnormality thresholds are automatically set (out of the box) on all metrics. 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. Abnormalities are used in Probable cause analysis, generally do not generate events, and are automatically closed when the generating condition no longer exists. Predefined Abnormality Event thresholds cannot be removed or cleared for any of the attributes. If the abnormality threshold is suppressed for any of the attributes, baselines are not generated and events are not triggered for those attributes. To disable the abnormality threshold select Suppress event and click Apply in Advanced option.
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. These help to alleviate issues with Absolute values that are set too low for the normal operating environment. Intelligent thresholds provide the following benefits: They reduce the aggravation to manually set and maintain hundreds of absolute thresholds. They reduce false events to a large extent, by guessing what the threshold should be for each attribute and device at any time or day of week. This eliminates the problem of over, or under, alerting. They facilitate faster detection of potential problems. This allows you to fix problems proactively.
Related Topics Setting event thresholds on page 246
Baselines
The baseline is the expected normal operating range for a metric or attribute of a monitor. The baseline is calculated by collecting the values for a monitors 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), taking a weighted average of these values over time. A higher weight is given to the latest data being factored into the baseline average. The accuracy of the baseline improves over time. To track the anomalies in behavior for different attribute types different patterns are required. For example, for attributes that change frequently, a pattern captured at hourly intervals may be best. Hourly interval ranges represent a smaller number of data points and will have a tighter range, which is best suited for capturing frequent changes. BMC ProactiveNet captures the following baseline patterns:
Hourly baseline - Each hour of the day has a high or low value that is tracked.
This tracks the pattern for that metric on an hourly basis, and is repeated for each
day. An hourly baseline is initialized after the monitor instance is created and 24 hours of data collection has occurred.
Daily baseline - A high or low value is derived from the moving average of each
consecutive day. This high or low range is taken from a larger number of data values and consequently will be a wider range than the hourly. A daily baseline is initialized after the monitor instance is created and 24 hours of data collection has occurred. days share the same 24-hour baseline. A weekly baseline is initialized after the monitor instance is created and 168 hours of data collection has occurred. and Sunday. These two days share the same 24-hour baseline.
Weekday Pattern - Baseline is calculated daily from Monday to Friday. All these
Weekend Pattern - Baseline is calculated separately for the weekend - Saturday
Seasonal baseline - Baseline is calculated separately for pre-determined days
when your business experiences out of the ordinary workloads or other special behavior. These days, if calculated into the baseline, artificially will raise or lower the baseline, causing unnecessary abnormalities.
Auto-baseline
Out of the box thresholds are set to use Hourly, Daily, Weekly, or All baselines, this works well in majority of the cases, but it might be more appropriate to use one specific baseline type in order to catch the exceptional behavior. 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. By default auto-baseline feature is enabled for new customers, out of the box thresholds will have auto-baseline option set. For upgrade users the Auto-baseline feature is enabled, but the user has to set threshold with auto-baseline option manually.
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.
The abnormalities generated have a severity field, which records which baseline was exceeded for a significant number of points (helping determine the severity of the abnormality). Generally, abnormalities that exceed Weekly baseline are more serious in nature than ones that exceed Daily baseline, and abnormalities that exceed Daily baseline are more serious in nature than ones that exceed Hourly baseline. By default, if no signature threshold is set, abnormalities are still generated. A minimum of five data points are required. If the sample window is set too small (sample window is set in time duration), the algorithm will still automatically wait for five data points to come in. For example, if you set a sample window to 10 minutes on a specific monitor attribute but the polling rate of that monitor is 5 minutes, 25 minutes must pass before an abnormality is generated. For this reason, it is better to use lower polling rates for monitors. Abnormalities are closed when the number of data points exceeded in the last window sample size is not considered significant. For example, if six out of seven data points out of range are statistically significant, then as soon as the last exceeded points drop to five out of seven points, the abnormality will be closed. By default, even if no explicit global or instance signature threshold is set, BMC ProactiveNet will generate abnormalities for above baseline conditions.
Setting event thresholds

The display of threshold options such as Edit Absolute Global Threshold, Absolute Instance Threshold, Signature Global Threshold, and Signature Instance Threshold depends on the access type of the monitor, and permission to set thresholds. You will be able to set thresholds on a monitor only if you have write access to the monitor (user group is present in the WLS field of the CI to which the monitor is associated), and permission to set instance or global thresholds. If you select an event on which to set the threshold, and the CI to which the event belongs has write access, only then are the various threshold options displayed in the Tools menu. If the threshold is an instance threshold and the user has permission to set instance thresholds, then the instance thresholds menu will display. The global threshold options will be displayed only if the user has permission to set global thresholds.
In the BMC Cloud Lifecycle Management environment, out-of-the-box threshold values are not set for storage and network monitor types. This is because these values are absolute values in BMC Cloud Lifecycle Management and a range cannot be set for such values. If you have permission to set both instance and global thresholds, the threshold options will be displayed. Note that the Intelligent Event history page represents the event and the threshold on which the event was raised. If the event was generated by setting an instance threshold, and the user has instance threshold permission, then only the instance threshold option is displayed in the Intelligent Event history page. When a user does not have permission to set thresholds (instance and global), the following changes are evident in the display:
The Threshold link in Options > Administration appears as locked. The Tools menu for monitors does not show the thresholds-related menu options.
Note
Click the Advanced link to set thresholds with minimum sampling window, threshold, absolute deviation, and percentage deviation. This option is applicable only for Signature and Abnormality Event thresholds.
To set event thresholds

1 On the Event Summary tab, 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. 3 From the Tools list, select the threshold to create based on the type of threshold (absolute, signature, or abnormality) and the level of coverage (either global for all instances or for a particular monitor instance or event). Alternatively, you can reach the threshold setting through the Options => Administration tab. Click the Edit link beside Intelligent Event Thresholds and then click Edit for the relevant monitor type and threshold type. To set Abnormality Event thresholds, click Edit link beside Abnormality Events.
Note
4 Set threshold values for the relevant attributes using the parameters displayed on the Edit Thresholds screen, as summarized in Table 47 on page 248. Table 47: 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 12 parameters that are KPIs for the application. Name of the monitored attribute to which the threshold setting applies. Severity of the event createdMinor, Major, 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. The same duration is required to close an event, starting with the first data point where threshold is no longer violated.
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 >, <, ==, >= or <=. This is available only for the Absolute Global and Instance Thresholds. For example, if you select the >= operator for an attribute and set the threshold value to 90%, events are generated when the threshold value is greater than or equal to 90%. The range of values for which events are triggered. This range does not include the threshold. For example: Above checked - An event is generated if data is continually greater than the threshold for the specified duration. Below checked - An event is generated if data is continually lesser than the threshold for the specified duration. Outside Baseline The baseline to associate with the threshold. This helps to reduce false events associated with latest trends. For example, response time may be higher during peak time. In this case, associating the response time with appropriate baseline will cover any false event. If you select Auto-baseline on page 245 an event is generated accordingly. Other options are Hourly, Daily, Weekly, Hourly and Daily and All Baselines. Predict Select this option to generate predictive events. For more information, see Viewing predictive events on page 124.
Threshold
Item Auto Close
Description Clear this option if you do not want BMC ProactiveNet to automatically close the triggered event, when it returns to normal state. This is useful for events that have a very short duration.
Parameters for signature or abnormality thresholds Above or Below Reference point for the following parameters: Above High - Above the High baseline Below Low - Below the Low baseline Auto-baseline - an event is generated accordingly. Other options are Hourly, Daily, Weekly, Hourly and Daily and All Baselines. For more information see Auto-baseline on page 245. Minimum Sampling Window 1 Threshold 1, 2 Define minimum window of time to keep raw data points that will be considered for intelligent threshold computation. Data points outside this range are usually discarded. The threshold field is used as an additional constraint, which must be met for the Signature Event to be generated. Usually, a signature event is generated if the data values go outside the baseline range. When the threshold field is set, it additionally requires the data to be above or below the threshold value. This is useful to filter out insignificant abnormalities. Deviation is a way of introducing tolerance into the baseline values. If there is a small change in baseline that is not significant for reporting purposes, deviation can be set to ignore this small change. For example, if baseline low value is 40, baseline high value is 100, and deviation is set to 2, then a signature event will be generated when the average of all data values inside the threshold duration goes above 102 or below 38. The deviation value is additive (not multiplicative) and is given in the same units being measured by the particular monitor attribute (that is #,%, bytes, milliseconds, and so on). The default value for Absolute deviation is 5 units. Percent Deviation has the same meaning as the existing deviation field, except that the actual value of the deviation is expressed in terms of a percent of the baseline value (rather than an absolute value).The default value for percentage deviation is 5%. (Abnormality events only) If suppress event is enabled baselines projection and abnormality detection will not happen for that specific attribute.
Absolute Deviation 1, 2
Percentage Deviation 1, 2
Suppress Event 1
1 Advanced parameter 2 Threshold, Absolute Deviation, and Percentage Deviation are additional filters for triggering events. All set values must be exceeded to trigger an event. No event is generated if a single value is exceeded.
Managing event rules
Note Click the Advanced link to set thresholds with minimum sampling window, threshold, absolute deviation, and percentage deviation. This option is applicable only for Signature and Abnormality Event thresholds.
5 Select the Enabled check boxes for all relevant attributes, and then click Apply. Related Topics Understanding event thresholds on page 242

Event rules define the set of actions that can be performed when an event occurs. To define event rules, you must be assigned Allow Event Rule Management privileges by the BMC ProactiveNet administrator. You perform event rule management from the Event Rule Administration page. To display the Event Rule Administration page, choose Edit next to the Event Rules entry under the Event Administration heading on the Administration tab. The Event Rule Administration page displays the list of event rules. Depending on your privileges, you can see your event rules or, as an administrator, you can view all event rules.
Default event rules

A group of default event rules are provided out-of-the-box. 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. When any one of the threshold values are exceeded, an event is triggered. Table 48: Attributes of default event rules
Event rule JVM Monitor Included Attributes Selected Action(s) JVM/Thread Count, Process CPU time Diagnostics/Remote Actions: JVM Detail Diagnostics Default event rule
Linux - Top Processes by CPU Included Monitors Linux System
Event rule Included Attributes Selected Action(s)
Default event rule Total CPU Utilization DD_Command: Top Processes-CPU(Linux)
Linux - Top Processes by Memory Included Monitors Included Attributes Selected Action(s) Linux System Swap Space Used DD_Command: Top Processes-Mem(Linux)
Oracle - Top SQL Statements Included Monitors Included Attributes Selected Action(s) Solaris - Top IPs by Traffic Included Monitors Included Attributes Selected Action(s) SolarisTM TCP Bytes Received, Bytes Sent DD_Command: Top IP Traffic Oracle Intelliscope, Oracle Query CPU Usage by Sessions, 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 - Top Processes by Memory Included Monitors Included Attributes Selected Action(s) WebLogic - Active Info Included Monitors Included Attributes Selected Action(s) WebSphere - Top EJBs Included Monitors Included Attributes Selected Action(s) WebSphere - Top Servlets WebSphere Thread Pool Maxed, EJB Activates, EJB Avg Method Response Time, EJB Passivates, EJB Total Method Calls, Web App Response Time DD_Command: TopEJBs-WebSphere WebLogic Server 6.1, 7.0, or 8.1 JVM Memory Used, Execute Queue Usage DD_Command: ActiveInfo-WebLogic Solaris System Swap Space Used DD_Command: Top Processes-Mem(Solaris)
Event rule Included Monitors Included Attributes Selected Action(s) Web URL - Get Page Included Monitors Included Attributes Selected Action(s)
Default event rule WebSphere Thread Pool Maxed, EJB Activates, EJB Avg Method Response Time, EJB Passivates, EJB Total Method Calls, 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 - Top Processes by CPU Included Monitors Included Attributes Selected Action(s) Windows System System CPU Utilization, Total CPU Utilization, User CPU Utilization DD_Command: Top Processes-CPU(Windows)
Windows - Top Processes by Memory Included Monitors Included Attributes Selected Action(s) installation. Windows System Swap space used DD_Command: Top Processes-Mem(Windows)
a The default event rule will not be created if the administrator E-Mail ID is not provided during server
Filtering the event rule list

The Action Type, Rule Type, and Status lists display the No Filter value by default. The remaining filtering fields are left blank. Consequently all event rules that you have permission to view are displayed. To focus on specific categories of event rules, you can filter the list according to the various criteria for managing event rules.
To perform the filtering action

1 On the Event Rule Administration page, choose values from among the following filter criteria described in Table 49 on page 253. You can specify one or more filter criteria. Table 49: Event rule filtering criteria
Fields Action Type Options List containing values indicating the actions that you can associate with an event. These actions include: No Filter E-Mail SNMP Trap Run Server Command Remote Actions/Diagnostics E-Mail Group RSD Incident BEM event AO event Groups Lists the available groups that you associate with the event. Click No Filter to open the Group Filter dialog box. You can choose to include or exclude selected groups. After making your selection, click Apply. Text box where you can enter a full or partial string to retrieve matching event names List that contains the available rule types. Valid values are No Filter Basic Advanced
Rule Name Rule Type
Fields Status
Options List of the event status values: No Filter Enable Disable
Email groups associated with event rules cannot be filtered.
Note
Event rule types

Event rules are designated by one of the following types described in the following table.
Table 50: Event rule types Type Basic Description This rule type is used to trigger the full range of actions for BMC ProactiveNet intelligent events, for external device-associated events, and for external events triggered by event adapters. It is often used to trigger email notifications. When distinguishing a basic event rule type, you can choose to select an intelligent event type, an external event type, or both (the default). If you select an intelligent event type only, you can specify the full range of monitor type, event, and abnormality, and predictive event filter options. If you select an external event, then you can specify only the severity level and event state (open, close, acknowledged, and/or assigned) filter. Advanced This rule type is used to trigger the full range of actions for ProactiveNet intelligent events, not external events. It is often used to trigger diagnostic and remote actions. When distinguishing an advanced rule type, you can specify monitor types and instances, together with their attributes; an event state filter notification for the event statuses open, close, acknowledge, and assigned; and an abnormality event filter.
Event rules or event management policies

Event rules can trigger actions that overlap with actions that event management policies can also trigger. (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.) For example, an event rule can trigger an email notification in much the same way as an event
management notification policy can. Generally speaking, event rules are easier to configure and execute than event management policies. Nevertheless, if you are building an advanced rule type that uses multiple event slot values, using an event management notification policy with detailed event selector criteria might be the preferred choice.
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.
To add a basic event rule

1 On the Administration tab, click Edit next to the Event Rules entry to display the Event Rule Administration page. 2 Click Add to display the Add Event Rule (Page 1/3) window. 3 On the Add Event Rule (Page 1/3) screen, complete or modify the text boxes and selections listed in the following table: Table 51: Fields on the Add Event Rule (Page 1/3) window
Item Event Rule Name Description Time Range/Schedule Description Required. Alphanumeric string that describes the name of the event Description of the event You can select either the Time Range or the Schedule option. Time Range: Time of Day Range - Select the time range in days. To include 24 hours, select 00:00-00:00. Days of Week - Select this option to include the day of the week. Schedule: Click New to create a new schedule or Edit to edit an existing schedule from the list. For detailed steps, see Managing schedules on page 474 Temporarily disable Event Rule Event Rule Type Groups Filter Disables the event from being applied immediately Click Basic Event Rule.
Item No Filter Include Selected Groups Exclude Selected Groups
Description The No Filter option is available to all users. Select No Filter to apply the event rule to all monitors. Include Selected Groups: Applies the event rule to the selected group. Exclude Selected Groups: Does not apply the event rule to the selected group. If you choose either the Include Selected Groups or Exclude Selected Groups option, then only device-associated events trigger the event rule. If you choose No Filter, then both device-associated and non deviceassociated events can trigger the event rule. Use an event management policy to trigger non device-associated events exclusively. See the Event Policy tab of the BMC ProactiveNet Administration Console.
Available Groups Selected Groups Hierarchy
Available Groups lists only those monitors in the group which you can access. Select from the list and use the arrows to move it to the Selected Groups.
Use hierarchy on or off to switch over to the corresponding view type.
4 Click Next to display the Add Event Rule (Page 2/3): Select Event/Monitor/ Severity Information page. Complete the options listed in the following table: Table 52: Event, monitor, and severity options of event rules on the Add Event Rule (Page 2/3): Select Event/Monitor/Severity Information window
Options Event Type Filter Description
Options Intelligent Events External Events
Description 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. BMC ProactiveNet Operations Manager (POM) users do not see Intelligent Events. External Events: External events refer to device-associated events and events received from external event adapters. By default, both options are selected. You can select one or both options. When you select both Intelligent Events and External Events options, then you enable the filter options that apply to both options: Event severity filter (but not the relationship direction Any, Up, or Down) Event states Open, Close, Acknowledge, and Assigned Upon selecting both Intelligent Events and External Events options, the following filters are disabled: Monitor Type filter options Relationship direction Any, Up, or Down options of the event severity level Abnormality and Predictive event filters For External Events, remote actions apply only to device-associated events. Run Agent Diagnostic actions, however, apply only to Intelligent Events. Note for upgrade users: If you have an existing basic event rule without external 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. If you have an existing basic event rule with external events, then the event rule is upgraded and mapped to a basic event rule with the External Events option selected and the Intelligent Events unchecked.
Monitor Type Filter
Options No Monitor Type Filter/Select Monitor Types
Description Select No Monitor Type Filter, if no specific monitors are needed. By default, this will enable all available monitors. 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.
Severity/State Filter Event tab Any Triggers event rule for any severity level that matches the specified severity. 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 258 BMC ProactiveNet User Guide 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
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. Triggers event rule every time when an abnormality is closed. Use this option to filter abnormal events that have abnormality score from the list.
Specifies the severity level of the predicted event. 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 53: 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
Options To Message Format
Description Recipient e-mail address. 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. For detailed steps, see To create or edit an E-Mail Group on page 268 Customizes the settings for all email alerts. For more information, see Customizing event text on page 309. Click Add to include a Send Email action.
Send SNMP Trap action SNMP Host (Name/IP) To send events to a management system that accepts standard SNMP traps, enter the SNMP host name or IP address, and click Add. For detailed information see, Managing BMC ProactiveNet events through SNMP traps on page 268.
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. Then click Add. Note: To add an AlarmPoint notification for a data-only implementation, create an event rule using the AlarmPoint command. Enter the pw_AlarmPoint - u userName in the Path field. If you do not enter the user name, the event is sent to the default user. E-mail will be sent to the configured user. See also Managing the AlarmPoint integration on page 280. For detailed information on the run command, see Managing BMC ProactiveNet events through Run Command on Server on page 278. Run Agent Diagnostics For systems running BMC ProactiveNet agents, add a preconfigured command to an event rule using the Agent Diagnostics Command. Then choose the process to inquire about from the list, and click Add. See also Managing BMC ProactiveNet events through Diagnostic Commands on the BMC ProactiveNet Server on page 279. Run Agent Diagnostic actions apply to intelligent events.
Options Run Remote Actions/Diagnostics
Description For systems without BMC ProactiveNet agents, create and register a userdefined command to associate with the event rule. Then choose the process to inquire about from the list, and click Add. See also Managing BMC ProactiveNet events through Diagnostic Commands on the BMC ProactiveNet Server on page 279. Remote actions are triggered by device-associated events, where the device is the target system on which the remote action is executed. The event must be mapped to the device through a device alias. The device must have its authentication credentials defined so that the remote action can access the device.
Integrate with BMC Remedy Service Desk, 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). For detailed information see, Integration configuration for event actions (Remedy Service Desk) on page 281.
Send event to BMC Event Manager Sends an event to BMC Event Manager (BEM). For more information see,Integration configuration for event actions (BEM) on page 292. Send event to BMC Atrium Orchestrator Integrate with BladeLogic Execute Blade Action Runs the snapshot on BladeLogic automatically. Do not use this action for any other event rule apart from DefaultRule-BladeEvent. For more information see Integrating with BMC Server Automation on page 487. Sends an event to BMC Atrium Orchestrator. For more information see, Managing BMC ProactiveNet events BMC Atrium Orchestrator (formerly known as BMC Run Book Automation) on page 300.
6 After adding actions to the event, click Done to save the event rule type and its attributes.
The newly created event rule is displayed in the event rule list of the Event
Rule Administration page.
Note The triggering of action happens on any specified event when the event rule is satisfied even when the other slots or information are changed.
Adding an advanced rule type

Add an advanced event rule type to trigger actions, including remote and diagnostic actions, on monitored, attribute-level events. Advanced rule types apply only to intelligent events.
To add an advanced rule

1 Complete steps 1 through 3 as described under To add a basic event rule on page 255. Be sure to select the Advanced Rule option under Event Rule Types. 2 Click Next to display the Add Advanced Rule (Page 2/3): Select Attribute Information page. The Attribute, Instance, or Severity Filter selections are based on the filter options you chose to include or exclude on Page 1/3. 3 To include all instances of a particular monitor type, select Monitor Type and Attribute under Attribute/Instance/Severity Filter, and click Add to display the Monitor Type Filter dialog box. a In the Monitor Type Filter dialog box, select the monitor type or types. The corresponding attributes are displayed. b Select one or more of the corresponding attributes, and click Add. The attributes are displayed in the Selected Attributes table. 4 Alternatively, to include specific instances of a monitor, select Monitor Instance and Attribute and click Add to display the Instance Selector window. a Select one or more monitor types, and click Next. The monitor instances and respective attributes are displayed. b Select one or more instances and attributes, and then click Apply. The instances and attributes are displayed in the Selected Attributes table. You can select and add monitor types and attributes together with monitor instances and attributes. 5 In the Selected Attributes table, specify a severity level for each attribute. The default is abnormality. You can choose from the following severity levels:
Abnormality Predictive Minor Predictive Major Predictive Critical
Note
Minor Major Critical
6 Indicate whether you want to include severity levels greater than the selected one by selecting the and higher option. 7 Select which attributes you wish to associate with the event. (You can click Delete to remove selected attributes.)
Note The selections that you make in the Selected Attributes table are based on the current filter selection. If you modify the filter selection later, the selected attributes remain the same because they are based on the original filter selection.
8 Under Event State Filter, 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, specify a value, or no filter under Abnormality Score Filter. 10 Click Next to display the Add Event Rule (Page 3/3): Action Information 11 Complete the options listed in Table 53 on page 259. 12 Click Done to save the event rule type and its attributes.
Editing a basic or an advanced rule

To edit any of the rule types, click Edit next to the corresponding rule in the event rule list of the Event Rule Administration page. In the Event Rule wizard, you can edit any field except for the event rule type. The procedures are the same as for adding an event rule.
WARNING When editing an existing basic event rule, you need to determine the impact that the selection of an external event type, intelligent event type, or of both types would have on actions that are already assigned to the event rule. For example, if you edit a rule that originally applied to both external and intelligent event types so that now it applies to external events only, then any Run Agent Diagnostic actions, which apply to intelligent events only, would be removed from the event rule definition.
Deleting an event rule

The deletion action removes the event rule and its related actions from the BMC ProactiveNet server.
To delete an event rule

1 On the Event Rule Administration screen, select the corresponding check box under the Select column to delete an event rule. 2 Click the Delete tab. 3 Click OK in the confirmation screen. BMC ProactiveNet deletes the event rule and refreshes the Event Rule Administration window.
Updating event actions

Through the Update Action tab, you can add, modify or delete any actions of the event rule. By default, the Update Action tab is disabled. Any updates to an event automatically trigger corresponding notification events.
To update event action

1 On the Event Rule Administration window, select the event rule which requires changes. To select all the event rules click Select All. 2 Click Update Action. The Update Action screen appears. 3 Select the desired Action Type to update action. 4 Click Apply to update the action.
Enabling and disabling event rules

Event rules are associated with different actions such as sending an email, run scripts on remote target, send events to BEM and so on. You can suppress these actions by disabling the entire event rule. Enabling event rule would re-instantiate all the actions.
To enable or disable an existing event rule

1 On the Event Rule Administration screen, select the corresponding check box under the Select column to enable or disable the event rule. 2 Click the relevant option:
To enable an event rule, click Enable. To disable an event rule, click Disable.
3 Click OK in the confirmation screen. The status of the selected event rule gets changed.
Supplying arguments to a server command

By default, the server passes nine arguments to the script or program that is executed as a result of an event action launch. 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> - Description of the event <Event ID>: Unique ID of the event associated with the event. Event ID is
different for each new event that affects the state of the event. For example, if an event transitions from high to critical, that is a new event, accompanied by it's own event ID. When the event closes, that is also a new event.
< Intelligent Event ID>: Unique ID of the intelligent event. Intelligent Event ID
remains constant for the duration of the intelligent event, i.e., until it closes.
<Device IP>: IP address of the device hosting the monitor from where the event
originated. Device IP is a string denoting the 4 octets of the device IP address. For event actions triggered by SNMP based monitors, the source agent will always be the IP Address of machine hosting the BMC ProactiveNet Server.
<Source Agent IP>: IP address of the device hosting the BMC ProactiveNet Agent.
Heres an example of a script that was launched with only the default arguments:
/usr/pw/pronto/usr_apps/bin/notify.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. Heres an example of passing 'value1' and 'value2' into the event script. Note the use of the 'flags' parameter:
/usr/pw/pronto/usr_apps/bin/notifycce.csh&flags=value1&flags=value2
Separating the values using the ampersand and the term flags (&flags) is optional. When additional user arguments are specified, they are passed into the script before the default arguments. Heres an example:
/usr/pw/pronto/usr_apps/bin/notify.csh value1 value2 rule_name time_stamp device_name severity status description eventId AlarmId
Note
Default arguments are passed into the script, regardless of whether the event scripts intend to use them or not. The scripts can simply ignore these arguments if they are not needed. User-defined arguments are passed first to the server, followed by the default arguments.The default arguments are passed in the order given above. For an example of a script that uses these parameters, see /usr/pw/pronto/bin/
generic_script.pl.
Note
While passing arguments to command on server, do not pass + character as an argument. The character + is used as a keyword internally by the BMC ProactiveNet Server. For example, if the Command on Server is specified as 'chmod +x abc.sh', ProactiveNet Server will execute the command chmod x abc.sh. This may lead to unexpected results. The workaround is to write the command in a script file and execute the script using Command On Server Action.
Note
Defining email groups

An email group is a group of email addresses by which event rule actions, can be sent to an email group. The group consisting of email addresses is notified. 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. When setting up event rules, you must determine the way in which event notifications will be sent. BMC ProactiveNet can send event notifications through e-mail when an event is generated. event e-mails contain the same information as the events viewed from the event Summary page. E-mails can be sent in HTML format. E-mail notification, which includes the event listing, is similar to how it would be viewed from the BMC ProactiveNet Operations console. If your e-mail client supports HTML format, relevant graphs can be viewed. Details of the SMTP Server to be used for email alerts are stored in pronet.conf under installDirectory /pw/custom/conf:
pronet.api.emailer.smtp.host=mail.bmc.com pronet.api.emailer.smtp.port=25
These entries are dynamically generated. Please refrain from editing these without prior impact assessment. Any changes to these entries will impact all mail related BMC ProactiveNet actions (event notification/reports/alerts). HTML event notifications contain partial GIFs of the event summary detail, along with the event graph. It is important that your ISP, e-mail client, and network support HTML e-mails. HTML format is preferred if your e-mail client supports it. HTML provides for enhanced report layout and inclusion of graphs. Similarly, subject and body of a particular Email Alert can also be customized using Event Text Customization for Individual Event Rules.
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. File size is often limited to 2MB. Check with your administrator. In case of notification through HTML e-mail, timestamp included in the subject refers to the time when the threshold was first crossed. The actual time of event generation could be much later, depending on threshold duration and polling interval.
Note
To create or edit an E-Mail Group

1 On the Event Rule Administration page, click the E-Mail Group Administration tab. 2 On the E-Mail Group Administration page, click Add 3 Type the name of the group and list of e-mail address. 4 Select the preferred E-mail type from the list. 5 Click Add to add the E-mail group. 6 Click Done to save the E-mail group options.

Through the action options of event rules on the Add Event Rule (Page 3/3): Action Information for Event Rule window, you can manage all events in the external environment monitored by BMC ProactiveNet. This external environment also refers to integrations with the following BMC products: BMC Remedy Service Desk, BMC Event Management, and BMC Atrium Orchestrator.
Managing BMC ProactiveNet events through SNMP traps

Use the following procedure to specify event notifcation based on SNMP traps. 1 From the BMC ProactiveNet Operations Console, select Options->Administration>Event Rules. The Event Rule Administration screen is displayed.
2 Click Add. Do not change any of the other fields. The Add Event Rule screen is displayed.
3 In the Event Rule Name field, enter a name for the rule, such as SNMP Trap. 4 Click Next. The Add Event Rule: Select Event/Monitor/Severity Information screen is displayed.
5 Deselect the External Events option.
6 Click Next. The Add Event Rule: Action Information for Event Rule screen is displayed.
7 In the Send SNMP Trap area, enter the name or IP address of the target SNMP host in the SNMP Host field. If you want to manage events from Computer Associates Unicenter NSM traps, you must run the Computer Associates Unicenter NSM integration utility available at <ProactiveNetServer_installDir>\pw\apps3rdparty\CAUnicenterNSM.
Note
BMC ProactiveNet SNMP trap details

The BMC ProactiveNet Enterprise OID is 1.3.6.1.4.1.3287.2.2. Variable bindings that are sent as part of the BMC ProactiveNet trap are: Table 54: BMC ProactiveNet Trap Variable Bindings
OID 1.3.6.1.4.1.3287.2.1.1.1.1 1.3.6.1.4.1.3287.2.1.1.1.3 1.3.6.1.4.1.3287.2.1.1.1.4 1.3.6.1.4.1.3287.2.1.1.1.5 1.3.6.1.4.1.3287.2.1.1.1.6 1.3.6.1.4.1.3287.2.1.1.1.7 1.3.6.1.4.1.3287.2.1.1.1.8 1.3.6.1.4.1.3287.2.1.1.1.9 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. By default, the value is set to 100. ifType of Interface. By default, this OID is sent blank. ANY (0), CLOSE (0), ABNORMAL (1), MINOR (2), MAJOR (3), CRITICAL (4), REPORT (5), SLA (6), UNKNOWN (7), OK (8), INFO (9), WARNING (10), PREDICTIVE_MINOR (0x101), PREDICTIVE_MAJOR (0x102), PREDICTIVE_CRITICAL (0x103) Status of the event. Can either be OPEN or CLOSED event description Device types to which this event is related are AppServer, DBServer, FireWall, Other, Mail Server, Remote Agent, Router, Server, Switch, WebServer. Threshold type that is whether it was Absolute, Signature, Change-Event or Imported Event. Threshold Type is an integer defined as 156: Crossed absolute threshold. Applicable to all instances of specified monitor type157: Crossed signature threshold. 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.161: Crossed absolute threshold. Applicable to a specific monitor instance162: Crossed signature threshold. Applicable to a specific monitor instance event rule name.
1.3.6.1.4.1.3287.2.1.1.1.10 1.3.6.1.4.1.3287.2.1.1.1.11 1.3.6.1.4.1.3287.2.1.1.1.12 1.3.6.1.4.1.3287.2.1.1.1.13
1.3.6.1.4.1.3287.2.1.1.1.14
OID 1.3.6.1.4.1.3287.2.1.1.1.15 1.3.6.1.4.1.3287.2.1.1.1.16 1.3.6.1.4.1.3287.2.1.1.1.17 1.3.6.1.4.1.3287.2.1.1.1.18 1.3.6.1.4.1.3287.2.1.1.1.19 1.3.6.1.4.1.3287.2.1.1.1.20 1.3.6.1.4.1.3287.2.1.1.1.21 1.3.6.1.4.1.3287.2.1.1.1.22 1.3.6.1.4.1.3287.2.1.1.1.23
Description Abnormality score. This indicates how closely the event relates to the probable cause of the problem. The URL of the page on BMC ProactiveNet web server where detailed information of the event can be found. Escalation information. event suppression. If set to true, the event suppresses other BMC ProactiveNet events. Device name. Monitor type. Instance name. More Info is an important piece of information for determining the reason for event. Device description.
HP OpenView integration
You can use HP OpenView in conjunction with the BMC ProactiveNet Server and Proactive Remote Agent (UNIX). HP OpenView integrates BMC ProactiveNet traps into Network Node Manager (NNM). The traps are correctly formatted and displayed in the Event Console. All BMC ProactiveNet traps are seen under the Pronto Proactive Events category. It also allows you to launch BMC ProactiveNet from the pop-up menu as well as the menu bar. MIB for the BMC ProactiveNet Server is also loaded so that you can use the MIB Browser and navigate down BMC ProactiveNet Server MIB. See the System requirements and product compatibility information in the online technical documentation for BMC ProactiveNet at http://docs.bmc.com/docs/ display/PN90/System+requirements+and+product+compatibility for compatible versions of HP OpenView Network Node Manager.
Note
Integration (for version 6.41 and later)

In addition to the integration package, BMC ProactiveNet provides an enhanced integration package for HP OpenView. 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
Prerequisites
The correct version of HP OpenView Network Node Manager must be installed
on a supported version of HP-UX. For supported versions, see the See the System requirements and product compatibility information in the online technical documentation for BMC ProactiveNet at http://docs.bmc.com/docs/display/ PN90/System+requirements+and+product+compatibility. read-write enabled Open View Map must be opened on the computer where the BMC ProactiveNet Integration package has been installed. For installation and uninstallation, it is not necessary that Open View Map be open.
For a status change to be reflected when a BMC ProactiveNet event is received, a
To install the new integration package

1 Source the Open View environment. This can be done by sourcing ov.envvars.sh or ov.envvars.csh. The default path for ov.envvars.sh under UNIX is /opt/OV/ bin. 2 Untar the ovproactivenet.tar file. The ovproactivenet directory is created. 3 Change directory to ovproactivenet. 4 Run the following command:
./instl-proactivenet-ov.sh
A welcome note displays, details of the installation log and its availability. A confirmation message to install the package appears. Click y (yes) The installer tries to determine the path to the browser executable. If the executable is not found in the default path, a message is displayed to supply the complete path to the browser. Once the browser path is determined, the installer installs the required registration, executable, symbol, and icon files in the appropriate directory. 5 After the installation is complete, 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. This can be done by sourcing ov.envvars.sh or ov.envvars.csh.
The default path for ov.envvars.sh under UNIX is /opt/OV/bin.
2 Change directory to ovproactivenet. 3 Execute ./uninstall to uninstall BMC ProactiveNet Package for HP Open View. 4 Restart Open View User Interface (ovw). 5 Remove BMC ProactiveNet Events category manually.
To delete BMC ProactiveNet events from the event browser:

1 On NNM Event Configuration Window, choose Options => Event Configuration. 2 On the Event Categories Window, choose Edit => Configure => Event Categories. 3 Delete the BMC ProactiveNet Events category. 4 Close Event Categories Window. 5 On the NNM Event Configuration window, choose File => Save. This deletes the BMC ProactiveNet Events category.
Viewing BMC ProactiveNet events on event browser
After installing BMC ProactiveNet Integration package, 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. To send SNMP Traps for events, create an event notification rule on the BMC ProactiveNet Server. 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.
Click Status corresponding to BMC ProactiveNet events to open the Event Browser for BMC ProactiveNet events. Each event message is shown in the following format: date trapSendingAgent trapMessage The options are listed in Table 55 on page 278.
Table 55: event message options

Option Date Trap Sending Agent Trap Message Description Time when BMC ProactiveNet trap was received. Time of the computer where HP OpenView is installed. BMC ProactiveNet Remote Agent that raised the event because of which the trap was generated. event received on ProactiveNetAgentHostname Description: ProactiveNetEventDescription event URL: URLToOpenProactiveNet EventDetailsPage
To view the event details page,

1 Select a BMC ProactiveNet event. 2 Select Actions => Additional Actions. 3 On the Additional Actions for BMC ProactiveNet Events screen, select Open ProactiveNet Event Page and click OK. 4 Select the Selected events check box. 5 Click OK to open the corresponding event details page. If no browser instance is open currently, then a new browser instance is opened. In this case, the user is required to log on to the BMC ProactiveNet Server.
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. You run the executables or scripts through the Run Command on Server You can run an application or script when an event occurs. Such applications or scripts can be used for escalation management, as well as event integration with other notification systems, such as AlarmPoint. They can also be used to send events directly to ticket systems such as BMC Remedy Service Desk. BMC ProactiveNet Administrator will choose the application or create the script and decide whether to run the application or script, on the server or on the agent system where the event occurred.
Path: Enter the script you want to execute when an event occurs.
The installDirectory /pw/pronto/bin/generic_script.pl script, which is provided as a model, shows how arguments can be passed to the script. The script can be modified and moved to the installDirectory /pw/pronto/usr_apps/bin directory.
Note While entering arguments to send server commands, do not enter the + character as an argument. The + character is used as a keyword internally by Proactive Server. For example, if the command on Server is specified as chmod +x abc.sh, Proactive Server will execute the chmod x abc.sh command. This may lead to unexpected results. The workaround is to write the command in a script file and execute the script using Command On Server Action.
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. Any exception that occurs while executing the command will be recorded in the ProactiveNet.log file in the installDirectory /pw/pronto/logs directory. If the BMC ProactiveNet Server stops responding, this log file can be checked for errors.
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, when a BMC ProactiveNet agent is installed and running
on the system
Run Agent-less Diagnostic/Remote Actions, 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. The Run Agent Diagnostics commands are predefined. You can select one to execute it. If the target system does not have an agent, you must define and register the remote action command and use the appropriate remote login protocol to retrieve the process information. See the BMC ProactiveNet Administrator Guide for information about diagnostic commands.
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. BMC ProactiveNet 8.0 is compatible with AlarmPoint for BMC Event and Impact Management (Advanced Edition), v. 2.1.0, and AlarmPoint Server 4. You can find the compatible AlarmPoint products at http://www.alarmpoint.com. The AlarmPoint integration can satisfy an event-only and a data-only implementation. Both implementations leverage the same AlarmPoint products. Follow the installation and configuration directions in the AlarmPoint documentation. Be sure to install the AlarmPoint client on the system where the BMC ProactiveNet cell server resides. For the data-only implementation, perform the additional configuration step described in the Remote Actions/Diagnostics chapter of the BMC ProactiveNet Administrator Guide.
Event-only implementation
In the event-only implementation, the AlarmPoint user goes through the BMC ProactiveNet Administration Console to create a notification event management policy specifically for AlarmPoint users. The AlarmPoint users are identified through a specially defined event criteria formula. When an incoming event matches the event criteria formula, it triggers the notification policy. The notification policy forwards the event to the AlarmPoint client, which forwards it to the AlarmPoint server and to the designated AlarmPoint users of the configured devicewhether it be SMS, e-mail, or phone messages. In the event-only implementation, the AlarmPoint user can perform management actions on the event, such as acknowledge, assign, close, and so forth. These actions are processed by the BMC ProactiveNet cell server. The notifications are then displayed in the Event List.
Data-only implementation
To prepare the data-only implementation, you must configure the installDirectory / custom/conf/pronet.conf file to enable AlarmPoint to communicate with the Product Short Server. See the Remote Actions/Diagnostics chapter of the BMC ProactiveNet Administrator Guide . You can create an event rule for AlarmPoint. In page 3/3 of the event rule wizard, you use the Run Command on Proactive Server action to define the action. Enter the
BMC ProactiveNet CLI pw_AlarmPoint -u userName in the Path field. When the event matches the event rule criteria, the event is escalated and the AlarmPoint user is notified. The data-only implementation is unidirectional. The AlarmPoint user cannot reply to the event with an action such as acknowledge. In either implementation, if an event notification fails, you can enable the debug option of the BMC ProactiveNet server and check for exception errors.
Managing BMC ProactiveNet events in the Remedy environment

An event generated in BMC ProactiveNet creates an AR system request in BMC Remedy Service Desk, 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. BMC ProactiveNet events based on Abnormalities also create AR System Requests. The severity of predictive events is changed to Warning before the AR System Request is changed. 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. When the event is closed in BMC ProactiveNet, the status of the AR system request gets changed accordingly as per the IBRSD setting. Ensure that Integration to BMC Remedy Service Desk (IBRSD) is installed to integrate BMC ProactiveNet and BMC Remedy Service Desk 7.0, 7.1, or 7.5.
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, click New. The Add RSD Configuration Details
window opens.
To edit an existing RSD Configuration, click Edit. The Edit RSD Configuration
Details window opens.
To delete an RSD Configuration, click Edit and then click Delete.
To add a new RSD Configuration

1 Click New to display the Add RSD Configuration Details window. 2 Choose the gateway entry from the IBRSD Gateway list. The gateway entries are populated from the mcell.dir file of the BMC ProactiveNet implementation that points to the IBRSD server. By default the Event Class is Event and Status is Active. 3 Click Done, and then click Close to return to the Add Event Rule (Page3/3): Action Information for Event Rule window. 4 After specifying the action for the event rule, click Add .
The added action is displayed under Actions To Perform.
Note
To remove a selected action

1 Select the action from Actions To Perform. 2 Click Remove. Specify all the actions for the event rule. 3 Click Done. BMC ProactiveNet returns to the Event Rule Administration screen. 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.dir file of the BMC ProactiveNet server cell.
cell cellName mchostIPaddress:3115
Note The default path of the mcell.dir for the Web Services Server is C:\Program Files \BMC Software\Impact\webServices\mcell. The default path of the mcell.dir for the BMC ProactiveNet server is C:\Program Files\ProactiveNet\pw\server \etc.
2 Rename the cell entry to the gateway entry gateway.ibrsd.
gateway.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, its severity level is set to warning.
Note
How the BMC ProactiveNet integration works with the AR System

The following block diagram explains the BMC ProactiveNet integration with AR System using IBRSD. Figure 9: BMC ProactiveNet integration with AR system using IBRSD
When an event is generated in BMC ProactiveNet, an AR System Request is
created simultaneously. When the event is closed in BMC ProactiveNet, the status of the AR request is changed in accordance with the IBRSD configuration.
The PN Event Sender reads the configuration file PN-ARS-Integration.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. IBRSD communicates with the IBRSD module installed in the AR Server and
creates an AR System Request on the AR Server.
Related topics: Configuration file details on page 285
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. If the event Id is the same for multiple BMC ProactiveNet events, the same ARS Request is updated at the AR System. In this case, only the status fields get updated. This is the business rule for Intelligent Incidents. If details, other than the status fields are to get updated in the AR System Request, the workflow at the AR System needs to be changed. The event data available at the time of event generation from BMC ProactiveNet, are sent to AR System. If you change the AR System Intelligent Incident business rule, the other details also get updated in the AR System Request. Related topics: External dependency on page 285 Setting up intelligent incident mappings on page 285 Limitation on page 287 Troubleshooting on page 287 High level flow chart on page 288 Event slots to AR system form field mapping on page 289
Note
External dependency
BMC Remedy Service Desk 7.0, 7.1, 7.5, or 7.6
Setting up intelligent incident mappings
Navigate to Quick Links on the Home Page of the BMC Remedy User application.
To set up intelligent incident mappings

1 Click the Custom Configuration tab. Figure 10: BMC Remedy Home Page
Figure 11: Custom configuration tab
2 Expand Integration for BMC Remedy Service Desk. 3 Expand Integration Configuration.
4 Select BMC Event Manager Incident Integration Setup. Figure 12: Incident integration setup
5 Add the contact information. Map each income severity to the appropriate severity in the AR system. Similarly for each incoming priority, map it to the appropriate priority in the AR System. Mention the status of the request when the event is closed.
Limitation
Once an AR System Request is closed in the Incident Management form, it cannot
be re-opened.
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,
use the AR System User Interface to check whether the Incident Management and Problem Management Applications are enabled.
Once the IBRSD configuration is complete, use the msend CLI to test the
msend -a EVENT -r CRITICAL -m "TestMessage" -b "mc_priority=PRIORITY_1;mc_ueid=UID_001;status=OPEN n @<IBRSDServer>:<IBRSDPort>#mc
installation. Send one event data point to IBRSD. Use the following syntax:
This should create an entry in the Incident form. If there is a failure in sending the data, the event data will be logged into the UnsentEvent log of the IBRSD.
Check whether the data exists in the Staging Form. Check the UnsentEvent log file in the IBRSD server.
If the data exists in the Staging Form and not in Incident Form, then the data point would have violated some of the workflow rules.
High level flow chart
This flow chart explains the functions of a PN Event Sender module.
The following flow chart explains the workflow in the AR System.
Event slots to AR system form field mapping

To map the Event Slots to AR System:
Edit DefaultMapping.map in the IBRSD server conf directory. Change the event slot names to AR System Form Field mapping. Use BEMUseCase maps for the changes.
You do not need to edit the DefaultMapping.map file if you have installed the IBRSD component that is part of the ProactiveNet server 8.0 installation package. The following event slot names are used to create the event data.
Note
Table 56: 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. Hence CRITICAL will be mapped to PRIORITY_1, MAJOR will be mapped to PRIORITY_2, and Minor will be mapped to PRIORITY_3 Severity [CRITICAL,MAJOR,MINOR, WARNING] Status [OPEN,CLOSED] BMC ProactiveNet DeviceInfo eventURL PNServerIP eventTime eventRule MonitorInstance PNServerName MonitorType EventScore HasDD eventAckStatus eventAckMessage BPMReconId. Host level Reconciliation ID stored in PN. In the case of BPM Adapter Monitor the Reconciliation ID is at the instance level. If the instance level Reconciliation ID is not blank, send it. Otherwise send the device level Reconciliation ID. When the event is created and if the Reconciliation ID is not blank, send that; if the Reconciliation ID is blank, dont send it. When the event is modified, Reconciliation ID is not sent. 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, 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
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.xml file under the installDirectory /pw/pronto/conf directory in the BMC ProactiveNet server. The Event Slot to AR System field mapping is done in the IBRSD DefaultMapping.map mapping file located in the conf directory of the IBRSD server. The BMC ProactiveNet event fields given in the diagram are fields that are available for use and they are case sensitive. Ensure that the following code is present in the DefaultMapping.map file in the IBRSD installations conf directory.
Short_Description=slot.msg $if(slot.product_tier1 != "") Product_Categorization_Tier_1=slot.product_tier1 Product_Categorization_Tier_2=slot.product_tier2 Product_Categorization_Tier_3=slot.product_tier3 $endif Event_Message=slot.msg Event_Priority=slot.mc_priority Event_Severity=slot.severity Status_Event=slot.status Mc_ueid=$Format("%s_%s",slot.mc_ueid,slot.pn_server_ip); Event_Requester=slot.submitter Event_Type="NEW" Keyword="BEM" z1D_FirstName="BEM" z1D_LastName="User" Application_Version="ITSM 7.0" Submitter=slot.submitter z1D_CellName=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_ueid,slot.event_rule,slot.event_time,slot.device_info,slot.monit or_type,slot.monitor_instance,slot.event_url,slot.pn_server_ip,slot.pn_serve r_name,slot.pn_event_score,slot.pn_event_has_dd,slot.pn_event_ack_status,slo t.pn_event_ack_message,slot.mc_smc_id,slot.mc_smc_alias,slot.mc_parameter,sl ot.mc_parameter_value,slot.mc_parameter_unit,slot.more_info);
Note
The above mapping is for the new events. Follow the same mapping to modify the events. The Work Info History list box in the Work Info Tab of BMC Remedy Service Desks Incident Management form captures the following details when a BMC ProactiveNet event is generated and if the AR System Request is created:
Note
Priority Severity Status Source Time and Date
The Work Info History list captures the above details for all the events, if multiple events are coming with the same mc_ueid. When multiple events are generated with the same event id (correlated events) but different severities, the ARS Request will have the severity of the latest event.
Note
Managing BMC ProactiveNet events in the BEM environment

An event generated in BMC ProactiveNet creates an event in BMC Event Manager, if the Send event to BMC Event Manager option is selected in the Add event Rule (Page3/3): Action Information for Event Rule screen. BMC ProactiveNet events based on Abnormalities also create BEM events. The severity of predictive events is changed to WARNING before the system creates the BEM Event. 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. When the event is closed in BMC ProactiveNet, the corresponding BEM Event also gets closed. Ensure that BMC Impact Solution is installed to integrate BMC ProactiveNet and BMC Event Manager.
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.
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:
For a new BEM event, click New. The Add BEM Configuration Details window
opens.
To edit an existing BEM event, click Edit. The Edit Configuration Details
window opens.
To delete an BEM event, click Delete.
To add new BEM configuration details

1 Click New to open the Add BEM Configuration Details window. 2 Select the BEM cell from the BEM Cell name list.
The cell name entries are populated from the mcell.dir file of the ProactiveNet
implementation that points to the BEM cell. By default the Event Class is PROACTIVE_INTELLIGENT_EVENT and the status is ACTIVE.
WARNING Do not select the local ProactiveNet server cell. 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. 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.
3 Click Done, and then click Close to return to the Add Event Rule (Page 3/3): Action Information for Event Rule window. 4 After specifying the action for the event rule, click Add. The added action is displayed under Actions To Perform.
To remove a selected action,

1 Select the action from Actions To Perform. 2 Click Remove. Specify all the actions for the event rule. 3 Click Done. BMC ProactiveNet returns to the Event Rule Administration screen. The updated event rule list is displayed.
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.dir of the BMC Impact Integration Web Services Server that is used by the BMC Event Management installation to the mcell.dir file of the BMC ProactiveNet server cell.
cell cellName mchostIPaddress:1828
The default path of the mcell.dir for the Web Services Server is C:\Program Files \BMC Software\Impact\webServices\mcell. The default path of the mcell.dir for the BMC ProactiveNet server is C:\Program Files\ProactiveNet\pw\server \etc. 2 Restart the BMC ProactiveNet server using the following command:
pw sys start
Note
Note In the integration with BMC Event Management, before an abnormality event is sent to the target application, its severity level is set to warning.
How the BMC ProactiveNet integration works with the BEM environment
The following block diagram explains the BMC ProactiveNet integration with BEM Event.
When an event is generated in BMC ProactiveNet, a BEM Event is created
simultaneously. When the event is closed in BMC ProactiveNet, the corresponding BEM Event is also closed.
The PN Event Sender reads the configuration file PN-BEM-Integration.xml (the
XML configuration file placed in the installDirectory /pw/pronto/conf) to determine the cell name pointing to BEM.
Transforms the event data to proper format and sends the event data to BEM.
Related topics: Configuration file details on page 295
Configuration file details

The configuration file details are as follows:
Cell Name Chapter 4 Event administration 295
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 296 BMC ProactiveNet BMC Event Manager cell event mapping on page 298
External dependency
Install a supported version of BMC Impact Solutions. For information on supported versions of BMC Impact Solutions, see the System requirements and product compatibility information in the online technical documentation for BMC ProactiveNet at http://docs.bmc.com/docs/display/PN90/System+requirements +and+product+compatibility.
High level flow chart
This flow chart explains the functions of a BEM Integrator module.
The following flow chart explains the workflow at the BEM System.
BMC ProactiveNet BMC Event Manager cell event mapping
The mapping between BMC ProactiveNet event Fields and Common Event Model complaint Slots is defined in the PN-BEM-Integration.xml file. This is located in the installDirectory /pw/pronto/conf directory in the BMC ProactiveNet server. To create an event in a BMC Event Manager cell, create the entries in the PN-BEMIntegration.xml file using the following mapping details:
Table 57: Mapping details PN Event Data AlarmId_PNServer IP Event Slot mc_ueid Comments Combination of eventId and BMC ProactiveNet Server IP. This is required if multiple ProactiveNet Servers are sending events to the same BMC Event Manager cell. String description of the event.
AlarmDescription
msg
PN Event Data no equivalent mapping field. The value is calculated instead.
Event Slot mc_priority
Comments In the BMC ProactiveNet event there is no concept of priority. CRITICAL is mapped to PRIORITY_1, MAJOR is mapped to PRIORITY_2, and Minor is mapped to PRIORITY_3. Severity determines how bad the technical problem is (device is up, down, somewhere in between); priority describes the business urgency (high, low, in between). Something that is down may have low urgency (for example if it happens on a Sunday). Data collection layer (ProactiveNet, PATROL, and so on) can usually not assess priority. [CRITICAL,MAJOR,MINOR, WARNING] [OPEN, CLOSED] BMC ProactiveNet Device IP Address For backward compatibility BMC ProactiveNet Server IP Address BMC ProactiveNet Server name Device name Cross-launch is enabled in the Event List for all slots that have hyperlinks included in their value. We send the eventURL to the mc_tool_uri slot. Combination of eventId and the BMC ProactiveNet Server IP address. This is required if multiple BMC ProactiveNet Servers are sending events to the BMC Event Manager cell. Event rule More information Monitor instance name Monitor type A slot in the event class for the BMC ProactiveNet 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 A slot in the event class for the BMC ProactiveNet events. pn_event_ack_status Event acknowledgement status. The pn_event_ack_status is defined as a slot in the event class for the BMC ProactiveNet events. Event acknowledgement message. The pn_event_ack_message is defined as a slot in the event class for the BMC ProactiveNet events.
AlarmAckMessage
pn_event_ack_message
PN Event Data BPMReconId
Event Slot mc_smc_id
Comments Host level Reconciliation ID stored in BMC ProactiveNet. In the case of BMC Performance Manager Adapter Monitor the Reconciliation ID is at the instance level. If the instance level Reconciliation ID is not blank, send it. Otherwise send the device level Reconciliation ID. When the event is created and if the Reconciliation ID is not blank, send that; if the Reconciliation ID is blank, dont send it. When the event is modified, Reconciliation ID is not sent. The attribute that caused the event. In the case of external events this slot 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.
AlarmAttribute
mc_parameter
AttrValueCausedEven mc_parameter_value t AttrValueUnit ComponentAlias mc_parameter_unit mc_smc_alias
Note When multiple events are generated with the same event id (correlated events) but different severities, the BMC Event Manager cell event reflects the severity of the latest event.
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. The active RBA Rules processes the event or event data, and after the successful rule validation an appropriate RBA Workflow is triggered depending on the specified logic. Please refer to the appropriate version of the BMC Atrium Orchestrator Development Studio User Guide for developing RBA Rules and RBA Workflow. All subsequent references to RBA in the User Guide would collectively mean BMC Run Book Automation and BMC Atrium Orchestrator. BMC ProactiveNet only supports unidirectional integration with RBA 3.0.06. BMC ProactiveNet also supports unidirectional integration with BMC Atrium Orchestrator 7.5.00.
Note
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.
Click the relevant option: For a new BMC Run Book Automation event, click New. The Add AO
Configuration Details window opens. window opens.
To edit an existing AO event, click Edit. The Edit Configuration Details
To delete an AO event, click Delete.
To add new AO configuration details

1 Click New to open the Add AO Configuration Details window. 2 Select the IMCOMM gateway from the AO Gateway Cell list. The IMCOMM entries pointing to the BEM-RBA gateways are populated from the mcell.dir file of the BMC ProactiveNet implementation that points to the BMC Atrium Orchestrator server. By default the Event Class is PROACTIVE_INTELLIGENT_EVENT and the status is ACTIVE. 3 Click Done, and then click Close to return to the Add Event Rule (Page3/3): Action Information for Event Rule window. 4 After specifying the action for the event rule, click Add. The added action is displayed under Actions To Perform.
Note
To remove a selected action

1 Select the action from Actions To Perform. 2 Click Remove. Specify all the actions for the event rule. 3 Click Done.
BMC ProactiveNet returns to the Event Rule Administration screen. 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.dir file of the BMC ProactiveNet server and by updating existing event rules that apply to the BMC Atrium Orchestrator integration.
To upgrade BMC Atrium Orchestrator integration

1 Add the gateway entry gateway.imcomm to the mcell.dir file of the BMC ProactiveNet server:
gateway.imcomm ao mchostIPaddress:1859
2 Restart the BMC ProactiveNet server using the following command:

pw sys start
3 Next, you edit existing event rules that apply to the BMC Atrium Orchestrator integration.
To update existing event rules that apply to the BMC Atrium Orchestrator integration
1 Open the BMC ProactiveNet Operations Console, and choose Options => Administration => Event Administration => Event Rules => Edit to open the Event Rule Administration page. 2 Select the event rule from the list, and click Edit to open the Edit Event Rule wizard. 3 Go to page 3/3 of the wizard, and click New next to the Send Event to BMC Atrium Orchestrator list under the Integration with BMC Remedy Service Desk, BMC Event Manager, and BMC Atrium Orchestrator title. 4 In the Add AO Configuration Details window, choose the gateway entry youve added to the mcell.dir file from the AO Gateway Name list. 5 Click Done to close the Add AO Configuration Details window. 6 Click Add next to the Send Event to BMC Atrium Orchestrator list to post the new action to the Actions to Perform list. 7 Select previously existing actions that were used by the BMC Atrium Orchestrator installation, and click Remove.
8 Click Done to save your changes and close the wizard. In the integration with BMC Atrium Orchestrator, before an abnormality event is sent to the target application, its severity level is set to warning.
Note
How BMC ProactiveNet integration works with BMC Atrium Orchestrator

The following block diagram explains BMC ProactiveNet integration with BMC Atrium Orchestrator. Figure 13: 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. If the rule validation succeeds,
the appropriate RBA Workflow is triggered
A list of integration features follows:

Creating RBA events - RBA events are created when the BMC ProactiveNet event
is opened, acknowledged, or closed based on the action set for the event. RBA Events can be created for BMC ProactiveNet abnormalities as well. 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. RBA events can be created for BMC ProactiveNet predictive events. The predictive event description is prefixed with the word Predictive to distinguish it from the other BMC ProactiveNet events, and the severity of the predictive event is changed to warning an RBA event is created.
Mapping BMC ProactiveNet event fields for RBA Event slots

Table 58: 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.
Combination of event Id & PN Server IP is required when multiple PN servers are sending events to the same RBA. For DHCP enabled systems, it is a combination of event Id and host name of the PN Server. string description of the event In BMC ProactiveNet event there is no concept of priority. Hence CRITICAL is mapped to PRIORITY_1, MAJOR is mapped to PRIORITY_2, and Minor is be mapped to PRIORITY_3. Severity determines how bad the technical problem is (device is up, down, or in between); priority describes the business urgency (high, low, or in between). Something that is down may have low urgency (for example if it happens on a Sunday). Data collection layer (PN, PATROL, etc.) can usually not assess priority. (CRITICAL,MAJOR,MINOR, WARNING) (OPEN, CLOSED) BMC ProactiveNet Device IP Address For backward compatibility PN Server IP Address PN Server Name Device Name
AlarmDescription no equivalent mapping field. The value is calculated instead.
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
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.1 release of BMC Impact Solutions. Sends the eventURL to the mc_tool_uri slot. Combination of eventId and PN Server IP. This is required when multiple PN servers send events to RBA. 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.
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. 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.
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. If the instance level Reconciliation ID is not blank, send it. Otherwise send the device level Reconciliation ID.
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. 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. See the System requirements and
product compatibility information in the online technical documentation for BMC ProactiveNet at http://docs.bmc.com/docs/display/PN90/System+requirements +and+product+compatibility for the supported versions of these products.
Reducing events
Configure the BEM-RBA monitor adapter used for the BEM-RBA integration to
accept events from BMC ProactiveNet.
Reducing events
BMC ProactiveNet allows you to limit the flow of events.
To configure intelligent events

1 Click Options on the top right of the BMC ProactiveNet Operations console. 2 Choose the Administration tab. 3 In the Event Administration area, click the Edit link to the right of Intelligent Event Reduction. The Event Reduction screen is displayed. 4 On the Event Reduction screen, clear the Enable Intelligent Events check box to map absolute threshold to the baselines. The outside baseline column can be set to Not Enabled, Hourly Baseline, Daily Baseline, Auto, or Weekly Baseline. Each threshold with Outside Baseline enabled activates when the data exceeds the specified baseline and absolute threshold. For full information on setting thresholds, see Setting event thresholds on page 246. This creates a new outside baseline column in the Event threshold administration screen. 5 Click Apply.
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. For more information, see Defining Intelligent Event Suppression relationships on page 463. The event suppression rule defines a relationship between the application and host system. For example, availability events related to application A are suppressed by the availability events on system B. If the system is offline, this causes the application to be unavailable. However, because the relationship is defined, BMC ProactiveNet does not send an alert for the application availability; but an alert is sent only for system availability.
Note
Reducing events
1 On Event Reduction screen, clear the Enable Event suppression check box to disable the suppression rules. 2 Click Configure Event Suppression link, the Relationship Administrator screen opens and you can define the relationships.
To enable or disable non KPI metrics

1 On Event Reduction screen, 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. By default, for fresh installations, the Enable Abnormality Detection and Baseline Generation for non-KPI metrics check box is disabled. However, for upgrade customers, this check box maintains the same non-KPI status that it had before the upgrade. For example, if the check box was enabled before the upgrade, it remains enabled. 2 Click Apply.
Note
Enabling baselines and abnormality detection for non KPI metrics

For baselines to be generated for an attribute, that attribute must have an active abnormality threshold. An active abnormality threshold means that the threshold exists and is not suppressed. By default, metrics that are not Key Performance metrics (non-KPI metrics) do not have an active abnormality threshold, so baselines are not set automatically for non-KPI metrics. If you want to generate baselines for non-KPI metrics, you must enable baseline generation for these metrics. For fresh installations, baseline generation and abnormality thresholds for non-KPI metrics are disabled by default. For upgrades, the status (enabled or disabled) of baseline generation and abnormality thresholds for non-KPI metrics from the previous version of BMC ProactiveNet is maintained. If the baseline generation is not enabled for non-Key Performance Indicator (KPI) metrics, only those attributes that have an active abnormality threshold and are also KPI attributes will have baselines generated for them. Absolute thresholds (with outside baseline) or signature thresholds do not satisfy these requirements. To enable or disable abnormality detection and baseline generation for non KPI metrics 1 From the Operations Console toolbar, choose Options.
Note
Customizing event text
2 Choose the Administration tab. 3 In the Event Administration section, click the Edit link for Intelligent Event Reduction. 4 On Intelligent Event Reduction screen, select from one of the following actions:
To enable baselines and abnormality detection for non-KPI metrics, select the
Enable Abnormality Detection and Baseline Generation for non-KPI metrics check box. metrics (which is disabled by default), deselect the Enable Abnormality Detection and Baseline Generation for non-KPI metrics check box.
To stop further baseline projection and abnormality detection for non-KPI
Note When the Enable Abnormality Detection and Baseline Generation for nonKPI metrics check box is selected, baselines are generated for KPI attributes irrespective of the presence of abnormality thresholds. When the check box is not selected, baselines are generated for both KPI and nonKPI attributes that have abnormal thresholds.
5 Click Apply. Turning on baselines and abnormality detection for non-KPI metrics can have a significant impact on the performance and scalability of the BMC ProactiveNet Server. Baselines and abnormalities are designed to be used with KPI metrics in order to provide the greatest value.

Event text customization enables you to insert event text for all email alerts. Certain event text customization variables are only available for ProactiveNet intelligent events. They are:
$EVENTID $MC_LONG_MSG $INSTANCE_NAME $ABNORMALITY
When applied to external events, these variables will have blank values.
For upgrade users

BMC ProactiveNet 8.0 provides additional out-of-the-box variables, such as $Status, $MC_HOST, and $MC_PRIORITY, for event text customization. See the table below for a complete list. Upgrade users cannot immediately select these additional variables. They have to add them manually. Upgrade users can enter the new variables that they need directly in the wizard.
To customize event text

1 Click the Options tab at the top right of the BMC ProactiveNet Operations Console. 2 On the Administration tab, choose Event Text Customization Edit link. 3 On the Global Event Text Customization screen, customize the subject and body of the Email Alerts. You can choose from among the following variables listed in in the table below. Table 59: Variables for customizing event text
Variable ($VAR) $ABNORMALITY $ACK $ACK_MSG 3.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
$ALARMRULE_NAME $ATTR_NAME $DEVICE $DEVICE_DESCR $EVENTID $FTIME_ASC $FULL_PATH $INSTANCE_NAME $LAST $LTIME_UTC $LTIME_ASC $MC_HOST
Variable ($VAR) $MC_HOST_ADDRESS $MC_LOCATION $MC_LONG_MSG $MC_NOTES $MC_OBJECT $MC_OBJECT_CLASS $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 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 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, 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. Name of the Monitor instance, encoded for safe use in URLs
a ACK_MSG retains the latest operations message. 4 Select Include MoreInfo in E-Mail Body to receive the detailed information in an email. 5 Click Apply.
Integrating BMC ProactiveNet with Service Level Management
Integrating BMC ProactiveNet with Service Level Management

This section provides information on integration of BMC ProactiveNet with Service Level Management. Managing BMC ProactiveNet with Service Level Management (SLM) - Performance data collected by BMC ProactiveNet is exposed in Service Level Management to be utilized in Performance Based Service Targets. The metrics can be from BMC ProactiveNet Monitors that are packaged with the product as well as from adapters to other enterprise performance monitoring solutions. 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.
BMC ProactiveNet only supports unidirectional integration with SLM. For more information on using the BMC ProactiveNet integration with SLM, see the BMC Service Level Management Users Guide and the BMC Service Level Management Configuration Guide.
Note
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. Using this feature, you can select a combination of monitors and attributes, and correlate data effectively. This feature gives you more control over information than the Show Graph option on the Tools menu. Customizing graphs helps you to:
choose the type of graphing format that works best for you. create graphs that show data from an individual monitor type or multiple attributes. create graphs for multiple monitors showing a single attribute but view the
statistics from multiple sites.
Custom Graphs that focus on an individual monitor enable you to chart thresholds and other indicators, such as Baseline, Peak, and so on. For more information, see Creating an individual/multiple monitor graphs on page 334. Multiple data type graphs enable you to compare data across sites, but do not allow you to chart thresholds or indicators, as they only relate to a single attribute. For more information, see Creating an individual/multiple monitor graphs on page 334. You can 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 313
Top N Graph Pie Graph Dial Gauge Graph
Note
When generating a graph, the graph displays only monitors accessible by the
user. Select the Attributes & Indicators tab to view and use the tools menu. The options available reflect the associated permissions. the Tools menu reflect user access privileges and permissions.
Custom graphs is authorization aware; the Graphs and any actions available from
Related Topics Limitations on page 314 Creating a line or area graph on page 315 Creating a x-y graph on page 320 Creating a Top N graph on page 321 Creating a pie graph on page 323 Creating a dial gauge graph on page 325
Limitations
When creating graphs, keep the following limitations in mind:
No more than twelve attributes can be displayed on a graph. No more than two measurement types can be displayed on a graph. For example, if two statistics are measured in percentage and two in units, then all
four appear in the graph because Y1 or Y2 allows a graph to have two likemeasurements each.
However, if you have three statistics, one being measured in percentage, one
being measured in units, and the other being measured in time, an error message appears (as shown below) and the graph does not display.
When choosing any Indicator, only one Attribute can be selected because the
Indicator cannot relate to more than one measurement. graph period.
Graph displays NO_DATA image when there are no data available for the total
Creating a line or area graph

Line graphs are the most common type of graphs that plot linear relationships. Area graphs are specialized line graphs. However, they can plot only single instance and single attribute selections, and indicators are not applicable to Area Graphs. To view parent and child instances for the selected monitor instance see, To show the parent instance for the selected monitor instance on page 319 and To show the child instances for the selected monitor instance on page 319
To create a line or area 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 Line Graph . 4 Select a Group Filter. Select the desired group. Choosing a filter limits your graph choices to the selected group and provides a means of organizing your data. Choosing No Filter lets you generate a graph from all resources in the system, regardless of whether they are in a group or not. 5 Select a Monitor Type. For an Individual Graph, choose only one Monitor Type. For Multiple Monitor Graphs, choose more than one Monitor Type. 6 Click Next to open the Monitor Instance area. A list of resource instances available under the Monitor Type you selected is displayed. 7 Select the resource instances to monitor, and click Apply. The Custom Graph screen is displayed. In the Custom Graphs screen, select graph options for the graphs. .
or Area Graph option
8 Select appropriate values in the Filter Area.

Show Graph for the last - Choose the amount of time you want to show on the
graph. The list lets you choose from 1 hour up to 3 months.
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, such as the last four hours. You can change the time and date when you want to view resource data for the previous day, week, or hour to compare measurements.
9 Select appropriate options in the Attributes area. The Attributes Area 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, however you are limited to 2 units of measure (that is, # and ms). For more information on attribute statistics and their function, see the BMC ProactiveNet Data Adapter and Monitor Guide. Figure 14: Attributes Area
10 Select appropriate options in the Indicators area.

Indicators provide options for dynamically changing the charting of data.
When choosing any indicator, only one statistic (attribute) is viewable at a time because the Indicator cannot relate to more than one measurement. These values can be used only if multiple attributes have not been selected. Thresholds and a Config attribute may also be graphed.
Hourly Baseline, Daily Baseline, Weekly Baseline, or Hourly & Daily
Baseline: There are two baselines: Baseline High and Baseline Low. Baseline
High represents the point at which 95% of the weighted average of the historical values fall below this value for that hour, day, or week. Baseline Low represents the point at which 90% of the weighted average of historical values for that hour, day, or week fall above this line. Baseline indicators always use the current week as baseline data. The baseline indicator is recalibrated for each hourly point per week.
All Baselines: Select this option to show condensed Baseline High and
Baseline Low for hourly, daily, and weekly baseline values.
Hourly Max: Highest values of data found for the specified graph period.
Peak indicator can be selected only when viewing data older than 24 hours. Low indicator can be selected only when viewing data older than 24 hours. the data type you are viewing, check boxes are displayed. These indicators show you what the event settings are relative to the performance of the data you are viewing. threshold, baseline associated to threshold, and applied PAD factor.
Hourly Min: Lowest values of data found for the specified graph period.
Minor, Major, 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,
baseline associated to threshold, and applied PAD factor.
Critical Signature Threshold: Composite values of signature critical
threshold, baseline associated to threshold, and applied PAD factor.
Abnormality Threshold: Composite values of abnormality threshold,
baseline, which is associated to threshold, and applied PAD factor.
Scheduled Downtime: To view the scheduled downtime for the monitor on
the graph. Due to the lag in start of a scheduled downtime event, a few data points may appear inside the shaded downtime. Similarly, in case of overlapping scheduled downtime, the shading may use a color different from that shown in the legend.
In case the Scheduled downtime is created after the start time and before the end time for the day, the graph will show the data points already collected.
Show Intelligent Events: If there are any intelligent events on the selected
attributes and for the selected duration, same will be displayed as an icon. There will be two different icons for open and closed intelligent events. the selected duration, same will be displayed as an icon.
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, or external events, the same will be displayed as an icon.
Show Violations: If there are any violations on the selected attributes and
for the selected duration, same will be displayed as an icon. There will be two different icons for open and closed violations.
Period Max: Displays highest attribute value on Y-axis. Period Min: Displays lowest attribute value on Y-axis. Period Avg: Displays average attribute value of all points of Period Min and
Period Max attribute values.
Shaded Baseline: Select this option to highlight the area corresponding to
the previous baseline selection.
Config Attributes: These attributes are displayed only if configuration
attributes are available on the monitor. For complete definition of configuration attributes and their functionality, see the BMC ProactiveNet Data Adapter and Monitor Guide.
Note SLO indicator will only be available for upgrade setups with existing views.
11 (optional) Select Schedule from the list. However, this is not available if Scheduled Downtime indicator is selected.
Click New to define a new schedule. Click Edit to change the selected schedule.
12 Select an appropriate Graph Option.

Show all attributes on a single graph - All attributes you choose are charted on
one graph.
Show each monitor instance on a separate graph - If you chose more than one
instance, each instance is charted on a separate graph.
Show each attribute on a separate graph - If you select more than one
attribute, each is charted separately on separate graphs.
Show selected attributes on the corresponding graph This will preserve the
existing graph settings. If you select some more attributes for the existing graph, the new attributes will also be added to the same graph.
13 Select Device Name, Instance Name or Attribute Name, to show the same in the legend. 14 Select the Data Type to be used.
Note When raw data is selected and if raw data is not available for the entire time range, rate data will be used.
15 Select Auto Scale if you need auto-scaling for the graph. Unless this option is unchecked, all graphs will be automatically scaled. 16 Select Refresh this page for every n minutes to refresh the page for the specified time. This option can be selected only if relative time range option is selected from the filter area. 17 Click Generate Graph. The individual or multiple monitor graph displays attributes selected. You can change the parameters on the displayed screen, or use the icons located on the side of the graph to perform other functions. For more information, see Additional information for changing graph display on page 335 for information about these icons.
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. If this instance does not have stats attributes, the Show Parent link displays the super parent which has stats attributes.
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. 2 Select any child instance to create a graph for that instance. A submenu of the child instances is displayed with all the instances that have stats attributes. You
can also choose to display the first 50 child instances using the All option. This option displays only the instances that have stats attributes. Figure 15: Show children
Creating a x-y graph

X-Y graphs are used to show a correlated view of two metrics. This graphing is especially useful for related metrics where the dependency is not very clearly known. Displaying this graph over a period of time can give you a visual representation of the relationship. A good example for online stores may be to correlate a business metric (like $s per hour) with Web server performance. This allows IT groups to justify performance improvements on IT hardware or software. All such scenarios, where the relationship between two metrics needs to be qualified, are appropriate for X-Y graphs.
To create a x-y 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 X-Y Graph option 4 Select a Group Filter. 5 Select Monitor Types. 6 Click Next. The system populates the corresponding monitor instances in the Monitor Instance area. 7 Select Monitor Instances for X and Y axis.
8 Click Apply. On the Custom Graphs (X-Y Graph) screen, 9 Select appropriate values in the Filter Area.
Show Graph for the last: Choose the time period you want to show on the
graph. The list lets you choose from 1 hour up to 3 months.
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, such as the last four hours. You can change the time and date when you want to view resource data for the previous day, week, or hour to compare measurements.
10 Select attribute for X and Y axis. 11 Select the Schedule.

12 Click Generate Graph(s). You can change the parameters on Graph Display screen, or use the icons located on the side of the graph to perform other functions. For more information, see Additional information for changing graph display on page 335 for information on these icons.
Creating a Top N graph

Top N Graph is a Pareto bar graph comparing Top N resources. You can create either a Top N or a Bottom N graph. Top N graphs compare monitored resources based on a common measurement. The Pareto bar chart includes resources with the highest average (based on the common measurement). BMC ProactiveNet administrator sets the number of bars in the graph. 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. Computation of Top N graphs provides an order to the individual elements within each graph. Example, in the Top 10 Interface in Utilization graph, the number one graph shows the highest average for all interfaces.
To create a Top N 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 Top N Graph option 4 Select the Group Filter. 5 Select the Monitor Type. You can select only one monitor type here. 6 Click Next. The system populates the corresponding attributes in the lower pane of the screen. 7 Select an Attribute. 8 Click Apply. 9 On the Customs Graphs screen, select the Graph Type: Top N or Bottom N. 10 Select the number of bars from the list. 11 Specify the duration, and select the units (Days or Hours) from the adjacent list. 12 Select the Values to be displayed: Average and High or Average and Low. 13 Select the Graph Preference: 2 Dimensional or 3 Dimensional 14 Select the Schedule.
The 3 Dimensional option is available only through the Operations Console. However, 3-dimensional graphs configured through the Operations Console retain the option during editing through the Administration Console. 15 Click Generate Graph.
Note
Note The Forward and Backward buttons that help you view graphs corresponding to the succeeding and preceding time ranges, respectively are not available for Top N Graphs.
The Description table located below the graph lists data resources of the Top N graph. The Num column provides a link to open the Individual graph for the resource. To modify the statistics, see Creating a line or area graph on page 315.
To view a stacked graph for any of the listed instances

1 Select the check box corresponding to the monitor instance. 2 Click Generate graph.
Listing all button

Most monitored categories, such as Availability and Utilization, contain numerous devices, interfaces, and services. Clicking List All at the bottom of the Top N table expands the table to list all resources that comprise the selected category. A list of sources used to compile the chart is displayed. The List All feature allows you to generate a maximum number of 100 items per page. You can also generate Individual graphs from each of these items.
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. Pie graphs are best suited for getting a high-level overview of the performance of a specific attribute, since only a single instance and attribute selection is plotted. Indicators are not applicable to Pie graphs. Description of slices is available in a file for each threshold or SLO at the following path: installDirectory /usr/pw/pronto/conf/ piebuckets.xml. Different slices are available for Major, Minor, and Critical thresholds. Pie graphs are available only on attributes that have set thresholds. If the selected threshold does not exist for the attribute to graph, the system prompts you to create or choose another threshold. If the threshold is unavailable after graph creation, a NO Data image appears for the pie chart even if there is data in the database. Reason being, 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.
Pie graphs offer a 3D option (available only through the Operations Console), and can be added to a view. Pie graphs allow users to see compliance to threshold over a period, and simultaneously see the percentage time where data is falling into each range of values. This kind of graph makes most sense in a view that updates automatically (on a daily basis).
To create a pie 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 Pie Graph option .
4 Select the Group Filter. 5 Select the Monitor Type. You cannot select more than one monitor type here. 6 Click Next. The system populates the corresponding attributes in the lower pane. 7 Select a single Attribute, and click Apply. 8 Make your selections on the Custom Graph screen. 9 Click Generate Graph. You can change the parameters here, or use the icons located on the side of the graph to perform other functions. For more information see Additional information for changing graph display on page 335 for information on these icons.
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. will be shown in terms of the unit that it is collected.
Although the breakdown is described in terms of % ranges, values in the graph
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. . .
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.
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 System requirements and product compatibility information in the online technical documentation for BMC ProactiveNet at http://docs.bmc.com/ docs/display/PN90/System+requirements+and+product+compatibility. 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:
Customizing monitor graphs
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.
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)

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 329 Attributes and indicators tab on page 330
Monitor information tab on page 332 Button options on page 332 Creating an individual/multiple monitor graphs on page 334
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 335. Figure 16: Graph Tab
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, 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 Data Adapter and Monitor Guide. Figure 17: Attributes and Indicators tab
For more details on Attributes and Indicators Tab, see Creating a line or area graph on page 315.
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 18: 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.
Add All to View - Adds all graphs to the view.
Figure 19: 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 20: 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.
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 335 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.
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 336 Exporting graph data to Microsoft Excel on page 337 Adding new monitors to a graph on page 337 Obtaining more information on page 337
Adding a graph to a view on page 337 Displaying all abnormalities for a graph on page 339 Navigating the graph page on page 339 Deleting a graph from a multi-graph view on page 339 Displaying graphs for a resource pool on page 340 Analyzing probable cause on page 340 Mailing the graph page on page 340 Sharing the graph page on page 340 Generating PDF on page 341
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.
Exporting graph data to Microsoft Excel

Use the Export to Excel icon to export all data into a Microsoft Excel file for viewing outside BMC ProactiveNet. This icon launches the Microsoft Excel application and displays all data in the .csv file.
Raw data is recorded after every polling interval (user-configured). When the recorded data is plotted in a graph and exported to Excel, Duration column shows 0 instead of the polling interval in seconds.
Note
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 to add a particular graph to a view category.
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 - links to the Domain Knowledge graph is automatically provided to aid users in troubleshooting.
Domain knowledge
Domain Knowledge information can be added whenever you add a graph to a view. The Domain Knowledge field is displayed on the Add this graph(s) to View page. Use this field to enter specific domain knowledge that other users may benefit from by looking at the graph. This information is also used by the Event Details page when events are generated against the same monitor - links to the Domain Knowledge graph are automatically provided to aid users in troubleshooting. Domain Knowledge information acts as a repository of graph information. For instance, if the relationship between an event and an event is recorded as domain knowledge, users can easily trace the event the next time a similar event occurs. Figure 21: Domain Knowledge field
To edit the Domain Knowledge information from the Graph Display page
1 Click Edit next to the Domain Knowledge field.
The Change Domain Knowledge screen is displayed.
2 Make changes to the information displayed, as required. 3 Click Update. A message indicating that the information has been updated is displayed. 4 In the Graph Description window, click Close.
Displaying all abnormalities for a graph

The All Abnormalities icon is displayed as an additional graphing function only for graphs plotted using attributes of the same Abnormality Index monitor instance. 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, Area, X-Y, and Pie graphs. The All Abnormalities icon is not displayed if a graph is plotted using attributes of multiple monitor types.
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. When generated, the Device At a Glance page shows a stacked line graph for all monitors on the device. 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 displayed from the Device Matrix page, the graph displays the last four hours.
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. Use this icon to delete a graph from a multi-graph view.
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.
Analyzing probable cause

Click the Go to Probable Cause icon to access the Event History page.
Mailing the graph page

To send the graph via e-mail
1 Click the Mail this Page icon .
2 Specify the From and E-mail Address in the displayed window. 3 A brief description can be sent via e-mail either in HTML or plain text format. 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. 2 Click Copy Shortcut in IE, Copy Link Location in Mozilla Firefox. This link can be sent to others via E-Mail or can be pasted in a shared location, so that it can be used by others.
To view this graph:

1 Copy and paste the link in the browser address location and click Enter. This opens the BMC ProactiveNet Login screen if you have not logged in. 2 Enter the User Name and Password and click Log On.BMC ProactiveNet navigates to the specified screen. This link is available in the following locations:
How setting the All Baselines option affects absolute instance thresholds
Custom Graph (all the graph formats) Drill-Downs from Views Drill-Downs from RCA 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.
Sometimes, the value of a threshold shown in a graph is different from the value of the absolute instance threshold that is set. A graph may show a threshold value different from the value that is set as the absolute threshold value. The value of a threshold is calculated as (all baselines + absolute threshold value). When the threshold is set to take baselines into consideration, the highest or lowest value (above or below threshold values respectively) of the threshold is calculated. During every poll, all three baseline values (hourly, daily and weekly) and the absolute threshold value are checked and the highest or lowest value becomes the threshold at that point. For example, assume that the absolute instance threshold value of a response time attribute is set to Minor when it is above 200 milliseconds, and the All Baselines option is selected. At one data point, if the value of the response time is 200 milliseconds, hourly baseline is 240 milliseconds, daily baseline is 230 milliseconds, and weekly baseline is 210 milliseconds for that point of time, no alarm is generated because it has not violated the highest threshold of 240 milliseconds and above. Related Topics
Adjusting graph axes on page 336 Exporting graph data to Microsoft Excel on page 337 Adding new monitors to a graph on page 337 Obtaining more information on page 337 Adding a graph to a view on page 337 Displaying all abnormalities for a graph on page 339 Navigating the graph page on page 339 Deleting a graph from a multi-graph view on page 339 Displaying graphs for a resource pool on page 340 Analyzing probable cause on page 340 Mailing the graph page on page 340 Sharing the graph page on page 340 Generating PDF on page 341
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. 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 and 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.
Chapter 6 Managing Views 343
Navigating the Views and Graphs drawer
Figure 22 on page 344 displays a single view and identifies the major areas within the Views screen. Figure 22: Views
The title bar contains icons for customizing the display and managing views. View details displays the owner, update frequency, and the date and time the
view was last updated above the graph thumbnail. By default, the View details are not displayed. You must select the Show View details at top of the page option when creating a view to display the details. enlarge the view, rename, or delete the graph. These options are available only for the graph-based view. Thumbnails provide a high-level view of all graphs that exist in the view. Thumbnails display data from the last update, and may not always represent the most current data.
View display shows the graph thumbnails. Using the graph thumbnails, you can
Note
The graph border colors act as visual notifications when data collection pertaining to that graph is in an alarming condition. The highlight color indicates the event severity.
Critical = Red Major = Orange Minor = Yellow
When an event is closed, the highlight color returns to blue. The graph labels are based on monitored attributes, data source, and the date and time the graph was generated. The source of the monitored data always appears within the description column of the graph tables.
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.
Generally, this happens with newly created instances. Figure 23: Inverted triangle symbol
The thumbnail appears blank if the monitored resource provides a minimum amount of data during the polling period. For detailed information on thumbnails, see Managing graph thumbnails for a view on page 351. Related topics: Managing graph thumbnails for a view on page 351 Customizing graphs on page 313 Managing view templates on page 353
Managing views
Through the Views tab you can create, edit, or delete any number of views. View settings that are configured when creating or editing a view differ for different types of views. Views can also be created using view templates. For more information see Managing view templates on page 353. Table 60 on page 345 lists the icons available on the View screen. Table 60: 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 345
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, click Add View. 2 In the Add View screen, provide the necessary information to create a view and add a graph to the view as described in Table 61 on page 346. The Operations Console does not support special characters such as \, ', ", \, <, and > in the view name. Any view name containing special characters is displayed in hexadecimal format on the Operations Console. Table 61: Inputs for the Graph-based Add View screen
Fields Add View View Title View Type 2.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. The layout type can be one of the following: Four columns: Displays a small size view, with fewer options Two columns: Displays a medium size view, with all options One column: Displays a large size view, with all options Description
Note
Layout Type
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. By default, the details are not displayed. You can toggle the display of view details using the Show/ Hide View icon. 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. For detailed instructions, see Creating custom graphs on page 313.
a You cannot configure the view type when editing an existing view. 3 Specify a name for the graph. 4 Click Add to View. 5 Click Finish. To edit an existing view, click Edit View on the View screen and follow the steps listed in To create or edit a graph-based view on page 346.
Tip
To create or edit a report-based view

1 In the View screen, click Add View. 2 In the Add View screen, provide the necessary information to create a view and add a report to the view as described in Table 62 on page 348.
Managing views
Note
Users with access to a view have unrestricted access to all the reports. The Order button sets the order of graphs or reports in the view. This option is
available when you create multiple graphs or reports.
Table 62: 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; select Report Based to create a report-based view Sets the preferences of the thumbnail. 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. The layout type can be one of the following: Four columns: Displays a small size view, with fewer options Two columns: Displays a medium size view, with all options One column: Displays a large size view, with all options Show View details at top of the page Displays the details in the View screen. By default, the details are not displayed. You can toggle the display of view details using the Show/ Hide View icon. 2.a Reports in View 2.b Add Reports Adds a report to the view. For detailed instructions, see Creating or editing a report on page 358.
a By default, generated reports are added to the view if they are not generated. b For Capacity Trend Reports, the bar graph thumbnail may not display all the indices in Y-axis. 3 In the Reports screen, select the default report(s) to add to the view, and then click Add To View.
Managing views
4 Click Finish. To edit an existing view, 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 319. Related topics: To show the child instances for the selected monitor instance on page 319 To create or edit a folder view on page 349 To delete a view on page 350 Managing view templates on page 353
Tip
To create or edit a folder view

1 In the View screen, click Add View. 2 In the Add View screen, provide the necessary information to create a view and add a folder to the view as described in Table 63 on page 349.
Note
Folder view administration is available from the Operations Console only. When adding a folder, the Available Top Level Views shows only top level
views. Access rights to folder view applies to all child views in the folder. the view to the top level first.
Individual views cannot be moved from one folder to another, without moving
If a folder view is deleted, the children in the folder are not deleted. Instead, all
the immediate children are moved to the top level.
A view can be a child of only one folder view. This is different in Group
behavior, where one group can be a sub-group of many other groups.
Table 63: Inputs for the Folder-based Add View screen

Fields View Title View Type Description Specifies the view name Indicates the type of view; select Folder to create a folder-based view
Managing views
Fields
Description
Show View details at top of the page Displays the details in the View screen. By default, the details are not displayed. You can toggle the display of view details using the Show/ Hide View icon. 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. To edit an existing view, click Edit View on the View screen and follow the steps listed in To create or edit a folder view on page 349. Related topics To create or edit a graph-based view on page 346 To show the child instances for the selected monitor instance on page 319 To delete a view on page 350 Managing view templates on page 353
Tip
To delete a view
1 Select the view that you wish to delete. 2 Click Delete View. 3 In the Confirmation dialog box, click OK. Related topics Customizing monitor graphs on page 328 Creating or editing a report on page 358
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, click Options. 2 In the Operations tab, under Layout Preferences, modify the following settings, as necessary.
Show Dashboard View - Displays a list of user-defined views for the top right
portion of the Grid View and Tree View . Dashboard View is displayed for Abnormalities, Devices, Groups, and Monitors. This enables the user to get a snapshot of the most important attributes being monitored simultaneously, while watching the event summary grid view. 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 option as the default view for the
Views & Graphs drawer in the Navigation pane.
3 Click Apply.

To switch to large view
1 In the Views & Graphs drawer in the navigation pane, select a view from the navigation tree. Thumbnails of any graphs associated with the view are displayed in the right view pane. 2 Right-click a graph thumbnail, and then click Large View. You cannot view the large view for a single layout type of graph.
Note
To rename a thumbnail
1 In the Views & Graphs drawer in the navigation pane, select a view from the navigation tree.
Thumbnails of any graphs associated with the view are displayed in the right view pane. 2 Right-click a graph thumbnail, and then click Rename. 3 In the Rename Graph dialog box, enter a name for the graph, and then click Apply.
To delete a thumbnail
1 In the Views & Graphs drawer in the navigation pane, select a view from the navigation tree. 2 Right-click a graph thumbnail, and then click Delete. 3 In the confirmation dialog box, click OK. You cannot delete or rename a graph that is created using a view template. However, you can view a large view for the same.
Note
To add graph(s) to a new or exiting view

1 In the Views & Graphs drawer in the navigation pane, select a view from the navigation tree. 2 Double-click a graph thumbnail to be added to an existing view. 3 In the Custom Graphs screen, click Add this Graph to View .
4 In the Add this graph(s) to Viewscreen, provide the necessary information as described in Table 64 on page 352. Table 64: 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.
Managing view templates
For detailed instructions, see To create or edit a graph-based view on page 346.
The Add to View screen does not consider views created using a view template. Related topics: Customizing graphs on page 313 Managing view templates on page 353
Note

View templates are reusable components that are place holders for details such as graph type, monitor type, attributes, and indicators. You can apply a view template to groups or services to create a view. A view that is created using a view template is automatically updated when a new instance is added or removed from the group. When you add a graph to a view template all the associated views are updated. Similarly, if a view is deleted from the view template, associated views are also deleted.
To create a view template

1 In the Views & Graphs drawer in the navigation pane, select a view from the navigation tree. 2 In the right view pane, click the View Template Administration button. 3 In the View Template Administration screen, click Add. 4 In the Create View Template screen, enter a name for the view template. 5 Click Add Graph. 6 In the Custom Graphs screen, select the graph type. 7 Select the Group filter, and then the applicable monitor type(s). 8 Click Next. 9 Select the attributes applicable to the graph, and then click Finish.
Note
In manual view creation, you can choose monitor instances, but in view
template creation, only monitor types are considered.
Based on the selected graph type the corresponding screen opens. For further
information, see Creating custom graphs on page 313.
View template supports and displays the count only for Graph based view.
Creating views for Report or Folder based views does not display the count in the view template wizard.
10 In the Create View Template screen, click Finish.

The View Template Administration screen displays the newly created template.
Tip In the View Template Administration screen, when you mouse over on the views count, all the views created from that template are listed.
To edit a view template

When you edit a view template, you can add, delete, or edit the graph in that template. 1 In the View Template Administration screen, under the Edit column, click Edit in the view template row that you wish to edit. 2 Make the necessary modifications. 3 Click Finish.
Note The Order button is used to set the order of graphs in the View Template. This option is available when multiple graphs are added.
To delete a view template

On deletion of a view template, the views created using the template become normal (manual) views, and therefore, no dynamic updates to the monitor instances take place. 1 In the View Template Administration screen, under the Select column, select the view template that you wish to delete. 2 Click Delete Selected. 3 In the confirmation dialog box, click OK.
To create a view using a view template

1 In the View Template Administration screen, under the Add View column, click the Add View button in the row for the view template that you want to use. 2 In the Add View screen, provide the necessary information to create a view using a view template as described in Table 65 on page 355. Table 65: 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; select Graph Based to create a graph-based view. Sets the preferences of the thumbnail. The layout type can be one of the following: Four columns: Displays a small size view, with fewer options Two columns: Displays a medium size view, with all options One column: Displays a large 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. By default, the details are not displayed. You can toggle the display of view details using the Show/ Hide View icon. 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 355 Indicates how the view is created; select Template to create a view using a view template. Displays a list of available view templates that you can apply to a view
3 Click Finish. There is a configurable entry in pronet.conf (pronet.viewTemplates.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. In such views, if the number of thumbnails exceed 200, it may take more than a minute to create the view. Under such circumstances a message is displayed.
Note
7
Generating Reports
Overview
The Reports tab in the Operations Console presents extensive information about creating, editing, deleting, copying, and changing the email based on the assigned access privileges for various report types. You can query the reports using filter options to view the applicable reports. Some of the report types also have default reports. In the initial display on the Reports tab, the defined reports are listed in tabular form. Table 66 on page 357 lists the columns of report attributes that appear for each report.
Table 66: Views of report information on the Report tab View Report Type Frequency Schedule Description Reports are generated based on the selected report type, for example, Administrative, General, or SLO Displays a list of report generation frequencies; Daily, Weekly, and Monthly at which the report is generated Displays a list of schedules; Business Hours and 24x7 based on which the report is generated. For example, schedule 24x7 considers data collected throughout the day for the entire week (including Saturday and Sunday). The schedule displayed in the report listing depends on the individual schedules of the components that make up the report. For example, if a report based on Service Level Objectives (SLOs) is made up of more than one SLO, the schedule is displayed as Mixed. Each SLO can have a different schedule. When the schedule is not applicable, a hyphen is shown. Name of the report owner Title of the report Report category
Owner Report Title Category
Related Topics Creating or editing a report on page 358

Chapter 7 Generating Reports 357
Overview
Deleting a report on page 362 Copying an existing report on page 362 Changing email settings in a report on page 363
Creating or editing a report

This section consists of common steps and attributes required for report creation. 1 On the Reports screen, click Add for a new report or select a report and click Edit to edit an existing report. 2 On the Add Step (1 of 3) - Enter Report Details screen specify the following basic report attributes listed in Table 67 on page 358. If you are editing a report, you need not specify attributes, simply make changes to the attributes.
Table 67: Report detail attributes Field Name Contact Information Report Type Enable Report Generation Description Enter a unique report name Enter report owners phone number Select a report type from the list. You cannot change the report type when editing an existing report. Select this check box to enable report generation for the report. By default, this check box is selected.
3 Click Next. 4 On the Add (Step 2 of 3) - Enter Report Details screen, set the attributes and contents for the specific report type. The settings at this point differ, depending on the report type. For a list of all the available report types and a complete list of reportspecific settings for each report type, see Report types available in BMC ProactiveNet on page 364. Table 68 on page 359 lists the attributes common to all report types.
Overview
Table 68: Common report attributes Attributes Select Group Description When generating reports, the No filter option in Groups filter lists monitor types based on your access. Use this filter to limit the report to only those instances that are present in the selected group. Select No filter to display a list of monitor types to which you have access, or select a Group to display monitors based on the group selected. Click Apply. Select Device Search for Generate Report to Monitor Type Sub Report Title Delete Sub Report Single Attribute Select a device from the list. Use the No Filter option to consider all available devices. Enter a device name to search a specific device Select the appropriate option to show configuration or monitor details Click the Agent Status link. When the Select Monitor Type screen opens, select a monitor type and click Apply. Enter the title for Sub Report. Select a sub report in the Added Sub Report Section, and click Delete Sub Report to delete the selected sub report. Use this filter to report only those events associated to the attribute being considered. Click the attribute link. When the Select Monitor Type screen opens, select a monitor type and click Apply. Select an attribute from the list. Use this filter to limit the report to a single attribute of a monitor type. Attribute Set Select an attribute set from the list to limit the report to those attributes present in the attribute set. The attribute set is a collection of attributes that are used for generating a report. To define a new attribute set, click New. When the Add Attribute screen opens. Select one or more monitor types and click Next. Attributes associated to the monitor types are displayed. Select one or more attributes and click Next. When the Add Attribute Set screen opens, enter a name for the new attribute and select attribute(s) and click Finish. A successful completion message is displayed. To edit an attribute select an attribute from the list and click Edit. When the Edit Attribute Set screen opens, select the attribute set type from the list and select the monitor types, click Finish. A successful completion message is displayed.
Overview
Attributes Schedule
Description The period corresponding to which the data will be considered for Report generation. For example, schedule 24x7 will consider data collected through out the day for the entire week (including Saturday and Sunday). The schedule displayed in the Report listing depends on the individual schedules of the components that make up the report. For example, if a report based on Service Level Objectives (SLOs) is made up of more than one SLO, the schedule is displayed as Mixed. Each SLO can have a different schedule. When the schedule is not applicable, a hyphen is shown. Select this option to reject misleading events and notifications during a scheduled down time. 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. To add multiple attributes Press Shift and select the attributes. Select one of the following options: Condensed Data - Select this option to calculate data on hourly bases for faster calculation. By default, Condensed data is selected. Avg, High, or Low rate values can be calculated and applicable for only condensed data. Raw Data - Select this option to calculate granular data for reports.
Data to be used for calculation
Note To edit sub-report, select a sub report in Added Sub Report Section, and click Edit Sub Report. Follow similar steps to delete a sub-report and click Delete Sub Report.
5 Click Next. 6 On the Add (Step 3 of 3) - Enter Report Details screen set the report details summarized in Table 69 on page 361, and then click Finish to generate the report.
Overview
Note This step is common to all the report types. Based on these settings report is displayed. Some of the display attributes are common to all the reports.
Table 69: Report display options Options Graph Type No. 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. The available options differ based on the report type. The number of rows to be displayed on a single page. Display the device name with the monitor information. By default the Monitor Information column is displayed even if you have not selected the Device name with Monitor Information check box. Display the source agent with the monitor information. By default the Monitor Information column is displayed even if you have not selected the Show Source Agent with Monitor Information check box. Display the report details. Also, specify the location (top or bottom of the page) to display the report details. Select this check box to view Global comments and Report Instance Comments on the report. Also, specify the location (top or bottom of the page) to display comments. If you add text to the Global Comments field, this option is selected automatically. If you do not select this option while creating a report but specify comments for a report instance, then the selections made on the Report Instance Comments window are automatically applied here. Information or other content that you want to associate with the report. If you select the Show Comments at option, comments that you enter here are displayed on all instances of the report. Global comments always precede report instance comments. Choose the font size for display of comments. Click URL Tag to enclose URLs, which are part of comments, in tags. 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. 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.99%. E-mail Options Enter E-mail Address E-mail used to send the report by email. Also, select the format (in which the report needs to be sent) from the list.
Global Comments
Overview
Options Add
Description Insert the email id and format into the email Address box. All applicable email IDs and the associated formats are listed in the email Addresses box. Repeat the procedure to add more email IDs and preferences. Remove the email ID from the Email Addresses list.
Delete Schedule Options Scheduled On Demand Schedule Report Period
Save the report in the system and generate it based on the frequency. Generate report based on the inputs. For more information see, Table 68 on page 359. Number of days selected from the list to be included in the report. This option is not available for SLO Capacity Trends, Asset, Threshold, SLO Compliance Matrix and Capacity Trends report types. Report periods for Event History, SLO Application Compliance and SLO Compliance History are listed based on the granularity selected for these reports. Sets the report generation frequency to Daily, Weekly, or Monthly. Sets report sharing parameters with everybody, group, or not to share. Select the check box if required.
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. 2 In the Select column of the Report screen, select the check box corresponding to the report. 3 Click Delete. A confirmation dialog box opens, click OK to delete.
Copying an existing report

To quickly create similar reports, the copy option can be used. Use the copy option to replicate an existing report's properties and create new reports. Then edit the new report to make specific changes if required.
Overview
To copy an existing report

1 Click the Reports tab. 2 In the Select column of the Report screen, select the check box corresponding to the report. 3 Click Copy. A confirmation dialog box opens, click OK to copy.
Changing email settings in a report

Use this option to add, modify, or delete email for the selected reports. Perform the following steps.
To change email settings in a report

1 Click the Reports tab. 2 In the Select column of the Report screen, select the check box corresponding to the report. 3 Click Change Email.
To add a new email ID

1 On the Change Email page, select Add option to add email IDs for all the selected reports. If the email ID exists then the newly entered email ID is appended to the existing list of Email IDs. 2 Enter the email ID to be added to the selected reports. 3 Select Email Type from the list. 4 Click Apply. 5 On the Change Email Summary page, click Done.
To modify an existing email ID

1 On the Change Email Summary page, select Modify. 2 Enter the existing email. 3 Enter the email ID to be replaced with the new or modified email ID.
Report types available in BMC ProactiveNet
Note When modifying the email ID, you cannot modify the email Type.
4 Click Apply to replace the existing email ID with a new email ID.
To delete a new email ID

1 On the Change Email page, select Delete option to delete the existing email ID from the selected reports. 2 Click Apply. 3 On the Change Email Summary page, click Done.

BMC ProactiveNet reports are divided into three categoriesAdministrative, General, and Service Level Objective (SLO). Table 7 presents the types of reports in each category and points you to further information about each report type.
Table 70: 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, see Asset on page 365 Threshold on page 366 User on page 367 Aggregate Performance on page 367 Availability Summary on page 370 Capacity Trends on page 371 Custom Graph on page 373 Element Distribution Summary on page 374 Event on page 376 Health Summary on page 380 Top Bottom Performers on page 382 Virtual Inventory on page 383
Category SLO
Report types
Further information, see
SLO Application Compliance SLO Application Compliance Report on page 384 SLO Capacity Trends SLO Compliance History SLO Compliance Matrix SLO Executive Summary SLO Health Summary SLO Capacity Trends Report on page 385 SLO Compliance History on page 386 SLO Compliance Matrix on page 386 SLO Executive Summary on page 388 SLO Health Summary on page 389
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.
Asset
The Asset report displays all monitor instances of a particular monitor type in a specific group, for the selected configuration parameters, over a specified time period. Table 71 on page 365 lists attributes specific to Asset reports that need to be entered along with the common attributes.
Table 71: Asset report attributes Attributes Select Group Select Device Generate Report To Description For further information see, Table 68 on page 359 For further information see, Table 68 on page 359 The Show Config Details option displays the configuration attribute details of monitor instances for the selected monitor type. The Show Monitor Details option displays the details of various monitor instances of the selected group and device. Monitor Type Include Control attributes Available Config Attributes For further information see, Table 68 on page 359 Include control attributes in the Available Config Attributes list. Displays configuration attributes corresponding to the selected monitor type. This option is displayed only if you have selected Show Config Details. Select a sort key from the list.
Sort Key
Attributes Show Config DD Sub Report Title Add Sub Report
Description Select this option to view configuration DD. For further information see, Table 68 on page 359 For further information see, Table 68 on page 359
Threshold
The Threshold report allows you to quickly view the threshold values configured. This report is an administrative type of report. Report thresholds are not considered for the Threshold report. Table 72 on page 366 lists the default Threshold report types.
Table 72: 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. 3) Signature Absolute Event Thresholds (Global Only) organized by Monitor Type. 4) Signature Event Thresholds (Instance Only) organized by Monitor Type.
Table 73 on page 366 lists attributes specific to Threshold reports that need to be entered along with common attributes.
Table 73: Threshold report attributes Attributes Consider Description Select the threshold type based on which to generate the report. Also indicate whether instance or global thresholds or both instance and global thresholds must be considered to generate the report. Select the criterion on which the threshold values must be organized in the report. The threshold values can be sorted by group, device, or monitor type. Select Flat List to lists all monitor types in a table. Monitor Type Threshold Type Default Sort Column Select the columns for the report. From the Default Sort Column list, choose the column that must be displayed first in the report. Select the monitor type based on which the report must be generated. To consider all monitor types, select No Filter.
Organize By
Attributes Add Sub Report
Description See Table 68 on page 359.
User
The User report filters user group, user class, and user status. This report displays the user details in a tabular format and the frequency of the report period is monthly.
Table 74: User default report types Default User Report Type Report Type Report Frequency Description User Monthly
Table 75 on page 367 lists attributes specific to User reports that need to be entered along with common attributes.
Table 75: User report attributes Attributes Name User Group Description Specify partial or full login name of the user to be reported. Choose No Filter option to list all the user groups or choose the appropriate user group to be reported. For more information, see User Management of BMC ProactiveNet Administrator Guide. Choose appropriate user class to be reported. Choose No Filter option to list all the user states (Active or Inactive) or appropriate user status to be reported. Select the attributes to be reported. See Table 68 on page 359. See Table 68 on page 359.
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, over a specified time period. The aggregation function can be Average, Sum, Maximum, Minimum, Median, Percentile, and Standard Deviation. The result of aggregation is displayed as multiple summary line graphs (stacked line graphs). Each graph reflects the aggregation result of attributes having same unit of measurement. If Table Display is enabled, 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, average, and maximum values for the specified attribute. Drill down from any of the instances to view the corresponding independent line graph for that instance.
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. The summary graph will be larger than the individual graphs. Aggregate Performance report can be made using multiple sub-reports, where each sub-report is a combination of different group-attribute-set and aggregate function. If Show detail table option is enabled for such reports, the first tab displays graphs corresponding to each sub-report, and the second tab displays different tables corresponding to each graph. The following default reports of the Aggregate Performance type are provided out-ofthe-box by BMC ProactiveNet:
Web Transaction Availability and Response Time - a weekly aggregation of data
with the following sub-reports:

Transaction Availability Transaction Response Time
Server Capacity - a weekly aggregation of data with the following sub-reports: Server CPU Capacity (includes sub-reports). Server Memory Capacity
Table 76 on page 368 lists attributes specific to Aggregate Performance report that needs to entered along with common attributes.
Table 76: Aggregate Performance report attributes Attributes Select Group Select Attributes Description See Table 68 on page 359. 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. Alternatively, use the search box to locate a specific attribute.
Attributes Select Aggregate Function
Description Avg - (Average) Sum of all data points for each instance-attribute and divided by the total number of instances. Sum - all data points for each instance-attribute. Min - (Minimum) Sort the data points from the various instances and take the lowest value. Max - (Maximum) - Sort the data points from the various instances and take the highest value. Median - Sort the data points from the various instances and take the middle value. Percentile - Value that X% of the monitors and below are reporting. (0 being the min, 100 being the max, 50 being the median) If percentile is selected, then the Weightage combo box is enabled for the user to select the appropriate nth weightage factor. Standard Deviation - It is the standard deviation across all the underlying instances.
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 68 on page 359. See Table 68 on page 359. Enter title for graph. See Table 68 on page 359. Select this option to view tables in separate tabs. Select this option to hide the attribute column from being displayed in the report. This option is enabled only when the Show Tables in separate Tab option is selected. Select this option to display individual graphs for each instance or attribute for the selected report period.
Show Graphs for each Instance/ Attribute
Note The report display can get distorted in the following scenarios:
When the report is viewed using IE 5.5. When the report has too much data.
Note If the report size appears to be small, add the following properties in the installationDirectory\pw\pronto\conf\pronet.conf file:
pronet.report.aggregate.instance.height=100 pronet.report.aggregate.motype.height=125
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. It is assumed that attributes displayed will be of type Availability, so Attribute Sets that have the string Availability in them are only considered by the report. The Availability Summary report can consist of multiple sub-reports, where each subreport may be a combination of different group-attributes, device type, range sets, and MTTR information. You can select or define the range set for the availability distribution. The report also can include information about Mean Time To Recovery (MTTR), for which you can select a predefined range set or can define a new one. If the MTTR option is selected, the report displays an additional pie graph that shows the MTTR distribution for each sub-report.
If the report period is greater than the instance creation time, the availability attribute does not show the accurate value. This is taken care when the report is generated again. Table 77 on page 370 lists the default report type for Availability Summary.
Table 77: Availability Summary default report type Default Availability Summary Report Type Web Transaction Availability Description
Note
Report Type: Availability Summary Report Frequency: Weekly Report Duration: Week Sub-Reports Included: Transaction Availability
Table 78 on page 371 lists attributes specific to Availability Summary report that needs to entered along with common attributes.
Table 78: Availability Summary report attributes Attributes Select Group Select Device Type Attribute Set Consider Sub Transactions if any Available attributes Description Click the list to select a group or no filter option to consider all the monitors. See Table 68 on page 359. See Table 68 on page 359. Select this option for the report to be generated considering dynamic attributes associated with the monitors of the Attribute set. Select the attributes (to be part of the sub report) and transfer to Selected Attributes. Use Ctrl and Shift keys to make multiple selections. Alternatively, use the search box to locate a specific attribute. Select the Availability Distribution range to use a pre-defined range set. Range sets define the Maximum-Minimum value of the stack in the graph. Select the Availability Custom Range Set option to specify and define the distribution range dynamically. Data collected is validated against the custom range specified here. Include Mean Time Recovery Information Select the Include MTTR information option to display the Mean Time to Recovery information in the report. When the option is selected, two additional options are displayed. Select MTTR Distribution range set to use a pre-defined range set to calculate the Mean time to recovery. Alternatively, select MTTR Custom Range set to define and assign values to the custom range set. Select this option to view related tables. See Table 68 on page 359. See Table 68 on page 359. See Table 68 on page 359. See Table 68 on page 359.
Availability 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 instancesattribute pairs that are predicted to violate event thresholds in the specified time period. The report contains a bar graph at the top that shows each instanceattribute pair predicted to violate event threshold in the specified time period. The maximum number of bars can be specified during report creation. The report displays Bar graph as follows:
The instance-attribute pair is displayed on the Y axis. Chapter 7 Generating Reports 371
The duration to violation (in days) is displayed on X axis. The table is sorted with instances, which are predicted to violate earliest (in any
violated instance are present, they would appear first). selected attribute along with the threshold line.
Drill down on the monitor instance in the table displays a line graph for the
The report displays Line graph as follows:

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.
A dotted line from the intersection point to the X axis will also be present.
Table 79 on page 372 lists Capacity Trend default report.

Table 79: Capacity Trend default report Default Capacity Report Type Infrastructure Capacity Trends Description Report Type: Capacity Trends Report Frequency; Weekly Duration: One Month
Table 80 on page 372 lists attributes specific to Capacity Trend sub-reports and report attributes that needs to be entered along with common attributes.
Table 80: 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 See Table 68 on page 359 See Table 68 on page 359 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 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
Report Type Use Event Thresholds as Capacity Limit
Descriptions Select this option to use Event capacity as thresholds. Highest Severity, Critical, Major, Minor, or All event thresholds can be selected. When All or highest severity threshold type is selected, then severity column is displayed and a table title is added displaying severity of each instance. When Critical, Major, or Minor event thresholds are selected, then severity column is hidden and a table title is added displaying severity type of each instance.
Do not consider data during Schedule DownTime Use Custom Group Threshold
Enter a value to assign downtime. Select this option to set custom group thresholds. This can be used only when the Groups filter is selected. Choose the respective groups and click New to set new thresholds. Custom group thresholds can be set for either a single attribute or group or multiple attributes or groups. See Table 68 on page 359. See Table 68 on page 359. Data to be used Specifies whether Condensed (Rate) or Raw (Granular) data is to be used. By default, Condensed data is selected. Avg, High, or Low rate values can be calculated and applicable for only condensed data. Show instance which will violate in the next - This is the forecast period. 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. Default is 7 days. Use Data for the last - This option governs the data points to be used for forecasting. Default value is 14 days. Maximum number of bars in graph Specifies the maximum number of bars to be displayed in the bar graph. Maximum number of bars cannot exceed 20. Default value is 20.
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. The graph types supported are Line, X Y correlation, Pie, and Area. The inputs for Graph-based reports are collected through a reports input wizard. Table 81 on page 374 lists attributes specific to Custom Graph report that need to be entered along with the common attributes.
Table 81: Custom Graph report attributes Attributes Graph Type Add Attributes Description See Table 68 on page 359. Click Add. The Select Instances for Line Graph screen opens. Select a Group Filter, and Monitor Type, click Next. The Monitor Instance to be graphed option opens. Select an instance and click Apply. Selected attributes are displayed in Selected Attributes. Click Clear to discard the selected attribute. Schedule Show More Info Data to be used Sub Report Title Add Sub Report See Table 68 on page 359. Select this option to display more information on the graph. See Table 68 on page 359. See Table 68 on page 359. See Table 68 on page 359.
Selected Attributes
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. Default ranges for percentage distribution in the stacked bar can be specified in the configuration file. Custom ranges can be defined in the Create (Step 2 of 3) - Enter Element Distribution Details screen. Drill down on any bar in the stacked bar graph displays a table based on the distribution ranges. This table is a list of all the elements for that distribution range sorted on their average values. Further drill down on each of the elements in the table leads to the individual graph for that element for the specified time period. Table 82 on page 374 lists Element Distribution Summary default report.
Table 82: 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 83 on page 375 lists attributes specific to Element Distribution Summary report that needs to be entered along with common attributes.
Table 83: Element Distribution Summary report attributes Attributes Select Group Single Attribute Attribute Set Consider Sub Transaction if any Hide Attribute Name and Column Distribution range based on Threshold Description See Table 68 on page 359. See Table 68 on page 359. See Table 68 on page 359. Select this option to generate reports considering dynamic attributes associated with monitors of the Attribute set. Select this option to hide attribute name and column during report display. 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. It defines the maximum and minimum values of the stacks in the graph. Select this option to generate report for a specific event severity. This option is displayed only if the distribution range is based on thresholds. Select this option to dynamically define the distribution range. Data is validated against the specified custom range. Report displays instance attribute values for the specified custom range in the form of multiple stacked bar graphs. Select one of the following custom ranges: Bad Poor Fair Good Excellent Distribution Details Select this option to set the graph display either as 2D or 3D. The available options differ based on the report type.
Threshold Severity Custom Distribution Range
Attributes Show data broken down by
Description Select this option to break down the report display. 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 68 on page 359. See Table 68 on page 359. See Table 68 on page 359.
Data to be used for calculation See Table 68 on page 359.
Event
Events are of two types, External and Intelligent events. 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 events coming from a device known to the BMC ProactiveNet server will be automatically associated to that device. 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. The graph lists all events consolidated, irrespective of their multiple occurrences in the bars of the graph. Drilldown from the bars of the graph shows events in that time interval block. Drilldown from a multiple options bar graph shows the list of events of the respective options. To see the severity and status history when you drill-down from the status, see Acknowledging events on page 155.
The Event Report is available only if you are a BMC ProactiveNet user upgrading from version of BMC ProactiveNet older than version 8.5. If you are upgrading from BMC ProactiveNet version 8.5 or higher, BMC recommends that you use BMC ProactiveNet Performance Management Reporting Studio to generate Event Reports.
Note
Table 84: 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
Report Type: Event Report Frequency Weekly Duration: Week
Table 85 on page 377 lists attributes specific to Event report that should be specified along with the common attributes.
Table 85: Event report attributes Attributes Event Selection Description All Events: Lists both BMC ProactiveNet and external events. External events refer to device-associated events and events received from external event adapters. Intelligent Events: Lists the BMC ProactiveNet events only. Filter Options
Intelligent Events All Events Events Associated with Deviceincludes only events associated with a device known to BMC ProactiveNet server Events Not Associated with a Deviceincludes events that are not associated with a device which are generated from a third party No Filterincludes all events during generation of the report Groupssee Table 68 on page 359. Devicessee Table 68 on page 359.
Attributes Attributes to report on
Description No Filterincludes all the events on all monitored instances during generation of the report Single Attributesee Table 68 on page 359. Attribute Setsee Table 68 on page 359. Consider Dynamic Attributes if any (applicable only to select monitors)includes events on all Dynamic attributes for the selected monitors Priorityincludes 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
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 Severitydetermines the severity level of the report. Select any of the following severities to be considered for the report: Critical Major Minor Warning Information OK Graph Options Show only Graphonly displays the graph Show only Tableonly displays the table Granularitycontrols the number of time intervals that the report is divided into By Hourone bar of the graph will represent the number of events that occur within an hour By Dayone bar of the graph will represent the number of events that occur within a day
The PDF option for event reports is disabled. Hence, the PDF option in E-mail Options (page 3 of 3) while creating or editing a report will not work.
Note
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. Performance is based on the total violation time for that instance. The Health Summary report consists of multiple sub-reports (if multiple groups attribute sets severity combinations have been specified). 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. Table 86 on page 380 lists Health Summary default report types.
Table 86: Health Summary default report types Default Health Summary Report Types Application Infrastructure Health Description
Report typeHealth Summary Report frequencyWeekly DurationWeek 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
Default Health Summary Report Types Application Infrastructure Hot Spots
Description
Report typeHealth Summary Report frequencyDaily DurationDay 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 87 on page 381 lists attributes specific to Health Summary report that needs to be entered along with common attributes.
Table 87: Health Summary report attributes Attributes Select Group Single Attribute Attribute Set Description See Table 68 on page 359. See Table 68 on page 359. See Table 68 on page 359.
Consider Dynamic Attributes only Select this option to include dynamic attributes. Intelligent Event Threshold Select this option to restrict report generation to a specific severity level. When All severity threshold type is selected the severity column is displayed and a table title is added displaying severity of each instance. Custom Threshold Show All Instances Select this option to restrict instance violation. Select this option to view all instances matching the input criteria. If the check box is not selected, then only violated instances are displayed.
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. See Table 68 on page 359. Select the column options to be displayed in the table. See Table 68 on page 359. See Table 68 on page 359. See Table 68 on page 359. Select this option to filter and view violations that meet the criterion in terms of absolute time or percentage of report period time violated. This option is applicable only for sub reports added without selecting the Show all instances option.
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.
Top Bottom Performers
The Top/Bottom Performers report displays all attribute or monitor instances of a specific monitor type of a group, in terms of the average value over a specified time period, as a bar graph. Table 88 on page 382 lists attributes specific to Top Bottom Performers report that need to be entered along with common attributes.
Table 88: 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 382 BMC ProactiveNet User Guide Description See Table 68 on page 359. See Table 68 on page 359. See Table 68 on page 359. Select the number of bars from the list to be displayed on the graph. Select one of the values to be displayed on the graph. Select this option to view a list of related tables. See Table 68 on page 359. See Table 68 on page 359. See Table 68 on page 359.
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, Virtual Machines (VMs), clusters, resource pools and their relationships, on a periodic basis. The Virtual Inventory Report lists the virtual entities such as ESX Hosts or VMs, Clusters or ESX Hosts and ResourcePools/VMs, along with their performance attributes. This report also lists the various configuration attributes and supports drill down to individual line graph.
If an ESX Host exists without VMs underneath it, the sub report generated with that option will be empty. 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. of the devices.
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. The ESX in clusters have a drill down to the VMS underneath it.
Table 89 on page 384 lists attributes specific to Virtual Inventory report that should be specified along with the common attributes.
Table 89: Virtual Inventory report attributes Attributes Sub Report Selection Description Available Groupsshows a list of all groups. However auto-created groups by VMware group has the type of group listed in parenthesis against each group. Select the group that will be considered to generate the report. Show Virtual Entitiesdisplays the entities you select. The common attributes for a given pair of entities change when you specify a different entity. ESX Hosts/VMs Resource Pools/VMs Clusters/ESX Hosts Select Attributesadd or delete attributes to be included in the report. You can search for the available attributes in the Search for field. 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). 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. Sub Report Titlespecify the title for the sub report Add Sub Report Report Options Consider Baseline See Table 68 on page 359. See Table 68 on page 359. The baseline data is used for computation. Select either Hourly, Daily or Weekly baselines for generating the report.
SLO Application Compliance Report
The SLO Application Compliance Report displays SLO Compliance information of an application. This report displays the following for each SLO type selected:
Pie Graph, which shows the compliance distribution of the SLO Instances over the
report period.
Bar Graph, which shows the compliance distribution of the SLO Instances for the
granularity selected.
Each SLO Type for the SLO is displayed in a sub section. Drill down on the pie graph displays a summary table based on the distribution ranges over the entire report period. This table is a list of all the SLO instances for that distribution range sorted on their compliance values over the entire report period. 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.
Table 90: 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. A single SLO name or multiple SLO names can be selected. For All SLOs, use SLO Type filter to select the SLO Types. This filter is available only when All SLOs are being considered for the report. Available SLO Select the SLO to be considered from the Available SLOs box and transfer to the Selected SLOs box. Use Ctrl and Shift keys to make multiple selections. Alternatively, use the Search For box to locate a specific SLO. See Table 68 on page 359. See Table 68 on page 359. See Table 68 on page 359. Specify the granularity for bars displayed in the graph.
Sub Report Title Add Sub Report Delete Sub Report Show data broken down
SLO Capacity Trends Report
SLO Capacity Trends report lists all monitor instanceattribute pairs that are predicted to violate the SLO threshold in the specified time period. The report contains a bar graph. Each instanceattribute pair predicted to violate the SLO Threshold in the specified time period are displayed as a bar on the Y axis. The X axis shows the duration to violation (in days). 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. Attribute that are not expected to violate the SLO Threshold will not appear in the bar graph or the table. The table is sorted with instances, which are predicted to violate earliest (in any violated instance are present, they would appear first). Drill down on the monitor instance in the table displays a line graph for the selected attribute along with the threshold line. 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. A dotted line from the intersection point to the X axis will also be present. Enter attributes list in Table 91 on page 385.
Table 91: SLO Capacity Trends 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. A single SLO name or multiple SLO names can be selected. For All SLOs, use SLO Type filter to select the SLO Types. This filter is available only when All SLOs are being considered for the report.
Attributes Available SLO
Description Select the SLO to be considered from the Available SLOs box and transfer to the Selected SLOs box. Use Ctrl and Shift keys to make multiple selections. Alternatively, use the Search For box to locate a specific SLO. Select this option if you do not want the Resource column to displayed in the report. For further information see, Administrator Guide. (Link will be provided at the time of document collation). This is the forecast period. Any instance predicted to violate SLO Threshold in this time period appears in the report. Any violations outside this forecast period are not considered. Specify the time period for which data points are to be used for forecasting.
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.
SLO Compliance History
SLO Compliance History report lists compliance values for specified set of SLOs for the specified time period. The report contain multiple, ordered bar graphs, one for each SLO, which will show the SLO compliance values corresponding to a particular day, week, month, or quarter within the specified time period for a particular SLO. The graph also displays a line corresponding to the compliance objective of the SLO. Drill-down to SLO Health Summary report for the corresponding time period is available for from each bar in the bar graph. Enter the attributes listed in Table 92 on page 386.
Table 92: SLO Compliance History 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. A single SLO name or multiple SLO names can be selected. For All SLOs, use SLO Type filter to select the SLO Types. This filter is available only when All SLOs are being considered for the report. Available SLO Select the SLO to be considered from the Available SLOs box and transfer to the Selected SLOs box. Use Ctrl and Shift keys to make multiple selections. Alternatively, use the Search For box to locate a specific SLO. Specify the granularity for bars displayed in the graph.
Show data broken down
SLO Compliance Matrix
The SLO Compliance Matrix report displays the compliance summary of selected SLOs. The report mainly displays SLO details and the recorded compliance levels for different periods chosen. At least one time period must be selected to generate this report.
The report also displays compliance details of instances of the SLOs listed. Only the SLO compliance details summary table is displayed in the report page. Clicking the SLO name in the summary table displays its instance compliance details in a separate page. Web transactions have dynamic or array-type attributes and sub transactions. So, 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. Clicking the History column in the report displays the SLO Compliance History report for the SLO. Clicking the Graph column displays the line graph for the SLO. Click the Show Compliance Matrix Report icon to view the Compliance Matrix report. Enter the attributes listed in Table 93 on page 387.
Table 93: SLO Compliance Matrix 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. A single SLO name or multiple SLO names can be selected. For All SLOs, use SLO Type filter to select the SLO Types. This filter is available only when All SLOs are being considered for the report. Available SLO Select the SLO to be considered from the Available SLOs box and transfer to the Selected SLOs box. Use Ctrl and Shift keys to make multiple selections. Alternatively, use the Search For box to locate a specific SLO. Select this option if you do not want the SLO Type column to be listed in the report.
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.
Attributes Select history periods to be displayed in the table
Description Previous Day - Select this option to create the report based on SLO compliance values of the previous day. Previous Week - Select this option to create the report based on SLO compliance values of the previous week. Previous Month - Select this option to create the report based on SLO compliance values of the previous month. Week to Date - Select this option to create the report based SLO compliance values of the last seven days, excluding the current day. Month to Date - Select this option to create the report based on SLO compliance values collected over the past thirty days, excluding the current day. Quarter to Date - Select this option to create the report based on SLO compliance values of the past three months, excluding the current day. Year to Date - Select this option to create the report based on data collected over the past one year. Previous Quarter - Select this option to create the report based on data collected during the previous quarter. Previous Year - Select this option to create the report based on data collected during the previous year.
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. Performance is based on the absolute percentage compliance or the delta from desired percentage compliance. The sort order and the performance criterion can be specified during report creation. The report contains a graph which shows each SLO's percentage compliance and compliance objective. The SLO names are present in the report instance details keyed to the serial number that appears in the X-axis of the graph. Drill-down to get more details in terms of a breakdown over the specified time period (see the SLO Compliance History report). Table 94 on page 389 lists SLO executive summary default report type Worst Performing SLOs.
Table 94: 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 95 on page 389.

Table 95: SLO Executive Summary 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. A single SLO name or multiple SLO names can be selected. For All SLOs, use SLO Type filter to select the SLO Types. This filter is available only when All SLOs are being considered for the report. Available SLO Select the SLO to be considered from the Available SLOs box and transfer to the Selected SLOs box. Use Ctrl and Shift keys to make multiple selections. Alternatively, use the Search For box to locate a specific SLO. Specify the sort (top or bottom) criteria. Based on this selection, either the top performing SLOs or the bottom performing SLOs (among the selected SLOs) will be graphed from left to right. Specify the sort criterion (absolute or delta) to be used when calculating the SLO performance. Absolute implies that the actual compliance values for the SLO over the specified time period will be used for reporting. 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. This is the maximum number of SLOs that will be displayed in the graph. Maximum supported number is 20. Select or clear the check box to enable or disable the option to show all SLOs in the table. If the check box is clear, then only details of SLOs present in the graph are displayed in the table.
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). The SLO Health Summary report consists of multiple sub-reports (if multiple SLOs have been specified), each of which may contain a summary bar graph at the top (if selected for display) which shows the top N violators. 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). This is a consolidated list per instanceattribute and not a list of individual violations for every instanceattribute pair. This table may have selected instances highlighted
Report Scheduler
flagged based on input criteria. The table has a limited list of entries based on the input criteria. You can drill-down from any of the entries to the independent line graph. Enter the attributes listed in Table 96 on page 390.
Table 96: 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. Select this option to include all instances. Select this option to specify the presence of a summary bar graph in this sub-section of the report.
Select Do not consider data during For further information see, Administrator Guide. (Link will be Schedule DownTime provided at the time of document collation). 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. 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. Select this option if you do not want the Attribute column to be listed in the report. See Table 68 on page 359. See Table 68 on page 359. Based on the selection, Raw data or Condensed (Rate) data is used for calculating the output values. Use this filter to view only those violations greater than the specified time period. This option is applicable only for sub reports added without selecting the Show all instances option. Use this filter to flag rows in the generated report table based on the specified criteria. Specify the maximum number of instances to be displayed in the table.
Report Scheduler
The Report Scheduler is responsible for triggering report generation at pre-set time intervals (Daily, Weekly, or Monthly). The following properties need to be set in the pronet.conf file for the scheduler module to work:
pronet.report.daily.minute The minutes of the hour (defined above) that the
Daily Report should triggered. Default is 30. triggered. Default is 4.
pronet.report.daily.hour The hour of the day that the Daily Report should be
Additional options
pronet.report.weekly.minute - The minutes of the hour (defined above) that the
Weekly Report should be triggered. Default is 45
pronet.report.weekly.hour - The hour of the day (the day is defined above) that
the Weekly Report should be triggered. Default is 4. Report should be triggered. Default is 1.
pronet.report.weekly.day - The day of the week (values from 1-7) that the Weekly
pronet.report.monthly.minute - The minutes of the hour (defined above) that the
Monthly Report should be triggered. Default is 0.
pronet.report.monthly.hour - The hour of the day (the day is defined above) that
the Monthly Report should be triggered. Default is 5.
pronet.report.monthly.day - The day of the month that the Monthly Report
should be triggered (valid number or a keyword last for end of month). Default is 1.
Additional options
BMC ProactiveNet displays a series of icons on the header of each report. Availability of these additional options are based on the report type (Scheduled Report and Preview Report, refer to Report Creation). Related Topics Show/Hide report header on page 392 Date drop-down on page 392 Deleting instances on page 392 Disable generation on page 392 Adding comments to a report on page 393 Scheduling on page 394 Adding a report to a view on page 394 Generating a report on page 394 Editing a report on page 395 Exporting to Portable Document Format (PDF) on page 395
Additional options
Exporting report data to Microsoft Excel on page 395 Mailing a report on page 396 Printing a report on page 397
Show/Hide report header

Use the Show/Hide Report header icons to view or hide the header display.
Date drop-down
Select the Report period from the list.
Deleting instances
This option is used to delete report instances. Earlier to 7.1 version, there was an option to delete a report but not its instances individually. This is taken care in this release, by the Delete Instances option in the Reports screen.
To delete Report Instances

1 Select the Date. 2 Click Delete Instances icon .
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, the second option is not displayed.
4 Click OK. 5 On the Confirm dialog, click OK.
Disable generation
Use the Disable Generation icon
to disable the generation of reports.
Additional options
Adding comments to a report

Use the Add Comment icon to access the Report Instance Comments window. Add comments you want to associate with the report instance generated. You can enter specific information that other users may benefit from by looking at that particular instance of the report. Report Instance comments are always displayed after Global comments of the report. For example, consider an Element Distribution Summary report created to denote Availability of Solaris Processes on a server. Report instances are to be generated Daily and the server is considered to be in Good state if the Availability is >=99.99%. On a particular day, due to power outage Availability falls below 99% and the server is considered to be in Bad state. 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.
To add a comment
1 Click the Add Comment icon .
The Report Instance Comments window is displayed. 2 Type in your comments and click OK. If required, change the font size. Click URL Tag to enclose URLs, which are part of comments, in tags. This creates hyperlinks for URLs in report comments. A message, indicating that the comment has been updated successfully, is displayed. 3 Click OK. If the Show Comments at option was not selected for a report, then the Report Instance Comments window displays the option. If you select the option here and specify the location of comments, the same is updated for the report and the Show Comments at option is not displayed for the report instance.
Additional options
Scheduling
Click the Schedule icon to schedule the report. Make changes as required in the Report Creation page. This icon is only available for reports where the On Demand option is selected during report creation.
Adding a report to a view

Use the Add to View icon to add a report to a view. You can add the report to an existing view or a new view.
To add a report to a view

1 Click the icon to launch the Add this Report to View pop-up window. 2 Specify the view to which you want to add the report. 3 Select Show Detailed Report, to show the report as a single large report. 4 Select the Layout Type. This is disabled when you select Show Detailed Report. 5 Click Add to View. Once a report 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 report in its View group.
Generating a report
Use the Generate Report icon to generate a report.
If the event life cycle (opened, acknowledged, assigned, and closed) is contained within the report generation period, all these statuses show up in the selected Status column. For example, 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. Similarly, if the event is acknowledged and assigned before being closed during the report generation period, the Status column displays corresponding entries for the open, acknowledged, assigned, and closed statuses.
Note
Additional options
Editing a report
Use the Edit Report icon to edit the report. For operational steps to edit report, refer to the Report Administration topic.
Exporting to Portable Document Format (PDF)

Use the PDF icon to save the report in PDF.
To save report in PDF

1 Click PDF icon. 2 Save the report with the.pdf extension for further action.
Note
Sometimes the Export to PDF function may not work properly on a system
running Windows 2000 Service Pack 4. BMC Software recommends Windows 2000 Service Pack 3 and Adobe Reader 6.0 to use the Export to PDF function effectively. disabled for new customers.
In Event reports, the PDF option is available only for upgrade customers and is
Exporting report data to Microsoft Excel

Use the Export to Excel icon spreadsheet. to export report data into a Microsoft Excel
To export report to Excel

1 Click the Export to Excel icon. 2 On the message screen, click Open to view the report in CSV format. 3 Click Save to save the report in CSV format. 4 Click Cancel to abort action. If reports with instance names containing commas are exported to Excel, the values are shifted to the next column.
Additional options
Mailing a report
To mail a report
1 Click the Mail this Page icon to display the Mail Details for Snapshot window. 2 From: The report sender's e-mail address. 3 Subject: The subject line of the email. By default, reportType reportName is displayed as the subject of the email. 4 Email address: The receivers' email address. 5 Message: A brief message description sent via mail either in HTML or Plain text format.
Note The configuration information for mailing a report is stored in InstallationDirectory / pw/custom/conf/pronet.conf.
If a problem occurs
If the report is not displayed properly in the email, change the following settings for Outlook 2003 and 2007:
In Outlook 2003 to view a report in email, click Tools => Options => Security and
click Change Automatic Download Settings. The Automatic Download Settings screen is displayed. Deselect Dont download pictures or other content automatically in HTML email. browser to view the mail in Internet Explorer in HTML format. limitation.
In Outlook 2007 open the message. From the Other Actions menu, select View in
If the mail size is too large the mail will not be delivered. This is a Microsoft
Managing all reports

The Administrator/Admin class users can now manage all the available reports (including private reports) that is, enable, disable and delete these reports. The Manage All tab is visible only when the conf entry in the pronet.conf file is enabled. Copy the pronet.report.manageAllReports.option=false property from the pw \pronto\conf\pronet.conf file to pw\custom\conf\pronet.conf and set the value to true. By default the value is set to false.
Points to Remember
To manage a report
1 Click the Manage All tab to display the Manage all Reports window. All reports (except SLA reports if the license is not valid) are displayed. 2 Select the check boxes for the reports that you want to enable, disable or delete. There will be no hyperlinks for the reports; therefore, the Admin user will not be able to navigate through the reports.
Note
Printing a report
To print the report, click the Print icon .
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. To retain a report for more than 7 days, change the prune period using pw commands. See the BMC ProactiveNet Administrator Guide for more information about CLI commands.
Points to Remember
Default reports cannot be restored once deleted. BMC ProactiveNet recommends
that default reports should not deleted from the system.
Asset Reports do not track changes made to the Monitor Wizard based monitors.
In case attributes associated with a monitor created through Monitor Wizard are changed after Asset Report creation, Asset report continues to report on the original attributes.
RAW data is archived after 8 days. To generate reports based RAW data for
longer periods, change the archive settings using pw commands (pw log period). Please note, increasing the archive period has performance impacts, and is not
Points to Remember
recommended. BMC ProactiveNet recommends using RATE data for generating reports for longer periods.
BMC ProactiveNet does not support use of special characters for sub-transaction
names. In case, any of the report includes web transaction monitors with special characters in the sub-transaction names, report is not generated.
For non-restricted users, 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.
8
Managing service levels
What is an SLO?
A service level objective (SLO) is a key component used to evaluate, monitor, and maintain acceptable service levels and compliance with service level agreements (SLAs). SLOs measure the performance of the service provider and are outlined to avert disputes between the two parties on misunderstanding. BMC ProactiveNet enables you to define SLOs in the BMC ProactiveNet system. BMC ProactiveNet monitors and reports on the various aspects of SLOs. SLO administration is the first step in integrating the SLO with the BMC ProactiveNet system.
The SLO Management Console

The SLO Management Console provides an integrated view of all SLOs. SLO views complement existing infrastructure-centric application management solutions. SLO business views help define, measure, and track SLOs. With new business views, business structures are available in a top-down hierarchical view that delivers near real-time service level views of application and service metrics. This view provides valuable information on performance status from an end users perspective for each business unit and SLO compliance. SLO views also represent application performance levels and service levels committed to within the organization. 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. Predefined and custom-defined indicators (SLO types, grouping of required attributes and metrics) present a relational view of objectives and the actual status of SLO compliance. Service level view enables you to take a proactive approach to meeting SLOs. Seamless integration with Violation Summary and Probable Cause
Chapter 8 Managing service levels 399
The SLO Management Console
Analysis within SLO views help extend the IT capability to troubleshoot and pinpoint problems quickly as SLO violations occur. BMC ProactiveNet computes SLO compliance at the end of each day. For example, computation of compliance for September 8, 2013 is available only on September 9, 2013. For more information, see To recalculate an SLO on page 413. Table 97 on page 400 presents the default tabs that are available in the SLO Management Console and additional tabs that you can define, and discusses their functions.
Table 97: 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 415 Viewing SLOs in a hierarchical tree on page 425 Managing SLOs on page 401
Tree
SLO Administration
Compliance Matrix
Viewing SLO compliance details and history on page 416
Also, 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 424 Viewing violation details for an SLO on page 419 Comparing compliance objectives with actual results on page 422
Violation Details Watch List
Also, there is a provision to select a Dashboard View from Options in the SLO Mgmt console.
Customizing basic settings for SLO data display

Using the Options screen, you can customize various aspects of SLO data display.
Managing SLOs
To customize SLO data display

1 Click the Options link at the top right of the Operation Console. 2 In the SLO Mgmt tab, under Display Preferences, modify the settings as necessary. Table 98 on page 401 summarizes the available settings. Table 98: 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, perform the following substeps to add, move, and delete the items to be displayed as tabs in the SLO Mgmt console. a Select an item from the General, SLO Details, or Views box. b Click Add Tab.
Note You can add multiple tabs only for Current Status. However, you must specify a different name for each tab.
c Optionally, to change the order of tabs in the console, use the arrows to the right of the Selected Tabs box. d Optionally, to delete a tab, select the tab in the Selected Tabs box, and then click Delete Tab(s). 4 Click Apply.
Managing SLOs
Through the SLO Administration tab on the SLO Management console, you can manage all the SLOs monitored by BMC ProactiveNet. Related Topics Creating or editing an SLO on page 402 Deleting SLOs on page 405
Managing SLOs
Managing SLO types during SLO configuration on page 405 Managing schedules during SLO configuration on page 406 Managing range sets during SLO configuration on page 408 Requesting guidance for setting SLO thresholds on page 409 Recalculating SLO data for modified time periods on page 412 Resetting SLO compliance data on page 414
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.
To create or edit an SLO

1 On the SLO Management console, click the SLO Administration tab. 2 Click the relevant option:
For a new SLO, click Add. To edit an existing SLO, click Edit.
3 On the first screen (Step 1) of the SLO wizard, specify or modify the SLO attributes summarized in Table 69 on page 361, and then click Next.
Note Only the fields indicated by a red asterisk are mandatory. For all other SLO attributes, you can accept the default settings.
Table 99: 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
Managing SLOs
SLO attribute SLO Contents
Description Type of objects that comprise the SLO, SLOs or Instances SLOs based on instances form base-level SLOs SLOs based on SLOs provide a consolidated view of related SLOs. The grouping can include SLOs based on instances and other nested SLOs. If you choose SLOs, you can create an SLO only for classification by selecting the Use this SLO for grouping only, and not to calculate Aggregate Compliance values option.
Copy from Groups SLO Type
Check this option and select groups to copy from the existing groups. This option is static and acts as a filter. The type of SLO based on the groups to which it is associated Basic SLO types are Availability, Response Time, and System Performance. You can add other types or edit the attributes of the SLO types at this point. See Managing SLO types during SLO configuration on page 405.
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, or if you chose Response Time as the SLO type and want a corresponding Availability SLO created. Select the schedule to apply to SLO monitoring. If required, you can select multiple schedules. This allows you to set threshold values for different time periods. For example, Response time threshold values may not be the same during business and non-business hours. Basic schedules are 24X7 and Business Hours. You can add other schedules or edit the attributes of the schedules at this point. See Managing schedules during SLO configuration on page 406.
SLO Compliance - Objective SLO Compliance - 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. See Managing range sets during SLO configuration on page 408.
4 On the second screen (Step 2) of the SLO wizard, select one or more Group Filter and at least one Monitor Type to associate with the SLO, and then click Next. 5 Select the Monitor Instances to add to the SLO, and then click Next. 6 On the third screen (Step 3) of the SLO wizard, you can modify any of the SLO values summarized in Table 69 on page 361.
Managing SLOs
To modify a specific SLO, enter values directly in the displayed table. To modify multiple SLOs, enter values in the fields below the table as described
in Table 100 on page 404 and then click Apply.
For guidance on setting values based on compliance values recommended by Product Short for the selected monitor instances, click SLO Guidance. For more information, see Requesting guidance for setting SLO thresholds on page 409.
Table 100: Configurable SLO values Setting Service Level Objective: Condition Service Level Objective: Value Minimum Duration Description Condition using which SLOs are compared with actual measurements, 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. 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. Weight associated with the SLO attribute, a whole number greater than zero Associated Weights define the relative importance of an attribute within the SLO (for computation requirements). For example, if Attributes A, B, and C have associated weights of 5, 10, and 15 (respectively), then Attribute C is thrice as important as A, and B is twice as important as A. To ignore SLO violations during computation, specify a weight of zero. 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, select the Set corresponding Instance Intelligent Event Threshold option, and then specify the severity and duration for the event. 8 If you are defining Transaction Monitors, such as a Web Transaction, you can now add (and subsequently delete) sub-transactions on the displayed list. 9 To add a sub-transaction, click Add Sub-Transactions, select sub-transactions from the displayed list and click Apply. 10 To delete sub-transactions, select the relevant sub-transactions and click Delete Sub-Transactions, and then click OK in the confirmation message.
Managing SLOs
11 Click Finish. The new SLO is created and displayed in the SLO list on the SLO Administration screen.
Deleting SLOs
To delete a SLO
1 Select the check box under the Select column corresponding to the SLO that you wish to delete. 2 Click Delete. 3 In the confirmation dialog box, click OK.
Managing SLO types during SLO configuration

An SLO Type is a grouping of related attributes across different monitor types registered with Product Short. An SLO Type defines the attributes to include in compliance calculations. Each SLO has one associated SLO Type. BMC ProactiveNet provides three default SLO Types: Availability, Response Time, and System Performance. You can create new SLO Types during the configuration of an SLO as described in Creating or editing an SLO on page 4023. You can also edit existing SLO Types, that is, add new monitor types and attributes to any existing SLO Type.
To define a new SLO Type

1 On the first screen (Step 1) of the SLO wizard during SLO configuration, click New beside the SLO Type field. 2 Select the Monitor Type(s) to associate with the SLO Type, and then click Next. 3 From the list of attributes corresponding to the selected Monitor Type(s), select the attributes to associate with the SLO Type, and then click Next. 4 Specify a name for the attribute set. 5 Click Finish. 6 In the confirmation dialog box, click OK.
Managing SLOs
To edit an existing SLO type

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

1 On the first screen (Step 1) of the SLO wizard during SLO configuration, select the relevant option:
To create a new schedule, click New beside the Schedule field. To edit an existing schedule, select the schedule in the list, and then click Edit.
2 Specify (or modify) a name for the schedule. 3 Perform the following substeps to define time periods for inclusion or exclusion: a For inclusion, define the start time and end time of the period during one or more days of the week. b Optionally, for exclusion, define either a one-time exclusion time period by specifying the start date and time and end date and time, or a monthly recurrence of days and times to be excluded. Exclusion periods take precedence over inclusion periods. c Click Add to add the period to the list of time periods within the schedule. d After adding all relevant time periods, click Done. e Click Close. To delete a time period included in the schedule, select it in the list and click Delete.
Note
Tip
To delete a schedule
1 On the first screen (Step 1) of the SLO wizard during SLO configuration, select a schedule that you wish to delete from the list, and then click Edit. 2 Click Delete Schedule. 3 In the confirmation box, click OK. 4 Click OK.
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. See Creating or editing an SLO on page 402.
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, select the relevant option:
To create a new range set, click New beside the Range Set field. To edit an existing range set, select the range set in the list, and then click Edit.
2 Specify (or modify) a name for the range set. 3 Select the severity and specify the upper limit of the range in the To Range field. The From Range field is auto-populated. 4 Click Add Compliance Range to add the range to the list of defined compliance ranges on the right. To delete a range from the list of defined compliance ranges (starting with the last defined range), click Remove Compliance Range. 5 Repeat List item. on page 351 and List item. on page 351 for all other relevant ranges in the range set. 6 Click Done.
Note
To delete a range set

1 On the first screen (Step 1) of the SLO wizard during SLO configuration, select the range set in the list, and then click Edit. 2 Click Delete Range Set. 3 In the confirmation dialog box, click OK.
Managing SLOs
Requesting guidance for setting SLO thresholds

During SLO configuration, you can request guidance from in setting thresholds and defining compliance objectives based on past performance. 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, click SLO Guidance. 2 Select the Suggest Thresholds for SLOs option, and then click OK. A list of suggested thresholds is displayed for the relevant monitor instances and attributes. Threshold values are recommended based on raw data points collected for each monitor instance (by default, from the last eight days). 3 Select the thresholds that you want to apply to your SLO, and then click Apply. The thresholds that you chose to apply are highlighted in green. If a threshold was not suggested, the value is highlighted in red. If the suggested value is inaccurate due to NO_RESPONSE data points, the value is highlighted in yellow.
Managing SLOs
Note
Threshold values cannot be suggested for instances without any past data points. Suggested threshold values may not be accurate if data points are repeated. Since data points of the Availability attribute are either 0 or 100%, the
recommended SLO value for the attribute is always 100%.
Changes in SLO compliance or threshold do not affect previously calculated
values, but only new calculations. The new values are displayed throughout the product even though the calculations are based on older values. when calculating the SLO compliance.
BMC ProactiveNet considers NO_DATA and NO_RESPONSE data points
By default, the pronet.businessview.skipND property is set to true and SLO
ignores NO_DATA points. If you set pronet.businessview.skipND to false, SLO treats NO_DATA points as violations.
To preview past compliance values

1 On the third screen (Step 3) of the SLO wizard during SLO configuration, click SLO Guidance. 2 Select the Preview Past Compliance option, and then click OK. 3 Click Close. Compliance values are displayed for each monitor instance and the SLO as a whole. By default, raw data points collected for the monitor over the past eight days are considered. All compliance values are as of the end of the previous day.
To display graphs of past performance

1 On the third screen (Step 3) of the SLO wizard during SLO configuration, click SLO Guidance. 2 Select the Show Past Performance option, and then click OK. 3 Click Close. Individual graphs are displayed in the Graph Display window for each monitor instance based on data collected over the last eight days. For more information, see Creating custom graphs on page 313.
Managing SLOs
Key SLO Computation

Retention for stats data should be at least two days. As generation or computation
happens the next day, Product Short requires the raw data of all the 24 hours for accurate calculation. Calculation begins on the next day after SLO addition. considers the days for which the SLO has been calculated only.
If an SLO is added in the middle of the month, month-to-date compliance
Irrespective of the exact time of creation of the SLO, Product Short considers all
data points for the day during computation. However, violation records (if any) are available immediately on SLO creation. the number of violated points in calculation and the number of violated points in violation details. be accurate and may not match the number of violated points in calculation. current date.
Any change in Service Level Threshold values may result in a mismatch between
In case of server restart, 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, the number of
violated points from calculation may not match the number of violated points in violations details. result in abnormal values for the current week or quarter. This abnormality is corrected from the subsequent week or quarter.
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, the
starting month of the quarter and the starting day of the week is configured in the pronet.conf file. changed.
All old compliance values are invalidated if the start of the week or quarter is
The corresponding default pronet.conf entries are as follows:

pronet.businessview.firstmonthofquarter=0
The above entry represents the first month of the quarter; valid entries are 0 to 11 (Jan to Dec).
Columns displayed in the Compliance Matrix are configured in the pronet.conf file.
Managing SLOs
The corresponding default pronet.conf entries are as follows:

pronet.businessview.showperiods=PD,WTD,MTD,QTD,YTD
The above entry represents the periods to be displayed in the compliance matrix page on the Operations Console. 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.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. When you recalculate a parent SLO, all its child SLOs are also recalculated.
Similarly, if a child SLO is recalculated, its compliance values are reflected in the parent SLO also.
If you change the pronet.businessview.firstdayofweek entry to begin
the week on any other day (by default, Sunday is the first day of the week), do not recalculate SLOs for the week, starting from the day when you changed the entry.
Managing SLOs
To recalculate an SLO
1 On the SLO Administration screen, select the SLOs that you want to recalculate. 2 Click Recalculate. In the SLO Recalculation screen, SLOs that you selected on the SLO Administration screen are displayed in the Selected SLOs field. When you mouse over the selected SLO, the tool tip displays the SLO type and associated schedule. 3 In the SLO Recalculation screen, select the days for which you want to recalculate the SLO values.
BMC ProactiveNet allows you to recalculate data for a period of eight days.
Tip
4 If you want to include or exclude certain time ranges during the specified time period, perform the following substeps: a Select either Inclusion or Exclusion. 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. If you click Recalculate without defining any external time ranges, the SLO is recalculated based on the existing schedule associated with it. When you define a time range and apply it while recalculating an SLO, compliance values are recalculated using the external time range and the associated schedule. The external time range overrides the associated schedule of the SLO. For example, if the associated schedule is to include data collected from 9 AM to 5 PM, and the external time range is to exclude data collected from 10 AM to 2 PM, the data exclusion clause overrides the inclusion clause. The SLO will report data collected from 9 AM to 10 AM and 2 PM to 5 PM. Similarly, for the same associated schedule, if the external time range is to include data collected from 4 PM to 8 PM, the SLO will report data collected between 9 AM and 8 PM. 5 Click Recalculate.
Note
Managing SLOs
Example 'Chk Availability' is an SLO defined to check the availability of a server. The server is expected to be available (Compliance: >= 90%) during business hours (Schedule: 8 A.M. to 5 P.M.). Compliance values of the server between May 9, 2005 and May 13, 2005 are as follow: 05.09.2005: 94% 05.10.2005: 93% 05.11.2005: 75% 05.12.2005: 76% 05.13.2005: 95% The server was made unavailable on May 11 and May 12 between 12 P.M. and 3 P.M. for some unscheduled maintenance tasks, and server compliance values fell below 90 on both days. To exclude the server downtime and recalculate the SLO compliance values anew for the week, the following values are used:
Select Days: From May 11, 2005 to May 12, 2005 Select External Inclusion or Exclusion Time Ranges: Exclusion, Every Day,
Start Time 12 P.M. and End Time 3 P.M.
To delete a time range

1 In the SLO Recalculation screen, select the time range that you want to delete. 2 Click Delete.
Resetting SLO compliance data

Resetting an SLO clears all the compliance history that has been collected for the SLO since it was created. On resetting SLO(s), all compliance values are lost. This action is irreversible.
WARNING
To reset the existing SLO(s)

1 On the SLO Administration screen, select the relevant SLOs in the table. 2 Click Reset SLO.
Viewing the current status of SLOs
Note
Reset SLO is not applicable to an SLO that is created for grouping alone. You
can select one SLO at a time or all the SLOs configured in the system. If you have selected more than one SLO, you are prompted to reset the child SLO attached to the parent SLO.
If you try to reset an SLO, which is referred by other SLO(s), you are prompted
to reset all the references. On clicking Cancel, the selected SLO is reset and not its referenced SLO(s). On clicking Continue, all the SLO(s) are reset.
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. Based on the user access level, you can create multiple versions of the SLO current status page. Each version shows up as a separate tab in the SLO Management console (based on selection). By default, the current status screen displays all the SLOs (configurable) in the system against the SLO Name, Availability, and Response Time. You can use the Set Current Status Preferences option to customize the contents of the current status screen. See Customizing the display of SLO status information on page 416. SLO status details are displayed in a table with several columns of information, as summarized in Table 101 on page 415.
Table 101: Columns of SLO status information on the Current Status tab Column Name Description Provides a link to the SLO Details page. You can expand a nested SLO to view its associated SLOs. Each SLO can be expanded further to view the instances linked to them. At an attribute level, click the hyperlink to view the Instance Details page. For more information, see Viewing a graphical history of SLO compliance and violations on page 424. Availability and Response Time for each SLO Current Status Problem Not Resolved Displays the current violation status for the SLO. In case of an existing violation, click the icon to view the violation details. Represents graphically the longest open violation (if any).
Viewing SLO compliance details and history
Column Previous Week Compliance
Description Previous week compliance of the SLO. It can be configured to display any one of the following: Previous month, Previous week, Week to date, Month to date, Quarter to date, and Year to date. Depending on the Global setting, the compliance is displayed as an icon or a number.
Customizing the display of SLO status information

The Preference screen helps in configuring the current status display. This option is at a user level and differs for each version of SLO current status.
To customize the display of SLO status information

1 Click the Set Current Status Preferences icon. 2 Select the SLOs for which you want to display status information. 3 Select the SLO Types for which you want to display status information. 4 In the Time Period box, select the time periods for which to display status information. 5 In the Other Options box, 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.

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, status, and the recorded compliance levels. The Compliance Matrix tab summarizes SLO details in a tabular format as described in Table 102 on page 417.
Note Compliance values for time periods do not include the data from the current date. All compliance values below the compliance objective are treated as a bad range and the cell is highlighted in red. Colors and ranges are configurable from the first screen (Step 1) of the SLO wizard during SLO configuration.
Table 102: Columns of SLO information on the Compliance Matrix tab Column SLO Type Description Displays the name assigned to the SLO. Provides a link to the Compliance Matrix screen that lists the components of that SLO. Displays the SLO Type associated with the SLO. The SLO Type is a grouping of related attributes across Monitor Types. This column does not apply to Nested SLOs (SLO based on SLOs). Provides a link to the SLO Details screen that gives complete information about the individual SLO, 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. It reflects the real-time Service Level Threshold violations at any level. Valid Statuses are: open (red icon) and closed (green dot). Provides a link to the Violation Details screen in case of an open violation. Provides a link to the SLO Compliance History Report screen. The icons on the top right of this screen let you view the report header, schedule a report, save the page as a PDF or CSV, send an email, or print the page. Displays the compliance objective associated with the SLO. The system compares the actual compliance value against this value. 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, click .
To save the contents of this screen in CSV format, click To view the Compliance Matrix report, click
Related Topics
Viewing a summary of details and compliance metrics for an SLO on page 418 Viewing violation details for an SLO on page 419 Viewing a history graph for an SLO on page 421 Viewing a breakdown of SLO metrics for various time periods on page 421
Viewing a summary of details and compliance metrics for an SLO

From the Compliance Matrix tab > SLO column, you can click an individual SLO link to display a detailed matrix corresponding to that SLO. The matrix lists childlevel SLO instances, and corresponding attributes depending on the type of the SLO. Table 103 on page 418 summarizes the columns that are displayed on drilling down into an individual SLO.
Table 103: 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), and violations. SLO Details tab provides complete information about the individual SLO, and a graphic representation of the compliance levels across different periods (depending on data collected to date). 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). Instance Details Tab is only available in the case of drill-down from instance level. For more information, see Viewing a graphical history of SLO compliance and violations on page 424.
Column Current Status
Description Displays the current status of SLO compliance. It reflects the real-time Service Level Threshold violations at any level. Valid Statuses are: open (red icon) and closed (green dot). Provides a link to the Violation Details screen in case of an open violation. Colors can be set for compliance values only and not for the current status. Icon display depends on the compliance value of the instance. Icons are tied to compliance values during range set definition, and the icon display in all the subsections depends on the corresponding range set definitions. Provides a link to the Graph Display page, 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, you can click an individual SLO link to display the Violations Details page corresponding to that SLO. The Violation Details page provides the Service Level Threshold violation summary and allows the user to sort columns. By default, this screen lists all the violations in the last 24 hours. The Violation Details screen links the SLO with Probable cause Analysis (PCA) and associates Service Level Violation Events and Infrastructure Events. Service Level Threshold violation records are purged at regular intervals. The default value is 31 days. Table 104 on page 419 summarizes the columns that are displayed on drilling down into the current status of an individual SLO.
Table 104: 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
Column SLO Details
Description This column provides a link to the SLO 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), and violations. SLO Details tab provides complete information about the individual SLO, and a graphic representation of the compliance levels across different periods (depending on data collected to date). 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). Instance Details Tab is only available in the case of drill-down from instance level. For more information, see Viewing a graphical history of SLO compliance and violations on page 424.
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. Violated points are not displayed for open violations. Description of the violation The icon in this column provides a link to the Probable Cause Analysis page
Filtering violations
By default, the Violations Details page lists all the violations recorded in the last 24 hours. You can use the query fields to filter the list by various criteria.
To filter the list of violations

1 In the query fields above the list of violations, 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; Min.: 15 minutes, Max: 1 day
Status of the violation record: either Open or Closed; the default is Open Time period: either a predefined interval or a custom time range defined by the
From and To times
2 Click Apply. The list of violations is refreshed according to the specified criteria.
Viewing a history graph for an SLO

From the Compliance Matrix tab > History column, you can click the graph icon for an individual SLO to display a graphical representation of the SLO compliance over a specified duration. The screen provides options to generate the graph for different predefined time ranges.
Viewing a breakdown of SLO metrics for various time periods

From the Compliance Matrix tab > time period columns (Previous Day, Week to Date, Month to Date, Quarter to Date, and Year to Date), 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. Table 84 on page 377 summarizes the columns that are displayed on drilling down into the time period of an individual SLO.
Table 105: 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. SLO Details tab provides complete information about the individual SLO, and a graphic representation of the compliance levels across different periods (depending on data collected to date). 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). Instance Details Tab is only available in case of drill-down from the instance level. For more information, see Viewing a graphical history of SLO compliance and violations on page 424. Graph Weight This column provides a link to the Graph Displays page, which provides options to generate a graph for different predefined time ranges Associated weight
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. Calculation of total points and violated points is based on the schedule of the SLO SLOs compliance objective Instance level compliance
Compliance Objective Compliance Value

The Watch List screen displays SLO records and computed delta values, which is the difference between the compliance objective and its value for the time unit. You can sort by any column. For example, you can sort the compliance percent value for the Month To Date column from worst to best. If the same SLO is displayed in two or more multi-tier SLOs, only one of them is displayed. This screen also provides filters to view specific records. Table 106 on page 422 summarizes the columns that are displayed on the Watch List screen.
Table 106: Columns of information on the Watch List screen Column SLO Type Description Name assigned to the SLO. Link on the name listing directs to the Watch list page specific to that individual SLO SLO Type associated with the SLO. The SLO Type is a grouping of related attributes across Monitor Types. Default SLO Types are Availability and Performance. This column provides a link to the SLO Details page, which provides complete information about the individual SLO, and a graphic representation of the compliance levels across different periods (depending on data collected to date). For more information, see Viewing a graphical history of SLO compliance and violations on page 424. Compliance Objective Month to Date Delta The compliance value associated with the SLO. The system compares the actual compliance value against this objective. SLO compliance for the current month. The compliance computation does not consider the current date. The difference between the compliance value and objective for the specified time period. The compliance computation does not consider the current date.
Details
Related Topics Accessing the Watch List on page 423 Filtering SLO records in the Watch List on page 423 Drilling down to an individual SLO in the Watch List on page 424
Accessing the Watch List

To access the watch list, you must have the Watch List tab added on the Operations Console.
Note
To view the Watch List

1 From the Options => SLO Mgmt tab, under Tab Selection, select Watch List. 2 Click the Watch List tab. 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. You can use the query fields to filter the list.
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.
The available values are: Previous Day, Week to Date, Previous Week, Previous Month, Month to Date, Quarter to Date, and Year to Date.
Show the following SLOs: Select the SLO grouping to view.
Viewing a graphical history of SLO compliance and violations
The available values are: All SLOs, SLOs with compliance below 100%, and SLOs which violate their compliance goals.
Show Top level SLOs Only: Select this check box if you want to include only
top level SLOs in the listing.
2 Click Apply.
Drilling down to an individual SLO in the Watch List

The drill-down from the SLO column displays details of the particular SLO.
Table 107: Columns of information on the Watch List Column SLO Name SLO Type Description SLO name. A link on the SLO name directs you to the Watch List page specific to that individual SLO. SLO type associated with the SLO. The SLO Type is a grouping of related attributes across monitor types. Default SLO types are Availability and Performance. The icon in this column provides a link to the Instance Details page. 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. For more information, see Viewing a graphical history of SLO compliance and violations on page 424. 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 system compares the actual compliance value against this objective.
SLO Details
Month to Date Compliance SLO compliance for the selected time period. The compliance computation does not consider the current date. Delta Weight Difference between the compliance value and objective for the specified time period. The compliance computation does not consider the current date. Associated weight for the attribute
Viewing a graphical history of SLO compliance and violations

Viewing SLOs in a hierarchical tree
From the Compliance Matrix tab, Watch List tab, and Violation Details tab, you can click the SLO Details icon for an individual SLO to view information about an SLO. The SLO Details page displays the following information:
SLO Information: Displays general information about the SLO. Compliance Summary: Displays a graphical representation of the compliance
levels within the last 24 hours.
SLO Violation History: Displays the various SLO instances with a description of
the threshold condition, a weight, a graphical indication of the current status, and a graphical representation of the violation history.
Tip On the Current Status tab, click the link in the Name column to view a graphical representation of an individual SLO.
From the SLO Details screen, you can perform the following tasks:
In SLO Information, click Edit to add comments. 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.
To generate an SLO Health Summary report, click Generate SLO Health
Summary Report
For more information on the health report, see Health Summary on page 380.
Viewing instance details

To access the Instance Details screen, click the link in the Thresholds Conditions column on the SLO Details screen. The Instance Details screen provides complete information about an individual instance, displays a line graph (default) and violations (if any) for the selected instance based on data collected over the last 24 hours.

The Tree tab in the SLO Management Console provides a real-time, interactive visualization of the SLO violation status. The SLO hierarchy and IT Groups are visible on a hyperbolic plane mapped to a circular display region.
SLOs displayed are based on the Access Control level of the user. For example, a user may be restricted to view only a subset of SLOs that exist in the system. If the BMC ProactiveNet Server is within the firewall and the Operations Console is outside the firewall, the tree might not be displayed properly in Firefox 1.5. To ensure proper display of the tree, perform the following steps on Windows 2000 or XP:
To ensure proper display of the tree on Firefox 1.5 browser

1 In the Control Panel, double-click the Java icon. 2 In the Java Control Panel, click Network Settings, and then change the default option, Use browser settings to Direct connection. Related Topics Controlling the display in the SLO Tree on page 426 Accessing further information from the SLO Tree on page 427
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. To control the display on the tree, you can perform the following tasks:
To change the focus point on the tree, drag any point on the tree. To focus on the SLO, right-click the SLO icon and choose Set As Root to set the
selected SLO as root.
Only the selected SLO and its child nodes are displayed.
To display or hide the legend, click Show Legend or Hide Legend. To filter SLOs by maximum violation duration, select the time from the Time list.
The SLO tree is refreshed to display only those SLOs for which violations occurred within the selected time duration.
To promote the page as an independent tab, click Promote as Tab, specify a name
for the new tab, and then click Apply.
To change the data refresh interval

1 Data refresh interval (in seconds) for the SLO Tree can be specified using the pronet.applet.slatree.refreshRate property in the installDirectory/usr/pw/ custom/conf /pronet.conf file.
Accessing further information from the SLO Tree

From the SLO tree, you can access various screens to view further information about the SLO or the SLO instance.
On the SLO level, you can perform the following operations: Access the SLO Details page, by right-clicking the SLO, and then choosing SLO
Details.
For more information, see Viewing a graphical history of SLO compliance and violations on page 424.
Access the Compliance Matrix page, by right-clicking the SLO, and then choosing
Compliance Matrix.
For more information, see Viewing SLO compliance details and history on page 416.
On the SLO instance level, you can perform the following operations: Access the SLO Instance Details page, by right-clicking the SLO instance, and then
choosing SLO Instance Details.
For more information, see Viewing instance details on page 425.

Access the Probable Cause Analysis page, by right-clicking the SLO instance, and
then choosing Probable Cause.
For more information, see Determining the probable cause for an event on page 221.
9
Managing 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. To use this option the BMC ProactiveNet administrator assigns the 'Allow Collect Data Management' privileges. The Data Collection option is available in the Tools menu of Device Matrix, Group Matrix, Device and Group nodes of Group Tree, Show Monitors, and Options Administration. Data collection management is available only to the following types of users:
Users who have administrator privileges. Users who have access to all CIs and have permission to manage data collection.
Restricted users with permission to manage data collection have access only at a Monitor level. Restricted users do not have access to the Manage Data Collection option on the Group and Device levels, even if the user is assigned the required permissions. For restricted users, the display is as follows:
The Data Collection link on the Options > Administration page appears as locked. The checkbox Data collection is selected in the Show Monitors page.
To change data collection settings

1 Click the Options link at the top right of the console.
Chapter 9 Managing BMC ProactiveNet data collection and infrastructure 429
Activating and deactivating data collection
2 On the Administration tab, under the Data Collection heading. Click Edit link of Data Collection. 3 Select the View Type (By Device, By Monitor Type, and By Group) for display on the Data Collection Administration screen. 4 Click the Device Name, Monitor Type, or Group Name to view associated monitors. 5 Perform the following actions at individual monitor level or at the Group, Device, or Monitor Type level: a Select the check box corresponding to the monitors to alter their data collection. b Select On/Off option from the list corresponding to the monitors. 6 Click Apply. Related Topics Scheduling downtime on page 431 Tracking changes to BMC ProactiveNet objects on page 438 Viewing BMC ProactiveNet and PATROL agent statuses on page 439 Managing attribute sets on page 443 Managing baselines on page 445 Knowledge patterns on page 225 Managing relationships on page 462 Managing schedules on page 474 Importing and exporting users on page 476 Viewing BMC ProactiveNet software information on page 479
Scheduling downtime
Scheduling downtime
The Scheduled Down Time feature for devices, monitors, and groups allows BMC ProactiveNet administrators to specify a time range during which the monitor, device, or group stops collecting data. Scheduled Down Time management is available only to the following types of users:
Users who have administrator privileges. Users who have access to all CIs and have permission to schedule down time.
Scheduled Down Time is not available to restricted users, even if the user is assigned the required permissions. For restricted users, the Scheduled Down Time link on the Options > Administration page appears as locked. The Scheduled Down Time feature supports multiple schedules with different time ranges. You can schedule down time for the following frequencies:
One-time Daily Weekly Monthly
The scheduler polls the database periodically for downtime events. By default, this period is five minutes; therefore, down-time events cannot be scheduled with finer granularity than five minutes. In addition, if a large number of devices is scheduled, it may take some time for the scheduler to turn off data collection for the scheduled devices. To avoid the possibility of false events at the beginning of the maintenance window, BMC ProactiveNet recommends that the downtime event be scheduled 15-20 minutes ahead of the actual maintenance period.
Scheduling downtime
Note While scheduling downtime, allow fair time for the device, monitor, or group to stop data collection. The time taken to stop data collection and then resume data collection depends on the server load, number of agents, and number of monitors scheduled for down time. In Windows Day and Time Properties, select Automatically adjust clock for daylight saving changes. This should always be selected to show the appropriate default time zone.
Note for upgrade users

New and upgrade users have different options available to them in this feature. Upgrade users can still access the Alarm/Event Generation, AlarmRule Action/ Notification, and Calculate Baseline options from the Add Device for Scheduled Down Time dialog. For example, 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, then the Calculate Baseline option is enabled. Upgrade users have the option to turn baseline calculation off or on when Data Collection is on. (When Data Collection is off, the Calculate Baseline option is disabled because there is no data to calculate.)
Usage scenario
This topic depicts a typical data sample that can consists of the following test data.
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 Time taken to stop data collection: 10 - 15 minutes
Scheduling downtime
Time taken to resume data collection: 1 - 5 minutes
To understand the usage of the Scheduled Down Time feature, let us look at the following example: Assumptions:
BMC ProactiveNet is monitoring a web server for availability and response time. The web server is brought down on Sunday between 4 A.M. and 8 A.M. for
maintenance.
Operations:
During regular monitoring, BMC ProactiveNet will poll for the monitored
attributes and report.
During downtime, both availability and response time will not return data and
alarms may be generated.
These alarms will automatically close after the web server is online again.
To schedule the web server downtime

1 Select the web server. 2 Select the Downtime option. Data collection is on. Alarm/Event generation is on. AlarmRule Action/Notification is off. 3 Frequency is Weekly. 4 Specify the Time and Date as applicable. 5 Add Time Range. Application: In the above case, BMC ProactiveNet will monitor the Web server for availability and response time even during the device downtime and generate event or alarm. However, any event or alarm generated during this period will not be notified. The advantage of this setup is that, BMC ProactiveNet console will display the events. Once the device is up again, the events will close. Thus the administrator can check the system and ensure that the web server is working as expected before the time to get it online. However, in case of SLOs defined for availability of this device, data collection can be switched off to avoid inconsistent SLO compliance calculation.
Scheduling downtime
Adding a downtime schedule

To add a downtime schedule
1 In the BMC ProactiveNet Operations Console, launch the Scheduled Down Time Administration window. Choose Options => Administration => Data Collection => Scheduled Down Time => Edit. In the BMC ProactiveNet Administration Console, select Tools => Schedule Device Downtime. The Scheduled Downtime Administration window is displayed. All devices or groups that are currently down are highlighted in Red. 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, Solaris, and Linux). 2 Choose a Filter. You can choose to filter the list by Device or by Group. If you choose to filter by Device, and are monitoring numerous devices, the list can be quite extensive. You can narrow your device search if Groups have been set up for your devices. 3 Click Add to open the Scheduler. Next, you specify the duration of the down time. 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, 1 Select the Device to be scheduled. New users can skip to step 3. 2 Upgrade users only. Select the Downtime option. These settings govern BMC ProactiveNet behavior during the scheduled downtime.
Scheduling downtime
Data Collection: Select On or Off to continue collecting data or stop data
collection respectively.
In case data collection is On,

Alarm/Event Generation: Specify if BMC ProactiveNet should generate Events/
Alarms against the data collected.
In case Alarm/Event Generation is On,

Alarm Rule Action/Notification: Specify if BMC ProactiveNet should send
alarm notification for the alarms generated during this period.
In case Calculate Baseline is Off, Calculate Baseline is a scheduled downtime for baseline calculations. During this period, previously calculated baseline is used. The baseline stays unaffected by new data. Hourly baseline is not recalculated and previous values are used. Daily and weekly baseline values are recalculated based on the hourly baseline. At the time of baseline calculation, BMC ProactiveNet checks for the pause period corresponding to the current time. During the pause period, only old values are used. Outside the pause period baseline calculation is performed using current data. 3 Select the Frequency:
Frequency One Time Setting Daily Weekly Monthly Description The downtime is scheduled to run once. It is not a recurring setting. The downtime is scheduled run daily at the specified time. The downtime is scheduled weekly at the specified day and time. The downtime is scheduled to occur monthly on the specified day and time.
4 Under Time Pattern field, select the Start and End Date. Manually specify the dates in mm/dd/yyyy format. Alternatively click the calendar link and select from the pop-up calendar. 5 Select the Start Time and End Time. By default, the server time is displayed here. 6 From the list, select the Time Zone. By default, the server time zone is displayed here. When you change the time zone, the Start Time and End Time change accordingly. If you change the Time Zone and the corresponding time falls either in the previous day or the next day, the Start Date changes accordingly.
Scheduling downtime
Note The Time Zone field displays GMT + Time Zone difference in hours, together with location.
From 7.1, Time Zone for Indiana-Starke displays GMT 05:00 US/Indiana-Starke instead of GMT 5:00 as in 7.0. 7 Click Add Time Range . 8 Click Yes to confirm.
To change the specified time and date combinations, Select the entry under Time Range Entry. Click Remove Time Range.
After specifying the required time and date combination, 9 Click Add. The system presents various alerts or confirmatory messages. On confirmation, BMC ProactiveNet adds the schedule to the device. 10 Click Yes to confirm the schedule. 11 In the Added Successfully dialog box, click OK . 12 After defining the required Device Downtime, click Close.
Edit/Delete downtime schedule

Once a schedule is set, you can view and edit it by following the procedure given below:
To edit/delete downtime schedule

1 If the Scheduler is closed, open it from Tools menu on the Administration Console.
The Scheduler presents the Devices Scheduled selection. Selection is displayed
in red if opened during its own scheduled time.
2 Highlight the device whose schedule you want to change and click Edit. (If you want to delete the schedule, click Delete.) 3 Modify the schedule as required, and click OK.
Scheduling downtime
Note BMC ProactiveNet does not allow editing of multiple schedules at a time.
To delete a schedule, select the schedule from the list and click Delete.
Special notes
Do not perform any operations (monitor creation, flash check, etc) on devices
during their scheduled downtime. This can result in unexpected behavior and display of invalid data. data collection.
If the devices data collection is off, schedule downtime has no affect on the device
From Release 6.5, editing multiple schedules is not allowed. A schedule cannot be edited while it is active (during downtime). In case of overlapping downtime, data collection resumes after the higher
schedule is completed.
Example: Consider the following schedules: Weekly: down at 9:00 A.M. - up at 10:30 A.M. Daily: down at 9:30 A.M. - up at 10:00 A.M. In this case, data collection resumes only after 10:30 A.M. (though the daily downtime is from 9:30 A.M. to 10:00 A.M., we have an overlapping weekly downtime from 9 A.M. to 10:30 A.M.). Related Topics Activating and deactivating data collection on page 429 Tracking changes to BMC ProactiveNet objects on page 438 Viewing BMC ProactiveNet and PATROL agent statuses on page 439 Managing attribute sets on page 443 Managing baselines on page 445 Knowledge patterns on page 225 Managing relationships on page 462 Managing schedules on page 474
Tracking changes to BMC ProactiveNet objects
Importing and exporting users on page 476 Viewing BMC ProactiveNet software information on page 479
Tracking changes to BMC ProactiveNet objects

In production environments, software and hardware requirements change constantly and need modification on the fly. This regular change necessitates a high degree of change management. BMC ProactiveNet can store and track configuration data, and provide information on the possible impact to your Web environment. The Configuration Changes option is available only to the following types of users:
Users who have administrator privileges. Users who have access to all CIs and have permission to Allow Change tracking.
For restricted users, the Configuration Change link on the Options > Administration page appears as locked.
To track changes in your environment

1 Go to Options => Administration => Configuration Changes => Add/View. 2 Set the Time Filter. Default is the current time 3 Select the Device from the list. List includes all devices in the system.
The screen displays all the available entries related to the selected device.
To add a new entry

1 Click Add. This displays the Add Configuration Change Event screen. This feature is also accessible from the following flows:
Devices (Grid View) => Tools. Devices (Grid View) => Monitor list => Tools. Groups (Grid View) => Tools.
Viewing BMC ProactiveNet and PATROL agent statuses
2 Inputs for Add Change Entry screen.

User: Name of the user. By default, the login name of the current user is displayed. 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. Related Topics Controlling the display in the Services Tree View on page 138 Managing configuration changes on page 158 Viewing further information for a specific event from the Tools Menu on page 51

The BMC ProactiveNet Agent controls all service monitors (non-SNMP monitors) and is responsible for spawning the creation of monitors, collecting their data, and delivering the data to the BMC ProactiveNet Server for storage in the database. Remote BMC ProactiveNet Agents are located on computers other than the computer hosting the BMC ProactiveNet Server. The local BMC ProactiveNet Agent or BMC ProactiveNet Server Agent is installed with and functions as a part of the BMC ProactiveNet Server. PATROL Agents are connected to the BMC ProactiveNet Server through the Integration Service which is hosted on BMC ProactiveNet Agents.
The Agent Status screen lists the current operating status of both the BMC ProactiveNet agents. The BMC ProactiveNet Agent Status screen also displays an event summary of the agents monitors. Go to Options => Administration => Agent Status. The BMC ProactiveNet Agent properties columns are listed in Table 108 on page 440.
Table 108: Status information for BMC ProactiveNet Agents Agent Properties Description The Agent column indicates if there is a BMC ProactiveNet Agent attached to the device, and its connection status (connected or disconnected). A green plugged-in icon indicates the ProactiveNet Agent is connected, and a red unplugged icon indicates the ProactiveNet Agent is disconnected. Agent Name Agent Version IP Address OS Name Last Connected Running Since Tunnel ID Connection Type Agent Status Displays the name of the ProactiveNet Agent as defined by BMC ProactiveNet administrator. Displays BMC ProactiveNet version and build number of the ProactiveNet Agent. Displays the IP Address of the system hosting the BMC ProactiveNet Agent. Displays the name and version of the operating system on the system hosting the BMC ProactiveNet Agent. Displays the latest date and time when the BMC ProactiveNet Agent connected to BMC ProactiveNet Server. Displays the date and time that the BMC ProactiveNet Agent started running. If a TunnelAgent is present, this column displays the Tunnel ID for the TunnelAgent. Displays the type of connection in use by the BMC ProactiveNet Agent. Displays the current operating status of the ProactiveNet Agent. Valid states are: Connection Active, indicated by the green plugged-in icon Agent Unreachable, indicated by the red unplugged icon No Agent, indicated by N/A. Monitors Provides access to all the monitors on that device or resource. Use the Monitors hyperlink to view event summary by Monitor Type (of all the monitors associated with a specific device). This screen displays events and provides tools for managing them.
The BMC PATROL Agent status columns are listed in Table 109 on page 441.
Table 109: Status information for BMC PATROL Agents Agent Properties Description Connection status of the PATROL Agent is displayed as two different icons in three different scenarios as explained in PATROL Agent status icon and tooltip on page 441. A tooltip on the PATROL Agent status icon displays the connection status of the PATROL Agent as well as the Integration Service. Name Port Proxy Agent Hostname/IP Proxy Agent Port Status Displays the name of the PATROL Agent as defined by BMC ProactiveNet administrator. Displays the port number on which the PATROL Agent is running. Displays the host name or IP address of the Integration Service (ProactiveNet Agent) on which the PATROL Agent is configured. Displays the port number on which the Integration Service is running. Displays the current operating status of the agent.
You can filter the PATROL Agents based on the PATROL Agent name, Integration Service name, and PATROL Agent status when you select the PATROL Agents tab.
Note
If the same PATROL Agent is configured on multiple Integration Services, the
Agent Status screen displays these PATROL Agents on multiple rows--one for each Integration Service. in the machine.
The PATROL Agents tab is available only if at least one PATROL adapter exists
The PATROL Agents tab is available only if the Proxy_Connection_Info KM is
imported and selected while creating the PATROL adapter instances in the system.
PATROL Agent status icon and tooltip

The agent status icons and the tooltip are displayed as follows in three different scenarios. Table 110: PATROL Agent status icon and tooltip
Scenario PATROL and the Integration Service are up and running. PATROL and the Integration Service are down or disconnected. Status icon Tooltip PATROL Agent - Connection Active PATROL Agent - Disconnected Integration Service - Disconnected
Scenario PATROL Agent is down, but the Integration Service is up and running.
Status icon
Tooltip PATROL Agent - Disconnected Integration Service - Connection Active
Drill down from the agent status table

To drill down from the agent status table
1 Click Monitors under the Monitors column.
BMC ProactiveNet displays all Monitors associated with the Agent.
2 Click the Severity Event icon to view Event List screen.

The Event List screen displays all open events corresponding to the monitor.
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. Related Topics Activating and deactivating data collection on page 429 Scheduling downtime on page 431 Tracking changes to BMC ProactiveNet objects on page 438 Managing attribute sets on page 443 Managing baselines on page 445 Knowledge patterns on page 225 Managing relationships on page 462 Managing schedules on page 474 Importing and exporting users on page 476 Viewing BMC ProactiveNet software information on page 479
Managing attribute sets

An Attribute Set is a list of related performance attributes (metrics) that, taken together, represent a more abstract functional grouping of those individual attributes. Custom Attribute Sets are required for creating advanced relationships. Once these functional groupings are established, they can be used to leverage relationships between various elements in the infrastructure. The product is delivered with a group of out-of-the-box attribute sets. These include, for example, to create a relationship between Web Servers and CPU usage, you can create an Attribute Set for all CPU usage performance attributes across all platforms. In this case, you can create an Attribute Set containing Windows System CPU usage, Solaris System CPU usage, AIX System CPU usage, etc. By creating an attribute set as discussed in the above example, we can do away with creating different relationships for each system monitor type. 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. To transfer performance data from BMC ProactiveNet Server to the report engine, create an attribute set of type External Report. To perform any operation (create/edit/ delete) on this attribute set, you must have "External Reports" permissions. By default, "External Reports" permissions are available for users with the following roles:
Full access Cloud Administrator Unified Central Admin.
For more information on roles and permissions, see the "Roles and Permissions" section in the BMC ProactiveNet Administrator Guide. This feature is recommended only for advanced users who are trained and familiar with the Probable Cause capabilities of BMC ProactiveNet. BMC ProactiveNet recommends not editing default Attribute Sets (with the exception of adding new custom monitors). During upgrade, the system only carries forward the new attributes (added), and does not check for deletions. See, Managing relationships on page 462 for more information on how Attribute Groups can be used.
To create or edit a new attribute set from the Operations Console

1 Go to Options => Administration => Attribute Sets => Edit.
2 Click the relevant option:

For a new attribute, click Add on the AttributeSet Administration screen. To edit an existing attribute, click Edit. Click Add Attributes to add more
attributes.
3 On the Add Attribute Set screen, select the Attribute Set Type from the list. Options are Global, Relationship, Report, SLO, External Report type. 4 Select the Monitor Type. Select all monitors types corresponding to the attributes to be grouped.
Use the Shift and Ctrl keys to make multiple selections. To locate a specific
monitor, use the Search For field.
5 Click Next. 6 Select the Attributes to be grouped from under each of the Monitor Types in the Attributes section.
Use the Shift and Ctrl keys to make multiple selections. To locate a specific
attribute, use the Search For box.
7 Click Next. 8 Specify a name for the Attribute Set. 9 Select the Attributes to be included by selecting the corresponding check boxes under the Select column. 10 Click Finish.
The new Attribute Set is available for use.
To delete an attribute set

1 Open the Attribute Set Administration screen. 2 Select the check box under Select corresponding to the Attribute Set to delete. 3 Click Delete. 4 Click OK in the confirmation screen.
BMC ProactiveNet confirms and deletes the Attribute Set.
5 Click OK to return to Attribute Set Administration screen.

Managing baselines
Default Attribute Sets cannot be deleted.
Related Topics Activating and deactivating data collection on page 429 Scheduling downtime on page 431 Tracking changes to BMC ProactiveNet objects on page 438 Viewing BMC ProactiveNet and PATROL agent statuses on page 439 Managing baselines on page 445 Knowledge patterns on page 225 Managing relationships on page 462 Managing schedules on page 474 Importing and exporting users on page 476 Viewing BMC ProactiveNet software information on page 479
Managing baselines
The baseline is the expected normal operating range for a metric or attribute of a monitor. The baseline is calculated by collecting the values for a monitors 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), taking a weighted average of these values over time. A higher weight is given to the latest data being factored into the baseline average. The accuracy of the baseline improves over time. To track the anomalies in behavior for different attribute types, different patterns are required. For example, for attributes that change frequently, a pattern captured at hourly intervals may be best. Hourly interval ranges represent a smaller number of data points and will have a tighter range, which is best suited for capturing frequent changes. BMC ProactiveNet captures the following baseline patterns:
Managing baselines
Hourly baseline - Each hour of the day has a high or low value that is tracked.
This tracks the pattern for that metric on an hourly basis, and is repeated for each day. An hourly baseline is initialized after the monitor instance is created and 24 hours of data collection has occurred. consecutive day. This high or low range is taken from a larger number of data values and consequently will be a wider range than the hourly. A daily baseline is initialized after the monitor instance is created and 24 hours of data collection has occurred. days share the same 24-hour baseline. A weekly baseline is initialized after the monitor instance is created and 168 hours of data collection has occurred. and Sunday. These two days share the same 24-hour baseline.
Daily baseline - A high or low value is derived from the moving average of each
Weekday Pattern - Baseline is calculated daily from Monday to Friday. All these
Weekend Pattern - Baseline is calculated separately for the weekend - Saturday
Seasonal baseline - Baseline is calculated separately for pre-determined days
when your business experiences out of the ordinary workloads or other special behavior. These days, if calculated into the baseline, artificially will raise or lower the baseline, causing unnecessary abnormalities.
Baseline Administration provides a better control over baseline calculations. For example, you can specify freeze points to discard values corresponding to specific period. Similarly, if the baseline is not correct, it can be easily reset. You can also create baselines for special or seasonal dates.
Requirements for baseline generation

For baselines to be generated for an attribute, that attribute must have an active abnormality threshold. An active abnormality threshold means that the threshold exists and is not suppressed. Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have an active abnormality threshold and are also KPI attributes will have baselines generated for them. Absolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements.
Pausing baseline calculation

Pausing baseline calculation allows you to schedule downtime for baseline calculations. During this period, the previously calculated baseline is used. The baseline stays unaffected by new data.
Managing baselines
For example, you might want to set a pause period for the holiday season when Web traffic is expected to peak. Because this is an isolated case and not a regular pattern, you might want to discard this data for the overall baseline. Hourly baseline is not recalculated and previous values are used. Daily and weekly baseline values are recalculated based on the hourly baseline. At the time of baseline calculation, BMC ProactiveNet checks for the pause period corresponding to the current time. During the pause period, only old values are used. Outside the pause period baseline calculation is performed using current data. Through the Options screen you can add new baseline calculation periods, as well as edit or delete previously defined baseline calculation periods.
To define or edit a Pause Baseline Calculation Period

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

1 Go to => Options => Administration tab. 2 Click Edit corresponding to Baseline Administration. On the Pause Baseline Calculation screen, select the check box (corresponding to the Pause Period to delete) under Select column. 3 Click Delete. 4 Click OK in the confirmation screen. The system deletes the Baseline Pause Period and returns to Administration screen. Confirmation is displayed on the Administration screen.
Resetting a baseline
Baseline can be reset to re-compute the baseline. On Reset, the baseline data is reinitialized based on previous data generated from the same instances. 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). Baseline values are refined over time as the pattern is relearned. The Reset Baseline option is displayed only to users who have administrator privileges and unrestricted access to groups.
Note
To reset a baseline
1 Click Reset Baseline on the baseline Administration screen. 2 Select the Monitor Instances.
Group - Select the Group to include all the instances in the group. 448 BMC ProactiveNet User Guide
Managing baselines
SLO - Select SLO to include all instances from the SLO. Device - Select the Device to include all the instances associated with the device. Monitor Type - Select the Monitor Type to include all instances of the monitor
type.
Monitor Instance - Select the Monitor Instance to include the single monitor
instance.
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.
Number of days for considering data.
4 Select the baseline types to be reset. Specify at least one of available baseline types (hourly, daily, or weekly). 5 Click Reset.
Note
Baseline reset at the attribute level does not change historic values. It modifies
only baseline values computed for future use.
If you select All Attributes as the Monitor Attribute Selector, then all baseline
values of the current day are reset. If you select a single attribute, then the attribute baseline value of the current hour is reset.
Baseline Administration is available only to the following types of users: Users who have administrator privileges. Users who have access to all CIs and have permission for baseline
administration.
This option is not available to restricted users, even if the user is assigned the required permissions.
Creating a separate baseline for seasonal or special dates

In your organization, there may be pre-determined days when your business experiences out of the ordinary workloads or other special behavior. These days, if
Managing baselines
calculated into the baseline, artificially will raise or lower the baseline, causing unnecessary abnormalities. 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. The seasonal baseline can be applied to all groups and services or to specified groups and services. There are two types of dates that you can account for using the baseline seasonality functionality:
specific seasonality datesplanned, single days with exceptional behavior, such
as special sales and holidays
recurring seasonality datesevents that repeat on a regular basis with exact
frequency, such as weekly or monthly payroll and backups
In the Operations console, you control the baseline seasonality feature using the Baseline Seasonality Administration page.
To access the Baseline Seasonality Administration page

1 From the Operations Console, choose Options. 2 On the Options page, choose the Administration tab. 3 In the Advanced area of the Administration page, next to Baseline, click Edit.
The Baseline Administration page is displayed.
4 On the Baseline Administration page, click the Baseline Seasonality link.

The Baseline Seasonality Administration page is displayed.
Use the Baseline Seasonality Administration page for

Creating a baseline seasonality instance on page 450 Editing or deleting a baseline seasonality instance on page 454
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. The data retention period for the device should be at least as long as the baseline
Managing baselines
seasonality schedule. If the retention period is insufficient, a warning message is displayed on the Baseline Seasonality Administration page. For example, if the default retention period for a device is 90 days and you schedule a baseline seasonality schedule for every six months, the data retention period is too short and the Baseline Seasonality Administration page will display a warning message that there insufficient data retention. For baseline seasonality to work, the rate and baseline data must cover the longest span of time between seasonality days that is in any seasonality schedule. For example, if the seasonality schedule is one year apart, then the longest span of time between days in the schedule is one year. In that case, the rate and baseline tables must be able to hold data for one year. For information about listing and setting the data retention period, see the pw log period CLI section in the BMC ProactiveNet Administration Guide.
Plan your baseline seasonality schedules so that there are no duplicate schedules
for any instance, group, or all instances.
If there are duplicate schedules, a specific group will take precedence over a global instance. If both schedules are for specific groups, precedence is determined alphabetically by the baseline seasonality name, not the group name. For example, if seasonality A is for group Z and seasonality B is for all instances, seasonality A takes precedence. If seasonality A is for group Z and seasonality B is for group Y, then A still takes precedence. If duplicate schedules are created, a warning message is displayed on the Baseline Seasonality Administration page. Related Topics: To create a seasonality baseline for single, specific seasonality dates on page 451 To create a seasonality baseline for events that occur on a regular basis on page 452
To create a seasonality baseline for single, specific seasonality dates

1 Access the Baseline Administration page as described in To access the Baseline Seasonality Administration page on page 450. 2 On the Baseline Seasonality Administration page, click Add. 3 In the Baseline Seasonality Name field, enter a general name to identify the specific dates that you will be entering. For example, Sale Days. 4 In the Monitor Instance Selector area, choose the monitor instances that will be affected by these special dates.
If the special dates will affect all of your systems and services, choose All
Instances.
Managing baselines
If the special dates only affect one or more of your systems and services, choose
Group and follow these steps:
a Click the linked text next to Group.

The Select/Group dialog box is displayed.
b From the Select/Group dialog box, choose the group that will be affected by the dates you are adding. c Click Apply to accept your selection and close the dialog box. 5 Choose the Set Specific Seasonality Dates radio button. 6 In the Pick Date field, select the month, day, and year of the special date for which you want to create a seasonality baseline. 7 Click Add Date. The date is displayed in the Included Dates list. 8 [Optional] Repeat List item. on page 452 and List item. on page 452 to add additional dates. 9 When you have finished adding dates, click Add. The date or group of dates that you added appears in the list of dates on the Baseline Seasonality Administration page.
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 450. 2 On the Baseline Seasonality Administration page, click Add. 3 In the Baseline Seasonality Name field, enter a general name to identify the specific dates that you will be entering. For example, Weekly Backups. 4 In the Monitor Instance Selector area, choose the monitor instances that will be affected by these special dates.
If the special dates will affect all of your systems and services, choose All
Instances.
If the special dates only affect one or more of your systems and services, choose
Group and follow these steps:
a Click the linked text next to Group.
Managing baselines
The Select/Group dialog box is displayed. b From the Select/Group dialog box, choose the group that will be affected by the dates you are adding.Click Apply to accept your selection and close the dialog box. 5 Choose the Set Seasonality Recurrence Pattern radio button. 6 In the Start From field, choose the date from you want to start the first occurrence of the seasonality baseline. The start date can be a past, current, or future date. You can either select the month, day, and year from the drop lists or you can click the calendar icon and double-click the desired date. 7 Specify the occurrence frequency of the special event that you are adding:
If the special event occurs every week or every few weeks, such as a weekly or
twice per week backup procedure, follow these steps:

Choose the Weekly radio button.
Enter the number of weeks between occurrences of the special event in the
Recur every __ weeks on field.
Select the check box for the day of the week on which the event occurs.
If your organization has a backup procedure every two weeks, enter 2 in the Recur every __ weeks on field. If the backup procedure occurs every week, you would enter 1 in the Recur every __ weeks on field.
Example
If the backup procedure always takes place on Sunday, select the Sunday check box.
If the special event occurs each month or every few months, such as payroll or
Example
inventory, follow these steps:
Choose the Monthly radio button. Specify the monthly frequency of the special event:
If the special event occurs on the same day each month or every few months, choose the Day __ of every __ month(s) radio button and enter the day of the month and the monthly frequency for the special event.
Managing baselines
Example If the special event always occurs on the 30th day of the month, you would enter Day _ 30 _ of every _ 1 _ month(s).
If the special event occurs on the same day of the week at the same frequency each month, choose the The __ __ of every __ month(s) radio button and select the monthly occurrence of the day of the week, the day of the week, and the monthly frequency for the special event. If the special event occurs on the last Friday of every third month, you would enter The _ Last _ _ Friday _ of every _ 3 _ month(s). 8 Click Add. The recurrence pattern that you added appears in the list of dates on the Baseline Seasonality Administration page.
Example
Editing or deleting a baseline seasonality instance

Once you have created a baseline seasonality instance, you can edit or delete it. If you delete a baseline seasonality instance that you have created, 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.
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 450. 2 On the Baseline Seasonality Administration page, click Edit to the right of the baseline seasonality instance that you want to edit.
The Edit Baseline Seasonality dialog box is displayed.
3 In the Edit Baseline Seasonality dialog box, make the required changes to the baseline seasonality instance. 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 450.
Managing baselines
2 On the Baseline Seasonality Administration page, select the check box of the seasonality baseline instance that you want to delete. 3 Click Delete. 4 In the confirmation dialog box, click OK.
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
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, so you need to create a seasonality baseline for these sale days to avoid triggering abnormalities due to the increased load on these days. Your organization is closed on Sundays and on the following holidays:
New Years Day, January 1 Groundhog Day, February 2 International Earth Day, March 20 International Tuba Day, May 8 International Picnic Day, June 18 International Talk Like a Pirate Day, September 19 World Teachers Day, October 5
Managing baselines
World Peace Day, November 17
When your organization is closed, the load on your systems and services drops considerably, 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. Your organization pays its employees every two weeks on Fridays and performs inventory quarterly. Based on these facts, your organization should set seasonality baselines as follows.
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 450. 2 On the Baseline Seasonality Administration page, click Add. 3 In the Baseline Seasonality Name field, enter Sale Days. 4 Because these sales increase the load on all your systems and services, in the Monitor Instance Selector area, choose All Instances. 5 Choose the Set Specific Seasonality Dates radio button. 6 In the Pick Date field, select May 31 of the current year. 7 Click Add Date. The date is displayed in the Included Dates list. 8 Repeat List item. on page 452 and List item. on page 452 to add the additional sale dates.
Managing baselines
Figure 25 on page 458 shows the Add Baseline Seasonality page after the data
has been entered.
Figure 24: 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.
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 450. 2 On the Baseline Seasonality Administration page, click Add. 3 In the Baseline Seasonality Name field, enter Sundays. 4 Because your business is closed, this decreases the load on all your systems and services. Therefore, in the Monitor Instance Selector area, choose All Instances.
Managing baselines
5 Choose the Set Seasonality Recurrence Pattern radio button. 6 In the Start From field, choose the first Sunday in January. 7 Choose the Weekly radio button. 8 In the Recur every __ weeks on field, enter 1. 9 Select the Sunday check box.
has been entered.
Figure 25: Baseline Seasonality for Sundays
10 Click Add.
Managing baselines
Every Sunday is added as a recurring pattern for a new seasonality baseline on the Baseline Seasonality Administration page.
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 450. 2 On the Baseline Seasonality Administration page, click Add. 3 In the Baseline Seasonality Name field, enter Holidays. 4 Because these holidays decrease the load on all your systems and services, in the Monitor Instance Selector area, choose All Instances. 5 Choose the Set Specific Seasonality Dates radio button. 6 In the Pick Date field, select January 1 of the current year. 7 Click Add Date. The date is displayed in the Included Dates list. 8 Repeat List item. on page 452 and List item. on page 452 to add the additional holiday dates. 9 Click Add. The group of holidays on which your business is closed appears in the list of dates on the Baseline Seasonality Administration page.
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 450. 2 On the Baseline Seasonality Administration page, click Add. 3 In the Baseline Seasonality Name field, enter Payroll Activity. 4 Because payroll activities increase the load only on the server used by your accounting department, in the Monitor Instance Selector area, choose Group. 5 Click the linked blue text to the right of the Group radio button (This text reflects the Group that currently is selected).
The Select Group dialog box is displayed.
Managing baselines
6 In the Select Group dialog box, browse to the group that you have defined that represents your accounting department. For example, it might be a service named Accounting. 7 Select the check box for the group that represents your accounting department and click Apply.
The Select Group dialog box closes and the group that you selected is displayed
to the right of the Group radio button.
8 Choose the Set Seasonality Recurrence Pattern radio button. 9 In the Start From field, choose the first Thursday in January of the current year. (Although your employees receive their checks every two weeks on Friday, the bulk of payroll activity occurs on the Thursday before the checks are received.) 10 Choose the Weekly radio button. 11 In the Recur every __ weeks on field, enter 2. 12 Select the Thursday check box.
has been entered.
Figure 26: Baseline Seasonality for Payroll activity
13 Click Add. Every other Thursday is added as a recurring pattern for a new seasonality baseline on the Baseline Seasonality Administration page.
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 450. 2 On the Baseline Seasonality Administration page, click Add. 3 In the Baseline Seasonality Name field, enter Quarterly Inventory. 4 Because quarterly inventory increases the load on your database, in the Monitor Instance Selector area, choose in the Monitor Instance Selector area, choose Group. 5 Click the linked blue text to the right of the Group radio button (This text reflects the Group that currently is selected).
The Select Group dialog box is displayed.
6 In the Select Group dialog box, browse to the group that you have defined that represents your inventory database. For example, it might be a service named Inventory. 7 Select the check box for the group that represents your inventory database and click Apply.
The Select Group dialog box closes and the group that you selected is displayed
to the right of the Group radio button.
8 Choose the Set Specific Seasonality Dates radio button. 9 In the Pick Date field, select March 31of the current year. 10 Click Add Date. The date is displayed in the Included Dates list. 11 Repeat List item. on page 452 and List item. on page 452 to add the inventory dates for each quarter (June 30, September 30, and December 31). 12 Click Add. The group of days on which your business conducts quarterly inventory appears in the list of dates on the Baseline Seasonality Administration page.
Managing relationships
Relationships allow you to specify how elements within the infrastructure are related. Relationships define dependencies between various monitored elements in the system and are used for Probable Cause Analysis, impact prediction, and event suppression. For example, we can monitor an application and the host system. By defining a relationship between application and the host system, available events related to system A are suppressed by available events of System B. Now, if the system goes offline, both the system and the application will not be available. However, due to the defined relationship, BMC ProactiveNet will not send out an alert for the application availability. Only the system availability alert will be sent out. As explained in the above example, relationships go a along way in customizing BMC ProactiveNet behavior. By managing relationships, higher level of validity can be achieved for both Probable Cause Analysis and events. Probable Cause Analysis Relationships are static relationships (in the probable cause smart filter) based on static rules. Probable cause and Business Impact features use this information to filter out events and violations, not related to the queried event. Instead of leveraging 'out-of-the-box' knowledge about how various monitor instances relate to one another, the Probable Cause algorithm can leverage very specific user domain knowledge - an important factor for maximizing the power behind the Probable Cause feature. Static Relationships relate different monitor types (not specific to any instances), and guide Probable Cause and Business Impact algorithms. Intelligent Event Suppression Relationships are NOT static relationships. For details about defining Intelligent Event Suppression Relationships, see Adding or editing an Intelligent Event Suppression relationship on page 467. Relationships for both probable cause and Intelligent Event Suppression are called Common relationships. Although common relationships (applicable to both Intelligent Event Suppression and Probable Cause Analysis) can be created, BMC ProactiveNet recommends using separate relationships for event suppression and probable cause analysis. User-defined relationships work together with static relationships to filter events. Generally, algorithms first check to see if the event instance belongs to any instance relationships. If it does, then the algorithm applies those relationship filters. If the event instance does NOT belong to any instance relationship, it uses the static relationship rules. BMC ProactiveNet recommends use of group-level relationships. Such relationships are easy to manage and all instances added to the group will inherit the relationship.
This preserves all built in rules even in environments where the instances are constantly being changed.
Defining Intelligent Event Suppression relationships

Because of changes to the service model, relationship administration was deprecated in BMC ProactiveNet version 8.5.00. However, if you upgraded from a version of BMC ProactiveNet older than 8.5, this functionality has been preserved as Intelligent Event Suppression. If this is your first installation of BMC ProactiveNet, or you did not use the relationship administration feature in previous releases, you will not see the Intelligent Event Suppression functionality. This functionality has been absorbed into the changes made to the service model in the current version of BMC ProactiveNet.
Best practices for defining Intelligent Event Suppression relationships

Before you begin defining Intelligent Event Suppression relationships, consider these best practices: 1 Define broad rather than narrow relationships. Relationships are used to ascertain the potential probable causes and related events. Narrow relationships may inadvertently filter out potential abnormalities by forcing BMC ProactiveNet to give them lower scores. BMC ProactiveNet recommends defining the broader relationships first. If more granular relationships are needed, you can always define additional relationships. 2 Think through the relationships before creating them. Plan the relationships well. Generally a scalable and well thought-out plan of related groups works best. 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. 3 BMC ProactiveNet includes default, Global relationships. Take advantage of this out-of-the-box functionality. Focus on creating relationships that are specific to your infrastructure.
Relationship example
Assumptions
Before attempting to establish relationships, a monitor for each relevant element in the Web infrastructure has already been created. This is a required, essential step since all relationships are defined in terms of monitor instances.
Scenario
Consider that you have an online store that sells widgets A, B, and C. Each type of widget is served by distinct WebServer pools, as well as by different Application servers and/or databases behind the Webservers. 1 Online Store A consists of one pool of Web servers (WebServer Pool A) dedicated to selling widget A items, but also depends on a pool of Application servers (Appserver Pool A) and on database A. 2 Online Store B consists of another pool of Web servers (Webserver Pool B) dedicated to selling widget B items, 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. In this scenario, you want to convey the above information into the BMC ProactiveNet system so it can be leveraged by Probable Cause Analysis algorithms. Using the Relationships folder located in the Administration Console, 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. This information is known as domain knowledge. Once these relationships are established, if there is a problem with any of these online stores and an event is triggered, as you drill down on the event through the Probable Cause pages, BMC ProactiveNet will guide you to the most accurate Probable Cause event that is related to the event, thus taking advantage of the domain knowledge injected into the system via the relationship mechanism. Without this information, the Probable Cause algorithm must rely strictly on out-of-the-box relationships, thus limiting the conclusions it can draw about the potential causes of an event.
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
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. After these Groups are established, relationships can easily be formed by creating a Relationship for each of these Groups. The four pools for online store A would form one relationship tree; the four pools for online store B would form another relationship, and the same for online store C. Each relationship has a unidirectional dependency. Related topics Managing relationships on page 462 Adding or editing an Intelligent Event Suppression relationship on page 467
Overview of the Intelligent Event Suppression screen

From the Intelligent Event Suppression screen, you can enable, disable, and delete Intelligent Event Suppression rules, as well as access the dialog box that allows you to create Intelligent Event Suppression rules. The Intelligent Event Suppression Administration screen is accessed by selecting Options=>Administration and in the Advanced area, clicking the Edit link to the right of Intelligent Event Suppression. Figure 27: 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. The Name column displays the name of the Intelligent Event Suppression relationship. Relationship names are formed from the primary group, device, or monitor (the event that suppresses the events from the secondary event) and the secondary group, device or monitor separated by an arrow to indicate the direction of the relationship. Default Global relationships are shipped with BMC ProactiveNet and are immediately visible when you access the Intelligent Event Suppression screen. These . out-of-the-box relationships are not editable. This is indicated by the lock icon in the Edit column for each of the default relationships. Only the Ping/ Availability=>Device SameDevice;SameSourceAgent relationship is enabled by default. You can obtain more information about the relationship by hovering your cursor over the more information icon . The information displayed by the more information icon is provided by the Description box available when you create an Intelligent Event Suppression relationship. For more information about providing a description, see Adding or editing an Intelligent Event Suppression relationship on page 467. The Precedence column displays the order in which the relationships are processed if multiple primary events exist for the same secondary event. 1 is the highest precedence. Events are suppressed by the primary event that passes the rule which has highest precedence. If there is a tie with rule precedence, the primary event with the highest severity is processed. The Enabled column allows you to enable and disable relationships. If a relationship is enabled, the Enabled check box for that relationship is selected. For more information see, Enabling or disabling Intelligent Event Suppression relationships on page 467. The Edit column allows you to edit the scope and other attributes of the associated relationship. For more information, see Adding or editing an Intelligent Event Suppression relationship on page 467. The Add button allows you to add a new Intelligent Event Suppression relationship. For more information, see Adding or editing an Intelligent Event Suppression relationship on page 467. The Delete button allows you to delete any Intelligent Event Suppression relationship that is selected in the Select column.
Enabling or disabling Intelligent Event Suppression relationships

Use the following procedure to enable or disable Intelligent Event Suppression relationships.
To enable/disable an Intelligent Event Suppression relationship

1 Click the Options menu at the top right of the console. 2 Choose the Administration tab. 3 In the Advanced area, to the right of Intelligent Event Suppression, click Edit. 4 On the Intelligent Event Suppression screen, in the Enabled column for the the Intelligent Event Suppression relationship rule that you want to enable or disable, perform one of the following actions:
To enable the Intelligent Event Suppression relationship, select the checkbox. To disable the Intelligent Event Suppression relationship, deselect the checkbox.
5 Click Apply. The status of the relationship is displayed in the Enable column.
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.0. If you have installed BMC ProactiveNet for the first time, this functionality is not supported. All relationships are defined in terms of monitor instances. Before attempting to establish any relationships, ensure that a monitor for each relevant element in your infrastructure has already been created.
Note
Before you add Intelligent Event Suppression relationships, you should: 1 Define a monitor for each element in your environment. To define any relationship between elements in your infrastructure, first define a monitor for each element, and then use the actual monitor to define the relationship. 2 Define groups for any set of related instances: For example, create groups for any pools of servers, applications, Web servers, and so on. Using a group to define a relationship makes it more practical to maintain relationships. Intelligent Event Suppression relationships can be either applied globally or to a specific monitor or monitors that you specify. You can create any of the following types of Intelligent Event Suppression relationships:
Global - the Intelligent Event Suppression relationship is applied to all monitors Group, device, or monitor-based - the Intelligent Event Suppression relationship
Tip
is applied to the monitors within a group or device, or to a specific monitor or monitors that you specify
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.
Accessing the Add Intelligent Event Suppression Relationship dialog box

To define any type of Intelligent Event Suppression relationship, you must first access the Add Intelligent Event Suppression Relationship dialog box. 1 Click the Options menu at the top right of the console. 2 Choose the Administration tab. 3 In the Advanced area, to the right of Intelligent Event Suppression, click Edit. 4 On the Intelligent Event Suppression screen, click Add. The Add Intelligent Event Suppression Relationship dialog box is displayed.
To add a Global Intelligent Event Suppression relationship

1 Access the Add Intelligent Event Suppression Relationship dialog box. 2 In the Scope area, choose Global. 3 In the Global Scope: Qualifiers area, use the check boxes to select whether the primary and secondary monitor instances in the relationship must reside on the same device, on the same source Agent, or both. 4 In the Primary Attribute Selector area, choose the attributes of the primary monitor that will trigger suppression for the selected attributes on the secondary monitor. Choose from the following:
All Attributes - an event on any attribute of the primary monitor will suppress
events on the secondary monitor
Single Attribute - an event on a single attribute for a specified monitor type
will suppress events on the secondary monitor. To specify a single attribute:
a Choose the Single Attribute option. b Click the link to the right of the Single Attribute option. (By default, the first monitor type in the monitor type list is selected.) The Select Monitor Type dialog box is displayed. c Choose the monitor type for the attribute and click Apply. 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, select the attribute for that monitor that will trigger events to be suppressed on the secondary monitor. The list of attributes available depends on the monitor type you selected.
Attribute Set - an event on any attribute in the selected attribute set will
suppress events on the secondary monitor. To specify an attribute set:
a Choose the Attribute Set option. b From the drop list, choose the attribute set to which you want to apply the relationship. 5 In the Secondary Attribute Selector area, choose the attributes for which events will be suppressed when the specified events occur on the primary monitor. Choose from the following:
All Attributes - an event on the selected attributes of the primary monitor will
suppress events on all attributes for the secondary monitor
Single Attribute - 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 - 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.) In the Description text box, enter a description of the relationship. HTML is supported; however, the <html>, <head>, and <body> tags are not supported. 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.)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 default wait time is 120 seconds. The shorter the notification wait time, 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:
If there is no event on the primary monitor at the end of the notification wait
time, BMC ProactiveNet sends notification for the event on the secondary monitor event as per the notification setting.
If there is an event on the primary monitor at the end of the notification wait
time, BMC ProactiveNet suppresses the event on the secondary monitor and sends the notification for the event on the primary monitor.
8 After completing the add relationship screen, Click Add. The system returns to Intelligent Event Suppression screen. The new relationship is enabled and listed.
To add a group, device, or monitor-based Intelligent Event Suppression relationship

1 In the Scope area, choose Specific Monitors. 2 In the Primary Monitor Instance Selector area, perform one of the following actions:
Define a relationship based on a single group or device:
1 From the drop list, choose Group or Device as the primary monitor instance. 2 From the drop list under the Group or Device selection, choose the group or device to be the primary monitor instance for the relationship. You can filter the list of groups or devices by entering search criteria in the Search for text box and pressing Enter. 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.
Define a relationship based on multiple groups or devices
1 From the drop list, choose Group or Device as the primary monitor instance. 2 From the drop list to the right of the Group selection, choose Regexp. 3 In the text box beneath the Regexp selection, use regular expressions to type a pattern for the groups or devices that you want to be primary monitor instances for the relationship. 4 Press the Enter key. BMC ProactiveNet searches for groups or devices based on the pattern you entered and displays the number of matches found. 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. All matches in the list will be primary monitor instances in the relationship.
Define a relationship
1 From the drop list, choose Monitor as the primary monitor instance. 2 From the drop list under the Monitor selection, choose the monitor that you want to be the primary monitor instance for the relationship. The drop list below the selected monitor displays the list of devices that have that monitor. The primary monitor instance in the relationship will be based on the selected monitor for all the
based on a listed devices. If the selected monitor is added to other devices, single monitor those devices will be included as the primary monitor instance. Define a relationship based on multiple monitors 1 From the drop list, choose Monitor as the primary monitor instance. 2 From the drop list to the right of the Monitor selection, choose Regexp. 3 In the text box beneath the Regexp selection, use regular expressions to type a pattern for the monitors that you want to be primary monitor instances for the relationship. For example, Agent*. 4 Press the Enter key. BMC ProactiveNet searches for groups or devices based on the pattern you entered and displays the number of matches found. 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. All matches in the list will be primary monitor instances in the relationship. 3 In the Primary Attribute Selector area, choose the attributes of the primary monitor that will trigger suppression for the selected attributes on the secondary monitor. Choose from the following:
All Attributes - an event on any attribute of the primary monitor will suppress
events on the secondary monitor
Single Attribute - an event on a single attribute for a specified monitor type
will suppress events on the secondary monitor. To specify a single attribute:
a Choose the Single Attribute option. b Click the link to the right of the Single Attribute option. (By default, the first monitor type in the monitor type list is selected.) The Select Monitor Type dialog box is displayed. c Choose the monitor type for the attribute and click Apply. 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, select the attribute for that monitor that will trigger events to be suppressed on the secondary monitor. The list of attributes available depends on the monitor type you selected.
Attribute Set - an event on any attribute in the selected attribute set will
suppress events on the secondary monitor. To specify an attribute set:
a Choose the Attribute Set option. b From the drop list, choose the attribute set to which you want to apply the relationship. 4 In the Secondary Monitor Instance Selector area, select Group, Device, or Monitor as the secondary monitor instance. 5 Using the same steps that you used for defining the primary monitor instance, select group(s), device(s), or monitor(s) to be the secondary monitor instance 6 (Optional.) In the Description text box, enter a description of the relationship. HTML is supported; however, the <html>, <head>, and <body> tags are not supported. 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.)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 default wait time is 120 seconds. The shorter the notification wait time, 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:
If there is no event on the primary monitor at the end of the notification wait
time, BMC ProactiveNet sends notification for the event on the secondary monitor event as per the notification setting.
If there is an event on the primary monitor at the end of the notification wait
time, BMC ProactiveNet suppresses the event on the secondary monitor and sends the notification for the event on the primary monitor.
8 After completing the add relationship screen, click Add. The system returns to Intelligent Event Suppression screen. The new relationship is enabled and listed.
Managing schedules
To edit an existing Intelligent Event Suppression relationship

1 On the Intelligent Event Suppression screen, click the Edit link for the relationship that you want to edit. The Add Intelligent Event Suppression Relationship dialog box is displayed. 2 Make the desired changes to the relationship. 3 Click Add. The system returns to Intelligent Event Suppression screen. The relationship is enabled and updated.
Deleting a relationship
To delete a relationship
1 Click the Options menu at the top right of the console. 2 Choose the Administration tab. 3 In the Advanced area, to the left of Intelligent Event Suppression, click Edit. 4 On the Intelligent Event Suppression screen, select the check box next to the relationship that you want to delete. 5 Click Delete. 6 Click OK to confirm that you want to delete the relationship. The system deletes the relationship definition and returns to Intelligent Event Suppression screen.
Related topics
Managing relationships on page 462 Adding or editing an Intelligent Event Suppression relationship on page 467
Managing schedules
A schedule is a defined period which includes hours of the day, days of the week, and so forth. BMC ProactiveNet uses schedules to consider recorded monitored
Managing schedules
attribute values for SLO computations. Example, SLO with schedule 24x7 will consider all recorded monitored attribute values for SLO computation. However, another SLO with schedule of 9 A.M. to 5 P.M. for 5 days a week (Monday to Friday) will only consider monitored attribute values recorded between 9 A.M. and 5 P.M., Monday to Friday. Schedules help put SLO compliance computation in the right perspective without distorting the values by including invalid periods. Through the option screen, you can define new schedules, 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. 2 Click the relevant option:
For a new schedule, against the Schedule field, click New. The Add New
Schedule screen opens.
To edit an existing schedule, click Edit. The Edit Schedule screen opens. To add
more days to the existing schedule, change the values in the Days, Start Time, and End Time fields and click Add.
3 Specify a Name for the schedule. 4 Choose an applicable Time zone from the list of time zones provided. The BMC ProactiveNet Servers time zone is selected by default. Use the list to change the time zone.
To define time range for a single day,
a Select the check box against the Day to include. b Select the Start Time and End Time from the list. c Click Add.
The system updates the new time range in the table below. To define same time range for multiple days,
d Select check boxes against the Days to include. e Select the Start Time and End Time from the list. Start and End time relate to the each of the days.
Importing and exporting users
f Click Add.
The system updates the new time range in the table below.
Specify both inclusion and exclusion period. Exclusion period takes precedence over inclusion period. 5 After adding the computation timings for all days to be part of the Schedule, click Done.
The system displays a confirmatory message.
6 Click Close.
The system updates the database and returns to the SLO Creation Wizard
screen 4 of 4. The new schedule is available in the list.
To delete a schedule
1 Click Delete Schedule. 2 After making the required changes, click Done. The system updates the entries and returns to the Create SLO Wizard screen 1 of 4.

Users (Export or Import) enables to export and import the users from one BMC ProactiveNet Server to the other, to maintain the user accounts across all the BMC ProactiveNet servers Enterprise environment. Using this option, user accounts from testing environment can be exported and imported to the production setup.
Note
First export the users and then import them. Ensure that the users you import are the same as you export. Do not open the exported XML file before importing it on another machine. Use
text editor if you want to open the exported XML file. 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.
- There is no need for the user to open the exported XML file before importing on a different machine - Use text editor, If user want to open the exported XML file for any security reasons.
The following scenarios help you understand the steps you will need to perform while importing users, user groups, and roles. Table 111: Scenarios while importing users
Import User(s) Exists User Group(s) Exists All Some None Procedure
Only user Only user Only user Only user
Yes No No No
Do not create the user as the user with this name already exists in the system. Create users and map to all the existing user groups. Create users and map only to the user groups which already exists. If Read Only user group exists
1 Create a user and assign it to the Read Only user group.

Else
1 Create a Read Only role if it does not exist. 2 Create a Read Only user group and assign the Read Only
role.
3 Create a user and assign the Read Only group created above.
Users, User Groups, and Roles Users, User Groups, and Roles Users, User Groups, and Roles Yes Skip
No
All
Create user and map it to all the existing user groups.
No
Some
1 Create user groups which do not exist from the XML file (if
required, create roles if the roles on which this user groups are dependent do not exist).
2 Create a user and map it to all the user groups (newly

created as well as existing).
Import
User(s) Exists
User Group(s) Exists None
Procedure
Users, User Groups, and Roles
No
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).
2 Create a user and assign it to all the above newly created

user groups.
To export users
1 Click Options => Administration => Advanced => Users. 2 Click the Export link corresponding to Users, to open the Export User Data screen. 3 Use the Filter options to select the users. Users can be selected based on the following options:
User Class Status User Name User Group or Role
4 Specify a User Name and User Group or Role. A table displays with the users. The User Class field displays only 2 values: Admin or User
Users who have been granted the permission Access to Administration
Note
Console" are classified as belonging to Admin class.
All other users belong to User class.
This distinction is useful in identifying an Admin class user when there are many users present in the system. 5 Select the User from the table, or check Select All to export all the users.
Viewing BMC ProactiveNet software information
6 Check Export User Groups and Roles if you want to also export user groups as well as the roles associated with the users. 7 Click Export to open the File Download window. 8 Click Save in the File Download window, to open Save As window. The default file name is userdata.xml, and the default location is desktop. 9 Click Save in the Save As window, to open Download Complete window. 10 Click Close in the Download Complete window. 11 Click Back to Administration link to return to Administration Tab.
To import users
1 Click Options => Administration => Advanced => Users. 2 Click Import link corresponding to the Users, to open the Import User(s) screen. 3 Specify the Import File name or use the Browse option to locate the file. Select Import User Groups and Roles if you want to import the user(s) along with the user groups and roles. This will import all the user groups and roles and associate them to the appropriate users. 4 Click Import, to display the User Import Summary screen. This screen gives the status of the import and the user details table. 5 Click Cancel in the Import User(s) screen to return to Administration Tab without importing the user.

This section provides links to view installation history, performance diagnostics and license usage information.
Installation history
The Installation history provides an audit trail of BMC ProactiveNet installation. It provides information of various patches, and hotfixes applied on BMC ProactiveNet Server.
To view installation history

1 Click the Options link at the top right of the console. The Options screen opens. 2 On the Administration tab, under the BMC ProactiveNet heading. Click View link of Installation Rules. 3 The View History File screen opens. 4 Use the filter to search for specific information.
Viewing BMC ProactiveNet performance diagnostics

BMC ProactiveNet offers both pre-configured and user-defined diagnostic tools to help monitor your system.
To view performance diagnostic details

1 On the Administration tab, under the BMC ProactiveNet heading. Click View link of Performance Diagnostics. 2 The BMC ProactiveNet Server Performance screen displays the options Performance Graphs, and Performance Diagnostic Details. 3 Click View link of Details to view performance diagnostic details. 4 The Performance Diagnostics Details screen displays the following details as described in Table 112 on page 480. Table 112: Diagnostic details
Performance diagnostic types General Details Cell metrics Description displays the server sizing details. describes the cell-based event activity and lists the event classes that are sending the events
Performance diagnostic types Remote Agent Device Monitor instance Monitor type Attribute User Data details Graph View Report SLO Event
Description displays the type of operating system on which BMC ProactiveNet is installed and Agent counts. displays the device type and count. displays if monitor instances are turned off by the device flag or device instance flag, number of active poll period in seconds, and custom API instances per second. displays the monitor type, poll period in second, number of instances, and instances per second. displays the monitor type, number of attributes per monitor type, monitor instances count, total number of attributes, and total instance attributes. User detail screen is categorized in to two types namely: configured users and logged in users. displays the minimum and maximum value of raw data retention period in hours, and minimum and maximum value of rate data retention period in hours. displays a list of all graphs including those that were not created by you. displays a list of all views including those that were not created by you. displays a list of all reports including those that were not created by you. Report details can either be hidden using the Show or Hide options. displays SLO details. displays the following event details: Signature Events - This give the number of open and closed signature events. Absolute events - This gives the number of open and closed absolute events. This also gives the details about the monitor type, attribute id and total number of events. These details can be displayed or hidden using the Show and Hide option. External events - This gives the number of open and closed external events, both device-associated and non-device-associated. However, you are restricted to view only those events that are created by you. Click View next to Performance Diagnostic Details to see a list of detailed statistics. Scroll down to the Event Details heading to see the number of open and closed events of all types.
System specific
displays the system specific details of the server. It can vary depending on the operating system of the server.
System information displays details about the physical system: its name, OS, processor, BIOS, physical memory, and so forth Routing displays routing details.
Performance diagnostic types TCP connection
Description displays the TCP connection details.
Performance Diagnostic page takes much longer duration to load (6 minutes) on WIndows.
Note
Viewing and exporting the license usage report

BMC ProactiveNet License Usage report displays information on the licensed features of BMC ProactiveNet Performance Management. The report displays exact number of licenses used for each feature or monitor. You must have admin privileges to access the license usage report. The report is refreshed once a day.
To view license usage details

1 On the Administration tab, under the BMC ProactiveNet section, click the View link of License Usage Report. The License Usage Details report displays your license information. The report provides the following details:
Current date and time of the report BMC ProactiveNet host name on which the report has run License Categories table displaying all license categories, unit of measurement
for each category, and the number of instances for each category if applicable. For more information on license categories, see Instances and managed assets details on page 485.
2 Click the number of instances link to view the details of the counted instances.
To export the license usage report to consolidated license UI

1 On the License Usage Details report, select the export type PDF or Consolidated License Report (available in CSV and XML formats). 2 Click Export and when prompted save the report file to your local computer.
The report is saved in a zipped file.
License usage report details

The license usage report displays information on the licensed features of BMC ProactiveNet, exact number of licenses used for each BMC ProactiveNet feature or monitor solution. The report is available from The Operations Console > Options > Administration tab > BMC Proactive Net section. The report is refreshed once a day.
BMC ProactiveNet native monitors are not counted. Existing customers can view native monitors by running the old license usage report. The following table describes the main elements of the report.
Field Report Date Host Description Displays the date and time stamp of the current report run. Displays the name of the BMC ProactiveNet host name
Note
Field
Description
License Categories Displays all license categories, unit of measurement for each category, number of instances for each category if applicable, and comments for each license category. Click the number of instances link to view the details of the counted instances. Server Monitoring and Analytics Application, Database and Middleware Monitoring and Analytics Units of measurement: per managed asset (server endpoint).
Unit of measurement: per managed asset (server endpoint ). Limitations: The host cannot be displayed for solutions with no I2D. For custom category, the user must edit the custom-solutionslicense-report.conf file in the pronet/conf folder:
<custom-solutions> <mo-types solution-name="My custom solution">P_PATROL_MSC_MAIN,_PATROL_MSC_SEC</mo-types> <mo-types solution-name="Another custom solution">P_PATROL_ACS</mo-types> </custom-solutions
mo-types element: solution name - the name of your solution element value - list of monitor types representing devices in the solution, separated by comma Cloud Resource Monitoring Group Tree view Units of measurement: per managed asset (server endpoint). Units of measurement: per instance. Counts a single instance of the BMC ProactiveNet Performance Management server where the hyperbolic tree is used for group or SLO views. Sentry Hardware Monitoring and Analytics Sentry Storage Monitoring and Analytics Sentry Microsoft Applications Monitoring and Analytics Sentry Monitoring Studio Synthetic Transaction 484 BMC ProactiveNet User Guide Monitoring and Analytics Application Units of measurement: per managed asset
Units of measurement: per managed asset
Units of measurement: Per instance (execution server). Counts instances of BMC Transaction Management Application Response Time execution server. Units of measurement: per managed asset (server endpoint).
Field
Description Unique Servers Units of measurement: per managed asset (server endpoint). Counts the number of unique OS instances within the following categories: Server monitoring and analytics Application, database and middleware monitoring and analytics Event and impact management Application diagnostics
Export Options
Select an export type for the report: PDF Consolidated License Report - available in CSV and XML format
Instances and managed assets details

This page displays the details of the instances or managed assets that were counted in the license usage report. The table shows the counted instance or managed asset host name and additional data relevant to the license category. For example, for Unique Servers category, the Relevant Server in Use is displayed. For Application Diagnostics category, the Black Box Type is displayed.
Pausing auto-refresh
The pausing auto-refresh feature enables you to pause refreshing the data views automatically when an Operations Console window is not active. When you enable the auto-refresh feature, auto-refresh of data views is paused when the Operations Console window is not accessed for a configured period of time. Pausing improves the application performance by reducing the BMC ProactiveNet Server workload. A window can be in an inactive state when you minimize the Operations Console, lock your computer, or when you are accessing another application other than the BMC ProactiveNet Operations Console.
To configure auto-refresh
1 On the Administration tab, under the BMC ProactiveNet heading, click the Edit link for Auto-Refresh Performance Enhancement. The Auto-Refresh Performance Enhancement screen is displayed. 2 Set Auto-Refresh Pausing to On or Off from the drop-down list. If you select On, the Inactivity Time Limit field is displayed. By default, Auto-Refresh Pausing is off. 3 Select the time limit from the Inactivity Time Limit drop-down list. Auto-refresh will be paused if you are inactive for the set period. Default time limit is 10 minutes. 4 Click Apply. The changes will be reflected only when you login again.
Note
The auto-refresh pause feature that you select here takes precedence over the
setting that you have selected in the Event List Preferences dialog box. For more information on refreshing the event list, refer to Refreshing the event list on page 72 section.
The auto-refresh pause feature is user specific. For example, consider a
scenario where there are two users, user A and user B. User A logs in and sets the time limit to 5 minutes. When user B logs in later, the time limit setting displayed is user B's and not user A's settings.
If the auto-refresh pause feature is On and the Operations Console window is
inactive, the Auto Pausing pop-up window is displayed. A message that all data refreshing is paused and a timestamp of when the last update occurred is displayed. The pop-up window disappears when you activate the Operations Console window again.
10
Integrating with BMC Server Automation
This chapter provides details on how to import BMC Server Automation information into BMC ProactiveNet so that you can factor BMC Server Automation job history into probable cause analysis.
Benefits of BMC Server Automation integration

A BMC Server Automation job might make a configuration change to a device which causes its behavior to change. Integrating BMC ProactiveNet with BMC Server Automation provides BMC Server Automation job history information to probable cause analysis, so that when you invoke probable cause analysis for an event, the probable cause analysis results page flags devices which have had BMC Server Automation jobs execute in the same time frame as the event that you are troubleshooting. In addition, certain events that are generated on BMC ProactiveNet will trigger the execution of a pre-defined snapshot job on BMC Server Automation. This snapshot job will be able to detect better the configuration changes made to the device. When you access probable cause analysis for a service degradation event, the probable cause analysis filters and ranks the events from most probable cause to least. The probable cause analysis results page indicates if there has been a BMC Server Automation job executed on the device before 24 hours and after 30 minutes from the current time stamp of the primary event. If a BMC Server Automation job has been executed on the device, the job name, job type, and start and end time of the job is displayed next to the device. For more information about probable cause analysis, see Determining the probable cause for an event on page 221. The following BMC Server Automation job types are considered during probable cause analysis:
Deploy Job (30) Deploy Job Attempt (205)
Chapter 10 Integrating with BMC Server Automation 487
Setting up the integration between BMC Server Automation and BMC ProactiveNet
File Deploy Job (40) Network Shell Script Job (111) Sync Job (190) Deploy Apply Job (203) Deploy Undo Job (204) Snapshot Job
Snapshot job executions are listed in the BladeLogic Device History page only if the snapshot job detects any changes. Batch jobs also are not listed in the probable cause analysis device history, unless the batch job contains any of the supported job types, such as a deploy job or an Network Shell Script job.
Note
To integrate BMC Server Automation with BMC ProactiveNet you must
install and license the BMC Server Automation RSCD Agent on the BMC
ProactiveNet Server (for instructions, see the BMC Server Automation documentation). This is required only for pw blade create packages command. Server to serve as the BMC Server Automation administrator account.
create a dedicated user account for the BMC Server Automation Application
enable web services on the BMC Server Automation Application server. set up the credentials on the BMC ProactiveNet Server for accessing BMC Server
Automation 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 BMC Server Automation administrator user account for the BMC Server Automation Application Server
1 Create a new user for the BMC Server Automation Application Server.
2 Assign that user to a single BLAdmins role. No other roles should be assigned to this user.
WARNING You must create a dedicated user account with only a BLAdmins role for using the BMC Server Automation Application Server. No other roles should be associated with this user account or the integration will fail.
To enable web services on the BMC Server Automation Application Server

1 Log in to the BMC Server Automation Application Server, using the BLAdmins account. 2 Start the BMC Server Automation Application Server Administration utility as appropriate for your operating system:
For Windows, choose Start => Programs => BMC Software
> BMC BladeLogic Server Automation Suite => Utilities => Application Server Administration.
For UNIX, access the /opt/bmc/bladelogic/NSH/br directory. From the
command line, enter blasadmin.
3 From the Application Server Administration utility, run the following command: set AppServer EnableTomcatService true 4 [optional] To configure the registration of web services in the BMC Atrium UDDI Server, 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. 5 Restart the BMC Server Automation Application Server. The BMC Server Automation Application Server log indicates if the web services registration was successful for LoginService, AssumeRoleService, and CLITunnelService.
You can remove the web services registration in the BMC Atrium UDDI Server
by restarting the Application Server Administration utility as described in step 3 and entering the following commands:
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 BMC Server Automation Application Server is shut down. These will be registered with the specified web services properties when you start the BMC Server Automation Application Server.
To set up credentials with the UDDI registry on the BMC ProactiveNet Server for accessing BMC Server Automation from BMC ProactiveNet
1 Log in to the BMC ProactiveNet Server as administrator. 2 Access a command line and enter: pw blade setup -use_uddi -uddiuser uddiUserName -uddipass uddiPassword host hostName [-port portNumber] -user userName -pass password Table 113: 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 Server Automation 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 BMC Server Automation Application Server Note: This should be the user account created for the BLAdmins role. password to connect to the BMC Server Automation Application Server
For example, pw blade setup use_uddi -uddiuser udaman -uddipass uopensesame host server.domain.com port 8080 user pronet pass opensesame If the connection is successful, a message Info: Connection to BladeLogic server succeeded. is displayed. 3 Follow the appropriate instructions based on the return code that you receive:
If the command returns 0, the credentials were created successfully. You can
now To change the time correlation filter on page 235.
If the command returns 1, there is a syntax error. Re-enter the pw blade setup
command correctly.
If the command returns a number other than 0 or 1, an execution error has
occurred. An error message is displayed indicating which error occurred.
To set up credentials without the UDDI registry on the BMC ProactiveNet Server for accessing BMC Server Automation from BMC ProactiveNet
1 Log in to the BMC ProactiveNet Server as administrator. 2 Access a command line and enter: pw blade setup -host hostName [-port portNumber] -user userName -pass password Table 114: 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 the Application Server hosting BMC Server Automation Web Services port number of the BMC Server Automation Web Services user name to connect to the BMC Server Automation Application Server Note: This should be the user account created for the BLAdmins role. password to connect to the BMC Server Automation Application Server
For example, pw blade setup host server.domain.com port 9843 user pronet pass opensesame If the connection is successful, a message Info: Connection to BladeLogic server succeeded. is displayed. 3 Follow the appropriate instructions based on the return code that you receive:
If the command returns 0, the credentials were created successfully. You can
now To change the time correlation filter on page 235.
If the command returns 1, there is a syntax error. Re-enter the pw blade setup
connection command correctly.
To test your credentials on the BMC ProactiveNet Server for accessing BMC Server Automation
1 Log in to the BMC ProactiveNet Server as administrator. 2 Access a command line and enter the command pw blade test. If the connection is successful, a message Info: Connection to BladeLogic server succeeded. is displayed. If the connection is unsuccessful a message, Error: BladeLogic connection information has not been setup. is displayed. 3 Follow the appropriate instructions based on the return code that you receive:
If the command returns 0, then the credentials that you set up are working
correctly. If desired, you can now To install the BMC ProactiveNet provided content on BMC Server Automation on page 494. connection command correctly.
If the command returns 1, there is a syntax error. Re-enter the pw blade test
occurred. An error message is displayed indicating which error occurred. Depending on the error message displayed, you may need to To clear the connection to BMC Server Automation that you created on the BMC ProactiveNet Server on page 492 and To set up credentials with the UDDI registry on the BMC ProactiveNet Server for accessing BMC Server Automation from BMC ProactiveNet on page 490 again.
To clear the connection to BMC Server Automation that you created on the BMC ProactiveNet Server
1 Log in to the BMC ProactiveNet Server as administrator. 2 Access a command line and enter: pw blade clear connection If the connection is successful, a message Info: Clearing of BMC BladeLogic connection information succeeded. is displayed. If the connection is unsuccessful a message, Warning: BladeLogic connection
information has not been setup. Warning: Clearing of BladeLogic connection information failed. is displayed.
3 Follow the appropriate instructions based on the return code that you receive:
Additional change information using snapshot job execution
If the command returns 0, the credentials that you set up are no longer
available. If desired, you can To set up credentials with the UDDI registry on the BMC ProactiveNet Server for accessing BMC Server Automation from BMC ProactiveNet on page 490 from a different user. connection command correctly.
If the command returns 1, there is a syntax error. Re-enter the pw blade clear
You can set up the BMC Server Automation integration while installing the BMC ProactiveNet Server. For more information on installing the BMC ProactiveNet Server, refer to the BMC ProactiveNet Getting Started Guide.
Note
Additional change information using snapshot job execution

Certain events (critical or major events) generated/received on BMC ProactiveNet can cause a BMC ProactiveNet provided snapshot job to be executed. This snapshot job captures change information on the device associated with the generated/ received event provided a BMC Server Automation RSCD Agent is also running on that device. This information can be viewed from the BMC Server Automation Device History results screen. For more information, see Viewing BMC Server Automation device history information on page 499. When events matching the criteria mentioned above are received/generated, BMC ProactiveNet refers to the <install_dir>/pronto/conf/ supportedDeviceTypesAndOSForBlade.conf mapping file to determine which snapshot jobs to run on BMC Server Automation. If a match is found, the snapshot jobs are executed. BMC ProactiveNet can run multiple snapshot jobs for a specific device type and operating system combination. The supportedDeviceTypesAndOSForBlade.conf file lists various combinations of device types and operating systems and their associated snapshot jobs.
Limitations
A default throttling logic time period of 10 minutes (can be altered in pronet.conf) needs to elapse before a snapshot job is executed again. This may lead to some
Installing the BMC ProactiveNet content
events on BMC ProactiveNet not triggering snapshot jobs on BMC Server Automation (since earlier snapshot jobs may not have completed).
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 BMC Server Automation Application Server. You can create content that is more tuned to your environment by customizing the BMC ProactiveNet provided content or by creating new content (as described in Creating new BMC Server Automation content on page 495). This content helps collect relevant configuration change information which helps probable cause analysis. BMC ProactiveNet provided content consists of three component templates, three associated snapshot jobs and three associated component discovery jobs. 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.
To install the BMC ProactiveNet provided content on BMC Server Automation

1 Log on to the BMC EPD website at https://webapps.bmc.com/epd/faces/ licensedProd.jsp. 2 In the Product Name column, expand BMC BladeLogic Server Automation Suite => BMC BladeLogic Server Automation Suite 8.1.00. Select the following links depending on your operating system to download the BMC ProactiveNet content installer :
OS Microsoft Windows Solaris Linux
Filename BSA 8.1.00 Server Automation PPM for Windows BSA 8.1.00 Server Automation PPM for Solaris BSA 8.1.00 Server Automation PPM for Linux
3 Copy the content installer to the machine where BMC Server Automation Application Server is installed.
Creating new BMC Server Automation content
4 Run the content installer which will import the BMC ProactiveNet provided content into the BMC Server Automation Application Server. 5 Edit all three component discovery jobs (PPM-SolarisOS-ComponentDiscovery, PPM-ApacheSolaris-ComponentDiscovery, PPM-WeblogicComponentDiscovery) to assign the proper targets and create an appropriate schedule for the component discovery jobs. Run all three component discovery jobs once. This step is mandatory. The component discovery job must run at least once on all targets so that components, if any, can be discovered. Snapshot jobs run on the same targets will not work unless components have been discovered. where v_n-nnn is the BMC Server Automation version number. 6 Edit all three snapshot jobs (PPM-SolarisOS-Snapshot, PPM-ApacheSolarisSnapshot, PPM-WeblogicSolaris-Snapshot) to assign the proper targets and create an appropriate schedule for the snapshot jobs. Run all three snapshot jobs once. This step is mandatory.

You can create content that is more tuned to your environment. The following procedure gives an example of how to create content for Apache on Linux which is not pre-defined sample starter content provided by BMC ProactiveNet.
To create new content

1 Create component template PPM-ApacheLinux-Template on the BMC Server Automation Application Server. a Log into the Server Automation Console. b Under the Folders tab, expand the Component Templates folder. c If PPM folder does not exist, select the Component Template folder and rightclick to get the context menu. Select New => Component Template Folder to create a new folder called PPM. d Select the PPM folder and right-click. From the context menu select New => Component Template to create a component template and provide the template name as PPM-ApacheLinuxTemplate.
e Select Discover, Browse and Snapshot from the Allowed Operations section and click Next three times. Click Finish to create a basic component template. 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. g Select the Parts, Discover, Browse, Snapshot and Local Properties tab to edit section. h In the Parts tab, add the parts that make up this component by clicking on the + sign which shows the Select Parts dialog. Click Add New button to display the New Component Template Part dialog. Select the type of the part with the first drop down (File, Directory, etc.) and then add the name. You can parameterize the name using properties (both local properties and global properties). Properties can be entered in the form APACHE_CONF_DIR. Click Ok twice to create the part. Add more parts if necessary. i To add a Rule Definition, click on the Show the Test Signature Screen button in the Discover tab. Local properties and global properties can be used. The discovery rule is used by the component discovery job to discover components on specified targets. 2 Create corresponding component discovery job PPM-ApacheLinuxComponentDiscovery on the BMC Server Automation Application Server and specify the PPM-ApacheLinux-Template as the template. Assign proper targets and create a schedule for the component discovery job. The component discovery job must run at least once on all targets so that components, if any, can be discovered. Snapshot jobs will not run on targets unless components have been discovered. 3 Create a corresponding snapshot job PPM-ApacheLinux-Snapshot on the BMC Server Automation Application Server and specify the PPM-ApacheLinuxTemplate as the template. Assign proper targets and create a schedule for the snapshot job. 4 To map the snapshot jobs created on the BMC Server Automation Application Server (PPM-ApacheLinux-Snapshot) onto the BMC ProactiveNet configuration file, add an entry to <install directory> /pw/pronto/conf/ supportedDeviceTypesAndOSForBlade.conf.
Creating packages to deploy BMC ProactiveNet Agents to BMC Server Automation managed systems
For example, add a new entry "WebServer,Linux,/PPM, PPM-ApacheLinuxSnapshot, PPM-ApacheLinux-Template ". The map file is in a CSV format which may either have single or multiple lines per device type. The format in the CSV file is DeviceType,OS,SnapShotPath,SnapshotJobName,ComponentTemplateName
DeviceType - The fields are BMC ProactiveNet Device type (for example, Server,
WebServer).
OS - Operating System type. SnapShotPath - Group name where BMC ProactiveNet provided snapshot job is
present.
SnapShotJobName - Name of the snapshot job that should be triggered.
If the snapshot job name on BMC Server Automation contains a comma, the snapshot job will not be triggered on BMC ProactiveNet.
ComponentTemplateName - Name of the component template that is associated
Note
with the snapshot job.
After you have set up and tested the credentials necessary to connect the BMC ProactiveNet Server to the BMC Server Automation managed system, you can create packages so that BMC Server Automation can deploy BMC ProactiveNet Agents to BMC Server Automation managed systems.
Before you begin

You must have administrator privileges to create these packages. A BMC Server Automation RCSD Agent must be installed on the BMC
ProactiveNet Server and it must be running.
The machine on which the BMC ProactiveNet Server is installed must be
reachable from the machine where BMC Server Automation Application Server is installed.
To create packages to deploy BMC ProactiveNet Agents from the BMC ProactiveNet Server to BMC Server Automation managed systems
1 Log in to the BMC ProactiveNet Server as administrator. 2 Access a command line and enter: pw blade create packages If the command succeeds the following message is displayed.
Creating BMC BladeLogic packages for BMC ProactiveNet agents This may take a long time... Info: Creation of BMC BladeLogic packages for BMC ProactiveNet agents succeeded.
3 Follow the appropriate instructions based on the return code that you receive:
If the command returns 0, execution was successful. If the command returns 1, there is a syntax error. Re-enter the pw blade create
packages command correctly.
The BMC ProactiveNet Agent software is loaded into the BMC Server Automation depot in the /Software/BMC/ProactiveNet directory as BMC_PN_Agent version_build_platform. The packages are created in the BMC Server Automation depot in the /Packages/ BMC/ProactiveNet directory as BMC_PN_Agent_ platform. Once the packages are created, use BMC Server Automation to create and run a deploy job to deploy the packages to BMC Server Automation managed systems.
Viewing BMC Server Automation device history information
Note
BMC recommends that the BMC Server Automation Application 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 Server Automation Application Server.
Before executing the pw blade create packages command you should delete
the existing software and packages on the BMC Server Automation Application Server. Go to the BMC Server Automation depot and delete the software BMC_PN_Agent version_build_platform in the directory /Software/ BMC/ProactiveNet. Also, delete the packages BMC_PN_Agent_ platform in the directory /Packages/BMC/ProactiveNet.

BMC Server Automation device history information is available from the Tools menu in the Operations Console or from the Probable Cause Analysis dialog box. Figure 28 on page 499 shows the BMC BladeLogic Device History results screen. Figure 28: BMC BladeLogic Device History screen
The Time filter displays 24 hours before and 30 minutes after the timestamp depending on where you launch BMC Server Automation device history from. You can launch it from the following three areas:
Events: Launching BladeLogic device history from the Tools menu of the
Operations Console. The Time filter displays the job details filtered 24 hours before and 30 minutes after the timestamp of the event. displays the job details filtered 24 hours before and 30 minutes after the system time.
Device: Launching BladeLogic device history for a device, the Time filter
Probable Cause Analysis: Launching BladeLogic device history from the
Probable Cause Analysis page, the time filter displays the job details filtered 24 hours before and 30 minutes after the timestamp of the primary event.
The Edit Time option allows you to edit the Relative and Absolute time. Setting the Relative time filters the events that occurred during the specified time until the system time. For example, if you specify 5 minutes and the system time is 10:00 A.M., the events that occurred from 09:55 to 10:00 A.M. are displayed. Absolute time allows you to specify the time range for displaying the events that occurred during the specified time period. History Filters allows you to filter out the BMC Server Automation jobs from the BladeLogic Device History page, if you do not want to view them from the current page as well as from all the BMC Server Automation pages. To add history filters, refer to To add history filters on page 502. Table 115 on page 500 lists the columns in the BMC BLadeLogic Device History results screen and describes the information that is contained in each column. Table 115: Description of BladeLogic Device History screen
Column Host Name Type Description Name of the device for which BMC Server Automation changes have occurred Name of the BMC Server Automation job that contributed the change Icon representing the type of job: : Deploy jobs : Nsh jobs or scripts : Snapshot jobs
Start End Status User
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
Column Template Part Changed
Description Details the changes to BMC Server Automation templates captured by snapshot jobs
To view BMC Server Automation device history from the Tools menu
1 From Event View, select any event. 2 Click the Tools menu icon for that event.
3 From the Tools menu, select BladeLogic Device History. The BladeLogic Device History screen displays the BMC Server Automation job details filtered for 24 hours before and 30 minutes after the timestamp of the event that you selected. For example, if you select the event which occurred on 08/2/10, at 4 PM, then the BMC Server Automation job details between 08/01/12 4 PM to 08/02/12 4:30 PM is displayed.
To view BMC Server Automation device history from the Probable Cause Analysis results page
1 From Event View, select the event you wish to launch the probable cause analysis 2 Click the probable cause analysis icon .
A summary of the BMC Server Automation device history is included in the BladeLogic History column in the probable cause analysis results page for the selected event. This column includes the icon for the job type, as well as the time of the last change. For more detailed BMC Server Automation device history, click the Tools menu icon for the event and choose BladeLogic Device History. The BMC BladeLogic Device History screen will be displayed. 3 The Probable Cause Analysis page has two tabs, By Score and By Device. Click on By Score tab and launch the BMC Server Automation device history. The job details filtered 24 hours before and 30 minutes after the timestamp of the event are displayed. Click on By Device tab and click on the Server Automation icon in the Most Recent BladeLogic Job Type column. This launches the BMC Server Automation device history which displays the job details filtered 24 hours before and 30 minutes after the primary event. For more information about probable cause analysis, see Determining the probable cause for an event on page 221 For more detailed information about BMC Server Automation, see the BMC Server Automation documentation.
Provisioning BMC ProactiveNet components with BMC Server Automation
To add history filters

1 Click on the link against History Filters to edit the filter. 2 Click on Add Exclusion Filter from the Device History Exclusion Filters screen that is displayed. 3 Select the job type from the drop down list. 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. To delete a filter, click the delete filter icon next to the filter you have defined. Restore Defaults option will remove all the specified filters. 5 Click on the Preferences icon on the BladeLogic Device History screen to specify the filter for all the BMC Server Automation device history pages.
Note

If you have integrated BMC Server Automation into your BMC ProactiveNet environment, you can create packages of the currently available components in the BMC ProactiveNet Central Monitoring Repository, load them into BMC Server Automation, create deployment jobs in BMC Server Automation to deploy and install those packages to remote hosts, and then use the BMC ProactiveNet Central Monitoring Administration console to automatically configure the products after they are installed. The provisioning process consists of the following tasks: 1 Creating packages for provisioning on page 503. 2 Creating a property instance in BMC Server Automation on page 505. 3 Creating BMC Server Automation jobs to deploy BMC ProactiveNet component packages to remote hosts on page 507.
Before you begin

Ensure that your environment is set up properly for the provisioning process as follows. For details, see Setting up the integration between BMC Server Automation and BMC ProactiveNet on page 488 except where otherwise noted.
Ensure that BMC Server Automation Agent is installed and licensed on the
computer that hosts the BMC ProactiveNet Server where the Central Monitoring Repository is installed, on all remote computers on which the product packages will be installed and configured, and on the computer that hosts the BMC Server Automation Server. Administration console are installed on the computer that hosts the BMC ProactiveNet Server. If you have a multiple server deployment, the repository and the console must be installed on each leaf server in your BMC ProactiveNet environment. See the BMC ProactiveNet Getting Started Guide. BLAdmins role.
Ensure that the Central Monitoring Repository and the BMC Central Monitoring
Create a BMC Server Automation administrator account and assign it to the
Ensure that Web Services are configured on the computer that hosts the BMC
Server Automation Server.
Use the pw blade test command to test the credentials that will be used to access
BMC Server Automation to ensure that the connection from BMC ProactiveNet is valid.
On Windows computers, ensure that command extensions are enabled.
For information about command extensions, see the Microsoft Windows product documentation.
Creating packages for provisioning

You can create packages of all currently available components in the BMC ProactiveNet Central Monitoring Repository, store those packages in BMC Server Automation, and then create a BMC Server Automation job to deploy those packages to servers to be installed and configured.
Before you begin

Ensure that your environment is properly set up. See Provisioning BMC ProactiveNet components with BMC Server Automation on page 502.
To create packages for provisioning

In this procedure, you push packages from the base BMC ProactiveNet Central Monitoring Repository to BMC Server Automation and then you push packages from the extended BMC ProactiveNet Central Monitoring Repository to BMC Server Automation. 1 On the computer that hosts the BMC ProactiveNet Server, open a command prompt, enter the following command, and click OK: pw blade auto_prov_prep By default, the Package.xml file is used to create the packages in BMC Server Automation from the base repository; therefore, you do not need to specify the name of the xml file when you execute this command. The following message is displayed on the command line while the packages are being created:
Auto provisioning the default package XML file. This may take a long time...
The process could take up to 20 minutes to complete. After the command executes, the following message is displayed on the command line:
Info: Creation of BMC BladeLogic objects succeeded.
BMC Server Automation is populated with packages of the BMC ProactiveNet monitoring components from the base repository. 2 On the computer that hosts the BMC ProactiveNet Server, open a command prompt, enter the following command, and click OK: pw blade auto_prov_prep -package Package_Extended.xml The following message is displayed on the command line while the packages are being created:
Auto provisioning the default package XML file. This may take a long time...
The process could take up to 20 minutes to complete. After the command executes, the following message is displayed on the command line:
Info: Creation of BMC BladeLogic objects succeeded.
BMC Server Automation is populated with packages of the BMC ProactiveNet monitoring components from the extended repository. If an error message is displayed, see the BMC ProactiveNet Troubleshooting Guide for information about possible causes of the errors and how to resolve them. For details about the pw blade commands, see the BMC ProactiveNet Command Line Interface Reference Manual. After you push the packages from the repository to BMC Server Automation, the next step is to create a property instance in BMC Server Automation. For details, see Creating a property instance in BMC Server Automation on page 505.
Creating a property instance in BMC Server Automation

After you push the packages from the repository into BMC Server Automation, you use the Property Dictionary in BMC Server Automation to create a property instance. You add the property instance to a deployment job. The values entered in the property instance are used to install and configure the component packages on the remote computers.
To create a property instance in the BMC Server Automation

1 Launch the BMC Server Automation Console. 2 From the Configuration menu, choose Property Dictionary View. The Property Dictionary opens in the BMC Server Automation Console. 3 Click on the Property Dictionary tab. 4 In the Property Dictionary view, expand the Property Dictionary folder until the PATROL Configuration folder is displayed and select Installation under that folder. 5 Select the Instances Tab. 6 In the Instances tab, select either a UNIX or Windows instance, right click, and choose Duplicate. An additional instance is displayed with Copy of added to the beginning of the instance name. 7 Select the Copy of instance, right click, and choose Edit.
The Modify Instance dialog box is displayed. 8 In the Modify Instance dialog box, perform the following steps: a Enter a unique name for the new instance. b (optional) Enter a description for the new instance. c Click on the value for the AGENT_PORT variable and enter the port number that the PATROL Agent uses. If you are using the default value for the PATROL Agent port number, then you do not need to change this value. d Click on the value for the PATROL_BASE_DIR variable, and enter the base directory where you want PATROL to be installed. If the computer on which you are installing the package already has a PATROL installation, the directory you enter for this variable must be the same directory where the existing PATROL installation is installed. e Click on the value for the PATROL3_DIR variable, and enter the subdirectory where you want PATROL to be installed. The value that you enter is appended to the base directory that you specify for the PATROL_BASE_DIR variable. If the computer on which you are installing the package already has a PATROL installation, the directory you enter for this variable must be the same directory where the existing PATROL installation is installed. f Click on the value for the INTEGRATION_SERVICE variable, and enter the name of the host computer where the Integration Service is installed. g If you are not deploying a PATROL Agent package, click on the value for the RULESET variable and remove the value, PIA_WIN.cfg, and leave this field blank. The PIA_WIN.cfg ruleset is used for PATROL Agent deployments only. If this ruleset is specified in the RULESET variable for any package other than a PATROL Agent package, the package deployment will fail. 9 Click OK on the Modify Instance dialog box.
Note
Note
Note
WARNING

After you complete creating the property instance, the next step is to create a deployment job in BMC Server Automation. For details, see Creating BMC Server Automation jobs to deploy BMC ProactiveNet component packages to remote hosts on page 507.
Creating BMC Server Automation jobs to deploy BMC ProactiveNet component packages to remote hosts
After you create and push the component packages into BMC Server Automation and create a property instance, you create deployment jobs in BMC Server Automation to deploy those packages to the remote hosts on which you want to install the components.
To create a deployment job

1 In the navigation tree of the BMC Server Automation Console, expand the Depot folder and then the Packages folder until the PATROL folder is displayed. 2 In the PATROL folder, select the package that you want to deploy, right click, and choose Deploy. The New Deploy Job wizard is displayed. 3 In the New Deploy Job wizard, perform the following steps: a On the General page, enter a job name and description, and select the directory into which you want to save the job. Click Next. b On the Package page, perform the following actions:
Click on the PATROL_INSTALL_CONFIG variable and select the property
instance that you created in the task Creating a property instance in BMC Server Automation on page 505 and click OK.
Ensure that the RULESET variable is blank unless you are deploying a
PATROL Agent package, in which case the value should be PIA_WIN.cfg
Click on the TAG variable and enter the tag created in the BMC ProactiveNet
Central Monitoring Administration console that you want to use to configure the components in this deployment. The TAG value must be in the following format: TagName="description"
Tags are defined in the Policies created in the BMC ProactiveNet Central Monitoring Administration console. For details about creating policies and defining the tags needed for the BMC Server Automation deployment jobs, see the BMC ProactiveNet Central Monitoring Administration console online Help. Click Next. c On the Targets page, in the Available Targets pane, expand the list of servers and select the servers that you want to deploy the package to and click the Add Selected button. The server name is displayed in the Selected Targets pane. Click Next. d On the Default Notification page, accept the defaults and click Next. e On the Phases and Schedules page, accept the defaults and click Next. f On the Job Options page, accept the defaults and click Next. g On the Phase Options page, accept the defaults and click Next. h On the Properties page, accept the defaults and click Next. i On the Permissions page, accept the defaults and click Finish. 4 In the navigation tree in the BMC Server Automation Console, expand the Jobs folder, select the job that you created, right click on that job, and choose Execute. The package is deployed to the servers that you specified and the components in the package are installed. The PATROL Agent connects to the Integration Service that is defined in the property instance that you associated with the package. The Integration Service communicates the tag that is defined in the property instance to the BMC ProactiveNet Central Monitoring Administration console. The BMC ProactiveNet Central Monitoring Administration console uses that tag to determine what configuration to use to configure the PATROL Agent. After the installation and configuration completes successfully, the PATROL Agent starts monitoring objects based on what is defined in the configuration.
Uninstalling components provisioned with BMC Server Automation

Perform the following procedures to uninstall the BMC ProactiveNet components that you installed by using BMC Server Automation. Perform these procedures on the computers where the components are installed.
To uninstall components on UNIX and Linux computers

These steps must be performed as root or with an account with equivalent permissions. 1 From a command line, execute the following command: rm -f /tmp/PATROL_Uninstall*.* 2 Change directory to /installationDirectory/InstallEngine/Install/instbin and execute the following command: thorinst.sh -uninstall /installationDirectory/InstallEngine/Install/instdata/ uninstall-all.ctl -log /tmp/PATROL_Uninstall.log 3 Execute the following command: rm -f /etc/init.d/PatrolAgent /etc/rc3.d/S50PatrolAgent /etc/rc3.d/K50PatrolAgent 4 Change directory to /etc/ and execute the following command: rm rf patrol.d 5 Change directory to /installationDirectory/ and execute the following command: rm -rf InstallEngine Patrol
To uninstall components on Windows computers

1 If you have multiple PATROL agents deployed on the same host, remove each instance by opening a command line and executing the following command for each agent instance: PatrolAgent-portNumber -remove 2 From the command line, execute the following command: del "C:\Windows\TEMP\PATROL_Uninstall*.*"
3 From the command line, change directory to installationDirectory\InstallEngine \Install\instbin\ and execute the following command: thorinst.exe -uninstall "c:\installationDirectory\InstallEngine\Install\instdata \uninstall-all.ctl" -log "C:\Windows\TEMP\PATROL_Uninstall.log" 4 From a command line, execute the following command rd /s /q "c:\installationDirectory\InstallEngine" 5 Check the uninstall log file, and reboot the computer if the log file indicates that a reboot is necessary.
11
Configuring BMC ProactiveNet Integrations
You can integrate BMC ProactiveNet with other BMC products using a postinstallation configuration utility that is accessed from the Operations Console. The following BMC products can be integrated with BMC ProactiveNet using the postinstallation configuration utility:

BMC Application Response System Server BMC Server Automation BMC Remedy Service Desk BMC Atrium Single Sign On LDAP
There are other possible integrations with BMC products that are not currently available for configuration using the post-installation configuration utility. Advantages
Note
Integrate the above BMC products with BMC ProactiveNet in a common interface by editing the required parameters for each configuration. Launch the integration interface from the Operations Console and configure all integrations. There is no need to log into the BMC ProactiveNet Server to enable integrations. Save time during the installation process by performing the integrations after the installation. Save time during server deployments by performing the integrations after the deployments.
Chapter 11 Configuring BMC ProactiveNet Integrations 511
Easily make changes to IP addresses and other configuration parameters previously set by launching the integration interface and modifying the required fields. Immediately test the integration for BMC Remedy Service Desk. Limitations
Once an integration is enabled, you cannot disable it through the interface. Active and inactive modes are available only for SSO and LDAP integrations. Testing functionality is available only for BMC Remedy Service Desk. All other integrations validate the data and do no require testing.
To configure BMC ProactiveNet integrations

1 In the BMC ProactiveNet Operations Console select Options > Administration. 2 Click Edit under Integrations with other BMC Products. The Configure BMC ProactiveNet Integrations window displays the available integrations and their relevant fields values. By default, all integrations are marked for configuration and their configuration fields appear on the screen. Empty text fields indicate that the integration is not configured. If text fields are populated with values, then the integration is enabled. You can hide integrations that are not relevant to your installation by clearing the checkbox next to the integration name.
Note When you select or deselect one or more integrations, other integrations might be automatically selected or deselected due to shared dependencies.
In an upgrade scenario, details of the integrations will already exist in the database. However, no data validation occurs during an upgrade. To initiate validation, modify the data in the configuration fields. All the fields that are available during installation are also available in the integration screen. 3 Scroll down and enter the configuration values for the integrations. BMC AR Server/CMDB
Input field AR Server Hostname AR Server Port Description Enter the host name of the AR Server. Enter the AR Server or CMDB port number. The default is 0. If AR is configured with a portmapper, enter port 0.
Input field AR Server User AR Server Password Publishing Mode
Description Enter the user name required to log in to the AR Server. The default is Demo. Enter the password required to log in to the AR Server. Select Single Server or Multiple Server depending on whether you installed BMC ProactiveNet on a single server of multiple server environment . Enter the host name of the UDDI registry for Atrium CMDB or the name of the Atrium Web Services Server. Enter the port number of the UDDI registry for CMDB or the port number of Atrium Web Services server for CMDB. Enter the UDDI registry user name. The default is admin. Enter the UDDI registry password. Select the application protocol. The default protocol is http. Select the port.
UDDI Hostname UDDI Port UDDI User UDDI Password BMC ProactiveNet Server Protocol BMC ProactiveNet Server Port
Note Logs for CMDB integration named integrate_atrium_cmdb.log are located in the <installation_path>/pw/pronto/logs directory.
BMC BladeLogic
Input field User Password User Role Use UDDI Description Enter the user name for the BMC BladeLogic (also referred to as BMC Server Automation) server. Enter the password for the BMC BladeLogic server. Enter the role that is defined to grant permissions to the BMC Server Automation user. Default is BLAdmins. Check to display additional UDDI options. To copy UDDI values from the CMDB integration, you can click Copy CMDB UDDI Values. UDDI Hostname UDDI Port UDDI User UDDI Password Enter the host name of the UDDI registry for Atrium CMDB and the name of the Atrium Web Services Server. Enter the port number of the UDDI registry for CMDB or the port number of Atrium Web Services server for CMDB. Enter the UDDI registry user name. The default is admin. Enter the UDDI registry password. Chapter 11 Configuring BMC ProactiveNet Integrations 513
Input field Web Services Host Web Services Port
Description Enter the Web Services host. This field is not displayed if you have selected the Use UDDI option. Enter the Web Services port. This field is not displayed if you have selected the Use UDDI option.
You can verify if the BMC BladeLogic integration is successful by performing the steps listed in the To verify the BMC BladeLogic integration on page 517 section. BMC Remedy Service Desk (IBRSD)
IBRSD is installed as part of the BMC ProactiveNet CMDB Extensions. When you install the BMC ProactiveNet CMDB Extensions, the IBRSD AR System module is installed by default. If you are upgrading from an earlier version of BMC ProactiveNet, you can use the post installation configuration utility to integrate your previously installed version on Integration for BMC Remedy Service Desk.
Note
Input field Instance Name Form Name
Description Read-only field. The default instance name is displayed. Enter the BMC Remedy Service Desk form name to which events are propagated. Default is INT:Staging. Enter the gateway port number to configure gateway entry in the mcell.dir and ibrsd.dir files. Enter the gateway encryption key to configure gateway entry in the mcell.dir and ibrsd.dir files.
Gateway Port Gateway Encryption Key
The Integration for BMC Remedy Service Desk required you to enable an event management policy that propagates events to BMC Remedy Service Desk. Perform the following steps to enable an event management policy in BMC ProactiveNet: a Log in to BMC ProactiveNet Administration Console. b In the Administration tab, click Event Management Policies on the left, and navigate to pncell_<server_name> > By Selector > IBRSD > All Critical Events. Policy details appear on the right c From the Edit menu, select Edit Policy. d In the Propagation Policy Details tab on the right, select Enabled.
During the installation of CMDB extensions, cell information is automatically updated in the IBRSD.dir file . However, if you have not defined additional cells, you need to update the IBRSD.dir manually with those cell entries. e You must have a valid entry pointing at the cell in <AR_HOME>/conf/IBRSD/IBRSD.dir file on the BMC AR Server: cell <cell_name> <key> <cell_host:port> f Restart the IBRSD/BMC AR Server service from services.msc that resides on the AR system. g Click Test to test the integration for BMC Remedy Service Desk. A result window appears indicating the integration status. Start Remedy Service Desk Service Status - even when the status shows SUCCESS, verify in the services file that the BMC Remedy Service Desk Service is actually running. Stop Remedy Service Desk Service Status - if the service is already stopped, the status will show failure. In this case, failure is not a concern. Verify that the CMDB configurations were implemented using the validate_atrium_cmdb CLI command. For more information, see "Validating BMC Atrium CMDB elements" in the BMC ProactiveNet Installation and Configuration guide. BMC Atrium Single Sign On
Input field Single Sign-On is Active Atrium SSO Server Hostname.Domain Description Once integrated, Single Sign On can be activated or deactivated by selecting or clearing this field. Enter the fully qualified domain name of the SSO Server.
Note
Input field BMC ProactiveNet Server Hostname.Domain
Description Enter the fully qualified domain name of the server where BMC ProactiveNet Server is installed. By default, this field is populated with the host name of the server on which the installer is executed. Note: Ensure that you enter the FQDN name of the server. If the FQDN name is not entered, a redirection error message may be displayed.
Atrium SSO HTTPS Port Searcher ID Searcher Password Atrium SSO AmAdmin Password Administrative User Group
Enter the Atrium SSO secure port number. The default port number is 8443. Enter the SSO Searcher ID used to search all user names and groups. Enter the password of the Searcher ID user. Enter the Atrium SSO Server AmAdmin password. Specify the user group that is to be created on BMC ProactiveNet and assigned Super Administrator privileges. This user group must also be present on BMC Atrium SSO.
LDAP
Input field LDAP Integration is Active Add LDAP Server LDAP Alias LDAP Version Host Name Description Once integrated, LDAP can be activated and deactivated by checking the box. Adds a new LDAP Server integration. The configuration fields for the integration appear below. Generated automatically by the system. You can change the name. LDAP version number. The most recent version is 3. Fully qualified host name where LDAP is installed. You can verify the connection between the LDAP server and the IAS using the ping command.x Port number to connect to the LDAP server. The default non-secure port number is 389. The default secure (SSL) port number is 636. The top level directory of the LDAP structure. This is the base Fully Qualified Distinguished Name (FQDN). The Distinguished Name represents an object and a path to the object in the directory hierarchical namespace. Objects are ordered from the most specific to the least specific. Login ID used by BMC ProactiveNet to connect to the LDAP server.
Port Base Domain
User
Input field Password
Description Authentication password (encrypted) that is used to connect to the LDAP server Note: Set the encrypted attribute to false and then enter the password in plain text. When IAS restarts, it encrypts the password and changes the encrypted attribute value from false to true.
User SSL User ID Attribute User Search Filter Group Search Filter Delete LDAP Server
Indicate whether LDAP authentication is using SSL. Attribute in the user entry that contains the login ID. Search filter that the LDAP server uses to look up a user entry. Search filter that the LDAP server uses to look up a user group entry. Deletes the current LDAP server.
4 Click Apply. The system tries to integrate with all the applications for you which you have modified the configuration values in one batch. The integration process may take several minutes before completing.
5 Verify the success or failure for each integration in the Results Window that is displayed.
To verify the BMC BladeLogic integration

1 In the command line interface, enter pw blade get_setup. The setup details display, reflecting what you entered in the Configure BMC ProactiveNet Integrations window. 2 Execute the pw blade test command to test the BMC BladeLogic integration. 3 Return to the Configure BMC ProactiveNet Integrations and verify the configuration details for BMC BladeLogic are still available, this indicates that the integration is active. The BMC BladeLogic auto-provisioning packages must be run separately. They are not included in the integration.
Note
To verify a successful Single Sign On integration

1 Launch BMC ProactiveNet web console. The BMC Atrium SSO login screen is displayed showing that single sign on has been activated.
2 Log in using your user name and password. 3 The BMC ProactiveNet Operations Console opens immediately and no further authentication is required until logging out.
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. Table 116: 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 519
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
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
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

The following core event slots provide data that is 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
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

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
VMwareRPSysMon
VMwareHostDiskMon
VMwareVMCPUTotMon
VMwareVMDiskTotMon
VMwareVMNetTotMon
VMwareHostCPUTotMon
VMwareHostDiskTotMon
VMwareHostNetTotMon
VMwareHostDSMon
VMwareMon
VMwareHostDatastorePathMon
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 96 event operation 96, 97 Acknowledged (ACK) event status icon 28 aggregated monitors 42 aggregated status monitors 42 area graph, creating 315 Assign To (event operation) 96 Assigned event status icon 28 Auto-baseline 245 configuring Events tab display settings 119 configuring BMC ProacitveNet integrations 511 creating local filter 89 current data 163 Custom Graphs 313 Custom graphs, creating a dial gauge graph 325 custom graphs, creating a line or area graph 315 Custom graphs, creating a pie graph 323 Custom graphs, creating a top N graph 321 Custom graphs, creating X-Y graphs 320 customizing Events tab display settings 119 Customizing_the_display_of_events 119
B
BMC Impact Explorer Event Groups, described 26 bookmarks, creating 19
D
Decline Ownership event operation 96, 97 icon 96 Details notebook, Canvas view 215 Details notebook, Graph view 215 Details notebook, Heat Map view 215 Details notebook, Tile view 215 dial gauge graphs, creating 325
C
Canvas view Details notebook 215 Canvas View, changing preferences 166 Canvas View, setting up and using 166 Central Monitoring Repository, provisioning BMC ProactiveNet components 505 central ProactiveNet Server 118 Changing chart attributes 212 Chart View, changing preferences 207 Chart View, setting up and using 207 child ProactiveNet Server 118 Close event icon 96 operation 96, 97 Closed event status icon 28 collectors event count affected by status 31 color event status icon 28 configuration items, finding 21
E
event collectors described 26 event count affected by status 31 event list folder, creating for remote cells 81 event operations, performing 96 event priority icons 29 setting 96 understanding 29 event severity icons 28 levels 28 Index 527
event status icons 27 understanding 27 events acknowledging 96 assigning to an individual 96 closing 96 declining ownership 96 manual events 103 performing operations 96 sending manual events 103 setting the priority 96 sorting 93 sorting fields 93 taking ownership 96 events list organizing 73 refreshing 72 Events View configuring display settings 119 customizing display settings 119
I
icons Acknowledge Event 96 Close event 96 Decline Ownership 96 event priority 29 event severity 28 event status 27 Set Priority 96 Take Ownership 96 Index Term 3337, 40, 56, 58, 74, 76, 100, 101, 105108, 124, 213, 218, 502, 503, 507, 509 instant poll 163 Integrate BMC ProactiveNet alarms BMC Run Book Automation 300 Integrating with SLM 312 integrations, configuring 511
F
filtering events, by severity 84 events, by slot name 84 events, overview 84, 221 SLO records in the Watch List 423 SLO violations 420 filters creating local 89 global 84 severity quick filter 84 slot quick filter 84 FlashCheck 163
L
launching originating ProactiveNet Server 118 line graphs, creating 315
M
monitors, aggregated 42 multiple ProactiveNet Server deployment 118
O
Open event status icon 28 operations console, changing user preferences in the Canvas View 166 operations console, changing user preferences in the Chart View 207 operations console, changing user preferences in the Graph View 191 operations console, changing user preferences in the Tile View 181 operations console, changing user preferences in the Tree Map View 203 operations console, setting up and using the Canvas view 166 operations console, setting up and using the Canvas View 166 operations console, setting up and using the Chart View 207 operations console, setting up and using the Graph View 191
G
Graph view Details notebook 215 Graph View, changing preferences 191 Graph View, setting up and using 191 Graph view, stacked graph layout 199 Graph view, topology layout 195 graphs, custom 313
H
Heat Map view Details notebook 215 Heat Map View, setting up and using 202
528
operations console, setting up and using the Heat Map View 202 operations console, setting up and using the Tile View 180 operations. See event operations, performing 96 organizing events in the event list 73 slot quick filter 84 sorting events multiple columns 93 single column 93 stacked graph layout 199 status affects event count for collector 31 event icons 27
P
pie graphs, creating 323 priority. See event priority 29 provisioning 505
T
Take Ownership event operation 96 icon 96 Tile view Details notebook 215 Tile View, changing preferences 181 Tile View, setting up and using 180 top N graphs, creating 321 topology layout 195 Tree Map View, changing preferences 203
Q
queries, creating filters when searching for configuration items 21 querying SLO records in the Watch List 423 SLO violations 420 quick filters severity 84 severity quick filter 84 slot quick filter 84
U
Unacknowledge Event event operation 97 user console, changing user preferences in the Canvas View 166 user console, changing user preferences in the Chart View 207 user console, changing user preferences in the Graph View 191 user console, changing user preferences in the Tile View 181 user console, changing user preferences in the Tree Map View 203 user console, setting up and using the Chart View 207 user console, setting up and using the Graph View 191 user console, setting up and using the Heat Map View 202 user console, setting up and using the Tile View 180 user preferences, changing for the Canvas View 166 user preferences, changing for the Chart View 207 user preferences, changing for the Graph View 191 user preferences, changing for the Tile View 181 user preferences, changing for the Tree Map View 203
R
refreshing the event list automatically 72 remote actions accessing results of 113 remote cells, creating event list folder 81 Reopen Event event operation 97 results of a remote action 113
S
sending manual events 103 Set Priority event operation 96, 97 icon 96 Setting up and using the Chart View 207 Setting up and using the Heat Map View 202 severity effect on event status icon 28 level indicator (Events View navigation) 29 quick filter 84
Index
529
X
X-Y graphs, creating 320
530
49532
*244855*

ProactiveNet User Guide 9.0

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ProactiveNet User Guide 9.0

Загружено:

Авторское право:

Доступные форматы

BMC ProactiveNet User Guide

BMC ProactiveNet User Guide

BMC ProactiveNet User Guide

BMC ProactiveNet User Guide

BMC ProactiveNet User Guide

To log on to the BMC ProactiveNet Operations Console

Chapter 1 Introducing the BMC ProactiveNet Operations Console

Accessing the Operations Console

To change your Operations Console password

To enable multiple Firefox sessions

Choosing the console type

To enable multiple Internet Explorer sessions

Choosing the console type

Chapter 1 Introducing the BMC ProactiveNet Operations Console

Navigating the Operations Console

Console Type SLO Management Console

To set the default logon console

Navigating the Operations Console

16 BMC ProactiveNet User Guide

Navigating the Operations Console

Navigating the Operations Console

Navigational element Reports

Views & Graphs

Changing navigation pane options

To set navigation pane options

18 BMC ProactiveNet User Guide

Navigating the Operations Console

dialog box open. box.

Hiding the navigation pane

To hide the navigation pane

Creating bookmarks in the navigation pane

Chapter 1 Introducing the BMC ProactiveNet Operations Console

Navigating the Operations Console

To add a folder to the Bookmarks drawer

To rename bookmark folders

20 BMC ProactiveNet User Guide

Navigating the Operations Console

Finding configuration items to view

To perform a basic search for a configuration item

Navigating the Operations Console

To use an existing filter to perform an advanced search for a configuration item

To create a new filter to perform an advanced search for a configuration item

22 BMC ProactiveNet User Guide

Navigating the Operations Console

and click Edit Queries.

Name dialog box.

To execute the search, click Find.

Navigating the Operations Console

view and access that folder. access that folder.

24 BMC ProactiveNet User Guide

Navigating the Operations Console

Abnormalities, Groups, Services, Devices, or Monitors nodes in the navigation

the parent folders)

Navigating the Operations Console

Event and component folders

26 BMC ProactiveNet User Guide

Navigating the Operations Console

Understanding event status

Chapter 1 Introducing the BMC ProactiveNet Operations Console

Navigating the Operations Console

Understanding event severity

28 BMC ProactiveNet User Guide

Navigating the Operations Console

Color faint grey