Tez uses YARN timeline as its application history store. Tez stores most of its lifecycle information into the history store, such as all the DAG information. You can monitor the Tez engine information, such as DAG % complete.

Tez relies on the application time line server as a backing store for the application data generated during the lifetime of a YARN application. Tez interfaces with the application timeline server and displays both a live and historical view of the Tez application inside a Tez web application.

The following image shows the Tez Hive Query properties on the Monitor tab in the Administrator tool:

You can monitor and view Hive tasks that use Tez to run Spark jobs. Or, you can monitor Tez engines for Hive mappings.

The following image shows a Hive task that uses Tez to run Spark jobs:

You can view the following information under the MR Job details for Tez:

Property	Applicable Values	Description
Job ID	Application_<name>	You can select the link under Job ID to view the application cluster. For example, if the Job ID property contains a value starting with the prefix application_ in the MR Job Details pane, the naming convention indicates that the Tez engine is in use. You can click the link under Job ID to view the application cluster. If you click the Tracking URL for the Tez job, you get redirected to the Hadoop Resource Manager. If you then click History, you can view the Tez view, which is provided by the Hadoop distribution in Ambari. For each application ID, there are multiple DAGs information.
Map % Complete	N/A	Map % is not applicable for Tez.
Reduce % Complete	N/A	Reduce % is not applicable for Tez.
DAG % Complete	0 - 100	You can specify a value from 0 through 100 for Tez.

When you specify a query in Hive, the script launches a Hadoop job, such as INSERT or DELETE query. Or, the script launches a Hive query. If the script launches no Hadoop jobs, it appears blank for the following fields, such as Job ID, reduce % complete, and DAG % complete.