BMC ProactiveNet Performance Management - SharePoint Monitoring

Transcription

1 BMC ProactiveNet Performance Management - SharePoint Monitoring User Documentation December 2013

2 Table of Contents User Goals and Features...9 Business Value...10 Supported Platforms...10 Adding Central Monitoring...12 Administration Tags Importing the Solution...14 into Central Administration Creating the Installation...16 Package Downloading the...21 Installation Package Installing the Package...21 Creating and Importing...25 an Adapter for a BMC PATROL KM Updating an Adapter...31 for a BMC PATROL KM Importing and Customizing...32 Thresholds Verifying the Data...33 Collection Managing Baselines...35 and Key Performance Indicators Configuring General...38 Settings Managing Policies...39 Configuring Monitor...40 Settings...42 Enabling the Debug Mode...43 Additional Configuration Variables Configuring Thresholds...46 Using BMC ProactiveNet...48 Performance Management...48 Navigating the BMC ProactiveNet Operations Console Adding attributes...51 to the graph...52 Viewing and manipulating attribute graphs Viewing monitors...52 for a device...53 Changing thresholds...53 Managing Baselines and Key Performance Indicators ASP.Net...57 Databases...57 HTTP Availability...58 Memory...58 Performance...59 Processes...59 Table of Contents 2

3 Sites...60 Virtual Server...60 Web...61 Windows Event Log...61 Windows Service...62 Table of Contents 3

4 Support Information

5 This section contains information about how to contact Customer Support and the levels of support offered for this and other releases. If you have problems with or questions about a BMC product, or for the latest support policies, see the Customer Support website at You can also access product documents and search the Knowledge Base for help with an issue at If you do not have access to the web and you are in the United States or Canada, contact Customer Support at Outside the United States or Canada, contact your local BMC office or agent. 5

6 Legal Notices

7 Copyright 2011 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. Linux is the registered trademark of Linus Torvalds. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. UNIX is the registered trademark of The Open Group in the US and other countries. The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation. BMC Softwa re Inc City W e st Blv d, Houston T X , USA Custom e r Support: (Unite d Sta te s a nd Ca na da ) or conta ct y our loca l support ce nte r 7

8 Key Concepts

9 The pages in this section provide a high-level overview of the product. User Goals and Features Business Value Supported Platforms Note that for conv enience and brev ity, reference to BMC Proactiv enet Performance Management - SharePoint Monitoring, may also be made as BPPM SharePoint Monitoring. User Goals and Features product allows you to view, monitor, and manage your entire Microsoft SharePoint environment by viewing the current and historical information through a centralized console. You can view detailed system metrics on all parts of your environment, such as: Database: Availability, size... Event Logs: Last matching events, Alarm and warning event counts... Performance: Current ISAPI extension requests, ISAPI extension requests per seconds, received bytes per seconds... Processes: Handle count, processor time, working set... Sites: Availability, number of hits, size... Virtual Servers: Availability, number of registered users, number of sites... Web: Last access date, last modification date, time since last access... Web Service: Current connectors, received bytes per seconds... 9

10 Business Value provides current and historical information through a centralized console so you can easily view and manage your entire Microsoft SharePoint environment. The product collects and brings critical performance data and useful metrics into the BMC ProactiveNet Performance Management environment and enables SAN Administrators to be warned whenever a problem occurs in their Microsoft SharePoint environment. is installed and loaded on the server running the Windows SharePoint Services (as a Web Extension on IIS). BPPM SharePoint Monitoring verifies the availability to the databases, sends requests and collects critical information relating to SharePoint content monitors all of the performance metrics and usage statistics of your SharePoint environment. It continuously monitors the activity of each component and is also able to build reports on past utilization statistics. Supported Platforms supports the following SharePoint equipments: Microsoft Windows SharePoint Services 2.0 Microsoft Windows SharePoint Services 3.0 Microsoft Office SharePoint Server 2003 Microsoft Office SharePoint Server 2007 Microsoft Office SharePoint 2010 Microsoft Office SharePoint 2013 Windows Server 2008 User Goals and Features 10

11 Planning

12 Adding Central Monitoring Administration Tags Adding Central Monitoring Administration tags should be taken into consideration before installation. A policy specifies a set of actions to be taken when a specific condition on the BMC PATROL Agent is fulfilled. A policy enables you to perform the following actions: Apply specific configuration to one or more BMC PATROL Agents Configure thresholds and set baselines on BMC ProactiveNet Child Servers Each policy is assigned a BMC ProactiveNet Central Monitoring Administration tag and each BMC PATROL Agent can have one or more tags assigned to it. When you assign a tag to a BMC PATROL Agent the associated policy is applied to the PATROL Agent. You can assign the tag value of a policy to a PATROL Agent in the following ways: You can add a PATROL Agent and set the tag as part of the configuration process that you perform from Central Monitoring Administration. For details, see Managing downloads in Central Monitoring Administration. If the PATROL Agent has already been installed, use PATROL Configuration Manager to set the following ruleset that provides the tags: /AgentSetup/Identification/Tags/TAG/tagName =tagdescription For example if the tag which has to be applied is oracletag, the ruleset is as follows /AgentSetup/Identification/Tags/TAG/oracleTag= ORACLE MONITORING In BMC Proactiv enet v ersion 9.0, the tag description is ignored, and only the tag name is used to ev aluate the policy. Adding Central Monitoring Administration Tags 12

13 Installing

14 The installation of can be handled from A to Z from BMC ProactiveNet Central Monitoring Administration. Once the latest version of the solution has been loaded into BMC ProactiveNet Central Monitoring Administration, administrators can create all the installation packages required for their different operating systems and platforms and save them for later use in the Monitoring Installation Packages list. These packages can then be deployed to multiple computers. Administrators just have to connect to BMC ProactiveNet Central Monitoring Administration from the machine where they want to install the package, download it and launch the installation. This section describes the different steps to follow to install BMC ProactiveNet Performance Management - SharePoint Monitoring: Creating the Installation Package Downloading the Installation Package Installing the Package. Importing the Solution into Central Administration The BMC ProactiveNet Central Monitoring Repository includes the versions of BMC components that can be used with BMC ProactiveNet. If the version available in the Repository does not correspond to the latest one, you will have to manually import it: 1. Log on to BMC ProactiveNet Central Monitoring Administration 2. Click the Repository drawer and select Manage Repository. Che cking the v e rsion a v a ila ble 14

15 3. Check that the version of the BMC component available is actually the latest one. If not, download it from the Sentry Software Website and save it on the local computer from which you are running the Central Monitoring Administration web-based console. 4. From the BMC ProactiveNet Central Monitoring Administration, click Import Im porting a Single Solution 5. Select Single solution. 6. Browse to a.zip source file. 7. Click Import. The selected archive file is imported to the repository and extracted. Importing the Solution into Central Administration 15.

