- Looking to create a custom report or view in TrueSight Capacity Optimization (TSCO). Need assistance extracting the desired performance and configuration data from the TSCO database. |
The creation of custom SQL is outside of the scope of TrueSight Capacity Optimization (TSCO) Technical Support. In general, customization of TSCO including custom SQL is provided via Professional Services on a fee for service basis. 000028422: What level of support is available for TSCO customization from TSCO Technical Support? (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000028422)One possible avenue for assistance with the creation of custom reports is the TSCO Community forum site (https://communities.bmc.com/community/bmcdn/service_assurance/capacity_management). The TSCO Community forum site is a user-to-user forum where people who use TSCO can ask and answer questions related to TSCO. The TSCO Community forum may be able to assist with the creation of custom SQL or with recommendations on different ways to obtain the same information from TSCO without the use of custom SQL. In general, for the extraction of system and configuration data from TSCO one would want to use the Public Views: 000095686: Request for TSCO Database Internal Schema documentation (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000095686) The TSCO documentation describes the Public Views and provides several query examples using those Public Views: https://docs.bmc.com/docs/display/btco2002/Accessing+data+using+public+views https://docs.bmc.com/docs/display/btco2002/Query+examples This document maps the metrics displayed on the system summary page to the internal metric names within the BCO database 000106518: In TSCO, How do I fill in the Summary tab for a system? (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000106518) One thing to be aware of in relation to TSCO is that each metric isn't a column in a table -- each metric is a row in a table. So, you'll see that there is a different Public View per data summarization level (detail, hourly, daily, monthly). Each Public View would then contain rows where each row represented a particular metric for a particular system for a particular interval. So, each row in the table represents the data for a single metric for a single point of time for a single system. So, a query to select CPU_UTIL would be identical to a query to select MEM_UTIL -- except in one query you'd have " PV_SYS_METRIC.METRIC = 'CPU_UTIL'" and the other you'd have "PV_SYS_METRIC.METRIC = 'MEM_UTIL' in the WHERE clause (See the "Given a system and a time series metric, find daily values for the last 7 days." example in the BCO documentation). TSCO supports the following data summarization levels:
The queries you run against the views would have the same structure but they would return different data summarization levels. Most of the time the PV_SYS_DATA_DH (Hourly) data is the level you are looking for. Note that in TSCO version 10.0 and later the PV_SYS_DATA_DETAIL level will only be populated with data if the ETL is bringing in data at a granularity less than hourly. If the base ETL is bringing in hourly data than SYS_DATA_DETAIL will be skipped and data will be imported directly to SYS_DATA_DH. The PV_SYS_METRIC public view lists every metric that has ever been associated with that entity in TSCO. That means that finding a metric associated with an entity in the PV_SYS_METRIC view doesn't mean that metric necessary is currently reporting data for that entity. It just means that at some point in the life system of the entity data had been reported for that metric. |