bppm 9.5 monitoring configuration best practices 9.5 monitoring configuration best practices ......

© Copyright 4/14/2014 BMC Software, Inc 1 BMC Proprietary & Confidential

BPPM 9.5 Monitoring Configuration Best Practices

NOTE: Some locations do not support cell phones and require a land line.

Int'l Toll and US Cell Phone: 913-312-1392 US/CAN Toll free: 855-483-3538 LOCAL: Local - Australia, Brisbane: +61 (0) 7 3123 0047 Local - Australia, Canberra: +61 (0) 2 6111 2007 Local - Australia, Melbourne: +61 (0) 3 9034 3217 Local - Australia, Sydney: +61 (0) 2 9126 3023 Local - Austria, Vienna: +43 (0) 1 2675 904 Local - Bahrain, Manama: +973 1619 9040 Local - Belgium, Brussels: +32 (0) 2 303 2273 Local - Brazil, Sao Paolo: +55 11 3163 0461 Local - Bulgaria, Sofia: +359 (0) 2 491 6411 Local - Canada, Montreal: +1 514 669 6112 Local - Canada, Toronto: +1 647 426 9209 Local - China: +86 400 120 2693 Local - China: +86 400 120 2693 Local - Czech Republic, Prague: +420 234 147 003 Local - Denmark, Copenhagen: +45 78 78 79 63 Local - Estonia, Tallinn: +372 622 5742 Local - Finland, Helsinki: +358 (0) 9 7479 0101 Local - France, Lille: +33 (0) 359 69 03 42 Local - France, Lyon: +33 (0) 426 10 30 24 Local - France, Paris: +33 (0) 1 70 71 29 53 Local - Germany, Berlin: +49 (0) 30 2555 5430 Local - Germany, Frankfurt: +49 (0) 69 1200 9864 Local - Germany, Munich: +49 (0) 89 1436 7911 Local - Hong Kong, Hong Kong: +852 3008 0383 Local - Hungary, Budapest: +36 1 577 9957 Local - India, Bangalore: +91 (0) 80 6127 5134 Local - India, Mumbai: +91 (0) 22 6150 2334 Local - Ireland, Dublin: +353 (0) 1 437 0560 Local - Israel, Tel Aviv: +972 (0) 3 721 9373

Local - Italy, Milan: +39 02 9978 1800 Local - Italy, Rome: +39 06 8743 4377 Local - Japan, Tokyo: +81 (0) 3 4455 1996 Local - Latvia, Riga: +371 6601 3678 Local - Lithuania, Vilnius: +370 5205 5590 Local - Luxembourg, Luxembourg: +352 2786 0224 Local - Malaysia, Kuala Lumpur: +60 (0) 3 7724 0847 Local - Mexico, Mexico City: +52 55 4777 2663 Local - Netherlands, Amsterdam: +31 (0) 20 262 0137 Local - New Zealand, Auckland: +64 (0) 9 929 1884 Local - Norway, Oslo: +47 21 95 32 33 Local - Poland, Warsaw: +48 (0) 22 295 36 31 Local - Portugal, Lisbon: +351 21 120 9698 Local - Romania, Bucharest: +40 (0) 21 529 1340 Local - Russian Federation, Moscow: +7 495 620 9818 Local - Singapore, Singapore: +65 6416 9957 Local - Slovakia (Slovak Republic), Bratislava: +421 (0) 2 3278 6632 Local - Slovenia, Ljubljana: +386 (0) 1 888 8397 Local - South Africa, Johannesburg: +27 11 589 8382 Local - Spain, Madrid: +34 91 080 0153 Local - Sweden, Stockholm: +46 (0) 8 4030 4953 Local - Switzerland, Geneva: +41 (0) 22 555 0258 Local - Switzerland, Zurich: +41 (0) 44 556 8481 Local - Taiwan, Taipei: +886 (0) 2 2650 7292 Local - United Kingdom, London: +44 (0) 20 8150 0796