16 Creating the Installation Package The installation package can be created directly from BMC ProactiveNet Central Monitoring Administration: 1. Log on to BMC ProactiveNet Central Monitoring Administration 2. Click the Repository drawer and select Monitoring Repository. Cre a ting the Insta lla tion Pa cka ge - Monitoring Re pository Importing the Solution into Central Administration 16

17 3. Click Add. Cre a ting the Insta lla tion Pa cka ge - Se le cting the OS a nd Pla tform 4. Select the operating system and platform for which you want to create a package. Creating the Installation Package 17

18 The components available in the repository for the selected operating system and platform are displayed: Cre a ting the Insta lla tion Pa cka ge - Se le cting Com pone nts 5. Select the Installation Package Component: From the Available components list, select SharePoint. From the Version list, select the latest version. Click the right arrow button to move the component into the Selected Components list By default, the appropriate BMC PA TROL A gent for the operating sy stem and platform that y ou chose is included in the Selected components list. Click Next. The Add Component Installation Package wizard is displayed. Creating the Installation Package 18

19 Cre a ting the Insta lla tion Pa cka ge - A dding a Com pone nt Insta lla tion Pa cka ge 6. Go through the wizard. The Installation Package Details is displayed: Creating the Installation Package 19

20 Cre a ting the Insta lla tion Pa cka ge - Insta lla tion Pa cka ge De ta ils 7. Verify that: the operating system and platform are correct the components that you want to include are listed in the Included Components list. 8. Provide the following information: Name: Enter a unique name for the package. (Optional) Description: Enter a description of the package. The description is displayed in the Monitoring Installation Packages list on the Monitoring Repository window. Format: Select a file compression format for the package. 9. Click Save Installation Package. 10. Click Close. The package is now available in the Monitoring Installation Packages list. Cre a ting the Insta lla tion Pa cka ge - Microsoft Sha re Point Insta lla tion Pa cka ge Creating the Installation Package 20

21 Downloading the Installation Package You can download an installation package and install the components on one or more hosts. The installation runs silently with the information entered during package creation. Recommendation If you defined the BMC ProactiveNet Integration Service variable for PATROL Agents in the installation package, ensure the agents are started in phases. Do not start newly deployed agents all at once. Start and configure monitoring for the agents in planned phases to reduce the performance impact on the Integration Service nodes and on the BMC ProactiveNet Server associated with the automatic workflow process. 1. Log on to BMC ProactiveNet Central Monitoring Administration from the computer on which the PATROL Agent is installed. 2. Click the Repository drawer and select Monitoring Repository. 3. (Optional) To filter the list of installation packages, select an operating system from the Filter by Operating System list. 4. Click the link for the installation package that you want to download. 5. Through the browser's download dialog box, save the installation package. Installing the Package 1. Download the installation package on the host where SharePoint needs to be installed 2. Extract the installation package as appropriate for your operating system. The package is extracted to the bmc_products directory on the current host. 3. From the bmc_products directory, run the installation utility for your operating system: (UNIX or Linux) RunSilentInstall.sh (Microsoft Windows) RunSilentInstall.exe The package is installed on the current host. If the package includes a BMC PATROL Agent, the agent sends a configuration request by passing its tags to BMC ProactiveNet Central Monitoring Administration, via the Integration Service. Central Monitoring Administration evaluates policies that match the tags, determines the final configuration to be applied, and sends the configuration information back to the agent. Monitoring is based on the configuration information received by the agent. If no policy matches the tags associated with the agent, the agent does not receive configuration information. The agent does not begin monitoring until a matching policy is created. Creating the Installation Package 21

22 Integrating with BMC ProactiveNet Performance Management

23 Overview To integrate a BMC PATROL KM into BMC ProactiveNet Performance Management, you need to install the KM on top of a PATROL Agent, then add a connection to the system to be monitored and finally create a specific adapter. An adapter for BMC PATROL is a software component designed to facilitate the integration of metrics collected by a BMC PATROL KM into BMC ProactiveNet. The adapter allows you to import application classes from a BMC PATROL KM into BMC ProactiveNet and displays the performance metrics into your BMC ProactiveNet Performance Management environment. It also ensures a periodical synchronization with the KM in order to provide updated and accurate data. A da pte r for BMC PA T ROL A rchite cture Two methods exist to create an adapter for BMC PATROL: The automated workflow (recommended): This method enables the PATROL Agent to automatically connect to the Integration Service, register itself, and start sending performance data to the Integration Service. The PATROL Agent is added to the default profile called "_SA_DEFAULT_" in the Integration Service. The Integration Service uses the SAdapter (Staging Adapter) to accept inbound connections from the PATROL Agents. The SAdapter is a component of the Integration Service which is used for the PATROL Agent phone-home feature. This method requires PATROL Agent v or higher. 23

24 A utom a te d W orkflow - T he PA T ROL A ge nt conne cts to the Inte gra tion Se rv ice The manual method: This method relies on the p3adapter profile. Each p3adapter is responsible for querying a set of PATROL Agents in a single security domain and retrieves data. This method is not documented in this guide. Ma nua l Me thod - Inte gra tion Se rv ice conne cts to PA T ROL A ge nt You can also use the following methods to send events directly to the BPPM cell but you would lose the benefit of the BMC ProactiveNet analytic engine (rate process). The rate process creates the alarms when thresholds are breached and directly sends them to the BPPM cell. PATROL Architecture Method to be Used PATROL 7 BMC Impact Integration for PATROL v7 PATROL 3 BMC Impact Integration for PATROL V3 (MCXP) PATROL Agent 9.0 Wpconfig (Events will be directly sent to cells) For more info about the abov e methods, please refer to the knowledge article: Integrating the Ev ents Generated by the KMs into BMC Ev ent Manager. 24

25 Creating and Importing an Adapter for a BMC PATROL KM Creating an Adapter for a BMC PATROL KM 1. In Wpconfig, make sure that: the /AgentSetup/integration/integrationServices variable is properly set for your PATROL Agents. It should point to the BPPM Remote Agent where the Integration Service is running (pproxsrv) using the following syntax: tcp:<bppm_remote_agent>:3183. the /AgentSetup/prealoadedKMs variable contains SEN_WSS.kml 2. Open the BMC ProactiveNet Administration Console. The BMC ProactiveNet Administration Console is displayed as shown in the following figure: A cce ssing the A dm inistra tion ta b in the A dm inistra tion Console 3. Expand the Adapters folder, right-click BMC PATROL, and select Import and Add BMC PATROL. This action can also be performed from the menu Tools > Configure > Integration Service. 4. Enter the required information: Creating and Importing an Adapter for a BMC PATROL KM 25

26 Se tting the conne ction pa ra m e te rs In the Instance Name field, enter a name for this instance of the Adapter that will perform the integration of the targeted KM into BMC ProactiveNet (e.g. Adapter for SharePoint). From the Source Agent list, select the BPPM remote agent to which your PATROL agents are sending data to Enter the Integration Service Agent hostname or IP address Enter the Integration Service Agent Port. The default port is Enter the required credentials to connect to the Integration Service Agent 5. Click Next to continue. If you have correctly set the integrationservices variable as explained above, your PATROL Agents will be listed: Creating and Importing an Adapter for a BMC PATROL KM 26

