HP OO Community Guides HP OO 10.X - SiteScope Monitoring Templates As with any application continuous automated monitoring is key. Monitoring is important in order to quickly identify potential issues, be alerted immediately in case of a problem, and reduce the impact This document describes the HP Site Scope 11.x monitoring templates for HP Operations Orchestration 10.0x. Overview In order to get you started with using HP Site Scope (SiS) to monitor you HP Operations Orchestration (OO) installation(s) we have created a set of templates that provides a good basis and that should get you up and running quickly. The following diagram shows the various resources and tools we can use in order to achieve efficient monitoring: HP Operations Orchestration HP Operations Orchestration (HP OO) is a next generation IT Process Automation solution that is designed from the ground up to increase automation adoption whether in a traditional data center or hybrid cloud environment. OO 10 Community This guide is created for the OO community. To get started with HP OO 10 check out our community onboarding kit that contains three persona-based learning tracks for administrators, flow authors, and end users. Each track provides knowledge assets of the following types: Videos Tutorials Quick Guides Presentations
SiteScope HP SiteScope is an agentless monitoring solution designed to help you ensure the availability and performance of distributed IT infrastructure and applications including servers, operating systems, network devices, network services, virtualization software, applications, and application components. SiteScope continually monitors more than 100 types of IT components through a Web-based architecture that is lightweight, highly customizable, that does not require installing data collection agents on your production systems. SiteScope monitors collect key performance measurements and report topology on a wide range of back-end infrastructure components. The monitors are individually configured to automatically test performance and availability of systems and services in the network environment. SiteScope monitoring includes alerting and reporting capabilities, along with a dashboard for a real-time picture of the monitored environments. SiteScope can be configured to send alerts whenever it detects a problem in the IT infrastructure. In addition, SiteScope can create reports for monitors or monitor groups that display information about how the servers and applications you are monitoring have performed over time. To help you deploy monitors with similar monitoring configuration criteria across the enterprise, you can define templates, or use preconfigured SiteScope solution templates. The use of templates enables you to develop and maintain a standardized set of monitor types and configurations in a single structure that can be repeatedly deployed and easily updated using global change and replace capabilities, without having to update each object individually. SiteScope also includes alert template types that you can use to communicate and record event information in a variety of media. You can customize alert templates to meet the needs of your organization. Structuring Templates and Monitors A SiS template contains one remote server type that works with one and only one connection method e.g. and NetBIOS. Not all of the monitors in the OO 10 SiS templates support both methods, thus we divided the templates accordingly. However, after the deployment, you can organize your monitors into logical folders\groups as seen in the screenshot below:
Variables You can deploy all the templates together. The remote servers will be created during deployment. All the relevant connection data is stored in variables which you will need to populate as you can see in the following screenshot: Template variables are substitution markers for monitor configuration settings. You create template variables to represent monitor configuration settings that you want to be able to modify whenever you deploy the template. You reference the variable in a text box in one or more template monitors. Each variable that is referenced in a monitor or group object in a template prompts the display of a corresponding entry box when the template is deployed. The variable name is used as a label for the text entry box.
The following list details the variables we have created. Template: vcentrallogspath: Path to the Central Java Application logs. vcentralfqdn: Fully Qualified Domain Name of the Central vcentrallogin: OS Login Name (Server Name\User Name) vcentralpwd: Central OS User password Template: vcentralfqdn: Fully Qualified Domain Name of the Central vcentraljmxport: The port used by JMX on the Central vcentrallogin: OS Login Name (Server Name\User Name) vcentralpwd: Central OS User password vdbschemaname: OO Database Name. vdbserverfqdn: Fully Qualified Domain Name of the OO Database vdbserverport: OO DB Port Number vdbusername: OO DB User Name (Set a user with suitable read permissions). vdbuserpwd: OO DB User Password. vjmxlogin: JMX Server Login Name vjmxpwd: JMX Server Password Template: vraslogspath: UNC Path to the OO logs folder (e.g. \\my-server\logs) vrasfqdn: Fully Qualified Domain Name of the RAS vraslogin: Login Name for RAS Remote Server (RAS Server Name\Login Name) vraspwd: RAS Server Password Template: vrasfqdn: Fully Qualified Domain Name of the RAS vrasjmxport: The port used by JMX on the RAS vcentralurl: URL for the Central Server (used by REST monitors). vcentraluser: Central App User vcentralpwd: Central App Password vraslogin: Login Name for RAS Remote Server (RAS Server Name\Login Name) vraspwd: RAS Server Password vjmxlogin: JMX Server Login Name vjmxpwd: JMX Server Password Monitors SiteScope monitors are tools for automatically connecting to and querying different kinds of systems and applications used in enterprise business systems. The different monitor types provide the generic capabilities for performing actions specific to different systems. We used the following monitor types: Custom Database Monitor JMX Monitor
Log File Monitor Service Monitor CPU Monitor Dynamic Disk Space Monitor Memory Monitor URL Content Monitor Central Monitors Layer\Group Template Monitor Name Description Database MySQL Custom Monitor A custom database monitor. Currently returns the following metrics: Connections utilization in % Threads Connected Aborted Connections DB Size Average Row Lock Time in ms vcentralfqdn: Fully Qualified Domain Name of the Central vdbschemaname: OO Database Name. vdbserverfqdn: Fully Qualified Domain Name of the OO Database vdbserverport: OO DB Port Number vdbusername: OO DB User Name (Set a user with suitable read permissions). vdbuserpwd: OO DB User Password. JVM JVM JMX Central Returns standard Java Metrics vcentralfqdn: Fully Qualified Domain Name of the Central vcentraljmxport: The port used by JMX on the Central vjmxlogin: JMX Server Login Name vjmxpwd: JMX Server Password Logs Central Wrapper Log vcentrallogspath: Path to the Central Java Application logs. vcentralfqdn: Fully Qualified Domain Name of the Central Execution Log vcentrallogspath: Path to the Central Java Application logs. vcentralfqdn: Fully Qualified Domain Name of the Central
Layer\Group Template Monitor Name Description General Log vcentrallogspath: Path to the Central Java Application logs. vcentralfqdn: Fully Qualified Domain Name of the Central Server Log vcentrallogspath: Path to the Central Java Application logs. vcentralfqdn: Fully Qualified Domain Name of the Central OS Central Service Returns the Central windows service status vcentralfqdn: Fully Qualified Domain Name of the Central CPU Returns the Central server CPU usage vcentralfqdn: Fully Qualified Domain Name of the Central Disk Space Returns the Central server free disk space vcentralfqdn: Fully Qualified Domain Name of the Central Memory Returns the Central server Memory usage vcentralfqdn: Fully Qualified Domain Name of the Central * Define thresholds according to your environment and experience (Let the monitors run for a while and tune the thresholds according to your statistics). * All templates include the relevant remote server. During deployment you will be asked to populate the vcentralfqdn variable, which is used for setting the remote server. Site Scope Out-Of-The-Box DB Monitors Site Scope includes very rich solution templates for IT infrastructure components including MS-SQL Server 2008 and Oracle 11G. We added a custom database monitor for MySQL as explained above. The current release of the SiS templates for OO10 does not handle the H2 DB, or customized MS-SQL and Oracle databases. The following screenshot is taken from the SiS out-of-the-box SQL Server 2008 Template:
The following screenshot is taken from the Site Scope Oracle Template:
RAS Monitors Layer\Group Template Monitor Name Description Central-RAS communication Uses the OO REST API in order to get the RAS status vcentralurl: URL for the Central Server vcentraluser: Central User Name vcentralpwd: Central Password JVM JVM JMX RAS Returns standard Java Metrics vrasfqdn: Fully Qualified Domain Name of the RAS vrasjmxport: The port used by JMX on the RAS vjmxlogin: JMX Server Login Name vjmxpwd: JMX Server Password Logs RAS Wrapper Log vraslogspath: Path to the Ras Java Application logs. vrasfqdn: Fully Qualified Domain Name of the RAS Execution Log vraslogspath: Path to the Ras Java Application logs. vrasfqdn: Fully Qualified Domain Name of the RAS OS RAS Service Returns the RAS windows service status vrasfqdn: Fully Qualified Domain Name of the RAS CPU Returns the RAS server CPU usage vrasfqdn: Fully Qualified Domain Name of the RAS Disk Space Returns the RAS server free disk space vrasfqdn: Fully Qualified Domain Name of the RAS Memory Returns the RAS server Memory usage vrasfqdn: Fully Qualified Domain Name of the RAS * Define thresholds according to your environment and experience (Let the monitors run for a while and tune the thresholds according to your statistics). * All templates include the relevant remote server. During deployment you will be asked to populate the vrasfqdn variable, which is used for setting the remote server.
General Setup Instructions 1. Import the OO10 templates 2. Read the How to Configure SiteScope to Monitor a Remote Microsoft Windows Server section of the SiteScope Help 3. Copy the JDBC driver used for your DB Monitors to \<SiteScope Install Dir>\WEB-INF\lib Disclaimer In this version we only provide templates for Windows installations, but it is our goal to add Linux monitors in a future release of these SiS templates. Furthermore, we would like to improve the log monitors as well as more advanced checks. The monitors were developed and tested on windows 2008 R2 machines for both Central and RAS. The monitors were tested with one RAS machine only. Log monitors were added but with limited functionality. The templates were configured and tested using SiS version 11.22. As with all our community assets, these templates are provided as-is and they are not considered part of the supported OO application. For help and discussion please refer to the practitioner community forum: https://hpln.hp.com/node/21/og/forum/37 References SiS information and resources are available at: https://hpln.hp.com/group/sitescope Operation Orchestration information and resources are available at https://hpln.hp.com/group/operationsorchestration