TOLL FREE: Int'l toll free - Argentina: 0800 666 2571 Int'l toll free - Australia: 1 800 635 764 Int'l toll free - Austria: 0800 295 994 Int'l toll free - Bahamas: 800 205 6295 Int'l toll free - Belgium: 0 800 72 785 Int'l toll free - Brazil: 0800 891 8445 Int'l toll free - Bulgaria: 00 800 115 1110 Int'l toll free - Chile: 123 0020 9601 Int'l toll free - China, Northern Region: 10 800 714 1853 Int'l toll free - China, Southern Region: 10 800 140 1378 Int'l toll free - Colombia: 01 800 518 0504 Int'l toll free - Czech Republic: 800 142 277 Int'l toll free - Denmark: 8088-6980 Int'l toll free - Dominican Republic: 1 888 751 4437 Int'l toll free - France: 0 800 914 669 Int'l toll free - Germany: 0 800 182 4414 Int'l toll free - Greece: 00 800 161 2205 1068 Int'l toll free - Hong Kong: 800 908 710 Int'l toll free - Hungary: 06 800 184 72 Int'l toll free - India: 000 800 100 7363 Int'l toll free - Indonesia: 001 803 011 2660 Int'l toll free - Ireland: 1 800 760 204 Int'l toll free - Israel: 1 80 945 2068 Int'l toll free - Italy: 800 873 593 Int'l toll free - Japan: 00531 12 0058 Int'l toll free - Korea, Republic Of: 00798 14 800 4574 Int'l toll free - Latvia: 800 03 656 Int'l toll free - Lithuania: 88 003 0200 Int'l toll free - Luxembourg: 800 25 164 Int'l toll free - Malaysia: 1 800 812 644 Int'l toll free - Mexico: 001 800 514 1058 Int'l toll free - Monaco: 800 93 304

Int'l toll free - Netherlands: 0 800 024 9645 Int'l toll free - New Zealand: 0 800 440 611 Int'l toll free - Norway: 800 191 83 Int'l toll free - Panama: 00 800 226 7179 Int'l toll free - Peru: 0800 55 444 Int'l toll free - Philippines: 1 800 111 00400 Int'l toll free - Poland: 00 800 112 41 37 Int'l toll free - Portugal: 800 819 382 Int'l toll free - Russian Federation: 810 800 2544 1012 Int'l toll free - Singapore, Singapore: 800 101 1738 Int'l toll free - Slovakia: 0800 606 314 Int'l toll free - Slovenia: 0 800 80815 Int'l toll free - South Africa: 0 800 999 562 Int'l toll free - South Korea, Korea, Republic Of: 003 0813 1654 Int'l toll free - Spain: 900 941 991 Int'l toll free - Sweden: 02 079 3671 Int'l toll free - Switzerland: 0 800 896 853 Int'l toll free - Taiwan: 00 801 126 826 Int'l toll free - Thailand: 001 800 12 066 3284 Int'l toll free - Trinidad and Tobago: 800 205 7179 Int'l toll free - United Arab Emirates: 800 017 7175 Int'l toll free - United Kingdom: 0 800 051 7166 Int'l toll free - Uruguay: 000413 598 2551 Int'l toll free - Venezuela: 0 800 100 2525

Participant passcode: 597271

Participant passcode: 597271

BMC Proprietary & Confidential

BPPM 9.5 Best Practice Monitoring Configuration


Overview

First Level Training - Basic Deployment Knowledge Best Practice vs. How To Covers Core BPPM Components Does not address every scenario Prior knowledge of BPPM components and terms


Agenda

Prerequisites & CMA Navigation Configuration Process Workflow CMA Repository Adding Integration Services in CMA Global Thresholds Controlling Policy Application Staging Policies Monitoring Policies Timeframes & Blackouts Policy Export/Import General Recommendations & Tips

Presenter

Presentation Notes


Prerequisites

Complete a scalability assessment Complete an implementation architecture design Decide if agents are going to be policy managed or not policy managed