27 Re v ie wing the Inte gra tion Se rv ice configura tion 6. Click Next. Creating and Importing an Adapter for a BMC PATROL KM 27

28 Se le cting A pplica tion Cla sse s to im port 7. Select the application classes to import Unselecting will delete the application classes that have already been imported during a previous operation. Application classes ready to be deleted are marked with a red x. 8. Click Next to start the import process. The system displays a summary of the application class import, click Next to continue. 9. Select the application classes you wish to auto-synchronize with the Integration Service Agent. Creating and Importing an Adapter for a BMC PATROL KM 28

29 Se le cting A pplica tion Cla sse s for A uto-sy nc 10. Click Next to continue. 11. If needed, set the Filter details. Creating and Importing an Adapter for a BMC PATROL KM 29

30 Se tting filte r de ta ils 12. Click Next to continue. 13. If needed, set the Auto-sync Poll Interval and/or Timeout. Creating and Importing an Adapter for a BMC PATROL KM 30

31 Sche duling A uto-sy nc polls 14. Click Finish. The system displays a summary of your settings, click Finish to confirm. The Adapter has been added to the Adapters folder of the Administration Console. 15. To see the class instances that have been imported by the Adapter, expand the Adapters folder, right-click the Adapter and select Details. We strongly recommend that you create a specific adapter for each KM you need to integrate into BMC ProactiveNet to enable the update of a single KM independently. Updating an Adapter for a BMC PATROL KM 1. Delete the Adapter instance 2. Go through the Add an Adapter wizard to actually delete the monitor types that had been created based on the previous version of the KM 3. Close 4. Resume the entire Creating an Adapter for a BMC PATROL KM procedure Creating and Importing an Adapter for a BMC PATROL KM 31

32 For complete and detailed information on these procedures, please refer to the BMC Proactiv enet documentation av ailable from BMC W eb site. Importing and Customizing Thresholds 1. Launch the BMC ProactiveNet PW Commands. On Windows 2008, you need to run the PW Commands as Administrator. La unching BMC Proa ctiv e Ne t PW com m a nds 2. Execute the following command line: pw adapter -type patrol -get_thresholds <file name> -pproxy_host <hostname ipaddress> [-pproxy_port <port_number>] [-pproxy_user <username>] [-pproxy_passwd <password>] -i -v where -get_thresholds <file name> = File name with absolute path at which thresholds will be imported -pproxy_host <hostname ipaddress> = Host name or IP Address of Patrol Proxy Server -pproxy_port <port_number> = Port at which Patrol Proxy Agent communicates with Patrol Proxy Server -pproxy_user <username> = User name of Patrol Proxy user -pproxy_passwd <password> = Password to authenticate Patrol Proxy user -i = import Instance level thresholds -v = run in "verbose" mode, producing extra lines of output during extraction and conversion processes Updating an Adapter for a BMC PATROL KM 32

33 The command has produced a text file with all the parameter threshold settings. 3. Open the file in a text editor. Check that the global thresholds have been properly interpreted. 4. Then go to the # INSTANCE LEVEL THRESHOLDS section of the file. 5. Uncomment all instance level thresholds for the _PATROL SEN_WSS_ prefixed instances. Search the file for the 'NOT_IMPLEMENTED' occurrences to detect thresholds that were not properly converted by the PATROL Adapter. 6. Save the file. 7. Execute the following command: pw threshold loadpatrolthreshold [<thresholdfilename> [-v]] where: <thresholdfilename> is a thresholds file name. If no file path is specified then the default '<Installation Directory>/pw/tmp/' is -v enables the Verbose mode 8. Check the result in the BMC ProactiveNet Operations Console. Class-level thresholds can be displayed using the Absolute Global Thresholds panel in the BMC ProactiveNet Operator Console, while instance-level thresholds are displayed in the Absolute Instance Thresholds panel: Thresholds have been successfully imported into BMC ProactiveNet. Verifying the Data Collection You can check that data collection is performed at the BPPM Integration Service and BPPM server levels: Either by running a command on the BPPM Remote Agent machine where the Integration Service is running Or through the Operations console. Importing and Customizing Thresholds 33

34 Method 1: Running a Command 1. On the BPPM Remote Agent machine where the Integration Service is running, launch the command prompt 2. Go to BPPMAgent\Agent\pproxy\PNS\bin 3. Run the following command: pproxcli >c:\pprox.txt /connect -host <BPPM_integration_service_hostname> -port <port> -username <username> -password <password> Example: /connect -host carnap -port username admin -password ****** 4. Run the following command: /PATROL/query/getInstanceData -agent <patrol_agent>:<port> Example: /PATROL/query/getInstanceData -agent morgan: Check the output (c:\pprox.txt). 6. To get more information about the data collection status, run the following commands: Command Description /PATROL/config/listAgent List the agents /PATROL/query/getAgentDetails -agent ALL Get all the agent details /PATROL/query/getMonitorDetails -agent ALL Get all the monitor details /PATROL/query/getMonitorInstanceDetails -agent ALL Get the monitor instance details /PATROL/query/getInstanceData -agent ALL Get instance data for all patrol agents /PATROL/query/getInstanceData -agent <agent_name>:<port_number> -appl <application_name> -inst <instance_name> -param <parameter_name> Get instance data for given agent. Application name, instance name and parameter name are optional Method 2: Through the BMC ProactiveNet Operations Console 1. In the Main navigation pane, click Devices. 2. Click to display the Grid View 3. Select the monitor/parameter for which you want to check the data collection status 4. Click and select Show Graph 5. Click frame. Export to Excel to get the list of all the data collection points between a selected time Verifying the Data Collection 34

35 Managing Baselines and Key Performance Indicators In order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNet calculates baselines per parameter (metrics or attributes) based on values collected over a specified period of time to determine a normal operating range. When the collected values for these parameters are out of range, an alert is triggered. Some parameters are identified by default as Key Performance Indicators and therefore automatically included in the base lining calculation. 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 monitor s attributes and metrics over a specified time period and establishing a low baseline value (consisting of the 10th percentile of all the values for a given time period) and a high baseline value (consisting of the 90th percentile of all the values for a given time period), 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. Requirements for baseline generation For baselines to be generated for an attribute, that 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. A bsolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements. Managing Key Performance Indicators The KPI attribute of a parameter can be activated or deactivated manually through the BMC ProactiveNet Administration Console. In this KM, some parameters or attributes have been designated as important indicators of performance (KPIs). We do not recommend that these default settings are modified. However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet Administration Console. To add or remove Key Performance Indicator (KPI) attributes for a monitor type 1. In the Administration Console, from the menu bar, choose Tools > KPI Administration. The Managing Baselines and Key Performance Indicators 35

