Central Monitoring Administration (CMA) has been redesigned for BPPM 9.5. You will need to create new monitoring policies in BPPM 9.5. CMA sends configuration information to PATROL agents 9.5 through BPPM child server and BPPM integration service.
Each monitoring policy in CMA contains a name and a set of tags to match PATROL agents. A PATROL agent can contain one or more tags in its pconfig variables. When a tag contained in a PATROL agent matches a tag specified in a monitoring policy criteria, all configuration contained in the policy is pushed to the PATROL agent as pconfig variable values whenever PATROL agent is connected to CMA (such as when PATROL agent restarts) and whenever the monitoring policy changes in CMA.
To start creating CMA policies, login into CMA and open 'Policies' drawer under 'Navigation' bar at left. Open 'Monitoring Policy Configuration' window. Follow the order in the menu to input information to two mandatory configuration selections first: General and Agent Selection. You will be asked to input policy name, precedence number, and a set of tags to match PATROL agents.
Then you can input information to seven optional configuration selections: Monitoring Configuration, Filtering Configuration, Agent Threshold Configuration, Server Threshold Configuration, Agent Configuration, Server Configuration, and Configuration Variables. Monitoring configuration is categorized by monitoring solution (package name), version number, monitoring profile (KML name), and monitor type (KM name). If you have created your own custom KMs, you will need to import them to Central Monitoring Repository first before you can create monitoring configuration for your custom KMs.
Most of the policy creation process is self explanatory if you follow the GUI, but it is a fairly time consuming process. Because one policy can match multiple tags and one PATROL agent can contain multiple tags, it is recommended that you carefully plan a systematic way to name all your tags based on operating systems, applications, versions, environments, and locations before starting massive policy creation process.
Similar to the process of creating rule sets in PATROL Configuration Manager (PCM), decide on a few common denominators first such as base UNIX OS policy and base Oracle policy. Then build your policies in hierarchy such as base Windows OS policy, followed by production Windows OS policy, followed by base SQL Server policy, and followed by production SQL Server policy. A lower precedence number indicates a higher precedence.
No comments:
Post a Comment