- Non-Policy Managed Agents iSeries (AS400) Open VMS Custom Knowledge Modules that are not 9.5 compliant Older operating systems such as Microsoft Windows 2000 Knowledge Modules not yet 9.5 compliant

Link to list of 9.5 compliant KMs. https://docs.bmc.com/docs/display/public/proactivenet95/List+of+Monitoring+Solutions+and+KMs+in+BMC+P

roactiveNet+Performance+Management - Compliant & Non-Compliant KMs

Install and configure BPPM server(s) and IS nodes - High Availability - Heap settings, etc.

Establish a naming convention scheme for all configurations Establish a policy precedence scheme

https://docs.bmc.com/docs/display/public/proactivenet95/List+of+Monitoring+Solutions+and+KMs+in+BMC+ProactiveNet+Performance+Management

https://docs.bmc.com/docs/display/public/proactivenet95/List+of+Monitoring+Solutions+and+KMs+in+BMC+ProactiveNet+Performance+Management


CMA Navigation

Policies - Monitoring - Blackout - Staging

Servers - Integration Services & Status - BPPM Servers & Status - Agent Status - Agent Query, Policy Managed, Agent Delete

Repository - Manage Repository - Deployable Package Repository - Integration Services - Administration Console

General - Clusters & Timeframes

Global Thresholds - BPPM Server Global Thresholds


CMA Navigation

Implement in the recommended process order Two configuration data categories - These are not labels in the product

- BPPM Solution Infrastructure Configuration PATROL Agent to Integration Service connections PATROL Agent Tags How PATROL Agents forward events PATROL Agent History Retention

- Monitoring Configuration Knowledge Modules that are loaded in the PATROL Agents for monitoring. Data collection and event propagation filtering Data collection frequencies Thresholds

- Do not mix Monitoring and Infrastructure configuration in the same policy. - Managed these different types of configuration in separate policies.


Configuration Process Workflow


Configuration Process

Plan, understand, and document the process

Create, test and validate before moving to production

Do not edit in production unless you find a problem in production that requires editing

When you enable policies in production you “go live” in production - Applies to policy managed agents - Backing out before then is easy - Backing out afterwards can be difficult depending on the situation

Start with a small number of agents in production to minimize risk

Avoid massive unintended data collection into the BPPM server due to poor policy configuration


CMA Repository

Manage Repository - Contains install packages from BMC - Base Repository - Extended Repository - Imported single solutions

- Do not import Base or Extended repositories for older BPPM server

versions (9.0) - Do not import the BPPM 9.5 Base or Extended repositories into

older BPPM server versions (9.0)

- Import the repository version for the matching BPPM server version only.

Deployable Package Repository


CMA Repository

Deployable Package Repository - Contains install packages that you create

- Define a standard and provide meaningful names Example Purpose: Basic RedHat Linux OS monitoring Example Name: RHELOSBasic

- Enter complete descriptions in every package

- Consider how polices will be assigned to agents carefully Plan and define agent tagging Assign tags in the deployable packages you create Create enough packages to cover the necessary combinations

of tags you need Leverage the ability to edit and save packages with a new

package name as a way to copy packages – Reduces work – Ensures consistency


Deployable Package Repository – Agent Tagging



Plan, define and follow a standard tagging scheme

Configure the tags in the deployable install packages

Configure appropriate matching tag values in the Agent Criteria of policies

Example environment to be monitored - Oracle databases running on RHEL 6.4 - SQL Server databases running on Windows 2008 R2 - Apache running on Windows 2008 R2 and RHEL 6.4 - WebLogic running on Windows 2008 R2 and RHEL 6.4



Example Packages with tags… Package Name: OracleRHEL Contains: Linux Agent, Linux OS KM Tags: LinuxOS, OracleDB Package Name: SQLWin Contains: Windows Agent, Windows OS KM Tags: WinOS, SQLDB Package Name: ApacheWin Contains: Windows Agent, Windows OS KM Tags: WinOS, Apache Package Name: ApacheRHEL Contains: Linux Agent, Linux OS KM Tags: LinuxOS, Apache Package Name: WebLogicWin Contains: Windows Agent, Windows OS KM Tags: WinOS, WebLogic