36 KPI Administration dialog box is displayed. 2. From the Monitor Type list, choose the monitor type for which you want to add or remove KPI attributes. A list of attributes for the selected monitor type is displayed. 3. In the KPI column for the attributes that you want to add or remove as Key Performance Indicators: select the KPI check box to add the corresponding attribute as a KPI deselect the KPI check box to remove the corresponding attribute from the KPIs for that monitor type For complete and detailed information on this procedure, please refer to the BMC Proactiv enet documentation av ailable from BMC W eb site. Parameters for which the system by default calculates baselines as well as parameters considered as KPIs are respectively identified by the following icons: Auto-baseline KPI Managing Baselines and Key Performance Indicators 36

37 Configuring After Installation

38 is configured when you create a policy. A policy is a template containing the configuration of a PATROL Agent. A policy can be assigned to one or more PATROL Agents using a unique tag (Central Monitoring Administration tag), and a PATROL Agent can be assigned one or more policies with different priorities. If you have not already added the Central Monitoring Administration tag to your PATROL Agents during the solution installation, then you must manually assign the tag after you have configured the policy. For details, see Adding Central Monitoring Administration Tags. Configuring General Settings Through the General tab of the Add Policy dialog, you can create a new policy. A policy specifies a set of actions to be taken when a specific condition on the PATROL Agent is fulfilled. First and foremost, actions include monitor configuration. Once a monitor is configured, policies can also specify threshold creation and the setting of baselines. A policy can also include intelligent server-side thresholds so that IT administrators can immediately be alerted on potential problems. Field Instructions Name Enter a policy name. Policy names must be unique. In an environment with tenants, policy names must be unique for a single tenant Tenant (For environments with tenants) Select a tenant name. See Policies and tenants for details. Global indicates a policy applicable to all tenants. Enable policy Select this option to enable the policy, or clear the option to disable the policy. The option is selected by default. If you clear the option, the policy and its associations remain intact, but the policy configuration is not applied until the policy is enabled again. Precedence Enter a number from 0 to 999. Description (Optional) Enter a policy description. Tag Enter a Central Monitoring Administration tag. Policies are applied to BMC PATROL Agents with matching tags. Tags are case sensitive and cannot contain spaces or any of the following characters: /, \, {, }, <, >,,, &. Provider indicates a policy applicable to the cloud service provider Policy precedence When more than one policy is applied to a BMC PATROL Agent and BMC ProactiveNet Child Server, configuration is a union of every attribute defined by the policies. If a conflict arises (that is, two policies configure the same attributes), it is resolved in one of the following ways: Policies with the same tag: If conflicting policies have the same tag, the precedence value determines the order the policies are applied. The policy with the lower number value for precedence is the policy from which the final configuration is applied. Policies with different tags: If conflicting policies have different tags, then the policies are applied according to the order they are listed on the BMC PATROL Agent. The policy listed last on the agent is the policy from which the final configuration is applied. 38

39 Managing Policies This topic provides general instructions for the following policy management tasks: editing, deleting, enabling and disabling. Before you begin Enable Central Monitoring Administration and log on to Central Monitoring Administration. Refer to the BMC documentation and more especially to the section Enabling and configuring Central Monitoring Administration for details. Policies with only threshold configuration or serv er side configuration are applicable only after a policy with monitor configuration is applied. To edit a monitoring policy 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Select a policy and click Edit. 3. Edit the Configuring general settings of the policy. 4. Edit information on one or more of the following tabs: Configuring monitor settings. Configuring threshold settings. 5. Click Update. To delete a monitoring policy Deleting a policy deletes all monitor instances and most settings configured through the policy. Devices remain in the User Groups to which they have been added. 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Select one or more policies and click Delete. 3. Click Yes to confirm deletion. To enable or disable a monitoring policy Enable or disable policies for maintenance and troubleshooting. When a policy is disabled, the policy and its associations remain intact, but the policy configuration is not applied until the policy is enabled again. 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Select one or more policies and click Enable or Disable. Configuring General Settings 39

40 Configuring Monitor Settings When you create or edit a policy, you can add and configure monitor types. The Add Monitor Types dialog box presents configuration fields for compatible BMC PATROL monitoring solutions that are located in the Central Monitoring Repository. For a list of monitoring solutions that you can configure through Central Monitoring Administration, see the Monitoring solutions configurable through Central Monitoring A dministration chapter in the BPPM online documentation. For configuration details for a specific monitor type, see the monitor documentation. To configure custom monitoring solutions through Central Monitoring Administration, ensure the solution is structured correctly; for details, see the Building a PA T ROL Know ledge Module Developers Guide on BMC Support website. To configure the Monitor Type settings using the Add Monitor Types dialog box 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Click Add to display the Add Policy dialog box. 3. Click the Monitor Configuration tab Click Add. From the Solution menu, select Microsoft SharePoint. From the Version menu, select the required version. From the Monitor Type menu, select the Monitor Type for which you want to add a policy, that is SharePoint. 8. Enter the Connection Settings to the Microsoft SharePoint server: Configuring Monitor Settings 40

41 Microsoft Sha re Point Monitoring Configura tion - Globa l Se ttings Username: Enter the username that will be used to access to the Microsoft SharePoint server. Password: Enter the password that will be used to access to the Microsoft SharePoint server. 9. Configure the monitoring settings: Use the spin button of the Discovery Interval field to enter the frequency in minutes of the discovery process. By default, the solution runs a discovery every 60 minutes Use the spin button of the Polling Interval field to indicate how often new data is collected. By default, the polling interval is set to every 2 minutes. Check the Disable Sites Monitoring box if you want to limit the number of instances created and therefore reduce the system resource consumption. Discovery and collect requests and operations will no longer be performed. Configuring Monitor Settings 41

42 Enabling the Debug Mode When you encounter an issue and wish to report it to Sentry Software, you will be asked to enable the Debug Mode and provide the debug output to the Sentry Software support team. To enable the debug mode 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Select the policy that applies to the PATROL Agent for which you need to enable the debug mode, and click Edit. 3. Click the Monitor Configuration tab. 4. Select the Microsoft SharePoint KM monitor type and click Edit. 5. Click the Advanced button. Ena bling the De bug Mode 6. Check the Enable Debug Mode option. The solution will store debug information in a log file. By default debug files are stored in the %PATROL_HOME%\log folder Configuring Monitor Settings 42

43 7. In the Debug End Time field, enter the date and time at which the system must stop logging debug information. Required format: yyyy/mm/dd hh:mm:ss. 8. Click Close to save your settings. For the debug mode to be enabled, the Enable Debug Mode must be checked and the Debug End Time must be properly set to a date and time in the future. Additional Configuration Variables Advanced configuration variables are used to manually set variables that are normally not available through the standard interface. These variables should only be set when instructed so by Sentry Software Support. To configure a variable 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Select the policy that applies to the PATROL Agent for which you need to enable the debug mode, and click Edit. 3. Click the Monitor Configuration tab. 4. Select the Microsoft SharePoint KM monitor type and click Edit. 5. Click the Advanced button. Configuring Monitor Settings 43

