Data Collector Catalog

Teradata® Viewpoint User Guide

brand
Analytical Ecosystem
prodname
Teradata Viewpoint
Teradata Workload Management
vrm_release
16.20
category
User Guide
featnum
B035-2206-107K

Data collectors gather information from different sources and make the data available to Teradata Viewpoint portlets.

Teradata Database Data Collectors

Teradata Database Data Collector Description Portlets Using Data
Account Info Queries the DBC.AccountInfo table in the database and collects a list of available account strings.

The Queries portlets use this data to list the available account strings for the Change Priority function.

The Workload Designer portlet uses this data to provide a list of available account strings when creating classification criteria.

  • My Queries
  • Query Groups
  • Query Monitor
  • Workload Designer
Alert Request
  • Monitors the dbcmngr.AlertRequest table on the Teradata Database system for incoming alert requests. If the table row contains valid data, the contents are forwarded to the Alert Service to process the alert action.
  • Monitors the dbcmngr.MonitorRequest table on the Teradata Database system. Any Teradata Database utility or user program can request Teradata Viewpoint to monitor its progress by inserting rows into the dbcmngr.MonitorRequest table. Each row includes fields that indicate the date and time by which the next row is inserted. If a new row is not inserted before the specified date and time, the collector forwards the contents to the Alert Service to process the alert action.
  • Monitors the dbc.sw_event_log table on the Teradata Database.
  • Alert Viewer
AWT Info Collects AMP worker task (AWT)-related information through the AMP Load (ampload) Teradata Database utility. The collector executes the MONITOR AWT RESOURCE request of PM/API instead of AMP Load (ampload). If this collector is not enabled, the portlets do not display AWT information.

The AWT Info collector is also required for alerts that depend on AWT information.

  • Metric Heatmap
  • Metrics Analysis
  • Node Resources
  • System Health
  • Today's Statistics
Database Space Queries the DBC.DataBaseSpace and DBC.DBase tables to collect database space usage metrics.

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.

  • Metric Heatmap
  • Space Usage
Dictionary Collects and caches information from the Teradata Data Dictionary.

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.

  • Data Labs
  • Lock Viewer
  • Monitored Systems
  • Query Group Setup
  • Query Monitor
  • Query Spotlight
  • Roles Manager
  • Space Usage
  • Workload Designer
  • Workload Monitor
Disk Space Obtains disk-space and database space usage data by querying the DBC.DiskSpace view of the DBC database.

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

  • Metric Heatmap
  • Metrics Analysis
  • System Health
Collects the perm space data and skew percentage for the DBC.TransientJournal table.
  • Alert Viewer
Elastic Limit Collects the current system CPU limit set in the Schmon utility or Workload Designer portlet.

Only enable this collector for Teradata Database systems leveraging Elastic Performance On Demand.

  • Elastic Performance
Elastic Usage Collects the overall node CPU usage from the DBC.ResUsageSPMA table.

Only enable this collector for Teradata Database systems leveraging Elastic Performance On Demand.

  • Elastic Performance
Lock Info Uses the data written to the DBC.DBQLXMLLockTbl table to capture lock information. For the Lock Info collector to run against Teradata Database 14.10 and later, DBQL query logging must be enabled with the WITH LOCK option.

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

For more information, see Lock Info Collector.

  • Lock Viewer
Query Count Teradata Database query count and query log data are collected by querying the DBC.DBQLogTbl and DBC.DBQLSummaryTbl tables. Query logging in the Teradata Database must be enabled for a query to be counted.

For more information, see Query Count Collector.

  • Metric Heatmap
  • Productivity
  • Today's Statistics
  • Workload Designer
Query Log Collects DBQL data from the PDCRDATA.DBQLogTbl_Hst table.

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 make sure only the most important data is collected.

  • Application Queries
  • Query Log
