Moviri Integrator for BMC Helix Capacity Optimization - HP SiteScope
“Moviri Integrator for BMC Helix Continuous Optimization – HP SiteScope” allows extracting information from HP SiteScope monitoring tool, transferring monitored servers performance and configuration data relevant for capacity management purposes. HP SiteScope from version 10.12 (and following minor releases) to version 11.00 (and following minor releases) Moviri Integrator for HP SiteScope supports SiteScope instances configured to export data to an external database. See next section for information about the supported DBMS technologies. HP SiteScope includes SOAP-based API to manage the configuration of the monitored environment. Access to this API is required too. Moviri Integrator for BMC Helix Continuous Optimization – HP SiteScope supports the following DBMS technologies as HP SiteScope export DB: As a first step, please ensure that the correct version of SiteScope is installed. You can perform this check from the “Help” section of the SiteScope Console: In order to enable the external database logging, you have to set up and configure a DBMS. Create a schema and a user with all privileges on it for reading and writing monitoring data. To configure your SiteScope instance for external database logging, please ensure the following requirements are respected: Make sure you have a SiteScope login with necessary privileges to access Infrastructure Preferences inside your SiteScope instance. To perform the configuration for external database logging, follow these steps: Set them as follows: _accessControlled=true _logJdbcAutoCommitSiteScopeLog=1 _logJdbcCreateSiteScopeLog=CREATE TABLE SiteScopeLog (datex VARCHAR(255), serverName VARCHAR(255), class VARCHAR(255), sample VARCHAR(255), category VARCHAR(255), groupName VARCHAR(255), monitorName VARCHAR(255), status VARCHAR(255), monitorID VARCHAR(255), value1 VARCHAR(255), value2 VARCHAR(255), value3 VARCHAR(255), value4 VARCHAR(255), value5 VARCHAR(255), value6 VARCHAR(255), value7 VARCHAR(255), value8 VARCHAR(255), value9 VARCHAR(255), value10 VARCHAR(255)) If you have a monitor which performs more than 10 measurements and you want to store them in your database, you will need to add the exceeding columns to the query. For example, if you have a monitor with the following measurements in your SiteScope console: You can read the number of counters (therefore measurements in the database) active and add the exceeding number of columns to the query: _logJdbcCreateSiteScopeLog=CREATE TABLE SiteScopeLog (datex VARCHAR(255), serverName VARCHAR(255), class VARCHAR(255), sample VARCHAR(255), category VARCHAR(255), groupName VARCHAR(255), monitorName VARCHAR(255), status VARCHAR(255), monitorID VARCHAR(255), value1 VARCHAR(255), value2 VARCHAR(255), value3 VARCHAR(255), value4 VARCHAR(255), value5 VARCHAR(255), value6 VARCHAR(255), value7 VARCHAR(255), value8 VARCHAR(255), value9 VARCHAR(255), value10 VARCHAR(255), value11 VARCHAR(255), value12 VARCHAR(255), value13 VARCHAR(255), value14 VARCHAR(255), value15 VARCHAR(255)) _logJdbcInsertSiteScopeLog=INSERT INTO SiteScopeLog VALUES(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) 9 standard columns 10 counters measurements with 19 parameters, the first 9 for standard columns from datex to monitorID and the other 10 for counters. If you increased the number of columns to store data, you will have to add the correct number of “?”. In the previous example, 9 standard columns + 15 counters produces 24 columns to be filled by the insert query. Therefore other 5 “?” will be added: _logJdbcInsertSiteScopeLog=INSERT INTO SiteScopeLog VALUES(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) 9 standard columns 15 counters measurements _logJdbcDriverSiteScopeLog=com.mysql.jdbc.Driver _logJdbcURLSiteScopeLog=jdbc:mysql://<server_address>:<server_port>/<database> _logJdbcUserSiteScopeLog=<mysql_user> _logJdbcPasswordSiteScopeLog=<mysql_password> Instructions have been provided for the MySQL case. The Oracle case is omitted since it comprises the same steps with similar values. Please refer to HP SiteScope documentation for further reference. Some important considerations Notice that the order of counters reported into the log table columns doesn’t correspond to the one showed in the “Dashboard” panel of SiteScope Console. The association order between counters and columns represents their selection order during the creation of the monitor and is reported in the “Properties” panel. For the previous example, after the default “counters in error” column, the other columns are associated with the counters as shown in the following figure: There are three sections (tabs) in the ETL run configuration page where the behaviour of “Moviri Integrator for BMC Helix Continuous Optimization - HP SiteScope” can be specified: In order to set the ETL configuration that match your needs, in this paragraph some common use cases are presented. Scenario 1: “Typical” systems capacity analysis and planning Scenario 2: “in-depth” capacity analysis and planning for specific systems The choice of correct configuration brings you benefits also in terms of shorter execution time and saved disk space on database. Every SiteScope ETL instance configuration applies to all systems selected, if there are different scenario needs for different systems, is recommended to create many ETL instances with different configuration which filters on particular systems (e.g. There are both a big and stable environment (scenario 1) and the introduction of a new service (Scenario2)) The following table is a reference to estimate the data extraction volume produced by the HP SiteScope connector as a function of the number of extracted days. The results presented above assume the following connector configuration (as per metric filters specified in Scenario 1): Under these assumptions, the estimated number of daily rows extracted by the connector, as a function of the number of servers, is presented below . In order to perform a historical recovery of data, please use “recovery mode properties” settings: If the ETL is newly created and has no last counter defined, the “default last counter” is used. The pre-condition for an historical extraction is the presence of data inside the external database in the selected time period. In order to communicate with Web Services with SSL protocol over HTTP (HTTPS) you must configure SiteScope to use SSL. Below an example of accessing SiteScope by HTTPS protocol. To properly configure the ETL, you need to enable the SSL authentication property in SiteScope – Settings tab and specify correctly the IP of the host where SiteScope is installed and the port with SSL (8443 in the following example). For all metrics imported by the ETL and described below in this section, the following apply: Supported BMC Helix Continuous Optimization Entity Type: System (Generic) For ETL troubleshooting, please refer to official BMC documentation available here. The SiteScope ETL connects to SiteScope and reads from external database monitors measurements performed on systems remotely. In the following table the supported metrics for OS families and the related SiteScope monitors and objects are reported. This is a list of configuration metrics extracted by SiteScope ETL. In addition to the metrics available from the data source, the following metrics are computed by the connector: The SiteScope ETL can compute a derived metric obtained by 2 source metrics only if they are included in the same monitor, i.e. they will be stored in the same raw inside the external database. For example if you want to include the SWAP_SPACE_UTIL metric for a Solaris system, you will need to instantiate a UNIX Resources Monitor which includes both the swap_resv and the swap_avail metrics related to the Memory object: All of the metrics managed by the connector are grouped in the following “Metric Classes” The following table shows for each metric class the contained metrics The SiteScope ETL can be configured to collect only specific metric classes by configuring the related custom properties. SiteScope can measure server performance metrics with two distinct categories of monitors: This leads to some metrics measured by both generic and OS specific monitors with the consequence of repeating or overlapping those measurements. In order to avoid the overwrite of common metrics measurements, the connector implements a mechanism of precedence for which, if both OS specific and generic monitors are monitoring the same metric for the same server, the OS specific monitor will have precedence over the generic one and only its measurements will be imported. Be aware of what follows: The ETL filters measurements only in case two monitors with overlapping metrics collect data for the same system The ETL will not make distinction on the sub-resource monitored, only on the monitor metrics and the host monitored. For example, following the table 10, if both the Dynamic Disk Space Monitor and the Microsoft Windows Resources Monitor collect the metric BYLDISK_UTIL for the host 10.31.168.156 and the sub-resource “C:”, only the measurement performed by the Microsoft Windows Resource Monitor will be imported. Besides if the Dynamic Disk Space Monitor collects metrics on a “D:” sub-resource, also this will not be imported, even if the Microsoft Windows Resource Monitor is not making measurements on it (i.e. the mechanism doesn’t distinguish any sub resource, only checks for monitor, host and metric). In the example, to monitor the “C:” and “D:” sub resources you can use a Dynamic Disk Space Monitor alone, which collects data on both logical disks, or a Microsoft Windows Resource Monitor on both “C:” and “D:”. Below the list of overlapped metrics: Moviri Integrator for BMC Helix Continuous Optimization connector uses standard BMC Helix Continuous Optimization ETL lookup mechanism. One single entry is used as entity identifier : Lookup field = “DEFAULT”. Through Object-Relationship panel in the ETL edit run configuration, the ETL arranges the collected systems under a domain of choice. When the “Recreate SiteScope hierarchy” option is set to true (see Section 5.1.3), the connector builds the hierarchy of groups and systems of SiteScope inside CO. The groups of SiteScope are inserted under the root domain and mapped with corresponding BMC Helix Continuous Optimization domains; the monitors instantiated into SiteScope are associated to the related systems which will be put under the respective domains. In the example below, each group under “Capacity” contains monitors associated to only one server, resulting in the following tree: The correspondent structure in HP SiteScope is showed here: Otherwise, if the “Recreate SiteScope hierarchy” option is set to false, all the systems related to SiteScope monitors will be inserted directly under the root domain (in the example below is called “Flat domain”). BMC Helix Continuous Optimization automatically creates a hierarchy rule associated to the ETL to process the Object-Relationship data. Requirements
Supported versions of data source softwareSupported configurations of data source software
Supported DBMS technology for integration
Datasource Check and Configuration
Preparing to connect to datasource software
Set up the DBMS for external logging
Preliminary SiteScope checks
Configuring SiteScope for external database logging
This leads to other 3 important points you should consider when activating database logging:Connector configuration
Connector configuration attributes
SiteScope - Settings
SiteScope - Data Selection
Guidelines to choose the most appropriate ETL configuration
Data volume considerations
Historical data extraction
Recovery mode active=true and filling the two properties “since date” and “to date” in order to specify the time window. When recovery mode is active, the last counter will not be updated and max day to extract will be ignored.
SSL Authentication
Supported Platforms
Troubleshooting
Configuration and Performance Metrics Mapping
Performance Metrics
Configuration metrics
Derived metrics
Metric Classes
Overlapping Metrics
Lookup Fields in SiteScope
Object Relationships