44 Configuring v a ria ble s 6. In the Configuration Variables section, enter the name and value of the configuration variable you wish to set: Variables Default Value Description bypassw3svccheck 0 = the KM Set this variable to 1 if the SharePoint service is manually started. ing only performs discoveries when the SharePoint service is started automaticall y. defaultreinitializatio noptions None List of default options to be executed bybmc ProactiveNet Performance Management - SharePoint Monitoring on reinitialization. The default values are: 0=unchecked; 1=checked resetthresholds resetthresholdmanagementmode resetalertactions resetotheralertsettings resetdebugmode Configuring Monitor Settings 44

45 Variables Default Value Description resetremovedpausedobjectlist resetreport resetsecuritysettings resetjavasettings Insert a colon ; between the variable and its value: resetthresholds;1 ; and if you enter multiple variables, they need to be separated by a carriage return. Example: resetthresholds;1 will display the remove thresholds option selected by default in the Reinitialize KM wizard. disablemissingdevic edetection 0 = Missing device detection enabled When set to 1, disables the detection of missing devices. disablepslexecutebu gworkaround 0= activated When set to 1, deactivates the workaround in the solution for a bug in the PslExecute() PSL function. If the solution detects that the version of the PATROL Agent is affected by the PslExecute() bug, it uses an alternate technique to create asynchronous threads with the event_trigger() function and the RemPsl standard event. The disablepslexecutebugworkaround variable disables this workaround. excludesites n/a Filter to exclude all sites whose names match the specified regular expression. forceclassicconfigm ode 0= disabled When the KM is used with BMC ProactiveNet, all the KM configuration menus are disabled in the PATROL Consoles. To enable them, set the forceclassicconfigmode variable to 1. maxfilesizeread (8 Specifies the maximum number of bytes that can be read in the log file during one MB) collection cycle. maxlocktimeout 600 seconds Time during which the collect/discovery is locked and no other collect/discovery can be executed. Unit: seconds pausedobjectlist n/a List of the PATROL object path of the paused objects. (i.e. for which no collection will be performed). pscommand n/a Command used on UNIX/Linux systems to retrieve the list of the currently running processes. Note: This command is used for debug purpose. removedobjectlist n/a List of instances that have been removed from the monitoring environment through the Remove KM Command in a PATROL console. startupdelay 0 second Specifies the number of seconds that the solution will wait before starting its discovery. ThresholdsManagem Retrieved Specifies how the KM should manage the alert thresholds on parameters. Please entmode from the KM read carefully the Configuring Thresholds chapter for more information on this topic. configuratio Possible values: n as (through PATROL for Event Management) tuning (through the standard "Override parameter" mechanism) none (No threshold is set by the KM) 7. Click Add to List. 8. Click Close to save your settings. You can easily modify or remove a variable by selecting it in the list and clicking either the Modify Selection or the Remove from List buttons. Configuring Monitor Settings 45

46 Configuring Thresholds Thresholds can be set from BMC ProactiveNet Central Monitoring Administration for all the monitors that have been configured with this platform. If you have not done so already, please refer to the section Configuring Monitor Settings. To add and configure monitor thresholds 1. Open the Add Policy dialog box. Click for steps: In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. Click Add, or select an existing policy and click Edit 2. Select the Threshold Configuration tab and click Add.. A dding a T hre shold 3. In the Add Thresholds dialog box, select an item from each of the following lists: Solution, Version, and Monitor Type. Configuration fields are displayed. 4. In the Scope list, the Instance option is automatically selected. Type an Instance Name string or regular expression to apply threshold configuration to instances with matching patterns. Select Match Device Name to include the associated device and use the entire <devicename> \<instancename> string for pattern matching. Instance thresholds are applied to the matched monitor instance names or instance names patterns. You can use the following regular expression patterns for the instance name:?, +, *, ( ),, [ ], { }, ^, $,. If the instance name contains one of the pattern characters (except for *), use a backslash ( \ ) before the pattern character. For example, to enter the instance name Storage1 (1), enter Storage1 \(1\). 5. From the Attribute list, select a monitor attribute. Configuring Thresholds 46

47 In the A ttribute list, some attributes are designated as key performance indicators (KPIs). Depending on the monitored env ironment and v ersion, the list of KPIs might appear differently in the BMC Proactiv enet Operations Console. 6. From the Type of Threshold list, select the threshold type. 7. Select and enter values for the threshold parameters. 8. To continue configuration, perform one or more of the following actions in the Add Thresholds dialog box, and then select a different monitor type, version, or solution: To add the configuration details for the threshold to the Threshold Configuration tab, click the Add button at the bottom of the window. To return the settings in the current window to default values, click the Reset button at the bottom of the window. The values on the current window are reset. Be sure to click the Add button to save the configuration on the Threshold Configuration tab. 9. When you finish configuration, click Close. The configuration details are displayed in the table on the Threshold Configuration tab. 10. When you finish configuring thresholds, click Save at the bottom of the Add Policy dialog box, or Update at the bottom of the Edit Policy dialog box. After you save or update the policy, new threshold configurations are pushed to BMC PATROL Agents with matching Central Monitoring Configuration tags. To edit a threshold configuration On the Threshold Configuration tab, select a threshold definition, and click Edit. Edit the configuration values and click Update. When you finish editing the threshold configuration, click Close. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box. After you update the policy, updated threshold configurations are pushed to BMC PATROL Agents with matching Central Monitoring Configuration tags. To delete a threshold configuration On the Threshold Configuration tab, select attributes, monitor types, versions, or solutions. Click Delete. After you delete one or more threshold configurations, click Close. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box. After you update the policy, deleted threshold configurations are removed from BMC PATROL Agents with matching Central Monitoring Configuration tags. Recommended Thresholds Thresholds define acceptable high and/or low values for the data collected. Thresholds can be created as part of a policy that can be applied to multiple monitors types on multiple BMC PATROL Agents. The Reference Guide provides a list of monitor types with their respective attributes and, when meaningful, a recommended threshold. Configuring Thresholds 47