Package Name: WebLogicRHEL Contains: Linux Agent, Linux OS KM Tags: LinuxOS, WebLogic Package Name: Oracle Contains: Oracle DB KM Tags: n/a Package Name: SQLServer Contains: SQL Server DB KM Tags: n/a Package Name: Apache Contains: ISM KM Tags: n/a Package Name: WebLogic Contains: WebLogic KM Tags: n/a


Deployable Package Repository

Define and follow standards for installation settings - Examples Installation directory on RHEL: /opt/bmc Agent User ID/password: Patr0L123 / password Agent Port: 3181

Use default settings as much as possible Do not specify Integration Services used for data collection in the deployable

packages. Leverage Staging Integration Services instead.


Adding integration Services in CMA

Add all Integration Service nodes through CMA Provide a meaningful name for each Integration Service node

- Example: Include Domain Name as part of the name

Avoid using the BMC ProactiveNet Server connected to the Integration Server option Avoid creating clusters in CMA as part of the process (New button)


Clusters

Use meaningful names for clusters Put the most impactful information at the beginning of the Cluster name Provide complete and detailed descriptions for the Clusters Clusters should be added only after all Integration Service nodes have been added to

CMA - Avoid creating clusters in CMA as part of the process where you add Integration

Service nodes to CMA. Do not try to add more than four Integration Service nodes to a cluster. Avoid adding Integration Service nodes while creating clusters. Recommended order - Install Integration Service nodes - Add Integration Service nodes to CMA - Create Cluster(s) - Create Staging Policy that will connect PATROL Agents to the cluster(s)


Global Thresholds

Global Thresholds apply in the BPPM server(s) not on PATROL Agents Enter Global Thresholds for KPIs and performance parameters Enter before you create Monitoring policies


Controlling Policy Application

Agent Criteria Recommended Primary Options - Tags - Agent host OS type - Hostnames - Agent IP Addresses - BPPM Server - Integration Service host

Controlling Policies across multiple BPPM Servers - Assumes the BPPM Servers share a common CMA instance - Use the following Agent Criteria options in the policies BPPM Server Integration Service host



Policy Managed Setting - This is a PATROL Agent configuration variable

/AgentSetup/integration/denyCfg = <false or true>

- If false the agent will be policy managed in CMA - If true the agent will NOT be policy managed in CMA - If the agent is policy managed, non-policy rules that conflict with policy based rules will be

ignored

- Decide if agents will be primarily policy configured or not

- Agents that cannot be policy managed should have this value set to false Examples

– Older agents that are not 9.5 compliant – KMs that are not 9.5 compliant

- Do not toggle this setting in production This could result in massive unintended data collection



Allow large domain collection like vSphere discovery to complete before review in the BPPM console Enable different policies in a controlled manner Do not enable policies until they have been tested and validated in

development and test environments Do not mix policy based and non-policy based configuration for one

Knowledge Module application class


Controlling Policy Application - Precedence

Policy Precedence - A lower precedence number indicates a higher precedence Number 1 will override number 5

- Precedence evaluation and conflict resolution is applied at the application class and monitor

type level Evaluation is not limited at the entire policy level

- Configuration settings within multiple policies that do not conflict are not overridden

- If the precedence number between two policies is the same, the conflicting configuration

from the most recently created policy overrides conflicting configuration from the policies created earlier.

- Precedence is not evaluated at the monitored instance level


Controlling Policy Application - Precedence

Range Monitored Technology Additional Details 1 - 10 Staging Policies Contains settings for data collection Integration Service nodes 11 - 99 Blackout Policies Contains settings for agent blackout periods based on specific time frames 100 - 199 Agent Configuration Contains settings such as agent user ID/password, agent tag, history retention, etc 200 – 210 Windows Operating System