Resource Usage Collects node resource usage data from the DBC.ResUsageSPMA table and DBC.ResUsageIPMA table. Resource Usage collects vproc usage data from the DBC.ResUsageSVPR table.

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.

  • Metric Heatmap
  • Metrics Analysis
Sessions Collects snapshots of Teradata Database session data for each login from the Teradata Monitor partition by using the Teradata Performance Monitor API.

For more information, see Sessions Collector.

  • Metric Heatmap
  • My Queries
  • Query Groups
  • Query Monitor
  • Query Spotlight
  • SQL Scratchpad
  • Stats Manager
  • System Health
  • Today's Statistics
  • Workload Monitor
Stats Manager Collects and retains statistic data used by Teradata Database system tables from the DBC.Dbase, DBC.TVM, DBC.Indexes, DBC.StatsTbl, TDStats.StatsTbl, TDStats.ObjectList, and TDStats.ExcludedTbl tables.
  • Stats Manager
System Config Collects and retains Teradata Database system configuration data used by portlets and collectors. The collector retrieves the Teradata Database version from DBC.DBCInfo. This information is critical to provide proper functionality of several portlets and other data collectors.

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.

This collector does not call Vproc Manager console partition utility.

  • Alert Viewer
  • Canary Response Times
  • Lock Viewer
  • Metric Heatmap
  • Metrics Analysis
  • My Queries
  • Node Resources
  • Productivity
  • Query Monitor
  • Query Spotlight
  • Space Usage
  • System Health
  • Today's Statistics
  • TVS Monitor
  • Viewpoint Monitoring
  • Workload Designer
  • Workload Health
  • Workload Monitor
System Stats Collects system, node, and vproc statistics data by querying the Teradata Monitor partition using the PM/API. Physical and virtual resource statistics are collected from Teradata Database system memory at a configurable sample rate.

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.

  • Metric Heatmap
  • Metrics Analysis
  • Node Resources
  • System Health
  • Today's Statistics
  • Workload Designer
  • Workload Health
  • Workload Monitor
Table Space Collects and retains data about the space used by Teradata Database system tables from the DBC.Dbase, DBC.TVM, DBC.Indexes, and DBC.DataBaseSpace tables. 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.
  • Metric Heatmap
  • Space Usage
  • System Health
TASM Config Obtains configuration information about the TDWM version and active ruleset in the Teradata Database from the TDWM database in Teradata.

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.

  • My Queries
  • Query Groups
  • Query Monitor
  • Workload Designer
  • Workload Health
  • Workload Monitor
TASM Distribution Collects information about the average percentage of CPU consumption used by each workload for each node in the Teradata Database system. The TASM Distribution data collector executes schmon -M -p -P in the Teradata Console partition to collect information for the CPU Consumption graph in the Distribution view. The collector executes the MONITOR WD request of PM/API instead of schmon.
  • Workload Monitor
TASM Exception Obtains TASM Exception data from the DBC.TDWMExceptionLog table.
  • Workload Monitor
TASM State Collects and retains system regulation data.

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.

  • Workload Health
  • Workload Monitor
TASM Summary Obtains data for each active workload in the Teradata Database. This collector sends queries to the Teradata Monitor partition using PM/API.
  • Workload Health
  • Workload Monitor
Virtual Storage Collects data on cylinder temperature and storage grade from space types managed by the Teradata Virtual Allocation Manager (TVAM) utility. This collector uses the GetTvsUdfViewpointSummary user-defined function, created by the Teradata Database DIP scripts, to collect this data.
  • TVS Monitor

Teradata Aster Data Collectors

Teradata Aster Data Collector Description Portlets Using Data
Cluster Status Collects cluster status and node status information for each node.
  • Node Monitor
  • System Health
Component Stats Collects statistics for each node of the Teradata Aster system, such as CPU, disk I/O, net I/O, and memory use.
  • Metric Heatmap
  • Metrics Analysis
  • Node Monitor
  • System Health