48 For details about baselines and Key Performance Indicators (KPI), see BMC ProactiveNet Central Monitoring Administration or BMC ProactiveNet documentation or refer to the "Managing Baselines and Key Performance Indicators" section. Using BMC ProactiveNet Performance Management This section provides a brief overview of how to navigate and use the product in the BMC ProactiveNet Operations Console. Navigating the BMC ProactiveNet Operations Console Adding attributes to the graph Viewing and manipulating attribute graphs Viewing monitors for a device Changing Thresholds For more detailed information, see BMC ProactiveNet User Guide in the PDF product guides. Navigating the BMC ProactiveNet Operations Console The BMC ProactiveNet Operations Console is a Web-based application that provides options to navigate through BMC ProactiveNet and view all of the information collected and computed by the BMC ProactiveNet Server related to events, views, and graphs. Navigation tree The navigation tree shows an at-a-glance synopsis of events and views. Event and component folders are displayed hierarchically and are divided into the following categories, or nodes. Object Definition Global node The Global node contains the following default collectors: All Event Collectors displays the entire event collector hierarchy All Abnormalities displays all the abnormality events All Services displays all the services All Groups displays all the groups All Devices displays all the devices Based on permissions, users can create event and component folders under this node to organize the event view. My Folder node Based on permissions, users can create event and component folders under this node to organize the event view. To further organize your display, beneath these top-level folders you can add event and component folders, including folders for Component Instances (CIs) associated with a service model. Your ability to Configuring Thresholds 48

49 add event and component folders depends on your permissions. 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, the green icon changes to a red icon, indicating a Critical event. The icons enable you to see the status of devices on your system immediately. For complete details, see the BMC ProactiveNet Getting Started Guide on the BMC Support website. Navigation drawers The navigation pane in the Operations Console contains a series of drawers that enable you to navigate through BMC ProactiveNet functions and views. You can select which drawers to display in the navigation pane. The following table describes the available drawers in the navigation pane and describes their functions. Drawer Description Main Provides access to event lists and displays event information and status. Other cells Lists available remote cells connected to the BMC ProactiveNet Server and monitored by BMC ProactiveNet. Reports Enables you to generate and manage reports based on data collected by BMC ProactiveNet. Note: You must have permission to view this drawer. Views & graphs Provides options for the management of views and graphs in the Operations Console Bookmarks Enables you to view, rename, and delete bookmarks of objects and their related views that you create in the navigation tree. Find CI Provides a search mechanism so that you can search for Component Instances that meet the specified search criteria. Note: You must have permission to view this drawer. 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 who are database administrators access to that event folder. You can drag components from one existing folder to another within the top-level folders in the navigation tree. You also can drag and drop CIs from the Tile or Graph view to an existing folder in the All Services folder. Using BMC ProactiveNet Performance Management 49

50 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 to provide operators with meaningful groups of events or abnormalities and to 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 criteria for those collectors. Nodes for static collectors remain in the navigation tree regardless of 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. Component folders are static or dynamic. You populate static component folders by selecting from a list of objects. You populate dynamic component folders by creating a query. Static folders always contain only the objects that you manually select. Dynamic folders contain the objects that match the query, so the contents of these folders can change without further editing. Operations Console views The following table shows the different views that are available, depending on what object you select in the navigation tree. Each view is accessed by clicking the associated Console view icon. If a view is not available for the object that is selected in the navigation tree, the icon for that view is not displayed in the toolbar. View Description Event The Event view displays all events in an event list. This is the default view for all objects. Use the Event view to check the details of events and to address events that highlight incorrect state. Probable Cause Analysis can help you to identify the cause of the event. An event could be assigned to other users, who can acknowledge and take ownership of the event, fix the problem, and close the event. You can also address the incorrect condition by invoking remote actions, detailed diagnostics, and local actions. The Graph view helps check the impacting service and you can cross-launch to Impact Model Designer, Service Level Manager and Product Catalog in BMC Remedy IT Service Management (BMC Remedy ITSM). You can display an Event view for: Using BMC ProactiveNet Performance Management 50

51 View Description Event collectors Abnormalities Services Groups Devices Monitors Title The Canvas view enables you to create a graphical representation of the components that are being monitored in your environment. The components are represented by objects that you can place 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: Event collectors services Groups Devices Tree/ Graph The Tree/Graph view displays information for a selected object as a tree that represents the hierarchy of the object. The Tree view is available for groups and services. You can use the Tree view to get a real-time, interactive visualization of the event status and other details of the selected group or service. In the Group hyperbolic tree, the entire group hierarchy and devices are visible on a hyperbolic pane that is mapped to a circular display region. Service tree is applicable only for the selected service. If a service is selected in the navigation tree, this view displays a graphical representation of the configuration items in the service model and shows how those configuration items relate to each other. Use the Graph view to monitor events for published service models that represent your business services. You can display a Tree/Graph view for: Services Groups Grid Grid view displays information for the selected object in a tabular format. you can view the event status and other details of the selected object through hyperlinks to graphs, views, etc. You can display a Grid view for: Abnormalities Groups Devices For more detailed information, BMC ProactiveNet Getting Started Guide on the BMC Support website. Adding attributes to the graph Following configuration, only one attribute is enabled for the graph of each monitor. You might want to add additional attributes to the monitor graph. 1. In the BMC ProactiveNet Operations console, select the Navigation drawer. 2. Select Global > Devices. 3. Select the Grid view. All the monitored devices are displayed in table format. 4. Select a device from the displayed table. 5. Select a monitor. Using BMC ProactiveNet Performance Management 51

52 6. Click Tools >Show Graph 7. Select the Attributes & Indicators tab. 8. Select one or more attributes. Up to 12 attributes of a monitor can be displayed on a single graph. Though only two units of measurement can be used. Viewing and manipulating attribute graphs The graph provides a visual display of the attributes of a monitor. Up to 12 attributes of a monitor can be displayed on a single graph In the BMC ProactiveNet Operations console, select the Navigation drawer. Select Global > Devices. Select the Grid view. All the monitored devices are displayed in table format. Select a device from the table. Select a monitor. Click Tools > Show Graph If Collect Data is not enabled then no data is av ailable. The Graph Display window opens, displaying a graph displaying the values of the selected attributes for this monitor. You can use the options available on this tab to manipulate the graph. For complete details, refer to BMC ProactiveNet User Guide on the BMC Support website. Viewing monitors for a device This section provides a brief overview of how to view the monitors for a selected device. For complete details, refer to BMC ProactiveNet User Guide on the BMC Support website. To view the Monitor types for a device In the BMC ProactiveNet Operations console, select the Navigation drawer. Select Global > Devices. Select the Grid view. All the monitored devices are displayed in table format. Select a device from the table. A hierarchical tree listing the monitors for that device is displayed. You can click the + and - to expand and collapse nodes of the hierarchical tree. The following information is displayed: Information Description Monitor Name Device name or process name, a device might appear more than once if it is monitored by several PATROL Agents Monitor Type Name of the monitor type. This will correspond to the element displayed in the Monitor Name column, specifying the type of device or process monitored Using BMC ProactiveNet Performance Management 52