Basic Configuration for Microsoft Windows operating system monitoring that covers basic settings and applies as a standard to most or all Windows servers

211 – 219 Windows Clusters Configuration for Microsoft Windows Cluster monitoring 220 – 229 Active Directory Configuration for monitoring Microsoft Active Directory 230 – 239 MS SQL Server Configuration for monitoring Microsoft SQL Server 240 – 249 SharePoint Configuration for monitoring Microsoft SharePoint 250 –259 Exchange Configuration for monitoring Microsoft Exchange 260 – 269 Microsoft DNS Configuration for monitoring Microsoft DNS servers 270 – 279 Microsoft DHCP Configuration for monitoring Microsoft DHCP servers 280 – 289 IIS Configuration for monitoring Microsoft IIS servers 290 – 299 Windows Operating System

Nonstandard Configuration for Microsoft Windows operating system monitoring that covers nonstandard configurations

300 – 329 Linux Operating System Basic Configuration for Linux operating system monitoring that covers basic settings and applies as a standard to most or all Linux servers

330 – 349 Linux Operating System Nonstandard

Configuration for Linux operating system monitoring that covers nonstandard configurations

350 – 369 Unix Operating System Basic Configuration for Linux operating system monitoring that covers basic settings and applies as a standard to most or all Linux servers

370 – 389 Unix Operating System Nonstandard

Configuration for Linux operating system monitoring that covers nonstandard configurations

390 – 399 Currently Not Used 400 – 449 Oracle Databases Configuration for monitoring Oracle Databases 450 – 499 Oracle Applications Configuration for monitoring Oracle Applications 500 – 549 Apache Configuration for monitoring Apache web servers


Staging Policies

Use Staging policies to assign agents to data collection Integration Service nodes

Avoid using the Agent Configuration settings in Monitoring policies to control Integration Service node configuration for agents

A Staging policy should always assign PATROL Agents to an Integration Service that processes performance data and events

Leverage the ability to control which agents Staging policies are assigned to based on BPPM Server instances and/or tags

Note the following regarding Staging policies - Staging policies/services will not "Activate" any non-staging or Monitoring polices - Agents will not forward data or events to the BPPM Server while connected to a "Staging"

Integration Service.


Monitoring Policies - General Information

Plan, define and use a standard naming scheme Enter complete descriptions in every policy description field - Put the most important information at the beginning of the description

Policies should be disabled until they have been tested and validated for production Follow the precedence scheme and observe all precedence rules

Policy Name Policy Purpose WinBasicOS Basic monitoring for Microsoft Windows operating systems that will apply to all

Microsoft Windows servers. RHELBasicOS Basic monitoring for RedHat operating systems that will apply to all RedHat

servers. OracleDBstd Monitoring for Oracle databases that will apply to all Oracle databases. SQLServerDBstd Monitoring for SQL Server databases that will apply to all SQL Server databases. Apachestd Monitoring for Apache that will apply to all Apache instances. WebLogicstd Monitoring for WebLogic that will apply to all WebLogic instances. WinDNSstd Windows DSN Server monitoring WinDHCPstd Windows DHCP Server monitoring


Monitoring Policies - Monitoring Configuration

Configure Monitoring policies to define - Which Knowledge Modules and Knowledge Module application classes will be activated on

agents - Agent resident thresholds - Service resident Instance level thresholds - PATROL Application class or monitoring type polling frequencies

By default an agent will monitoring nothing and no data will be sent to the BPPM

Server from the agent until it receives a policy - Assumes the following The agent is versions 9.5 Policy Managed Setting

– /AgentSetup/integration/denyCgf has not been set to true

Enter Monitoring Configuration settings for one type of managed technology per policy

- Windows Operating Systems - SQL Server Databases - Etc



Navigation Tip – Add all instances to a list of

monitored instances before you click the Add to list button for the Host Configuration

If you do not do this the result may be confusing



Navigation Tip – When editing a list of existing