Nodes Collects detailed information for each node, including the node storage and node virtual worker information.
  • Node Monitor
  • Space Usage
  • System Health
Processes Collects data about sessions logged into the system and processes. For active processes, detailed information about the statement and phases of the process is also collected.
  • Completed Queries
  • Query Monitor
  • System Health
Rulesets Collects the active ruleset information for the Teradata Aster system.
  • Workload Designer
Space Usage Collects database, table, and node storage information.
  • Node Monitor
  • Space Usage
  • System Health
System Config Collects the site ID and Aster Database version.
  • Monitored Systems
  • Workload Designer
Workloads Collects workload policy and workload service class data.
  • Completed Queries
  • Query Monitor

Teradata Machine Learning Engine Collectors

Teradata Machine Learning Engine Collector Description Portlets Using Data
Cluster Status Collects cluster status and information about Teradata Machine Learning Engine queen and workers.
  • Node Monitor
  • System Health
Component Stats Collects statistics on Teradata Machine Learning Engine queen and workers such as CPU, disk I/O, net I/O, and memory use.
  • Metric Heatmap
  • Metrics Analysis
  • Node Monitor
  • System Health
Pods Collects detailed information, including storage and virtual worker information.
  • Node Monitor
  • System Health
Processes Collects data about sessions logged into the system and processes. For active processes, detailed information about the statement and phases of the process is also collected.
  • Completed Queries
  • Query Monitor
  • System Health
System Config Collects the site ID and system version.
  • Monitored Systems

Teradata Hadoop Data Collectors

Teradata Hadoop Data Collector Description Portlets Using Data
HBase Collects the number of region servers that are running and configured and the amount of time the master server has been running.
  • Hadoop Services
HDFS Collects the number of files and directories in HDFS, the space capacity not currently used by HDFS, datanode process information, and the amount of time a name node is running.
  • Hadoop Services
  • Metric Heatmap
  • Metrics Analysis
  • Node Monitor
  • Space Usage
  • System Health
MapReduce (HDP 1.3) Collects map and reduce jobs statistics, jobtracker information, the number of map slots occupied and reserved, the number of reduce slots occupied and reserved, and the number of tasktrackers running and configured.
  • Hadoop Services
  • Metric Heatmap
  • Metrics Analysis
  • Node Monitor
  • System Health
Services Collects Hadoop services information.
  • Hadoop Services
  • Node Monitor
  • System Health
System Config Collects the list of nodes that make up the Teradata Hadoop system and the site ID from the system.

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

  • Hadoop Services
  • Node Monitor
System Stats Collects system statistics data from Hadoop Services.
  • Hadoop Services
  • Metric Heatmap
  • Metrics Analysis
  • Node Monitor
YARN (CDH and HDP 2.1 and later) Collects YARN statistics, ResourceManager information, the amount of cluster memory allocated and reserved, the number of containers allocated and reserved, and the number of applications running and pending.
  • Hadoop Services
  • Metric Heatmap
  • Metrics Analysis
  • Node Monitor
  • System Health

Teradata Presto Data Collectors

Teradata Presto Data Collector Description Portlets Using Data
Queries Collects information about queries run on a Teradata Presto system.
  • Completed Queries
  • Query Monitor

Teradata QueryGrid Data Collectors

Teradata QueryGrid Data Collector Description Portlets Using Data
Issues ( Teradata® QueryGrid™ 16.10 and later) Collects Teradata® QueryGrid™ issues.
  • QueryGrid
Queries Collects information about queries run on a Teradata QueryGrid system.
  • QueryGrid
System Config ( Teradata® QueryGrid™ 16.10 and later) Collects and retains the latest snapshot of Teradata® QueryGrid™ instances.

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

  • QueryGrid

Teradata AppCenter Managed System Data Collectors

Teradata AppCenter Managed System Data Collector Description Portlets Using Data
Metrics Collects service health metrics information for Teradata AppCenter. Service Health