53 Information Description Source Agent ProactiveNet server where the PATROL Agent and integration service are running Open Number of open alerts, a green globe is displayed if no alerts are open Closed Number of closed alerts Enabled Enabled if data is being collected Changing thresholds You can adjust the thresholds for the attributes of a monitor type either globally or for a specific device instance. In the BMC ProactiveNet Operations console, select the Navigation drawer Select Global > Devices. Select the Grid view. All the monitored devices are displayed in table format. Select a device from the table. Select a monitor. Select Tools > Thresholds. A menu containing the available thresholds is displayed. Global thresholds are applied to all monitor instances of the selected monitor ty pe. Instance thresholds are applied to the selected monitor instance. 6. Edit the Threshold settings 7. Click Apply. Managing Baselines and Key Performance Indicators In order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNet calculates baselines per attributes based on values collected over a specified period of time to determine a normal operating range. When the collected values for these attributes are out of range, an alert is triggered. Some attributes are identified by default as Key Performance Indicators (identitied with the therefore automatically included in the base lining calculation. icon) and 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 monitor s attributes and metrics over a specified time period and establishing a low baseline value (consisting of the 10th percentile of all the values for a given time period) and a high baseline value (consisting of the 90th percentile of all the values for a given time period), 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. Using BMC ProactiveNet Performance Management 53

54 Requirements for baseline generation For baselines to be generated for an attribute, that 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. A bsolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements. Managing Key Performance Indicators The KPI attribute of an attribute can be activated or deactivated manually through the BMC ProactiveNet Administration Console. In this KM, some attributes have been designated as important indicators of performance (KPIs). We do not recommend that these default settings are modified. However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet Administration Console. To add or remove Key Performance Indicator (KPI) attributes for a monitor type 1. In the Administration Console, from the menu bar, choose Tools > KPI Administration. The KPI Administration dialog box is displayed. 2. From the Monitor Type list, choose the monitor type for which you want to add or remove KPI attributes. A list of attributes for the selected monitor type is displayed. 3. In the KPI column for the attributes that you want to add or remove as Key Performance Indicators: select the KPI check box to add the corresponding attribute as a KPI deselect the KPI check box to remove the corresponding attribute from the KPIs for that monitor type For complete and detailed information on this procedure, please refer to the BMC Proactiv enet documentation av ailable from BMC W eb site. Using BMC ProactiveNet Performance Management 54

55 Reference Guide

56 This chapter provides statistical information about resources, operating status, and performances managed by the. It contains tables describing the attributes used in the KM, grouped by Monitor Types, and provides a brief description of each attribute and its default settings. Monitor Types ASP.Net Databases HTTP Availability Memory Performance Processes Sites Virtual Server Web Windows Event Log Windows Service Baselines and Key Performance Indicators Some attributes are identified by default as Key Performance Indicators (KPIs) and therefore automatically included in the base lining calculation. To learn more about auto baselining and KPIs, please refer to the "Managing Baselines and Key Performance Indicators" chapter. In this guide, attributes flagged as KPIs and included by default in the baseline calculation process are respectively identified by the following icon: 56

57 ASP.Net Attributes Name Description Units Default Alert Conditions BMC ProactiveNe t Attribute Type Worker Process Restarts* The number of times that the aspnet worker process restarted on the server computer. Restarts Warning = 1 Alarm = 2 Statistics * Parameters marked with an asterisk are used by default when v isualizing the corresponding monitor instance in BPPM. Databases Attributes Name Description Units Default Alert Conditions Availability* Displays the availability of the SharePoint Content Database {0= OK; 1 Warning = 1 = Alarm = 2 Degraded ; 2= Failed} Availability Size* Display the size of the SharePoint Content Database Gigabytes (GB) Statistics None BMC ProactiveNe t Attribute Type * Parameters marked with an asterisk are used by default when v isualizing the corresponding monitor instance in BPPM. 57

58 HTTP Availability Attributes Name Description Units Default Alert Conditions BMC ProactiveNe t Attribute Type Availability* Displays the availability of the SharePoint Virtual Site {0= OK; 1 Warning = 1 = Alarm = 2 Degraded ; 2= Failed} Availability HTTP Response Code Displays the response code of the current Virtual Site n/a n/a Statistics HTTP Response Time* Displays the response time of the current Virtual Site Seconds 15 to 30 = Warning Alarm > 30 Response Time * Parameters marked with an asterisk are used by default when v isualizing the corresponding monitor instance in BPPM. Memory Attributes Name Description Units Default Alert Conditions BMC ProactiveNe t Attribute Type Bytes In All Heaps* Displays the current memory allocated by all w3wp SharePoint processes for the GC Megabyte s (MB) None Statistics Large Object Heap Size Displays the current size of the Large Object Heap in bytes for all w3wp SharePoint processes Megabyte s (MB) None Statistics Percent Time In GC* Displays the percentage of time spent by all w3wp SharePoint processes performing the last GC Percentag None e (%) Statistics * Parameters marked with an asterisk are used by default when v isualizing the corresponding monitor instance in BPPM. HTTP Availability 58

59 Performance Attributes Name Description Units Default Alert Conditions BMC ProactiveNe t Attribute Type Current Connections* Number of current connections. Connectio ns None Statistics Current ISAPI Extension Requests Current ISAPI extension requests simultaneously being processed by the service. Requests None Statistics ISAPI Extension Requests PerSec The rate of ISAPI Extension requests that are simultaneously being processed by the Web service. Requests/ None s Statistics Received Bytes Per Second Number of bytes received per second by the Virtual Server Kilobytes/ s (KB/s) None Statistics Sent Bytes Per Second* Number of bytes sent per second by the Virtual Server Kilobytes/ s (KB/s) None Statistics For detailed information about B a se lining and K P I, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when v isualizing the corresponding monitor instance in BPPM. Processes Attributes Name Description Units Default Alert Conditions BMC ProactiveNe t Attribute Type Handle Count Displays the number of handles opened by the matching process(es). Handles None Statistics Percent Processor Time* Percentage of used processor time Percentag 90 to 100 % = e (%) Warning Statistics Private Bytes* Displays the processor time percent used by the matching process(es). Megabyte s (MB) None Statistics Working Set Displays the working set size of the matching process(es). Megabyte s (MB) None Statistics * Parameters marked with an asterisk are used by default when v isualizing the corresponding monitor instance in BPPM. Performance 59

60 Sites Attributes Name Description Units Default Alert Conditions BMC ProactiveNe t Attribute Type Availability Displays the availability of the SharePoint Virtual Site {0= OK; 1 Warning = 1 = Alarm = 2 Degraded ; 2= Failed} Availability Number Of Hits Displays the hits count for the current site collection Hits None Statistics Number Of Hits Per Minute* Displays the hits count per minute for the current site collection Hits/m None Statistics Size Displays the size of the current site collection Gigabytes (GB) None Statistics Time Since Last Hit Displays the elapsed time since last visit to the current site collection Days None Statistics * Parameters marked with an asterisk are used by default when v isualizing the corresponding monitor instance in BPPM. Virtual Server Attributes Name Description Units Default Alert Conditions BMC ProactiveNe t Attribute Type Availability* Displays the availability of the SharePoint Virtual Site {0= OK; 1 Warning = 1 = Alarm = 2 Degraded ; 2= Failed} Availability Number Of Registered Users Displays the number of users registered in the SharePoint default Site Collection Users None Statistics Number Of Sites Displays the number of site collections of the current web application Sites None Statistics Number Of SubSites Displays the number of subwebs of the current web application Sub-sites None Statistics * Parameters marked with an asterisk are used by default when v isualizing the corresponding monitor instance in BPPM. Sites 60