monitored instances, select the Host Configuration to edit first.

If you do not select the Host Configuration first your changes will not be saved.


Monitoring Policies - Filtering

Send events only for availability type parameters - Service Status - Process Status - Log file errors - Collector Status

Send data only for important performance parameters - KPI parameters - Parameters required in BPPM performance reporting - Parameters requiring “duration” thresholds - Parameters requiring “time of day” type thresholds - Parameters where predictive alarming and abnormality detection is needed.

Do not send both trended performance data and events for the same parameter to the BPPM Server

NOTE: If you filter a parameter after it has been streamed you will not be able to see data from PATROL for the parameter. Filter first if you are not sure. Stream later if needed.


Monitoring Policies - Agent Thresholds

Set agent thresholds for availability and Boolean type parameters - Windows Service status - Process up/down monitoring - Monitoring for error messages and strings in log files - Windows Event Log monitoring - Database Listener Status

Define agent threshold settings in policies that also contain monitoring configuration for the same monitor types so that the all settings specific to a monitor type are configured in the same policy Do not set agent thresholds for performance oriented KPI parameters or any

other parameters that will have trended data stored in the BPPM Server database

- Set Server or Global thresholds for this Do not mix threshold settings for parameters that are not also configured for

monitoring in the same policy. - The same applies to filtering and all other monitor type specific criteria - Keep all monitor type specific criteria in the same policy


Monitoring Policies – Server Thresholds

Set server thresholds for performance oriented KPI parameters and any other parameters that will have trended data stored in the BPPM Server database

- Examples include URL Response Time Application Response Time as reported from BMC EUEM or BMC TMART CPU Utilizations Disk Drive Free Space Queue Depth Memory Utilization Database Table Space Extents Left Heap Space Free

Define server threshold settings in policies that also contain monitoring configuration for the same monitor types so that the all settings specific to a monitor type are configured in the same policy. Do not set server thresholds for availability or Boolean oriented parameters or

any other parameters that will have events generated for them by the PATROL Agents


Monitoring Policies – Agent Configuration

Configure the settings shown in policies separate from policies that contain monitoring criteria


Monitoring Policies – Agent Configuration

Reduce polling frequencies if higher frequencies are not needed - Many PATROL parameters poll at a one minute interval

Define polling interval settings in policies that also contain monitoring

configuration for the same monitor types so that the all settings specific to a monitor type are configured in the same policy. Do not define tags under Agent Configuration - Define tags in the deployable packages

Do not define Integration Services under Agent Configuration - Use Staging policies


Monitoring Policies – Server Configuration

Do not use the automated group creation functionality excessively

- Avoid excessive/unnecessary quantities of groups

Plan the groups you need

appropriately and configure accordingly Use the copy baseline feature

only when you know the existing baseline is appropriate seed data for a new agent/device

- Example: Servers in an Apache web server group behind a load balancer


Monitoring Policies – Configuration Variables

If there is a policy setting available for a configuration use the policy

and avoid importing old configuration from PCM where it is not needed Do not try to manually convert policy data from the old format or from

PCM to the new format Do not try to import large rule sets from PCM - Large imports will fail - If you are not going to use polices for a KM or managed node then

use PCM and the PATROL console

NOTE: The preloaded Knowledge Module list is automatically populated with Knowledge Modules that you create policies for.


Timeframes

Avoid creating overlapping Timeframes

Do not create unnecessary Timeframes that will not be used

Establish a meaningful standard for naming Timeframes Provide a complete description for each Timeframes and put the most impactful

information at the beginning of the description


Timeframes

Configuration tip –

Timeframes that “span” midnight require the “duration” setting

Example: Saturday 6:00 PM to Sunday 6:00 AM


Blackouts

Establish a standard and provide meaningful names for Blackout policies Provide a complete description for each Blackout policy and put the

most impactful information at the beginning of the description Follow the recommendations for precedence values Avoid creating Timeframes as part of the Blackout policy creation

process Do not create overlapping Blackout Policies

