- From the Systems list, select the name of the Teradata system you want to update.
- From the Setup list, select Canary Queries.
Do one of the following:
Option Description Add Select to add a canary query. Copy Select in the row of the canary query you want to copy.
- Enter a name for the canary query.
- [Optional] Select the Enable query check box to enable the canary query.
- Under SQL, enter or modify the SQL for the query.
- Under Default Database, specify the default database.
If Login appears, select the login you want to use to run the system task.
- [Optional] Select the Log in each time the query executes check box to force a new log in connection to the Teradata system each time that the query runs.
[Optional] Enter a timeout value. The value indicates the number of seconds before abandoning the attempt to log in to the Teradata system.
Enter a value only if you selected the Log in each time the query executes check box. You cannot add an alert action for a log in timeout for a System Heartbeat canary query.
For Collect Data Every, specify the data collection frequency in minutes.
The recommended sample rate is 2 minutes. The initial retention policy is 1 year.
Under Execute, select one of the following options:
Option Description 24/7 Select 24/7 to execute the query 24 hours a day, 7 days a week. Custom
- Select Custom to execute the query during a time frame.
- Specify the start time and end time.
- Specify the start day and end day.
Under Delete Data, select one of the following options:
Option Description Date
- Select the After check box to set the calendar retention period.
- Enter a number and select a calendar value.
Teradata Viewpoint uses a retention policy to keep collected data for a time period or up to a certain size. For more information, see Data Collector Sample Rates.
- Select the Over check box to set the file size retention period.
- Enter a number and select a file size restriction.The size of the data actually retained by the collector is always larger than the specified number because data clean up only drops table partitions that exceed this number. A 1024 byte kilobyte is used, so 1 GB is actually 1,073,741,824 bytes.
If the operation is successful, appears. If the operation fails, appears. If you receive an error, verify that the settings are correct and try again.