61 Web Attributes Name Description Units Default Alert Conditions BMC ProactiveNe t Attribute Type Time Since Last Access Displays the time elapsed since the last access occurred on the site. Days None Statistics Time Since Last Modification Displays the time elapsed since the last modification occurred on the site. Days None Statistics Windows Event Log Attributes Name Description Units Default Alert Conditions BMC ProactiveNe t Attribute Type Alarm Event Count* Number of triggered alarm events Events Alarm = 1 Statistics Warning Event Count* Number of triggered warning events Events Alarm = 1 Statistics * Parameters marked with an asterisk are used by default when v isualizing the corresponding monitor instance in BPPM. Web 61

62 Windows Service Attributes Name Description Units Default Alert Conditions BMC ProactiveNe t Attribute Type Current Connections* The number of active connections to all monitored virtual servers. Connectio ns None Statistics Received Bytes Per Second The number of bytes received by all monitored virtual servers each second Kilobytes/ s (KB/s) None Statistics Sent Bytes Per Second* The number of bytes sent by all monitored virtual servers each second Kilobytes/ s (KB/s) None Statistics For detailed information about B a se lining and K P I, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when v isualizing the corresponding monitor instance in BPPM. Windows Event Log 62

63 -B- Index Baselines -A Abnormalities Adapter 23 35, 53 Add 25, 31 BMC PATROL 25 Create 25 Update 31 Add Monitor Types 40 Attribute 51, 52 Attributes Alarm Event Count 61 Availability 60 Bytes In All Heaps 58 Current Connections 59, 62 Current ISAPI Extension Requests 59 Databases 57 Handle Count 59 HTTP Availability 58 HTTP Response Code 58 HTTP Response Time 58 ISAPI Extension Requests PerSec 59 Large Object Heap Size 58 Number Of Hits 60 Number Of Hits Per Minute 60 Number Of Registered Users 60 Number Of Sites 60 Number Of SubSites 60 Percent Processor Time 59 Percent Time In GC 58 Private Bytes 59 Received Bytes Per Second 59, 62 Sent Bytes Per Second 59, 62 Size 57, 60 Time Since Last Access 61 Time Since Last Hit 60 Time Since Last Modification 61 Warning Event Count 61 Worker Process Restarts 57 Working Set BMC ProactiveNet Performance Management 35, 53 Generation 35, 53 Manage 35, 53 Requirements 35, 53 BMC PATROL 31 BMC ProactiveNet Performance 32 BMC ProactiveNet Performance Management Abnormalities 35, 53 Baselines 35, 53 Key Performance Indicators KPI 35, 53 BPPM Data Collection 33 Business Value 10 -CComponent folders 48 Configuration Variables bypassw3svccheckin 43 defaultreinitializationoptions 43 disablemissingdevicedetection 43 disablepslexecutebugworkaround 43 excludesites 43 forceclassicconfigmode 43 maxfilesizeread 43 maxlocktimeout 43 pausedobjectlist 43 pscommand 43 removedobjectlist 43 startupdelay 43 ThresholdsManagementMode 43 Configuring monitor settings 40 thresholds 46 Creating the Installation Package -DData Collection BPPM Index 35,

64 Data Collection Verify 33 Debug Mode -K- enabling 42 Downloading 21 Downloading the Installation Package Keep 21 -E- Volume 40 Key Concepts 9 Key Performance Indicators BMC ProactiveNet Performance Management 35, 53 Manage 35, 53 Event KPI collectors 48 folders 48 Exclude Volume BMC ProactiveNet Performance Management 35, 53 Manage 35, 53 KPIs FFeatures 56 -M9 Manage -GGenerate Baselines 35, 53 Goals 9 Graphs 51, 52 -IImport 14 Importing 14 Information Closed 52 Enabled 52 Open 52 Source Agent Installation Baselines 35, 53 Key Performance Indicators 35, 53 KPI 35, 53 Manage Repository 14 Microsoft Office SharePoint Microsoft Office SharePoint Microsoft Office SharePoint Server Microsoft Office SharePoint Server Microsoft Windows SharePoint Services Microsoft Windows SharePoint Services Monitor name 52 type 52 Monitor Settings 52 configuring 40 Monitor Type 25 Monitor Types ASP.Net 56, 57 Availability 57, 58 Databases 56 HTTP Availability 56 Memory 56, 58 Performance 56, 59 Processes 56, 59 Sites 56, 60 Virtual Server 56, 60 Web 56, 61 Windows Event Log 56, 61 Windows Service 56, 62 configuring 38 Installation package creating 16 downloading 21 Installing 14, 21 Integration BMC ProactiveNet Performance Management 23 Integration Service Agent 25 Index 64

65 Monitoring Repository 16 -V - -N- Variables Navigation bypassw3svccheckin 43 defaultreinitializationoptions 43 disablemissingdevicedetection 43 disablepslexecutebugworkaround 43 excludesites 43 forceclassicconfigmode 43 maxfilesizeread 43 maxlocktimeout 43 pausedobjectlist 43 pscommand 43 removedobjectlist 43 startupdelay 43 ThresholdsManagementMode 43 Verify drawers 48 tree 48 -OOperations Console views Event 48 Grid 48 Title 48 Tree/Graph 48 -PPackage 16, 21 PATROL Configuration Manager Policies Manage 39 ProactiveNet 25 PW Commands 32 Data Collection Volume 12 Exclude 40 Keep 40 -W Windows Server RReference guide 56 Repository 14, 16 -SSingle solution 14 Supported Platforms 10 -TTags 12 Thresholds adding 46 configuring 46 Customize 32 editing 46 Import 32 modifications 53 recommended 46 Index

66 About BMC Software BMC Software, Inc. NYSE:BMC, is a leading provider of enterprise management solutions that empower companies to manage their IT infrastructure from a business perspective. Delivering Business Service Management, BMC Software solutions span enterprise systems, applications, databases, and service management. Founded in 1980, BMC Software has offices worldwide and fiscal 2004 revenues of more than $1.4 billion. For more information about BMC Software, visit About Sentry Software Sentry Software, a strategic Technology Alliance Partner of BMC Software, provides key monitoring solutions specifically designed to expand the capabilities of BMC Performance Manager, thus enabling up to 100% coverage of any infrastructure. Sentry Software specializes in single solutions for multiplatform monitoring of hardware, custom applications or any IT component, and blackout windows. Sentry Software products are deployed in 45 countries across the globe and lead the list of BMC Software s third-party product sales. For more information about Sentry Software, please visit