Data Collector Catalog - Teradata Viewpoint

The Space Usage and Metric Heatmap portlets use the data collected by the Database Space collector. If this collector is not enabled, these portlets do not display current database space data.

If this collector is not enabled, the Query Group Setup and Workload Designer portlets do not display the most current usernames.

The Dictionary collector is required to generate Database Space alerts.

If this collector is not enabled, these portlets do not display the most current disk-space data.

This collector should be enabled only for Teradata Database systems leveraging Elastic Performance On Demand.

This collector should be enabled only for Teradata Database systems leveraging Elastic Performance On Demand.

The Lock Viewer portlet displays updated lock data only for the period of time when the collector is enabled.

For Teradata Database 14.0 and earlier, this collector uses the LockLogger database utility to capture a snapshot of lock information. For the Lock Info collector to run against Teradata Database14.0 and earlier, the LockLogger flag in DBSControl on the Teradata Database system must be set to TRUE.

For more information, see Lock Info Collector.

For more information, see Query Count Collector.

Up to 10 million rows of DBQL data is collected per day. When the number of DBQL rows exceeds 10 million, you can specify the name of a database view in the Monitored Systems portlet to load a subset of the query log data to ensure only the most important data is collected.

The recommended collection is the rate that this information is logged to these tables in the Teradata Database. You can set this rate in the Monitored Systems portlet by selecting Monitor Rates from the Setup list.

For more information, see Sessions Collector.

To gather physical system configuration data, the collector also uses the MONITOR PHYSICAL CONFIG request of the PM/API and executes STATUS PDE of the Vproc Manager console partition utility.

This collector cannot be disabled. The sample rate and initial retention policy for this collector cannot be modified.

For Teradata Database 14.0 or later, this collector does not call Vproc Manager console partition utility.

Collecting system statistics data more frequently than the resource sample rate in Teradata Database results in duplicate data being collected and wasted resource usage on the Teradata Database. You can set this rate in the Monitored Systems portlet by selecting Monitor Rates from the Setup list.

If this collector is not enabled, these portlets do not display system statistics data.

The Workload Designer portlet uses node and vproc counts from this collector to assist with the creation of rulesets.

The System Stats collector is required for system, node, vproc, and System Health alerting.

The Space Usage and Metric Heatmap portlets use the data collected by the Table Space collector. If this collector is not enabled, these portlets do not display the most current table space data.

The TASM Config collector needs to be enabled to use Workload Designer for a new Teradata Database system. If the collector is not enabled, the TDWM version information is not collected, and the Teradata Database system does not appear in the list of available Teradata Database Systems in Workload Designer.

You must enable both the TASM Config and TASM State collectors to be able to associate the active workload name with the session information displayed in these portlets.

This data is used by portlets and other collectors, so this collector cannot be disabled or modified.