TrueSight Capacity Optimization (TSCO) - How to use the "VMware - vCenter and ESX Server History Extractor" to recover historical data and consolidate it with the data collected by the "VMware - vCenter Extractor Service"? INCLUDES VIDEO
Knowledge Article
TrueSight Capacity Optimization (TSCO) - How to use the "VMware - vCenter and ESX Server History Extractor" to recover historical data and consolidate it with the data collected by the "VMware - vCenter Extractor Service"? INCLUDES VIDEO
In TSCO, how to use the "VMware - vCenter and ESX Server History Extractor" to recover historical data and consolidate it with the data collected by the "VMware - vCenter Extractor Service"?
TrueSight Capacity Optimization
Capacity Optimization
TrueSight Capacity Optimization 10*, 11* & 20*
TrueSight Capacity Optimization
Capacity Optimization
TrueSight Capacity Optimization 10*, 11* & 20*
'VMware - vCenter Extractor Service' for nightly data import there was a data gap in the imported data that like to fill in. How to use the 'VMware - vCenter and ESX Server History Extractor' to recover the data that failed to import by the regular nightly vCenter Extractor Service?
Since the "VMware - vCenter Extractor Service" is running, please create a "VMware - vCenter and ESX Server History Extractor" to recover historical data and consolidate it with the data collected by the "VMware - vCenter Extractor Service", these are the basic steps:
When creating the new "VMware - vCenter and ESX Server History Extractor", select:
1) In "Entity Catalog", select "Sharing Status"->"Shared Entity Catalog", "Sharing with Entity Catalog"->"Default Entity Catalog". 2) In "Exising domain", select the current vCenter Service Extractor's domain. 3) To resolve conflict select "ETL migration" option, 4) and then select the vCenter Service Extractor's Hierarchy Rule 5) In "VMware ETL configuration"-> "Extraction period", select the "From-to data extraction" option and set the extraction period. (Let's select a short period of time, like 5 days.) 6) Finally "Save changes" and run it.
When picking a historic period the ETL completes with a green OK status but doesn't import any historic data
This is a common problem when trying to import VMware data that is more than 7 days old via the VMware History Extractor. The typical problem is that the ETL is configured to pull data from, say, 30 days ago, but is configured with the 30 minute sample data which is only maintained on the vCenter side for 7 days.
In the ETL logs you'll see the following retention information:
[2017-10-13 07:41:16] REPORT Enabled from-to data extraction. Hierarchy relations will not be imported. Extracting data from Mon Sep 18 00:00:00 EDT 2017 to Tue Sep 26 00:00:00 EDT 2017
[2017-10-13 07:41:29] INFO Connected to hostname.domain.com - VMware vCenter Server 6.0.0 build-4191365 UUID: 4F3FC6A5-9385-423F-A520-C39FAA6F0811 version: 6.0 - api 2.5. Supported sampling intervals:Past day [300] (interval: 5m - level: 1 - retention: 1d); Past week [1800] (interval: 30m - level: 1 - retention: 7d); Past month [7200] (interval: 2h - level: 1 - retention: 30d); Past year [86400] (interval: 1d - level: 1 - retention: 365d) diff:-14400000 - parallelism: 5 [2017-10-13 07:41:29] INFO Starting metric download. Forced minimum date: 08/10/2017 07:41:16. Sampling interval: Past week [1800] (interval: 30m - level: 1 - retention: 7d).
Based upon the above data retention breakdown, if one were to run the ETL today only the 2 hour summarization interval has data going back 30 days ("Past month [7200] (interval: 2h - level: 1 - retention: 30d)"). The 30 minute summarization interval only has data going back 7 days.
The desired data summarization level can be set in the ETL Run Configuration.
vpxd.stats.maxQueryMetrics error during Cluster and Resource Pool data collection
The following error may be reported in the TSCO ETL logs:
[2017-10-08 17:59:17] FAILED Blocking exception raised by vCenter for entity:domain-c5832. Exception: com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: This operation is restricted by the administrator - 'vpxd.stats.maxQueryMetrics'. Contact your system administrator. Please see the server log to find more detail regarding exact cause of the failure.
This is a limitation on the vCenter side that affects the TSCO History Extractor ETL.
This error being reported only affects the import of data at the cluster and resource pool levels. The VMware host and guest level metrics should be imported normally by the vCenter History Extractor.
The Cluster and Resource Pool collection problem is flagged as a failure during data collection (causing the ETL to end in red ERROR state) but the failure only impacts the collection of cluster and resource pool metrics -- the other metrics successfully imported by the ETL will be properly loaded into the TSCO database (even though the ETL ends in ERROR state).