System Administration Reports > Data Collection Schedule Summary
  
Version 10.2.00
Data Collection Schedule Summary
Data collection performance may be impacted when multiple policies initiate at the same time. Use this single view of all successful active collection policy schedules to determine scheduling conflicts. Compare the schedule frequency with the start/end times to understand which data collectors may be competing for resources. Note that often long-running collections could be due to database persistence processing. This report can be useful for troubleshooting and implementing database efficiencies. See also, Cases Not Represented in the Data Collection Schedule Summary.
Policy Name
The type of system from which data is being collected, such as EMC VPLEX, Data Domain, or NetApp Cluster. The host name or IP address of the system that is the source of the data is appended to the product name, except for Host Resources collection.
Collector Name
Name of the data collector.
Collector Host Name
Name of host where data collector is deployed. Drill down to the Host Details.
Probe Type Name
The type of data collection probe, such as Capacity, Performance, or Inventory.
Schedule
The frequency of the data collection, such as Execute at 12:00 PM Daily. All times are relative to the Data Collector server.
Last Start Time
The date and time the last successful data collection started.
Last End Time
The date and time the last successful data collection ended.
Last Duration
Length of the last successful collection cycle. A color indicator highlights durations that are 50% above the average duration. Note that the duration is calculated from the time the first set of data is persisted in the database until the last data from the collection thread is persisted.
Average Duration
The average duration of all successful executions of this probe, including database persistence processes.
Duration Delta
The % difference between the last successful duration and the average successful duration, which is an indicator of collection and database persistence performance. If the last duration is unknown, the delta will be unknown.
# of Collections
Number of times the probe successfully collected data within the report scope.
Total Duration
Total Duration = (# of Collections) * (Average Duration). This column is useful for sorting purposes, to identify long-running collection and database persistence processes.
Collector Identifier
This metadata collector ID is useful for correlating collection events with the relevant log files. See also, Example of a Data Collector Log Request. For a VM, instead of a metadata ID, the name of the ESX server is listed in this table column.
Cases Not Represented in the Data Collection Schedule Summary
Due to the nature of certain types of collected data, the Data Collection Schedule Summary report cannot always display schedules for all collected products. Typically, these exception cases cannot be included in the report because there are no explicit start and finish transactions to be captured.
The following table lists the exceptions to the Data Collection Schedule Summary report, where the collected subsystems cannot be represented in the report.
Collected Subsystem
StorageConsole Licensed Module
Why the data is not listed in the report
File Analytics - CIFS
File Analytics
No explicit start and finish transactions are collected.
Host Resources
Capacity Manager
May be supported in a future StorageConsole version.
Example of a Data Collector Log Request
When troubleshooting data collection issues, you can use the Support Tools feature to create a Support Package Request to download relevant files. When you add a Support Package Request, the Collector Identifier, listed in the Data Collection Schedule Summary, can be entered for the name, to retrieve a specific data collection log.
1. Generate the Data Collection Schedule Summary report.
2. In the Data Collection Schedule Summary, select the Collector Identifier for the data collection thread that needs further investigation.
3. Ctrl-C copy the identifier.
4. Go to the Support Tools: Admin > Advanced > Support Tools
5. Click Add to create a Support Package Request, supply the following details, and click OK.
• Name: Paste the Collector Identifier into this field and also place a wildcard asterisk (*) before and after the identifier.
• Data Collector Server: Select this radio button.
• Data Collector: Select the data collector associated with the collection thread listed in the Data Collection Schedule Summary.
• Path to File/Folder: Enter the path to the log files. For a Linux data collector server, this path typically is
/mbs/logs.
• Email: Enter your email address so that you can be notified when the package becomes available.