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 Cases Not Represented in the Data Collection Schedule Summary.
Table: Data Collection Schedule Summary
Column name | Description |
|---|---|
|
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 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. |