NOTES: - The timeframe for Blackout policies is applied according to the PATROL

Agent local time - Leverage Blackout configuration in event management for KMs that do not

support Blackout policies


Policy Export/Import

Policy Export/Import allows you to move policies from one CMA instance to another You can Export/Import from/to the same CMA instance to copy a policy You can rename a policy in the exported data as part of the export process - Useful for creating copies that will be edited to make new policies - Do not rename if you are not making a copy to edit

Policies are disabled in the exported data so that they are disabled when imported Only Monitoring and Blackout policies and Timeframes will be exported and imported Integration Service and/or Cluster configuration details entered in the Agent

Configuration section of Monitoring Policies are not included Policies based on KMs that are not in the target CMA repository will not be imported Staging Policies and Clusters are not included You should treat names as case sensitive



A file is created for each policy and Timeframe that is exported - Monitoring Policies: <policy name>.mo - Monitoring Policies: <policy name>.bo - Timeframes: <timeframe name>.tf



Follow the same policy naming standards you established for the environment and use in the CMA UI when you rename policies during an export to make copies Leverage the export/import utility to move policies between development, test,

and production CMA instances when these environments do not share a common CMA instance Maintain the same policy names between development, test, and production

CMA instances Do not try to export and import a policy to make a copy without renaming the

policy when you export it. Do not rename policies when you use the export/import utility to move policies

from test to production


General Recommendations & Tips

There is no merge for agent rules in CMA The Patrol agents version 9.5 default setting for loadPnlyPreloadedKMs is “Yes”. If you load a

Knowledge Module that is not in the preloaded list with a patrol console, the console will show that the Knowledge Module is disabled. 9.5 PATROL Agents supports "customer overlay" configuration files in the "lib" directory to

manage alterations to the “config.default” settings. - The files are named “<name>.current” where “<name>” is whatever file name desired. - Any ".current" configuration files that exist in the lib directory are read after config.default

and before the pconfg DB is read.



Use caution with policies. They can have global impact Non policy managed Knowledge Modules must be included in the

preloaded Knowledge Module list manually outside CMA Ensure that "load only preloaded KMs" is set to true on all agents

before adding the agents to BPPM. Do not propagate all agent disconnected events to IBRSD Do not enable policies for production agents until tested Do not do change marked for delete timing for CMA BPPM Servers that

are also used for trending, etc, in production



Configuration for event integration and monitoring for Availability parameters first. Set marked for delete in CMA Central BPPM Servers to 30 minutes to deal with

agents that are temporarily in the BPPM Server. Use the default setting of KPI mode for the BPPM Server. Use the most descriptive names available when defining instances to monitor.

- Example: leverage the “Display name” for monitoring Windows Services instead of the “Service name”.

Do not increase the PATROL Agent buffer setting WARNING: Do not delete and/or disable policies in production without considering

consequences. - All corresponding instances on related managed nodes will be marked for

deletion - Could result in MASSIVE unintended data collection - Do the following:

Create a new policy with a lower precedence number that will override the older policy. After you have tested, validated and enabled the new policy in production delete the old

policy.


Additional Resources & Information

Online Documentation - BPPM 9.5 Best Practices

https://communities.bmc.com/docs/DOC-28658 - BPPM 9.5 Product Documentation

https://docs.bmc.com/docs/display/public/proactivenet95/Home

BMC Communities (public forum) - BMC website documents discussions whitepapers additional information

- https://communities.bmc.com/communities/community/bmcdn/service_assurance - Recording of today’s presentation and content https://communities.bmc.com/docs/DOC-28658 Follow/Subscribe to the page to be notified about updates

https://communities.bmc.com/docs/DOC-28658

https://docs.bmc.com/docs/display/public/proactivenet95/Home

https://communities.bmc.com/communities/community/bmcdn/service_assurance

https://communities.bmc.com/docs/DOC-28658

bppm 9.5 monitoring configuration best practices 9.5 monitoring configuration best practices ......

Documents