· Contents Chapter 1. Monitoring Agent for Hadoop................................................................1 Chapter 2. Dashboard in the Cloud APM console

Monitoring Agent for HadoopVersion 08.19.09.00

Reference

IBM

Note

Before using this information and the product it supports, read the information in “Notices” on page289.

This edition applies to version 08.19.09.00 of the Monitoring Agent for Hadoop and to all subsequent releases andmodifications until otherwise indicated in new editions.© Copyright International Business Machines Corporation 2015, 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

Contents

Chapter 1. Monitoring Agent for Hadoop................................................................1

Chapter 2. Dashboard in the Cloud APM console....................................................3Default dashboard pages............................................................................................................................ 3Widgets for the Default dashboard pages..................................................................................................6Custom views.............................................................................................................................................36Attribute details.........................................................................................................................................36

Chapter 3. Thresholds......................................................................................... 37Predefined thresholds............................................................................................................................... 37Customized thresholds..............................................................................................................................41

Chapter 4. Attributes.......................................................................................... 43Data sets for the monitoring agent.......................................................................................................... 44Attribute descriptions................................................................................................................................48

Ambari Metrics data set...................................................................................................................... 48Atlas data set....................................................................................................................................... 52Big SQL data set.................................................................................................................................. 55Cluster Metrics data set...................................................................................................................... 59Cluster Overview data set................................................................................................................... 60ClusterDetails data set........................................................................................................................ 63DataNode data set...............................................................................................................................66Druid data set...................................................................................................................................... 75Falcon data set.....................................................................................................................................78Flume data set..................................................................................................................................... 82FS Name System data set...................................................................................................................85HBase data set.....................................................................................................................................92HDFS data set...................................................................................................................................... 95Hive data set........................................................................................................................................ 99HOS Performance Object Status data set........................................................................................ 102Hosts nodes data set........................................................................................................................ 106JVM Metrics data set.........................................................................................................................107Kafka data set....................................................................................................................................113Knox data set.....................................................................................................................................116Mahout data set.................................................................................................................................120MapReduce2 data set........................................................................................................................123NameNode data set...........................................................................................................................127NiFi data set.......................................................................................................................................134NiFi Registry data set........................................................................................................................ 138NodeManager Metrics data set.........................................................................................................141Oozie data set....................................................................................................................................143Operating System data set................................................................................................................147Performance Object Status data set................................................................................................ 148Pig data set........................................................................................................................................ 151Queue Metrics data set..................................................................................................................... 155Ranger data set..................................................................................................................................162Roles data set.................................................................................................................................... 165RPC data set...................................................................................................................................... 166Schema Registry data set................................................................................................................. 170Services Overview data set...............................................................................................................173

iii

Slider data set....................................................................................................................................174SmartSense data set......................................................................................................................... 177Solr data set.......................................................................................................................................181Spark data set....................................................................................................................................184Sqoop data set...................................................................................................................................188Startup Progress data set................................................................................................................. 191Streaming Analytics Manager data set.............................................................................................195Superset data set.............................................................................................................................. 198Take Action Status data set.............................................................................................................. 202Tez data set........................................................................................................................................204Thread Pool Status data set............................................................................................................. 207Titan data set.....................................................................................................................................210UGI Metrics data set......................................................................................................................... 213Unified Console data set................................................................................................................... 215YARN data set....................................................................................................................................219ZooKeeper data set........................................................................................................................... 222

Chapter 5. Workspaces..................................................................................... 227Workspace descriptions..........................................................................................................................228

Hadoop navigator item...................................................................................................................... 228Performance Object Status navigator item...................................................................................... 228Services navigator item..................................................................................................................... 228Hadoop Hosts subnode..................................................................................................................... 229

Chapter 6. Situations.........................................................................................231Predefined situations.............................................................................................................................. 231Situation descriptions............................................................................................................................. 232

Hadoop navigator item...................................................................................................................... 232Performance Object Status navigator item...................................................................................... 232Services navigator item..................................................................................................................... 233Hadoop Hosts subnode..................................................................................................................... 233

Chapter 7. Take Action commands.....................................................................235Predefined Take Action commands........................................................................................................235Take Action command descriptions....................................................................................................... 235

Chapter 8. Policies............................................................................................ 237Predefined policies..................................................................................................................................237Policy descriptions.................................................................................................................................. 237

Policy1 name......................................................................................................................................237KVM_VM_Created...............................................................................................................................237MS_SQL_DB_free_space_critical....................................................................................................... 238

Chapter 9. Event mapping................................................................................. 239

Appendix A. Documentation library................................................................... 283Prerequisite documentation................................................................................................................... 283Related documentation...........................................................................................................................284Tivoli Monitoring Community on Service Management Connect...........................................................284Other sources of documentation............................................................................................................284Conventions used in the documentation............................................................................................... 285

Accessibility features........................................................................................ 287Notices..............................................................................................................289

Programming interface information....................................................................................................... 290Trademarks.............................................................................................................................................. 290Terms and conditions for product documentation................................................................................ 291

iv

IBM Online Privacy Statement............................................................................................................... 292Safety and environmental notices..........................................................................................................292

Index................................................................................................................ 293

v

vi

Chapter 1. Monitoring Agent for Hadoop

The Monitoring Agent for Hadoop offers a central point of management for your Hadoop environment orapplication.

The software provides a comprehensive means for gathering the information that is required to detectproblems early and to prevent them. Information is standardized across the system. You can monitormultiple servers from a single console. By using the Hadoop agent you can easily collect and analyzeHadoop specific information.

Installing and configuring the agent

Install the monitoring agent on the system where the application that you want to monitor is located.

For more information, see the agent installation and configuration topics in IBM Knowledge Center:

• IBM Cloud Application Performance Management• IBM Cloud Application Performance Management, Private

For supported operating systems, see System Requirements in the APM Developer Center.

© Copyright IBM Corp. 2015, 2019 1

http://www.ibm.com/support/knowledgecenter/SSMKFH

http://www.ibm.com/support/knowledgecenter/SSHLNR

https://developer.ibm.com/apm/docs/system-requirements/

2 Monitoring Agent for Hadoop: Reference

Chapter 2. Dashboard in the Cloud APM console

Open the Application Performance Dashboard in the Cloud APM console to see a status summary of allyour applications. As you drill down to dashboard pages for specific applications and their supportingelements, more details are available about the selected item. Use the Hadoop agent dashboard pages toproactively monitor your Hadoop deployment. Each page contains views with key performance indicators.

When an application that includes Hadoop managed resources is selected, the navigator and the StatusOverview tab show Hadoop in the Components group:

• Click Components to see a single Hadoop group widget that is displayed along with a group widget forevery other data source type in the application.

• Click the Hadoop subgroup to see a group widget for each managed resource in the application.• Click inside a Hadoop group widget or click a Hadoop managed resource from the navigator Instances

section to open a dashboard page with KPIs from the selected managed resource.• IBM® Cloud Application Performance Management, Advanced users also have deep-dive diagnostics for

Hadoop applications. In the Request Summary view of the details dashboard page, click Diagnose toopen the Hadoop deep-dive dashboard page.

For more information about the KPIs, click in the view or click in the dashboard banner.

Default dashboard pagesAmbari Metrics

Use the Ambari Metrics dashboard to view the details of Ambari Metrics service in Hadoop cluster.Atlas Metrics

Use the Atlas Metrics dashboard to view the details of Atlas service in Hadoop cluster.Big SQL Metrics

Use the Big SQL Metrics dashboard to view the details of Big SQL service in Hadoop cluster.DataNode Overview

Use the DataNode Overview dashboard to know the following details of the Hadoop DataNodes:

• The trend of block operations, such as number of blocks that are read, written, and removed fromthe node

• The trend of the number of blocks that are read from the local and remote clients• The trend of the number of blocks that are written from the local and remote clients• The trend of the number of blocks that are replicated and removed• The trend of the average time that is required for heartbeat operations and time

Druid MetricsUse the Druid Metrics dashboard to view the details of Druid Service in Hadoop cluster.

Falcon MetricsUse the Falcon Metrics dashboard to view the details of Falcon service in Hadoop cluster.

File System DetailsUse the File System Details dashboard to know the following information about the HadoopDistributed File System:

• The rate of change in the number of files in the cluster• The number of blocks in the cluster, such as total, corrupt, missing, and excess• The percentage of HDFS capacity used• Information about the High Availability (HA) state• Information about the block capacity


Flume MetricsUse the Flume Metrics dashboard to view the details of Flume service in Hadoop cluster.

HBase MetricsUse the HBase Metrics dashboard to view the details of HBase service in Hadoop cluster.

HDFS MetricsUse the HDFS Metrics dashboard to view the details of Hadoop Distributed File System(HDFS) servicein Hadoop cluster.

Hive MetricsUse the Hive Metrics dashboard to view the details of Hive service in Hadoop cluster.

JVM Memory DetailsUse the JVM Memory Details dashboard to know the following details of a Java virtual machine (JVM)in the cluster:

• The memory heap details for a node• Information about the number of threads and logs for a node• Comparative information about memory heap and non-heap usage for a particular node• The historical trend per daemon on a node

JVM Memory HistoryUse the JVM Memory History dashboard to know the following details of a JVM in the cluster:

• The historical trend of the memory heap details for a selected daemon• The historical trend of the number of threads and logs for a selected daemon• The historical trend of the comparative information about memory heap and non-heap usage for a

selected daemon

Kafka MetricsUse the Kafka Metrics dashboard to view the details of Kafka service in Hadoop cluster.

Knox MetricsUse the Knox Metrics dashboard to view the details of Knox service in Hadoop cluster.

Mahout MetricsUse the Mahout Metrics dashboard to view the details of Mahout client in Hadoop cluster.

MapReduce2 MetricsUse the MapReduce2 Metrics dashboard to view the details of MapReduce2 service in Hadoop cluster.

NiFi MetricsUse the NiFi Metrics dashboard to view the details of NiFi service in Hadoop cluster.

NiFi Registry MetricsUse the NiFi Registry Metrics dashboard to view the details of NiFi Registry service in Hadoop cluster.

Nodes OverviewUse the Nodes Overview dashboard to know the details of nodes in the Hadoop cluster, such as thesubnode name and status of the Java virtual machine, Queue, File System, Remote Procedure Calls(RPC), DataNode, and Hadoop services and their status.

Oozie MetricsUse the Oozie Metrics dashboard to view the details of Oozie service in Hadoop cluster.

Pig MetricsUse the Pig Metrics dashboard to view the details of Pig client in Hadoop cluster.

Queue DetailsUse the Queue Details dashboard to know the following details of a queue:

• Information about the status of an application, such as submitted, running, and pending for the topnine queues in the cluster

• Information about the memory status, such as reserved, pending, allocated, and available for thetop nine queues in the cluster


• Information about all the applications in the cluster• Historical trend of the application status and the memory status for a selected queue

Ranger MetricsUse the Ranger Metrics dashboard to view the details of Ranger service in Hadoop cluster.

RPC DetailsUse the RPC Details dashboard to know the following details of a RPC in the cluster:

• The amount of data that is sent and received through the first nine ports• The amount of data that is sent and received through all ports• The RPC authentication and authorization details for the first nine ports• The RPC authentication and authorization details for all ports• The average queue time and process time for the first nine ports• The average queue time and process time for all ports• The number of open connections for the first nine ports• The number of open connections for all ports

Schema Registry MetricsUse the Schema Registry Metrics dashboard to view the details of Schema Registry service in Hadoopcluster.

Slider MetricsUse the Slider Metrics dashboard to view the details of Slider client in Hadoop cluster.

SmartSense MetricsUse the SmartSense Metrics dashboard to view the details of SmartSense service in the Hadoopcluster.

Solr MetricsUse the Solr Metrics dashboard to view the details of Solr service in Hadoop cluster.

SparkUse the Spark Metrics dashboard to view the details of Spark service in Hadoop cluster.

Sqoop MetricsUse the Sqoop Metrics dashboard to view the details of Sqoop client in Hadoop cluster.

Streaming Analytics Manager MetricsUse the Streaming Analytics Manager Metrics dashboard to view the details of Streaming AnalyticsManager service in Hadoop cluster.

SummaryThe summary dashboard shows the overall status and availability of each monitored Hadoop cluster.Click anywhere on the group widget to drill down to open the Nodes Overview page. Review theresource usage and investigate any warning or critical thresholds. If the Events tab shows a warning orcritical status indicator, open the tab to see the open events and status for the application.

Superset MetricsUse the Superset Metrics dashboard to view the details of Superset service in Hadoop cluster.

Tez MetricsUse the Tez Metrics dashboard to view the details of Tez client in Hadoop cluster.

Titan MetricsUse the Titan Metrics dashboard to view the details of Titan client in Hadoop cluster.

Unified Console MetricsUse the Unified Console Metrics dashboard to view the details of Unified Console service in Hadoopcluster.

YARN MetricsUse the YARN Metrics dashboard to view the details of YARN service in Hadoop cluster.

ZooKeeper MetricsUse the ZooKeeper Metrics dashboard to view the details of ZooKeeper service in Hadoop cluster.

Dashboard in the Cloud APM console 5

Additional group widgetsThese pop-up group widgets are displayed after you click a group widget for more details. Some groupwidgets have links to more granular information in a popup widget, described here.

Widgets for the Default dashboard pagesAmbari Metrics

Use the Ambari Metrics dashboard to view the details of Ambari Metrics service in Hadoop cluster.The following widgets are available in this dashboard page:Ambari Metrics Service

The Ambari Metrics Service group widget provides a grid widget that displays information aboutthe component name, host name, service status and maintenance state of Ambari Metricscomponents in the Hadoop cluster, and the time when the Ambari Metrics information wascollected.

The following KPIs for the widget are derived from the attributes as described:

• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 AMBARIMETRICS data set.Derived from a singleattribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 AMBARIMETRICS data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings andstatus change indicators. This data is derived from the maintenance state attribute in the KH8AMBARIMETRICS data set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 AMBARIMETRICS data set.Derived from a single attribute.

• Service Status: The status of the service. This data is derived from the none attribute in the Nonedata set.The status of the service.

• Sort Service: The sorted status of the service. This data is derived from the none attribute in theNone data set.The sorted status of the service.

• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 AMBARIMETRICS data set.Derived from a single attribute.

• placeholder - in case there are none

Atlas MetricsUse the Atlas Metrics dashboard to view the details of Atlas service in Hadoop cluster.The following widgets are available in this dashboard page:Atlas Service

The Atlas Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Atlas components in theHadoop cluster, and the time when the Atlas information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 ATLAS data set.Derived from a single attribute.

• Host Name: Name of the host on which the service is running. This data is derived from the hostname attribute in the KH8 ATLAS data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 ATLASdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 ATLAS data set.Derived from a single attribute.




• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 ATLAS data set.Derived from a single attribute.


Big SQL MetricsUse the Big SQL Metrics dashboard to view the details of Big SQL service in Hadoop cluster.The following widgets are available in this dashboard page:Big SQL Service

The Big SQL Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Big SQL components in theHadoop cluster, and the time when the Big SQL information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 BIGSQL data set.Derived from a single attribute.

• Host Name: Name of the host on which the service is running. This data is derived from the hostname attribute in the KH8 BIGSQL data set.Derived from a single attribute.

• Maintenance State: Maintenance mode that decides whether to suppress alerts, warnings, andstatus change indicators. This data is derived from the maintenance state attribute in the KH8BIGSQL data set.Derived from a single attribute.

• Service Name: Name of the service that is being monitored. This data is derived from the servicename attribute in the KH8 BIGSQL data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 BIGSQL data set.Derived from a single attribute.


DataNode OverviewUse the DataNode Overview dashboard to know the following details of the Hadoop DataNodes:

• The trend of block operations, such as number of blocks that are read, written, and removed fromthe node

• The trend of the number of blocks that are read from the local and remote clients• The trend of the number of blocks that are written from the local and remote clients• The trend of the number of blocks that are replicated and removed• The trend of the average time that is required for heartbeat operations and time

The following widgets are available in this dashboard page:Blocks Overview

The Blocks Overview group widget provides a line chart that displays information about the blockoperations, such as the number of blocks written, read, replicated, and removed. The chart alsodisplays the number of blocks that are read from local and remote clients and number of blocksthat are written to local and remote clients.

Attention: The Nodes Overview page shows the warning or critical status due to the followingreasons:

• DataNode warning: Block read or block write operations are not performed on the DataNode.


• DataNode critical: Block read and block write operations are not performed on the DataNode.


• Read Blocks: The delta of blocks read from DataNode. This data is derived from the BlocksReadattribute in the KH8 DATANODE data set.Derived from a single attribute.

• Reads From Local Client: The rate of change in number of read operations from local client. Thisdata is derived from the ReadsFromLocalClient attribute in the KH8 DATANODE data set.Derivedfrom a single attribute.

• Reads From Remote Client: The rate of change in number of read operations from remote client.This data is derived from the ReadsFromRemoteClient attribute in the KH8 DATANODE dataset.Derived from a single attribute.

• Removed Blocks: The number of process blocks that are removed from the DataNode. This datais derived from the BlocksRemoved attribute in the KH8 DATANODE data set.Derived from asingle attribute.

• Replicated Blocks: The number of process blocks that are replicated in the DataNode. This datais derived from the BlocksReplicated attribute in the KH8 DATANODE data set.Derived from asingle attribute.

• Timestamp: The time at which the data was collected. This data is derived from the collecttimestamp attribute in the KH8 DATANODE data set.Derived from a single attribute.

• Writes From Local Client: The rate of change in number of write operations from local client. Thisdata is derived from the WritesFromLocalClient attribute in the KH8 DATANODE data set.Derivedfrom a single attribute.

• Writes From Remote Client: The rate of change in number of write operations from remoteclient. This data is derived from the WritesFromRemoteClient attribute in the KH8 DATANODEdata set.Derived from a single attribute.

• Written Blocks: The delta of blocks written to DataNode. This data is derived from theBlocksWritten attribute in the KH8 DATANODE data set.Derived from a single attribute.


DataNodeThe DataNode group widget provides a line chart that displays the rate of change of data (in bytes)per second that is read from the DataNode, and the rate of change of data (in bytes) per secondthat is written on the DataNode.


• DataNode warning: Read or write operations are not performed on the DataNode.• DataNode critical: Read and write operations are not performed on the DataNode.


• Read (Bytes): The rate of change in amount of data (in bytes) read from DataNode. This datais derived from the BytesRead attribute in the KH8 DATANODE data set.Derived from a singleattribute.


• Written (Bytes): The rate of change in amount of data (in bytes) written to DataNode. This datais derived from the BytesWritten attribute in the KH8 DATANODE data set.Derived from a singleattribute.


Heartbeat Time (ms)The Heartbeat Time (ms) group widget provides a line chart that displays the average time (inmilliseconds) for heartbeat and heartbeat operation.



• Heartbeat Average Time: The rate of change in average Heartbeat time (in milliseconds) that isspent to complete the communication between the DataNode and the NameNode. This data isderived from the HeartbeatsAverageTime ms attribute in the KH8 DATANODE data set.Derivedfrom a single attribute.

• Heartbeat Operations: The delta of number of heartbeat operations. This data is derived fromthe HeartbeatsOperations attribute in the KH8 DATANODE data set.Derived from a singleattribute.



Druid MetricsUse the Druid Metrics dashboard to view the details of Druid Service in Hadoop cluster.The following widgets are available in this dashboard page:Druid Service

The Druid Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Druid components in theHadoop cluster, and the time when the Druid information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 DRUID data set.Derived from a single attribute.

• Host Name: Name of the host on which the service is running. This data is derived from the hostname attribute in the KH8 DRUID data set.Derived from a single attribute.

• Maintenance State: Maintenance mode that decides whether to suppress alerts, warnings, andstatus change indicators. This data is derived from the maintenance state attribute in the KH8DRUID data set.Derived from a single attribute.

• Service Name: Name of the service that is being monitored. This data is derived from the servicename attribute in the KH8 DRUID data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 DRUID data set.Derived from a single attribute.


Falcon MetricsUse the Falcon Metrics dashboard to view the details of Falcon service in Hadoop cluster.The following widgets are available in this dashboard page:Falcon Service

The Falcon Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Falcon components in theHadoop cluster, and the time when the Falcon information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 FALCON data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 FALCON data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 FALCONdata set.Derived from a single attribute.


• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 FALCON data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 FALCON data set.Derived from a single attribute.


File System DetailsUse the File System Details dashboard to know the following information about the HadoopDistributed File System:

• The rate of change in the number of files in the cluster• The number of blocks in the cluster, such as total, corrupt, missing, and excess• The percentage of HDFS capacity used• Information about the High Availability (HA) state• Information about the block capacity

The following widgets are available in this dashboard page:File System

The File System group widget provides a bullet chart that displays information about the usedcapacity of the Hadoop Distributed File System (HDFS) and information about blocks and blockscapacity. The chart also displays the information about the status of the High Availability node.

Attention: The Nodes Overview page shows the warning or critical status for the File System in thefollowing scenarios:

• File System warning: The percentage of used HDFS capacity is greater than 80 or the percentageof missing or corrupt blocks is greater than 20 or Standby NameNode is running but ActiveNameNode is down.

• File System critical: The percentage of used HDFS capacity is 90 or greater, or the percentage ofcorrupt or missing blocks is 50 or greater.


• Block Capacity (MB): The storage capacity of a block in MB. This data is derived from theBlockCapacityMB attribute in the KH8 FSNAMESYSTEM data set.Derived from a single attribute.

• HA State: The state of the high availability of the NameNode. This data is derived from theHasState attribute in the KH8 FSNAMESYSTEM data set.Derived from a single attribute.

• Percentage Of Capacity Used: The percentage of HDFS capacity used. This data is derived fromthe CapacityUsedPercent attribute in the KH8 FSNAMESYSTEM data set.Derived from a singleattribute.

• Percentage Of Corrupt Blocks: The percentage of corrupt blocks in HDFS. This data is derivedfrom the none attribute in the None data set.The percentage of corrupt blocks in HDFS.

• Percentage Of Missing Blocks: The percentage of missing blocks in HDFS. This data is derivedfrom the none attribute in the None data set.The percentage of missing blocks in HDFS.


File System OverviewThe File System Overview group widget provides a line chart that displays information about therate of change in the total number of files that are available in the cluster. The chart also displaysinformation about the blocks in the cluster, such as total, excess, corrupt, and missing.



• Corrupt: The number of corrupt blocks in the cluster. This data is derived from the CorruptBlocksattribute in the KH8 FSNAMESYSTEM data set.Derived from a single attribute.

• Excess: The number of excess blocks in the cluster. This data is derived from the ExcessBlocksattribute in the KH8 FSNAMESYSTEM data set.Derived from a single attribute.

• Missing: The number of missing blocks in the cluster. This data is derived from the MissingBlocksattribute in the KH8 FSNAMESYSTEM data set.Derived from a single attribute.

• Rate Of Change in Total Files: The delta of number of files and directories. This data is derivedfrom the TotalFiles attribute in the KH8 FSNAMESYSTEM data set.Derived from a singleattribute.

• Timestamp: The time at which the data was collected. This data is derived from the collecttimestamp attribute in the KH8 FSNAMESYSTEM data set.Derived from a single attribute.

• Total Blocks: The number of blocks in the cluster. This data is derived from the BlocksTotalattribute in the KH8 FSNAMESYSTEM data set.Derived from a single attribute.


Flume MetricsUse the Flume Metrics dashboard to view the details of Flume service in Hadoop cluster.The following widgets are available in this dashboard page:Flume Service

The Flume Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Flume components in theHadoop cluster, and the time when the Flume information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 FLUME data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 FLUME data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 FLUMEdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 FLUME data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 FLUME data set.Derived from a single attribute.


HBase MetricsUse the HBase Metrics dashboard to view the details of HBase service in Hadoop cluster.The following widgets are available in this dashboard page:HBase Service

The HBase Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of HBase components in theHadoop cluster, and the time when the HBase information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 HBASE data set.Derived from a single attribute.


• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 HBASE data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 HBASEdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 HBASE data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 HBASE data set.Derived from a single attribute.


HDFS MetricsUse the HDFS Metrics dashboard to view the details of Hadoop Distributed File System(HDFS) servicein Hadoop cluster.The following widgets are available in this dashboard page:HDFS Service

The HDFS Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Hadoop Distributed FileSystem (HDFS) components in the Hadoop cluster, and the time when the Hadoop Distributed FileSystem (HDFS) information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 HDFS data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 HDFS data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 HDFSdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 HDFS data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 HDFS data set.Derived from a single attribute.


Hive MetricsUse the Hive Metrics dashboard to view the details of Hive service in Hadoop cluster.The following widgets are available in this dashboard page:Hive Service

The Hive Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Hive components in theHadoop cluster, and the time when the Hive information was collected.



• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 HIVE data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 HIVE data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 HIVEdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 HIVE data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 HIVE data set.Derived from a single attribute.


JVM Memory DetailsUse the JVM Memory Details dashboard to know the following details of a Java virtual machine (JVM)in the cluster:

• The memory heap details for a node• Information about the number of threads and logs for a node• Comparative information about memory heap and non-heap usage for a particular node• The historical trend per daemon on a node

The following widgets are available in this dashboard page:History

The History group widget provides a grid widget that displays the list of daemons used by theselected nodes.


• Daemons: The name of the process of the node in the cluster. This data is derived from theProcessName attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.


JVM OverviewThe JVM Overview group widget provides a bar chart that displays information about the amountof heap and non-heap memory (in MB) that is used by all the nodes in the cluster.

Attention: The Nodes Overview page shows the warning or critical status for the Java virualmachines due to these reasons:

• JVM warning status: The percentage of heap or nonheap memory that is used for any of theHadoop daemons is greater than 80.

• JVM critical status: The percentage of heap or nonheap memory that is used for any of theHadoop daemons is 90 or greater.


• Heap Committed (MB): The heap memory (in MB) that is committed by the Java Virtual Machineof the daemon. This data is derived from the MemoryHeapCommittedMB attribute in the KH8JVMMETRICS data set.Derived from a single attribute.

• Heap Used (MB): The heap memory (in MB) that is used by the Java Virtual Machine of thedaemon. This data is derived from the MemoryHeapUsedMB attribute in the KH8 JVMMETRICSdata set.Derived from a single attribute.


• Max Memory (MB): The maximum amount of memory (in MB) that is assigned to the Java VirtualMachine of the daemon. This data is derived from the MemoryMaximumMB attribute in the KH8JVMMETRICS data set.Derived from a single attribute.

• Non Heap Committed (MB): The non-heap memory (in MB) that is committed by the Java VirtualMachine of the daemon. This data is derived from the MemoryNonHeapCommittedMB attributein the KH8 JVMMETRICS data set.Derived from a single attribute.

• Non Heap Used (MB): The non-heap memory (in MB) that is used by Java Virtual Machineof the daemon. This data is derived from the MemoryNonHeapUsedMB attribute in the KH8JVMMETRICS data set.Derived from a single attribute.

• Process Name: The name of the process of the node in the cluster. This data is derived from theProcessName attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.


Memory DetailsThe Memory Details group widget provides a bar chart that displays the memory heap and non-heap information.


• Memory Heap Committed (MB): The heap memory (in MB) that is committed by the Java VirtualMachine of the daemon. This data is derived from the MemoryHeapCommittedMB attribute inthe KH8 JVMMETRICS data set.Derived from a single attribute.

• Memory Heap Used (MB): The heap memory (in MB) that is used by the Java Virtual Machineof the daemon. This data is derived from the MemoryHeapUsedMB attribute in the KH8JVMMETRICS data set.Derived from a single attribute.

• Non Heap Free (MB): The non heap memory (in MB) that is available in the node of the cluster.This data is derived from the MemoryNonHeapFreeMB attribute in the KH8 JVMMETRICS dataset.Derived from a single attribute.


• Process Name: The name of the process of the node in the cluster. This data is derived from theProcessName attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.


Threads and LogsThe Threads and Logs group widget provides a bar chart that displays the number and status ofthreads, such as new, runnable, blocked, waiting, timed waiting, and terminated. The chart alsodisplays the log information, such as fatal, error, and warning.


• Blocked: The number of threads that are in the blocked state. This data is derived from theThreadsBlocked attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• Error: The number of logs that are in the error state. This data is derived from the LogErrorattribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• Fatal: The number of logs that are in the fatal state. This data is derived from the LogFatalattribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• New Threads: The number of new threads that are available in the cluster. This data is derivedfrom the ThreadsNew attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• ProcessName: The name of the process of the node in the cluster. This data is derived from theProcessName attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• Runnable : The number of threads that are in the runnable state. This data is derived from theThreadsRunnable attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• Terminated: The number of terminated threads. This data is derived from theThreadsTerminated attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.


• Timed Waiting: The number of threads that are in the timed waiting state. This data is derivedfrom the ThreadsTimedWaiting attribute in the KH8 JVMMETRICS data set.Derived from a singleattribute.

• Waiting: The number of threads that are in the waiting state. This data is derived from theThreadsWaiting attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• Warning: The number of logs that are in the warning state. This data is derived from the LogWarnattribute in the KH8 JVMMETRICS data set.Derived from a single attribute.


JVM Memory HistoryUse the JVM Memory History dashboard to know the following details of a JVM in the cluster:

• The historical trend of the memory heap details for a selected daemon• The historical trend of the number of threads and logs for a selected daemon• The historical trend of the comparative information about memory heap and non-heap usage for a

selected daemon

The following widgets are available in this dashboard page:History

The History group widget provides a grid widget that displays the list of daemons used by theselected nodes.


• Daemons: The name of the process of the node in the cluster. This data is derived from theProcessName attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.


JVM Overview (History)The JVM Overview (History) group widget provides a line chart that displays the historicalinformation about the amount of memory (in MB) that is used by the selected daemons in thecluster.


• Heap Committed (MB): The heap memory (in MB) that is committed by the Java Virtual Machineof the daemon. This data is derived from the MemoryHeapCommittedMB attribute in the KH8JVMMETRICS data set.Derived from a single attribute.

• Heap Used (MB): The heap memory (in MB) that is used by the Java Virtual Machine of thedaemon. This data is derived from the MemoryHeapUsedMB attribute in the KH8 JVMMETRICSdata set.Derived from a single attribute.

• Max Memory(MB): The maximum amount of memory (in MB) that is assigned to the Java VirtualMachine of the daemon. This data is derived from the MemoryMaximumMB attribute in the KH8JVMMETRICS data set.Derived from a single attribute.

• Non Heap Committed (MB): The non-heap memory (in MB) that is committed by the Java VirtualMachine of the daemon. This data is derived from the MemoryNonHeapCommittedMB attributein the KH8 JVMMETRICS data set.Derived from a single attribute.


• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.


Memory Details (History)The Memory Details (History) group widget provides a line chart that displays the historicalinformation about the heap and non-heap memory (in MB) that is used for the selected daemons.



• Memory Heap Committed (MB): The heap memory (in MB) that is committed by the Java VirtualMachine of the daemon. This data is derived from the MemoryHeapCommittedMB attribute inthe KH8 JVMMETRICS data set.Derived from a single attribute.

• Memory Heap Used (MB): The heap memory (in MB) that is used by the Java Virtual Machineof the daemon. This data is derived from the MemoryHeapUsedMB attribute in the KH8JVMMETRICS data set.Derived from a single attribute.

• Non Heap Free (MB): The non heap memory (in MB) that is available in the node of the cluster.This data is derived from the MemoryNonHeapFreeMB attribute in the KH8 JVMMETRICS dataset.Derived from a single attribute.




Threads and Logs (History)The Threads and Logs (History) group widget provides a line chart that displays the numberof threads and the historical status of threads, such as new, runnable, blocked, waiting, timedwaiting, and terminated for a selected daemon. The chart also displays the historical informationabout the log, such as fatal, error, and warning for a selected daemon.


• Blocked: The number of threads that are in the blocked state. This data is derived from theThreadsBlocked attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• Error: The number of logs that are in the error state. This data is derived from the LogErrorattribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• Fatal: The number of logs that are in the fatal state. This data is derived from the LogFatalattribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• New: The number of new threads that are available in the cluster. This data is derived from theThreadsNew attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• Runnable : The number of threads that are in the runnable state. This data is derived from theThreadsRunnable attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• Terminated: The number of terminated threads. This data is derived from theThreadsTerminated attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.


• Timed Waiting: The number of threads that are in the timed waiting state. This data is derivedfrom the ThreadsTimedWaiting attribute in the KH8 JVMMETRICS data set.Derived from a singleattribute.

• Waiting: The number of threads that are in the waiting state. This data is derived from theThreadsWaiting attribute in the KH8 JVMMETRICS data set.Derived from a single attribute.

• Warning: The number of logs that are in the warning state. This data is derived from the LogWarnattribute in the KH8 JVMMETRICS data set.Derived from a single attribute.


Kafka MetricsUse the Kafka Metrics dashboard to view the details of Kafka service in Hadoop cluster.The following widgets are available in this dashboard page:


Kafka ServiceThe Kafka Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Kafka components in theHadoop cluster, and the time when the Kafka information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 KAFKA data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 KAFKA data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 KAFKAdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 KAFKA data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 KAFKA data set.Derived from a single attribute.


Knox MetricsUse the Knox Metrics dashboard to view the details of Knox service in Hadoop cluster.The following widgets are available in this dashboard page:Knox Service

The Knox Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Knox components in theHadoop cluster, and the time when the Knox information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 KNOX data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 KNOX data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 KNOXdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 KNOX data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 KNOX data set.Derived from a single attribute.


Mahout MetricsUse the Mahout Metrics dashboard to view the details of Mahout client in Hadoop cluster.The following widgets are available in this dashboard page:


Mahout ServiceThe Mahout Tool group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Mahout components in theHadoop cluster, and the time when the Mahout information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 MAHOUT data set.Derived from a singleattribute.

• Host Name: Name of the host on which the service is running. This data is derived from the hostname attribute in the KH8 MAHOUT data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings andstatus change indicators. This data is derived from the maintenance state attribute in the KH8MAHOUT data set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 MAHOUT data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 MAHOUT data set.Derived from a single attribute.


MapReduce2 MetricsUse the MapReduce2 Metrics dashboard to view the details of MapReduce2 service in Hadoop cluster.The following widgets are available in this dashboard page:MapReduce2 Service

The MapReduce2 Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of MapReduce2 componentsin the Hadoop cluster, and the time when the MapReduce2 information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 MAPREDUCE2 data set.Derived from a singleattribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 MAPREDUCE2 data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings andstatus change indicators. This data is derived from the maintenance state attribute in the KH8MAPREDUCE2 data set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 MAPREDUCE2 data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 MAPREDUCE2 data set.Derived from a single attribute.


NiFi MetricsUse the NiFi Metrics dashboard to view the details of NiFi service in Hadoop cluster.


The following widgets are available in this dashboard page:NiFi Service

The NiFi Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of NiFi components in theHadoop cluster, and the time when the NiFi information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 NIFI data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 NIFI data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 NIFIdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 NIFI data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 NIFI data set.Derived from a single attribute.


NiFi Registry MetricsUse the NiFi Registry Metrics dashboard to view the details of NiFi Registry service in Hadoop cluster.The following widgets are available in this dashboard page:NiFi Registry Service

The NiFi Registry Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of NiFi Registry componentsin the Hadoop cluster, and the time when the NiFi Registry information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 NIFIREGISTRY data set.Derived from a singleattribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 NIFIREGISTRY data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings andstatus change indicators. This data is derived from the maintenance state attribute in the KH8NIFIREGISTRY data set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 NIFIREGISTRY data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 NIFIREGISTRY data set.Derived from a single attribute.



Nodes OverviewUse the Nodes Overview dashboard to know the details of nodes in the Hadoop cluster, such as thesubnode name and status of the Java virtual machine, Queue, File System, Remote Procedure Calls(RPC), DataNode, and Hadoop services and their status.The following widgets are available in this dashboard page:Top 100 Nodes Overview Status

The Top 100 Nodes Overview Status group widget provides a grid widget that displays informationabout the Hadoop nodes, such as the subnode name, the status of the Java Virtual Machine (JVM),File System, Remote Procedure Call (Rpc), DataNode, and Queue for a host name. It also displaysHadoop services for Ambari and their status.


• DataNode: The status of the DataNode. This data is derived from the none attribute in the Nonedata set.The status of the DataNode.

• File System: The file system status. This data is derived from the none attribute in the None dataset.The file system status.

• Host Name: The resource name of this subnode. This data is derived from the SubnodeResource Name attribute in the KH8 HOSTS NODES data set.Derived from a single attribute.

• JVM: The status of the Java virtual machine (JVM). This data is derived from the none attributein the None data set.The status of the Java virtual machine (JVM).

• Queue: The status of the queue process. This data is derived from the none attribute in the Nonedata set.The status of the queue process.

• RPC: The status of the remote procedure call. This data is derived from the none attribute in theNone data set.The status of the remote procedure call.

• Service Name: Name of the Ambari services/components available in Hadoop Clustermonitored by Hadoop agent. This data is derived from the ServiceName attribute in the KH8SERVICESOVERVIEW data set.Derived from a single attribute.


• Sort Service: For sorting the service status. This data is derived from the none attribute in theNone data set.For sorting the service status.


Oozie MetricsUse the Oozie Metrics dashboard to view the details of Oozie service in Hadoop cluster.The following widgets are available in this dashboard page:Oozie Service

The Oozie Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Oozie components in theHadoop cluster, and the time when the Oozie information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 OOZIE data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 OOZIE data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 OOZIEdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 OOZIE data set.Derived from a single attribute.




• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 OOZIE data set.Derived from a single attribute.


Pig MetricsUse the Pig Metrics dashboard to view the details of Pig client in Hadoop cluster.The following widgets are available in this dashboard page:Pig Tool

The Pig Tool group widget provides a grid widget that displays information about the componentname, host name, service status and maintenance state of Pig components in the Hadoop cluster,and the time when the Pig information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 PIG data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 PIG data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 PIG dataset.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 PIG data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 PIG data set.Derived from a single attribute.


Queue DetailsUse the Queue Details dashboard to know the following details of a queue:

• Information about the status of an application, such as submitted, running, and pending for the topnine queues in the cluster

• Information about the memory status, such as reserved, pending, allocated, and available for thetop nine queues in the cluster

• Information about all the applications in the cluster• Historical trend of the application status and the memory status for a selected queue

The following widgets are available in this dashboard page:Applications

The Applications group widget provides a grid widget that displays information about the statusof the applications, such as submitted, running, pending, killed, failed, and completed. The groupwidget also displays information about the status of memory usage by the applications, such aspending, allocated, reserved, and available.



• Allocated: The amount of allocated memory (in MB) for a queue. This data is derived fromthe AllocatedSpaceMB attribute in the KH8 QUEUEMETRICS data set.Derived from a singleattribute.

• Apps Pending: The number of applications that are in the pending state. This data is derivedfrom the ApplicationsPending attribute in the KH8 QUEUEMETRICS data set.Derived from asingle attribute.

• Available: The amount of available memory (in MB) for a queue. This data is derived from theAvailableSpaceMB attribute in the KH8 QUEUEMETRICS data set.Derived from a single attribute.

• Completed: The number of completed applications. This data is derived from theApplicationsCompleted attribute in the KH8 QUEUEMETRICS data set.Derived from a singleattribute.

• Failed: The number of applications in failed state. This data is derived from theApplicationsFailed attribute in the KH8 QUEUEMETRICS data set.Derived from a single attribute.

• Killed: The number of applications that are killed in the cluster. This data is derived from theApplicationsKilled attribute in the KH8 QUEUEMETRICS data set.Derived from a single attribute.

• Memory Pending: The amount of pending memory (in MB) in a queue. This data is derived fromthe PendingSpaceMB attribute in the KH8 QUEUEMETRICS data set.Derived from a singleattribute.

• Queue: Full Queue path name. This data is derived from the QueueName attribute in the KH8QUEUEMETRICS data set.Derived from a single attribute.

• Reserved: The amount of reserved memory (in MB) in a queue. This data is derived from theReservedSpaceMB attribute in the KH8 QUEUEMETRICS data set.Derived from a single attribute.

• Running: The number of applications that are in the running state. This data is derived fromthe ApplicationsRunning attribute in the KH8 QUEUEMETRICS data set.Derived from a singleattribute.

• Short Queue Name: Short Queue name. This data is derived from the ShortQueueName attributein the KH8 QUEUEMETRICS data set.Derived from a single attribute.

• Submitted: The number of submitted applications in the cluster. This data is derived from theApplicationsSubmitted attribute in the KH8 QUEUEMETRICS data set.Derived from a singleattribute.

• User: Name of the user. This data is derived from the User attribute in the KH8 QUEUEMETRICSdata set.Derived from a single attribute.


Applications - Top 9The Applications - Top 9 group widget provides a bar chart that displays information about thestatus of applications, such as submitted, running, pending, killed, failed, and completed.

Attention: The Nodes Overview page shows the warning or critical Queue status due to thefollowing reasons:

• Queue warning: The percentage of applications that are killed or failed is greater than 20percent.

• Queue critical: The percentage of applications that are killed or failed is 50 percent or greater.






• Pending: The number of applications that are in the pending state. This data is derived fromthe ApplicationsPending attribute in the KH8 QUEUEMETRICS data set.Derived from a singleattribute.





Memory - Top 9The Memory - Top 9 group widget provides a bar chart information about the memory status for aselected queue, such as pending, allocated, available, and reserved.


• Queue warning: The percentage usage of the allocated memory is greater than 80 percent.• Queue critical: The percentage usage of the allocated memory is 90 percent or greater.




• Pending: The amount of pending memory (in MB) in a queue. This data is derived from thePendingSpaceMB attribute in the KH8 QUEUEMETRICS data set.Derived from a single attribute.




Ranger MetricsUse the Ranger Metrics dashboard to view the details of Ranger service in Hadoop cluster.The following widgets are available in this dashboard page:Ranger Service

The Ranger Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Ranger components in theHadoop cluster, and the time when the Ranger information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 RANGER data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 RANGER data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 RANGERdata set.Derived from a single attribute.


• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 RANGER data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 RANGER data set.Derived from a single attribute.


RPC DetailsUse the RPC Details dashboard to know the following details of a RPC in the cluster:

• The amount of data that is sent and received through the first nine ports• The amount of data that is sent and received through all ports• The RPC authentication and authorization details for the first nine ports• The RPC authentication and authorization details for all ports• The average queue time and process time for the first nine ports• The average queue time and process time for all ports• The number of open connections for the first nine ports• The number of open connections for all ports

The following widgets are available in this dashboard page:Average Time in RPC (ms)

The Average Time in RPC (ms) group widget provides a bar chart that displays the average queuetime and average processing time for the first nine ports.


• Average Processing Time: The average time that is required for processing RPC requests.This data is derived from the RpcProcessingAverageTime ms attribute in the KH8 RPC dataset.Derived from a single attribute.

• Average Queue Time: The average time that is spent by an RPC request in the queue. This datais derived from the RpcQueueAverageTime ms attribute in the KH8 RPC data set.Derived from asingle attribute.

• Port: The port number that is used to connect to the Hadoop cluster. This data is derived fromthe Port attribute in the KH8 RPC data set.Derived from a single attribute.


Average Time in RPC (ms)The Average Time in RPC (ms) group widget provides a grid widget that displays the averageprocess time and average queue time for RPC requests.


• Average Processing Time: The average time that is required for processing RPC requests.This data is derived from the RpcProcessingAverageTime ms attribute in the KH8 RPC dataset.Derived from a single attribute.

• Average Queue Time: The average time that is spent by an RPC request in the queue. This datais derived from the RpcQueueAverageTime ms attribute in the KH8 RPC data set.Derived from asingle attribute.

• Port Number: The port number that is used to connect to the Hadoop cluster. This data isderived from the Port attribute in the KH8 RPC data set.Derived from a single attribute.



Open ConnectionsThe Open Connections group widget provides a bar chart that displays the number of openconnections at the first nine ports in the cluster.

Attention: The Nodes Overview page shows the warning status because open connections are notavailable on any of the ports of this node.


• Open Connections: The number of open connections on a port in the cluster. This data is derivedfrom the OpenConnections attribute in the KH8 RPC data set.Derived from a single attribute.



Open ConnectionsThe Open Connections group widget provides a grid widget that displays the number of openconnections at every port in the cluster.


• Number of Open Connections: The number of open connections on a port in the cluster. Thisdata is derived from the OpenConnections attribute in the KH8 RPC data set.Derived from asingle attribute.



RPC Authentication or AuthorizationThe RPC Authentication or Authorization group widget provides a bar chart that displays thenumber of Remote Procedure Call (RPC) authentication and authorization calls that failed for thefirst nine ports in the cluster.

Attention : The Nodes Overview page shows the warning status during the following conditions:

• Sum of authentication successes for all ports is zero and sum of authentication failures for allports is not zero.

• Sum of authorization successes for all ports is zero and sum of authorization failures for all portsis not zero.

• Sum of authentication failures for all ports is greater than the sum of authentication successesfor all ports.

• Sum of authorization failures for all ports is greater than the sum of authorization successes forall ports.


• Authentication Failures: The number of failed RPC authentication calls. This data is derived fromthe RpcAuthenticationFailures attribute in the KH8 RPC data set.Derived from a single attribute.

• Authorization Failures: The number of failed RPC authorization calls. This data is derived fromthe RpcAuthorizationFailures attribute in the KH8 RPC data set.Derived from a single attribute.



RPC Authentication or AuthorizationThe RPC Authentication or Authorization group widget provides a grid widget that displays thenumber of RPC authentication and authorization calls that failed for all ports in the cluster.



• Authentication Failures: The number of failed RPC authentication calls. This data is derived fromthe RpcAuthenticationFailures attribute in the KH8 RPC data set.Derived from a single attribute.

• Authorization Failures: The number of failed RPC authorization calls. This data is derived fromthe RpcAuthorizationFailures attribute in the KH8 RPC data set.Derived from a single attribute.



RPC OverviewThe RPC Overview group widget provides a bar chart that displays the amount of data (in MB) thatis sent and received by the node through the first nine ports.

Attention: The Nodes Overview page shows the warning status when read or write operations arenot performed on any of the ports of the node.



• Received: The number of RPC bytes (in MB) received by the node. This data is derived from theReceivedBytesMB attribute in the KH8 RPC data set.Derived from a single attribute.

• Sent: The number of RPC bytes (in MB) sent by the node. This data is derived from theSentBytesMB attribute in the KH8 RPC data set.Derived from a single attribute.


RPC OverviewThe RPC Overview group widget provides a grid widget that displays information about the portsand the amount of data (in MB) that is sent and received by the node on each port.



• Received (MB): The number of RPC bytes (in MB) received by the node. This data is derived fromthe ReceivedBytesMB attribute in the KH8 RPC data set.Derived from a single attribute.

• Sent (MB): The number of RPC bytes (in MB) sent by the node. This data is derived from theSentBytesMB attribute in the KH8 RPC data set.Derived from a single attribute.


Schema Registry MetricsUse the Schema Registry Metrics dashboard to view the details of Schema Registry service in Hadoopcluster.The following widgets are available in this dashboard page:Schema Registry Service

The Schema Registry Service group widget provides a grid widget that displays information aboutthe component name, host name, service status and maintenance state of Schema Registrycomponents in the Hadoop cluster, and the time when the Schema Registry information wascollected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 SCHEMAREGISTRY data set.Derived from asingle attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 SCHEMAREGISTRY data set.Derived from a single attribute.


• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings andstatus change indicators. This data is derived from the maintenance state attribute in the KH8SCHEMAREGISTRY data set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 SCHEMAREGISTRY data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 SCHEMAREGISTRY data set.Derived from a single attribute.


Slider MetricsUse the Slider Metrics dashboard to view the details of Slider client in Hadoop cluster.The following widgets are available in this dashboard page:Slider Tool

The Slider Tool group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Slider components in theHadoop cluster, and the time when the Slider information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 SLIDER data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 SLIDER data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 SLIDERdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 SLIDER data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 SLIDER data set.Derived from a single attribute.


SmartSense MetricsUse the SmartSense Metrics dashboard to view the details of SmartSense service in the Hadoopcluster.The following widgets are available in this dashboard page:SmartSense Service

The SmartSense Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of SmartSense components inthe Hadoop cluster, and the time when the SmartSense information was collected.


• Component Name: Name of the component that is associated with the service. This data isderived from the component name attribute in the KH8 SMARTSENSE data set.Derived from asingle attribute.


• Host Name: Name of the host on which the service is running. This data is derived from the hostname attribute in the KH8 SMARTSENSE data set.Derived from a single attribute.

• Maintenance State: Maintenance mode that decides whether to suppress alerts, warnings, andstatus change indicators. This data is derived from the maintenance state attribute in the KH8SMARTSENSE data set.Derived from a single attribute.

• Service Name: Name of the service that is being monitored. This data is derived from the servicename attribute in the KH8 SMARTSENSE data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 SMARTSENSE data set.Derived from a single attribute.


Solr MetricsUse the Solr Metrics dashboard to view the details of Solr service in Hadoop cluster.The following widgets are available in this dashboard page:Solr Service

The Solr Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Solr components in theHadoop cluster, and the time when the Solr information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 SOLR data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 SOLR data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 SOLRdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 SOLR data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 SOLR data set.Derived from a single attribute.


SparkUse the Spark Metrics dashboard to view the details of Spark service in Hadoop cluster.The following widgets are available in this dashboard page:Spark Metrics Service

The Spark Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Spark components in theHadoop cluster, and the time when the Spark information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 SPARK data set.Derived from a single attribute.


• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 SPARK data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 SPARKdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 SPARK data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 SPARK data set.Derived from a single attribute.


Sqoop MetricsUse the Sqoop Metrics dashboard to view the details of Sqoop client in Hadoop cluster.The following widgets are available in this dashboard page:Sqoop Tool

The Sqoop Tool group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Sqoop components in theHadoop cluster, and the time when the Sqoop information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 SQOOP data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 SQOOP data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 SQOOPdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 SQOOP data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 SQOOP data set.Derived from a single attribute.


Streaming Analytics Manager MetricsUse the Streaming Analytics Manager Metrics dashboard to view the details of Streaming AnalyticsManager service in Hadoop cluster.The following widgets are available in this dashboard page:Streaming Analytics Manager Service

The Streaming Analytics Manager Service group widget provides a grid widget that displaysinformation about the component name, host name, service status and maintenance stateof Streaming Analytics Manager components in the Hadoop cluster, and the time when theStreaming Analytics Manager information was collected.



• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 STREAMINGANALYTICSMANAGER dataset.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 STREAMINGANALYTICSMANAGER data set.Derived from a singleattribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings andstatus change indicators. This data is derived from the maintenance state attribute in the KH8STREAMINGANALYTICSMANAGER data set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 STREAMINGANALYTICSMANAGER data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 STREAMINGANALYTICSMANAGER data set.Derived from asingle attribute.


SummaryThe summary dashboard shows the overall status and availability of each monitored Hadoop cluster.Click anywhere on the group widget to drill down to open the Nodes Overview page. Review theresource usage and investigate any warning or critical thresholds. If the Events tab shows a warning orcritical status indicator, open the tab to see the open events and status for the application.The following widgets are available in this dashboard page:Hadoop Summary

The Hadoop Summary group widget provides information about the overall health of the Hadoopcluster, such as number of Hadoop nodes, and the status of Java virtual machine (JVM), FileSystem, DataNode, Remote Procedure Call (RPC), and queue. The group widget also providesinformation about the status of Hadoop services, like Zookeeper, HDFS, Ambari-Metrics forAmbari based Hadoop installations.


• DataNode status (Critical): The status of the DataNode, such as normal, warning,critical or unknown. This data is derived from the DatanodeStatus attribute in the KH8CLUSTEROVERVIEW data set.Derived from a single attribute.

• DataNode status (Normal): The status of the DataNode, such as normal, warning,critical or unknown. This data is derived from the DatanodeStatus attribute in the KH8CLUSTEROVERVIEW data set.Derived from a single attribute.

• DataNode status (Unknown): The status of the DataNode, such as normal, warning,critical or unknown. This data is derived from the DatanodeStatus attribute in the KH8CLUSTEROVERVIEW data set.Derived from a single attribute.

• DataNode status (Warning): The status of the DataNode, such as normal, warning,critical or unknown. This data is derived from the DatanodeStatus attribute in the KH8CLUSTEROVERVIEW data set.Derived from a single attribute.

• File System status (Critical): The status of the file system, such as normal, warning,critical or unknown. This data is derived from the FileSystemStatus attribute in the KH8CLUSTEROVERVIEW data set.Derived from a single attribute.

• File System status (Normal): The status of the file system, such as normal, warning,critical or unknown. This data is derived from the FileSystemStatus attribute in the KH8CLUSTEROVERVIEW data set.Derived from a single attribute.


• File System status (Unknown): The status of the file system, such as normal, warning,critical or unknown. This data is derived from the FileSystemStatus attribute in the KH8CLUSTEROVERVIEW data set.Derived from a single attribute.

• File System status (Warning): The status of the file system, such as normal, warning,critical or unknown. This data is derived from the FileSystemStatus attribute in the KH8CLUSTEROVERVIEW data set.Derived from a single attribute.

• Hadoop nodes: The IP address of the Hadoop node. The IP address must be mapped to thehost name in the hosts file, which is available on the node where the agent is installed. If thismapping is not provided in the hosts file, the IP address will be same as host name. This data isderived from the IP Address attribute in the KH8 CLUSTEROVERVIEW data set.Derived from asingle attribute.

• JVM status (Critical): The status of the Java virtual Machine, such as normal, warning, critical orunknown. This data is derived from the JVMStatus attribute in the KH8 CLUSTEROVERVIEW dataset.Derived from a single attribute.

• JVM status (Normal): The status of the Java virtual Machine, such as normal, warning, critical orunknown. This data is derived from the JVMStatus attribute in the KH8 CLUSTEROVERVIEW dataset.Derived from a single attribute.

• JVM status (Unknown): The status of the Java virtual Machine, such as normal, warning, criticalor unknown. This data is derived from the JVMStatus attribute in the KH8 CLUSTEROVERVIEWdata set.Derived from a single attribute.

• JVM status (Warning): The status of the Java virtual Machine, such as normal, warning, critical orunknown. This data is derived from the JVMStatus attribute in the KH8 CLUSTEROVERVIEW dataset.Derived from a single attribute.

• Queue status (Critical): The status of the Process Queue, such as normal, warning, critical orunknown. This data is derived from the QueueStatus attribute in the KH8 CLUSTEROVERVIEWdata set.Derived from a single attribute.

• Queue status (Normal): The status of the Process Queue, such as normal, warning, critical orunknown. This data is derived from the QueueStatus attribute in the KH8 CLUSTEROVERVIEWdata set.Derived from a single attribute.

• Queue status (Unknown): The status of the Process Queue, such as normal, warning, critical orunknown. This data is derived from the QueueStatus attribute in the KH8 CLUSTEROVERVIEWdata set.Derived from a single attribute.

• Queue status (Warning): The status of the Process Queue, such as normal, warning, critical orunknown. This data is derived from the QueueStatus attribute in the KH8 CLUSTEROVERVIEWdata set.Derived from a single attribute.

• RPC status (Critical): The status of the Remote Procedure Call, such as normal, warning, criticalor unknown. This data is derived from the RpcStatus attribute in the KH8 CLUSTEROVERVIEWdata set.Derived from a single attribute.

• RPC status (Normal): The status of the Remote Procedure Call, such as normal, warning, criticalor unknown. This data is derived from the RpcStatus attribute in the KH8 CLUSTEROVERVIEWdata set.Derived from a single attribute.

• RPC status (Unknown): The status of the Remote Procedure Call, such as normal,warning, critical or unknown. This data is derived from the RpcStatus attribute in the KH8CLUSTEROVERVIEW data set.Derived from a single attribute.

• RPC status (Warning): The status of the Remote Procedure Call, such as normal, warning, criticalor unknown. This data is derived from the RpcStatus attribute in the KH8 CLUSTEROVERVIEWdata set.Derived from a single attribute.

• Service Status (Normal): The service is up and running. This data is derived from theServiceStatus attribute in the KH8 SERVICESOVERVIEW data set.Derived from a single attribute.

• Service Status (Stopped): The status of the service is stopped. This data is derived from theServiceStatus attribute in the KH8 SERVICESOVERVIEW data set.Derived from a single attribute.


• Service Status (Unknown): The status of the service is unknown. This data is derived from theServiceStatus attribute in the KH8 SERVICESOVERVIEW data set.Derived from a single attribute.

• Service Status (Warning): The service is in the warning state. This data is derived from theServiceStatus attribute in the KH8 SERVICESOVERVIEW data set.Derived from a single attribute.


Superset MetricsUse the Superset Metrics dashboard to view the details of Superset service in Hadoop cluster.The following widgets are available in this dashboard page:Superset Service

The Superset Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Superset components inthe Hadoop cluster, and the time when the Superset information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 SUPERSET data set.Derived from a singleattribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 SUPERSET data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings andstatus change indicators. This data is derived from the maintenance state attribute in the KH8SUPERSET data set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 SUPERSET data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 SUPERSET data set.Derived from a single attribute.


Tez MetricsUse the Tez Metrics dashboard to view the details of Tez client in Hadoop cluster.The following widgets are available in this dashboard page:Tez Service

The Tez Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of Tez components in theHadoop cluster, and the time when the Tez information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 TEZ data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 TEZ data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 TEZ dataset.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 TEZ data set.Derived from a single attribute.




• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 TEZ data set.Derived from a single attribute.


Titan MetricsUse the Titan Metrics dashboard to view the details of Titan client in Hadoop cluster.The following widgets are available in this dashboard page:Titan Tool

The Titan Tool group widget provides a grid widget that displays information about the componentname, host name, service status and maintenance state of Titan components in the Hadoopcluster, and the time when the Titan information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 TITAN data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 TITAN data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 TITANdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 TITAN data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 TITAN data set.Derived from a single attribute.


Unified Console MetricsUse the Unified Console Metrics dashboard to view the details of Unified Console service in Hadoopcluster.The following widgets are available in this dashboard page:Unified Console Service

The Unified Console Service group widget provides a grid widget that displays information aboutthe component name, host name, service status and maintenance state of Unified Consolecomponents in the Hadoop cluster, and the time when the Unified Console information wascollected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 UNIFIEDCONSOLE data set.Derived from asingle attribute.

• Host Name: Name of the host on which the service is running. This data is derived from the hostname attribute in the KH8 UNIFIEDCONSOLE data set.Derived from a single attribute.

• Maintenance State: Maintenance mode that decides whether to suppress alerts, warnings, andstatus change indicators. This data is derived from the maintenance state attribute in the KH8UNIFIEDCONSOLE data set.Derived from a single attribute.

• Service Name: Name of the service that is being monitored. This data is derived from the servicename attribute in the KH8 UNIFIEDCONSOLE data set.Derived from a single attribute.




• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 UNIFIEDCONSOLE data set.Derived from a single attribute.


YARN MetricsUse the YARN Metrics dashboard to view the details of YARN service in Hadoop cluster.The following widgets are available in this dashboard page:YARN Service

The YARN Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of YARN components in theHadoop cluster, and the time when the YARN information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 YARN data set.Derived from a single attribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 YARN data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings and statuschange indicators. This data is derived from the maintenance state attribute in the KH8 YARNdata set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 YARN data set.Derived from a single attribute.



• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 YARN data set.Derived from a single attribute.


ZooKeeper MetricsUse the ZooKeeper Metrics dashboard to view the details of ZooKeeper service in Hadoop cluster.The following widgets are available in this dashboard page:ZooKeeper Service

The ZooKeeper Service group widget provides a grid widget that displays information about thecomponent name, host name, service status and maintenance state of ZooKeeper components inthe Hadoop cluster, and the time when the ZooKeeper information was collected.


• Component Name: Name of the component associated with the service. This data is derivedfrom the component name attribute in the KH8 ZOOKEEPER data set.Derived from a singleattribute.

• Host Name: Name of the host on which service is running. This data is derived from the hostname attribute in the KH8 ZOOKEEPER data set.Derived from a single attribute.

• Maintenance State: Maintenance Mode decides whether to suppress alerts, warnings andstatus change indicators. This data is derived from the maintenance state attribute in the KH8ZOOKEEPER data set.Derived from a single attribute.

• Service Name: Name of the service being monitored. This data is derived from the service nameattribute in the KH8 ZOOKEEPER data set.Derived from a single attribute.




• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 ZOOKEEPER data set.Derived from a single attribute.


Additional group widgetsThese pop-up group widgets are displayed after you click a group widget for more details. Some groupwidgets have links to more granular information in a popup widget, described here.The following widgets are available in this dashboard page:Applications (History)

The Applications (History) group widget provides a line chart that displays the historicalinformation about the status of applications, such as submitted, running, pending, killed, failed,and completed. The chart also displays the historical information about the memory status, suchas reserved, pending, allocated, and available.



• Applications Pending: The number of applications that are in the pending state. This data isderived from the ApplicationsPending attribute in the KH8 QUEUEMETRICS data set.Derivedfrom a single attribute.





• Memory Pending: The amount of pending memory (in MB) in a queue. This data is derived fromthe PendingSpaceMB attribute in the KH8 QUEUEMETRICS data set.Derived from a singleattribute.




• Time: The local time at the agent when the data was collected. This data is derived from theTimestamp attribute in the KH8 QUEUEMETRICS data set.Derived from a single attribute.



Custom viewsAfter you select an application that includes a Hadoop managed resource, the Custom Views tab isavailable for displaying and building custom dashboard pages with attribute values from the Hadoopagent. You can quickly build monitoring pages for an application and save them for viewing.

Only a subset of Hadoop agent attributes, which are the most useful for reporting, are available forcustom views. These attributes are shown in italic in Chapter 4, “Attributes,” on page 43.

Attribute detailsAfter you select a Hadoop managed resource instance, the Attribute Details tab is displayed in thedashboard. Open the tab to display options for creating a table or chart with attribute values from theHadoop data set that you select.


Chapter 3. Thresholds

Thresholds test for certain conditions on your managed resources, such as memory usage over 95%,and raise an event when the conditions have been met. The agent comes with predefined thresholds thatyou can use to monitor your Hadoop environment. You can create additional thresholds for the areas ofinterest.

After you click System Configuration > Threshold Manager, select Hadoop as the data source type tosee all the available thresholds.

Predefined thresholdsThe thresholds are organized in the Cloud APM console Threshold Manager by the data set for which theywere written. The Hadoop agent has the following predefined thresholds:KH8_Allocated_Memory_Critical

The percentage of allocated memory has reached the critical threshold.

The default configuration has the following SQL syntax:

*IF *VALUE KH8_QUEUEMETRICS.AllocatedMemoryPercent *GE 90

This threshold is evaluated every 1 minute.

The severity of this threshold is Critical.

The threshold is evaluated for each distinct value of the QueueName attribute.

This threshold uses the following attributes: QueueMetrics.AllocatedMemoryPercent[KH8QUEUEME.ALLOCATED0] (not visible in the UI), QueueMetrics.Hostname[KH8QUEUEME.HOSTNAME].

KH8_Allocated_Memory_WarningThe percentage of allocated memory has reached the warning threshold.


*IF *VALUE KH8_QUEUEMETRICS.AllocatedMemoryPercent *GT 80 *AND *VALUEKH8_QUEUEMETRICS.AllocatedMemoryPercent *LT 90


The severity of this threshold is Warning.


This threshold uses the following attributes: QueueMetrics.AllocatedMemoryPercent[KH8QUEUEME.ALLOCATED0] (not visible in the UI), QueueMetrics.Hostname[KH8QUEUEME.HOSTNAME].

KH8_Applications_Failed_CriticalThe percentage of applications that are in the failed state has exceeded the critical threshold.


*IF *VALUE KH8_QUEUEMETRICS.FailedApplicationsPercent *GE 50





This threshold uses the following attributes: QueueMetrics.FailedApplicationsPercent[KH8QUEUEME.FAILEDAPPL] (not visible in the UI), QueueMetrics.Hostname[KH8QUEUEME.HOSTNAME].

KH8_Applications_Failed_WarningThe percentage of applications that are in the failed state has reached the warning threshold.


*IF *VALUE KH8_QUEUEMETRICS.FailedApplicationsPercent *GT 20 *AND *VALUEKH8_QUEUEMETRICS.FailedApplicationsPercent *LT 50




This threshold uses the following attributes: QueueMetrics.FailedApplicationsPercent[KH8QUEUEME.FAILEDAPPL] (not visible in the UI), QueueMetrics.Hostname[KH8QUEUEME.HOSTNAME].

KH8_Applications_Killed_CriticalThe percentage of applications that are terminated in the cluster has exceeded the critical threshold.


*IF *VALUE KH8_QUEUEMETRICS.KilledApplicationsPercent *GE 50




This threshold uses the following attributes: QueueMetrics.KilledApplicationsPercent[KH8QUEUEME.KILLEDAPPS] (not visible in the UI), QueueMetrics.Hostname[KH8QUEUEME.HOSTNAME].

KH8_Applications_Killed_WarningThe percentage of applications that are terminated in the cluster has reached the warning threshold.


*IF *VALUE KH8_QUEUEMETRICS.KilledApplicationsPercent *GT 20 *AND *VALUEKH8_QUEUEMETRICS.KilledApplicationsPercent *LT 50




This threshold uses the following attributes: QueueMetrics.KilledApplicationsPercent[KH8QUEUEME.KILLEDAPPS] (not visible in the UI), QueueMetrics.Hostname[KH8QUEUEME.HOSTNAME].

KH8_Capacity_Used_CriticalThe percentage of capacity that is used for the Hadoop distributed File System (HDFS) has exceededthe critical threshold.


*IF *VALUE KH8_FSNAMESYSTEM.CapacityUsedPercent *GE 90



The threshold is evaluated for each distinct value of the Hostname attribute.


This threshold uses the following attributes: FSNamesystem.CapacityUsedPercent[KH8FSNAMES.CAPACITYU2], FSNamesystem.Hostname [KH8FSNAMES.HOSTNAME].

KH8_Capacity_Used_WarningThe percentage of capacity that is used for the Hadoop distributed File System (HDFS) has reachedthe warning threshold.


*IF *VALUE KH8_FSNAMESYSTEM.CapacityUsedPercent *GT 80 *AND *VALUEKH8_FSNAMESYSTEM.CapacityUsedPercent *LT 90




This threshold uses the following attributes: FSNamesystem.CapacityUsedPercent[KH8FSNAMES.CAPACITYU2], FSNamesystem.Hostname [KH8FSNAMES.HOSTNAME].

KH8_Capacity_Used_Warning_ClusterThe percentage of capacity that is used for the Hadoop distributed File System (HDFS) has reachedthe warning threshold.


*IF *VALUE KH8_CLUSTERDETAILS.CapacityUsedPercent *GT 80



The threshold is evaluated for each distinct value of the ClusterID attribute.

This threshold uses the following attributes: ClusterDetails.CapacityUsedPercent[KH8CLUSDET.CAPACITYU2].

KH8_Corrupt_Blocks_CriticalThe percentage of corrupt blocks in the cluster has exceeded the critical threshold.


*IF *VALUE KH8_FSNAMESYSTEM.CorruptBlocksPercent *GE 50




This threshold uses the following attributes: FSNamesystem.CorruptBlocksPercent[KH8FSNAMES.CORRUPTBL0] (not visible in the UI), FSNamesystem.Hostname[KH8FSNAMES.HOSTNAME].

KH8_Corrupt_Blocks_WarningThe percentage of corrupt blocks in the cluster has reached the warning threshold.


*IF *VALUE KH8_FSNAMESYSTEM.CorruptBlocksPercent *GT 20 *AND *VALUEKH8_FSNAMESYSTEM.CorruptBlocksPercent *LT 50




This threshold uses the following attributes: FSNamesystem.CorruptBlocksPercent[KH8FSNAMES.CORRUPTBL0] (not visible in the UI), FSNamesystem.Hostname[KH8FSNAMES.HOSTNAME].

Thresholds 39

KH8_HighAvailabilityStandby NameNode is running but Active NameNode is down.


*IF *VALUE KH8_FSNAMESYSTEM.HasState *NE 'active' *AND *VALUEKH8_FSNAMESYSTEM.HasState *NE 'standby'




This threshold uses the following attributes: FSNamesystem.HasState [KH8FSNAMES.HASTATE],FSNamesystem.Hostname [KH8FSNAMES.HOSTNAME].

KH8_Missing_Blocks_CriticalThe percentage of process blocks that are missing in the cluster has exceeded the critical threshold.


*IF *VALUE KH8_FSNAMESYSTEM.MissingBlocksPercent *GE 50




This threshold uses the following attributes: FSNamesystem.MissingBlocksPercent[KH8FSNAMES.MISSINGBL0] (not visible in the UI), FSNamesystem.Hostname[KH8FSNAMES.HOSTNAME].

KH8_Missing_Blocks_WarningThe percentage of process blocks that are missing in the cluster has reached the warning threshold.


*IF *VALUE KH8_FSNAMESYSTEM.MissingBlocksPercent *GT 20 *AND *VALUEKH8_FSNAMESYSTEM.MissingBlocksPercent *LT 50




This threshold uses the following attributes: FSNamesystem.MissingBlocksPercent[KH8FSNAMES.MISSINGBL0] (not visible in the UI), FSNamesystem.Hostname[KH8FSNAMES.HOSTNAME].

KH8_Missing_Blocks_Warning_ClusterThe percentage of process blocks that are missing in the cluster has reached the warning threshold.


*IF *VALUE KH8_CLUSTERDETAILS.MissingBlocks *GT 0



The threshold is evaluated for each distinct value of the ClusterID attribute.

This threshold uses the following attributes: ClusterDetails.MissingBlocks[KH8CLUSDET.MISSINGBLO].


Customized thresholdsYou can use the predefined thresholds as a starting point for event monitoring, and create your ownthresholds as conditions arise that you want to monitor.

The Hadoop agent has many data sets that you can use to create thresholds to monitor for specificconditions. For descriptions of the data sets, see Chapter 4, “Attributes,” on page 43.

Tip: The hover help for the Threshold Editor Data set field has a Learn more link to the attributedescriptions for the selected data set.

Thresholds 41


Chapter 4. Attributes

Attributes are the application properties that are being measured and reported by the Monitoring Agentfor Hadoop. Attributes make up the key performance indicators (KPIs) that are reported, and you can usethem to create situations or thresholds for conditions that you want to monitor.

About attributesAttributes are organized into data sets (also referred to as attribute groups). The values can be selectivelydisplayed in dashboard pages or used to define a threshold.

Attributes in a group can be used in queries, query-based views, situations, policy workflows, take actiondefinitions, and launch application definitions. Chart or table views and situations are two examples ofhow attributes in a group can be used:Chart or table views

Attributes are displayed in chart and table views. The chart and table views use queries to specifywhich attribute values to request from a monitoring agent. You use the Properties editor to applyfilters and set styles to define the content and appearance of a view based on an existing query.

SituationsYou use attributes to create situations that monitor the state of your operating system, database, orapplication. A situation describes a condition that you want to test. When you start a situation, thevalues you assign to the situation attributes are compared with the values collected by the Hadoopagent and registers an event if the condition is met. You are alerted to events by indicator icons thatare displayed in the Navigator.

The most recent data sample of the attributes in the data set are used after you open a dashboard page orstart a threshold.Dashboard pages

Only a subset of Hadoop agent attributes is displayed in the dashboard pages. Queries to thedashboard data provider specify which attribute values to request from the managed resource. Theseattributes are shown in italic in this chapter. You can use these attributes to create the charts andtables in custom dashboard pages.

ThresholdsYou can define thresholds that monitor the state of your operating system, database, or applicationand open an event when the threshold is exceeded. You use attributes to define thresholds thatdescribe a condition that you want to test. After the threshold is started, the attribute values thatare specified in the threshold are compared with the values collected by the Hadoop agent. Afterthe condition is met, an event is registered and you are alerted by indicators in the ApplicationPerformance Dashboard navigator, All My Applications summary boxes, and the Events tab.

The Hadoop agent comes with predefined thresholds that are enabled and started with the agent. Ifyou edit a predefined threshold, such as to change the condition or severity, it is no longer treated as apredefined threshold but considered a custom threshold.

All Hadoop agent attributes, unless otherwise noted, can be used to create custom thresholds. TheEvents tab has a table of open events with information, including threshold name, severity, source,and display item. You can expand an event row to see the formula and drill down to the dashboardpage for the managed resource.

Some attributes names display differently in the Threshold Editor, as shown in parentheses after thename, such as "Object Count (OBJECT_COUNT)".

When the sampled values for the attributes that are referenced in a threshold or situation meet thecondition (such as attribute A is greater than 80%), an event is opened. Note the following conditions:

• When no data can be collected for a data set, an empty result is returned (no rows of data)• When a specific attribute cannot be collected, the value 0 or "" is returned unless otherwise

specified in a particular attribute (for example, "N/A")


• Any numeric attribute value that is greater than the largest (positive or negative) number that can berepresented by that type returns the corresponding maximum or minimum value. For example, themaximum value for a 32-bit number is 2,147,483,647.

These values are displayed as text values that are defined by the data set, such as "Value ExceedsMaximum" or "Value Exceeds Minimum".

Historical data configurationsThe Hadoop agent collects historical data for key data sets that are shown in the dashboard pages. Apage that includes historical views from the managed resource instance has a time selector tool foradjusting the time range. With line charts, you can also compare the values with a previous day, up tothe number of days that have been saved.

Additional information about attributes

For more information about using attributes and data sets in the Tivoli® Enterprise Portal, see the TivoliEnterprise Portal User's Guide.

Note the following conditions:

• When no data can be collected for a data set, an empty result is returned (no rows of data)• When a specific attribute cannot be collected, the value 0 or "" is returned unless otherwise specified in

a particular attribute (for example, "N/A")• Any numeric attribute value that is greater than the largest (positive or negative) number that can be

represented by that type returns the corresponding maximum or minimum value (for example, themaximum value for a 32-bit number is 2,147,483,647). These values are displayed as text values thatare defined by the data set, such as "Value Exceeds Maximum" or "Value Exceeds Minimum".

Numeric attributes have characteristics that are indicated in parentheses after the data type, such as"(32-bit numeric property)". A numeric attribute value can be 32-bit or 64-bit or some other size. Thevalue type can be gauge, which means it varies, like a speedometer; counter, which counts and alwaysincreases; or numeric property, such as disk size.

For a list of the data sets, a list of the attributes in each data set, and descriptions of the attributes in theHadoop agent, see “Data sets for the monitoring agent” on page 44 and “Attribute descriptions” onpage 48.

Data sets for the monitoring agentThe Hadoop agent contains the following data sets.

• Data set name: Ambari Metrics

– Table name: KH8AMBARIS– Historical table name: KH8_AMBARIMETRICS or KH8AMBARIS

• Data set name: Atlas

– Table name: KH8ATLASSE– Historical table name: KH8_ATLAS or KH8ATLASSE

• Data set name: Big SQL

– Table name: KH8BIGSQL– Historical table name: KH8_BIGSQL

• Data set name: Cluster Metrics

– Table name: KH8CLUSTER– Historical table name: KH8_CLUSTERMETRICS or KH8CLUSTER

• Data set name: Cluster Overview

– Table name: KH8CLUSTE0


– Historical table name: KH8_CLUSTEROVERVIEW or KH8CLUSTE0• Data set name: ClusterDetails

– Table name: KH8CLUSDET– Historical table name: KH8_CLUSTERDETAILS or KH8CLUSDET

• Data set name: DataNode

– Table name: KH8DATANOD– Historical table name: KH8_DATANODE or KH8DATANOD

• Data set name: Druid

– Table name: KH8DRUIDSE– Historical table name: KH8_DRUID or KH8DRUIDSE

• Data set name: Falcon

– Table name: KH8FALCONS– Historical table name: KH8_FALCON or KH8FALCONS

• Data set name: Flume

– Table name: KH8FLUMESE– Historical table name: KH8_FLUME or KH8FLUMESE

• Data set name: FS Name System

– Table name: KH8FSNAMES– Historical table name: KH8_FSNAMESYSTEM or KH8FSNAMES

• Data set name: HBase

– Table name: KH8HBASESE– Historical table name: KH8_HBASE or KH8HBASESE

• Data set name: HDFS

– Table name: KH8HDFSSER– Historical table name: KH8_HDFS or KH8HDFSSER

• Data set name: Hive

– Table name: KH8HIVESER– Historical table name: KH8_HIVE or KH8HIVESER

• Data set name: HOS Performance Object Status

– Table name: KH8HOSPOS– Historical table name: KH8_HOS_PERFORMANCE_OBJECT_STATUS or KH8HOSPOS

• Data set name: Hosts nodes

– Table name: KH8HOSDS– Historical table name: KH8_HOSTS_NODES or KH8HOSDS

• Data set name: JVM Metrics

– Table name: KH8JVMMETR– Historical table name: KH8_JVMMETRICS or KH8JVMMETR

• Data set name: Kafka

– Table name: KH8KAFKASE– Historical table name: KH8_KAFKA or KH8KAFKASE

• Data set name: Knox

Attributes 45

– Table name: KH8KNOXSER– Historical table name: KH8_KNOX or KH8KNOXSER

• Data set name: Mahout

– Table name: KH8MAHOUTS– Historical table name: KH8_MAHOUT or KH8MAHOUTS

• Data set name: MapReduce2

– Table name: KH8MAPREDU– Historical table name: KH8_MAPREDUCE2 or KH8MAPREDU

• Data set name: NameNode

– Table name: KH8NAMENOD– Historical table name: KH8_NAMENODE or KH8NAMENOD

• Data set name: NiFi

– Table name: KH8NIFI– Historical table name: KH8_NIFI

• Data set name: NiFi Registry

– Table name: KH8NIFIREG– Historical table name: KH8_NIFIREGISTRY or KH8NIFIREG

• Data set name: NodeManager Metrics

– Table name: KH8NODEMAN– Historical table name: KH8_NODEMANAGERMETRICS or KH8NODEMAN

• Data set name: Oozie

– Table name: KH8OOZIESE– Historical table name: KH8_OOZIE or KH8OOZIESE

• Data set name: Operating System

– Table name: KH8OPERSYS– Historical table name: KH8_OPERATINGSYSTEM or KH8OPERSYS

• Data set name: Performance Object Status

– Table name: KH8POBJST– Historical table name: KH8_PERFORMANCE_OBJECT_STATUS or KH8POBJST

• Data set name: Pig

– Table name: KH8PIGSER– Historical table name: KH8_PIG or KH8PIGSER

• Data set name: Queue Metrics

– Table name: KH8QUEUEME– Historical table name: KH8_QUEUEMETRICS or KH8QUEUEME

• Data set name: Ranger

– Table name: KH8RANGERS– Historical table name: KH8_RANGER or KH8RANGERS

• Data set name: Roles

– Table name: KH8ROLES– Historical table name: KH8_ROLES


• Data set name: RPC

– Table name: KH8RPC– Historical table name: KH8_RPC

• Data set name: Schema Registry

– Table name: KH8REGISTR– Historical table name: KH8_SCHEMAREGISTRY or KH8REGISTR

• Data set name: Services Overview

– Table name: KH8SERVICE– Historical table name: KH8_SERVICESOVERVIEW or KH8SERVICE

• Data set name: Slider

– Table name: KH8SLIDERS– Historical table name: KH8_SLIDER or KH8SLIDERS

• Data set name: SmartSense

– Table name: KH8SMARTSE– Historical table name: KH8_SMARTSENSE or KH8SMARTSE

• Data set name: Solr

– Table name: KH8SOLRSER– Historical table name: KH8_SOLR or KH8SOLRSER

• Data set name: Spark

– Table name: KH8SPARKSE– Historical table name: KH8_SPARK or KH8SPARKSE

• Data set name: Sqoop

– Table name: KH8SQOOPSE– Historical table name: KH8_SQOOP or KH8SQOOPSE

• Data set name: Startup Progress

– Table name: KH8STARTUP– Historical table name: KH8_STARTUPPROGRESS or KH8STARTUP

• Data set name: Streaming Analytics Manager

– Table name: KH8STREAML– Historical table name: KH8_STREAMINGANALYTICSMANAGER or KH8STREAML

• Data set name: Superset

– Table name: KH8SUPERSE– Historical table name: KH8_SUPERSET or KH8SUPERSE

• Data set name: Take Action Status

– Table name: KH8TACTST– Historical table name: KH8_TAKE_ACTION_STATUS or KH8TACTST

• Data set name: Tez

– Table name: KH8TEZSERV– Historical table name: KH8_TEZ or KH8TEZSERV

• Data set name: Thread Pool Status

– Table name: KH8THPLST– Historical table name: KH8_THREAD_POOL_STATUS or KH8THPLST

Attributes 47

• Data set name: Titan

– Table name: KH8TITANSE– Historical table name: KH8_TITAN or KH8TITANSE

• Data set name: UGI Metrics

– Table name: KH8UGIMETR– Historical table name: KH8_UGIMETRICS or KH8UGIMETR

• Data set name: Unified Console

– Table name: KH8UNIFCON– Historical table name: KH8_UNIFIEDCONSOLE or KH8UNIFCON

• Data set name: YARN

– Table name: KH8YARNSER– Historical table name: KH8_YARN or KH8YARNSER

• Data set name: ZooKeeper

– Table name: KH8ZOOKEEP– Historical table name: KH8_ZOOKEEPER or KH8ZOOKEEP

•

Attribute descriptionsAttributes in each Hadoop agent data set collect data that the agent uses for monitoring.

The descriptions of the data sets contain information such as description, type, source, and names foreach attribute in the data set. Some attributes are designated as key attributes, which are identifierattributes for the data set. An attribute in italic indicates that it is available for display in the Cloud APMconsole dashboard pages.

Ambari Metrics data setThis data set monitors the metrics for server and client components of Ambari Metrics Service in theHadoop cluster for Ambari based Hadoop installations. Thresholds for this data set are associated withthe Hadoop component. This data set is displayed as KH8 AMBARIMETRICS in the threshold editor. Adata sample is sent to the server every minute and is maintained for 8 days by default. The attributesshown in italic are visible in the UI. All attributes are available for thresholds.

This data set contains the following attributes:Component Name

Name of the component associated with the service. This attribute is a key attribute. The type isstring.

The source for this attribute is

This attribute can be verified by using the following method:

The following names are defined for this attribute: COMPONENT_NAME or COMPONENT_ (historicalname), Component Name (caption), component_name (attribute name), and COMPONENT_ (columnname).

HostnameName of the host on which service is running. This attribute is a key attribute. The type is string.




The following names are defined for this attribute: HOST_NAME (historical name), Hostname(caption), host_name (attribute name), and HOST_NAME (column name).

Maintenance StateMaintenance Mode decides whether to suppress alerts, warnings and status change indicators. Thetype is string.



The following names are defined for this attribute: MAINTENANCE_STATE or MAINTENANC (historicalname), Maintenance State (caption), maintenance_state (attribute name), and MAINTENANC (columnname).

NodeThe managed system name of the agent. This attribute is a key attribute. The type is string.

The source for this attribute is the agent


The following names are defined for this attribute: NODE (historical name), Node (caption),ORIGINNODE (attribute name), and ORIGINNODE (column name).

Service NameName of the service being monitored. The type is string.



The following names are defined for this attribute: SERVICE_NAME or SERVICE_NA (historical name),Service Name (caption), service_name (attribute name), and SERVICE_NA (column name).

StateThis attribute indicates the current state of the service component, if the service component is ofserver type then status 'installed' means service component is stopped. The type is string.



The following names are defined for this attribute: STATE (historical name), State (caption), state(attribute name), and STATE (column name).

TimestampThe local time at the agent when the data was collected. The type is string.



The following names are defined for this attribute: TIMESTAMP (historical name), Timestamp(caption), Timestamp (attribute name), and TIMESTAMP (column name).

Cluster NameThe name of Hadoop cluster where service is running. The type is string.



The following names are defined for this attribute: CLUSTER_NAME or CLUSTER_NA (historical name),Cluster Name (caption), cluster_name (attribute name), and CLUSTER_NA (column name).

Desired Stack IdThe Hadoop stack on which the service is desired. The type is string.


Attributes 49


The following names are defined for this attribute: DESIRED_STACK_ID or DESIRED_ST (historicalname), Desired Stack Id (caption), desired_stack_id (attribute name), and DESIRED_ST (columnname).

Desired StateThis attribute indicates the allowed State transitions of a service component. The type is string.



The following names are defined for this attribute: DESIRED_STATE or DESIRED_S0 (historical name),Desired State (caption), desired_state (attribute name), and DESIRED_S0 (column name).

HDP VersionVersion of Hadoop Distribution Platform where service is installed. The type is string.



The following names are defined for this attribute: HDP_VERSION or HDP_VERSIO (historical name),HDP Version (caption), hdp_version (attribute name), and HDP_VERSIO (column name).

Init Count in ClusterThis attribute indicates the count of service components in init state. The type is integer (32-bitgauge).



The following names are defined for this attribute: INIT_COUNT_IN_CLUSTER or INIT_COUNT(historical name), Init Count in Cluster (caption), init_count_in_cluster (attribute name), andINIT_COUNT (column name).

Install failed Count in ClusterThis attribute indicates the count of service components in the install failed state. The type is integer(32-bit gauge).



The following names are defined for this attribute: INSTALL_FAILED_COUNT_IN_CLUSTER orINSTALL_FA (historical name), Install failed Count in Cluster (caption), install_failed_count_in_cluster(attribute name), and INSTALL_FA (column name).

Installed Count in ClusterThis attribute indicates the count of installed service components. The type is integer (32-bit gauge).



The following names are defined for this attribute: INSTALLED_COUNT_IN_CLUSTER or INSTALLED_(historical name), Installed Count in Cluster (caption), installed_count_in_cluster (attribute name),and INSTALLED_ (column name).

Other Count in ClusterIn case of some Ambari versions, the attributes like 'init_count_in_cluster','install_failed_count_in_cluster', 'unknown_count_in_cluster' are not available that time this'other_count_in_cluster' attribute indicates the count of service components neither started norinstalled, which may be in init, install_failed or unknown state. The type is integer (32-bit gauge).




The following names are defined for this attribute: OTHER_COUNT_IN_CLUSTER or OTHER_COUN(historical name), Other Count in Cluster (caption), other_count_in_cluster (attribute name), andOTHER_COUN (column name).

Stack IdThe Hadoop stack on which the service is running. The type is string.



The following names are defined for this attribute: STACK_ID (historical name), Stack Id (caption),stack_id (attribute name), and STACK_ID (column name).

Stale ConfigsThis attribute indicates if the host components need to be restarted. The type is string.



The following names are defined for this attribute: STALE_CONFIGS or STALE_CONF (historical name),Stale Configs (caption), stale_configs (attribute name), and STALE_CONF (column name).

Started Count in ClusterThis attribute indicates the count of started service components. The type is integer (32-bit gauge).



The following names are defined for this attribute: STARTED_COUNT_IN_CLUSTER or STARTED_CO(historical name), Started Count in Cluster (caption), started_count_in_cluster (attribute name), andSTARTED_CO (column name).

Total Count in ClusterThis attribute indicates the total count of service components. The type is integer (32-bit gauge).



The following names are defined for this attribute: TOTAL_COUNT_IN_CLUSTER or TOTAL_COUN(historical name), Total Count in Cluster (caption), total_count_in_cluster (attribute name), andTOTAL_COUN (column name).

Unknown Count in ClusterThis attribute indicates the count of service components in the unknown state. The type is integer(32-bit gauge).



The following names are defined for this attribute: UNKNOWN_COUNT_IN_CLUSTER orUNKNOWN_CO (historical name), Unknown Count in Cluster (caption), unknown_count_in_cluster(attribute name), and UNKNOWN_CO (column name).

Upgrade StateThis attribute indicates if the service component needs an upgrade. The type is string.



The following names are defined for this attribute: UPGRADE_STATE or UPGRADE_ST (historicalname), Upgrade State (caption), upgrade_state (attribute name), and UPGRADE_ST (column name).

Attributes 51

Atlas data setThis data set monitors the metrics for server and client components of Atlas Service in the Hadoop clusterfor Ambari based Hadoop installations. Thresholds for this data set are associated with the Hadoopcomponent. This data set is displayed as KH8 ATLAS in the threshold editor. A data sample is sent to theserver every minute and is maintained for 8 days by default. The attributes shown in italic are visible inthe UI. All attributes are available for thresholds.






HostnameName of the host on which the service is running. This attribute is a key attribute. The type is string.













































Attributes 53









Other Count in ClusterIn case of some Ambari versions, the attributes like 'init_count_in_cluster','install_failed_count_in_cluster', 'unknown_count_in_cluster' are not available at that time this'other_count_in_cluster' attribute indicates the count of service components neither started norinstalled, which may be in init, install_failed or unknown state. The type is integer (32-bit gauge).








Stale ConfigsThis attribute indicates if the host components need to restart. The type is string.




Started Count in ClusterThis attribute indicates the count of service components that are started. The type is integer (32-bitgauge).

















Big SQL data setThis data set monitors the metrics for server and client components of Big SQL Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 BIGSQL in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.










Attributes 55

Maintenance StateMaintenance mode that decides whether to suppress alerts, warnings, and status change indicators.The type is string.








Service NameName of the service that is being monitored. The type is string.




StateThis attribute indicates the current state of the service component. For example, if the servicecomponent is of server type, then the status installed means that the service component is stopped.The type is string.

























Init Count in ClusterThis attribute indicates the count of service components that are in init state. The type is integer (32-bit gauge).




Install failed Count in ClusterThis attribute indicates the count of service components that are in the install failed state. The type isinteger (32-bit gauge).








Other Count in ClusterIn case of some Ambari versions, if the attributes like 'init_count_in_cluster','install_failed_count_in_cluster', and 'unknown_count_in_cluster' are not available, then the'other_count_in_cluster' attribute indicates that the count of service components is neither startednor installed, which might be in an init, install_failed, or unknown state. The type is integer (32-bitgauge).



Attributes 57






Stale ConfigsThis attribute indicates whether the host components need to restart. The type is string.












Unknown Count in ClusterThis attribute indicates the count of service components that are in the unknown state. The type isinteger (32-bit gauge).




Upgrade StateThis attribute indicates whether the service component needs an upgrade. The type is string.





Cluster Metrics data setThis data set provides the performance metrics of the Hadoop cluster. Note: If you define a threshold forthis data set, any events are not displayed in the Events tab of the Application Performance Dashboard.Instead, they are sent to Netcool/OMNIbus if event forwarding is configured. This data set is displayedas KH8 CLUSTERMETRICS in the threshold editor. A data sample is sent to the server every minute andis maintained for 8 days by default. The attributes shown in italic are visible in the UI. All attributes areavailable for thresholds.

This data set contains the following attributes:Active NodeManagers

The number of active NodeManagers. The type is integer (64-bit gauge).



The following names are defined for this attribute: ACTIVENODEMANAGERS or NUMACTIVEN(historical name), Active NodeManagers (caption), ActiveNodeManagers (attribute name), andNUMACTIVEN (column name).

Cluster MetricsThe name of the node through which the cluster metrics are collected. The type is string.



The following names are defined for this attribute: CLUSTERMETRICS or CLUSTERMET (historicalname), Cluster Metrics (caption), ClusterMetrics (attribute name), and CLUSTERMET (column name).

Collect TimestampThe time at which the data was collected. The type is timestamp.



The following names are defined for this attribute: COLLECT_TIMESTAMP or COLLECT_TI (historicalname), Collect Timestamp (caption), collect_timestamp (attribute name), and COLLECT_TI (columnname).

ContextThe context in which the data is collected. The type is string.



The following names are defined for this attribute: CONTEXT (historical name), Context (caption),Context (attribute name), and CONTEXT (column name).

Decommissioned NodeManagersThe number of decommissioned NodeManagers. The type is integer (64-bit gauge).



The following names are defined for this attribute: DECOMMISSIONEDNODEMANAGERSor NUMDECOMMI (historical name), Decommissioned NodeManagers (caption),DecommissionedNodeManagers (attribute name), and NUMDECOMMI (column name).

HostnameThe name of the host. This attribute is a key attribute. The type is string.


Attributes 59


The following names are defined for this attribute: HOSTNAME (historical name), Hostname (caption),Hostname (attribute name), and HOSTNAME (column name).

Lost NodeManagersThe number of lost NodeManagers. The type is integer (64-bit gauge).



The following names are defined for this attribute: LOSTNODEMANAGERS or NUMLOSTNMS (historicalname), Lost NodeManagers (caption), LostNodeManagers (attribute name), and NUMLOSTNMS(column name).





Rebooted NodeManagersThe number of rebooted NodeManagers. The type is integer (64-bit gauge).



The following names are defined for this attribute: REBOOTEDNODEMANAGERS or NUMREBOOTE(historical name), Rebooted NodeManagers (caption), RebootedNodeManagers (attribute name), andNUMREBOOTE (column name).





Unhealthy NodeManagersThe number of unhealthy NodeManagers. The type is integer (64-bit gauge).



The following names are defined for this attribute: UNHEALTHYNODEMANAGERS or NUMUNHEALT(historical name), Unhealthy NodeManagers (caption), UnhealthyNodeManagers (attribute name), andNUMUNHEALT (column name).

Cluster Overview data setThis data set provides the overall summary of the Hadoop cluster. Thresholds for this data set areassociated with the Hadoop component. This data set is displayed as KH8 CLUSTEROVERVIEW in thethreshold editor. A data sample is sent to the server every minute and is maintained for 8 days by default.The attributes shown in italic are visible in the UI. All attributes are available for thresholds.

This data set contains the following attributes:


DataNode StatusThe status of the DataNode, such as normal, warning, critical or unknown. The type is integer (32-bit gauge) with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), Unknown (0), Normal (1), Warning (2),Critical (3). Any value that does not have a definition here is displayed in the User Interface.



The following names are defined for this attribute: DATANODESTATUS or DATANODEST (historicalname), DataNode Status (caption), DatanodeStatus (attribute name), and DATANODEST (columnname).

File System StatusThe status of the file system, such as normal, warning, critical or unknown. The type is integer (32-bit gauge) with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), Unknown (0), Normal (1), Warning (2),Critical (3). Any value that does not have a definition here is displayed in the User Interface.



The following names are defined for this attribute: FILESYSTEMSTATUS or FSSTATUS (historicalname), File System Status (caption), FileSystemStatus (attribute name), and FSSTATUS (columnname).

HostnameThe Hadoop nodes that are configured with the Hadoop agent. The type is string.




IP AddressThe IP address of the Hadoop node. The IP address must be mapped to the host name in the hostsfile, which is available on the node where the agent is installed. If this mapping is not provided in thehosts file, the IP address will be same as host name. The type is string.



The following names are defined for this attribute: IP_ADDRESS (historical name), IP Address(caption), IP_Address (attribute name), and IP_ADDRESS (column name).

Java Virtual Machine StatusThe status of the Java virtual Machine, such as normal, warning, critical or unknown. The type isinteger (32-bit gauge) with enumerated values. The following values are defined: Value ExceedsMaximum (2147483647), Value Exceeds Minimum (-2147483648), Unknown (0), Normal (1),Warning (2), Critical (3). Any value that does not have a definition here is displayed in the UserInterface.



The following names are defined for this attribute: JVMSTATUS (historical name), Java Virtual MachineStatus (caption), JVMStatus (attribute name), and JVMSTATUS (column name).



Attributes 61



Queue StatusThe status of the Process Queue, such as normal, warning, critical or unknown. The type is integer(32-bit gauge) with enumerated values. The following values are defined: Value Exceeds Maximum(2147483647), Value Exceeds Minimum (-2147483648), Unknown (0), Normal (1), Warning (2),Critical (3). Any value that does not have a definition here is displayed in the User Interface.



The following names are defined for this attribute: QUEUESTATUS or QUEUESTATU (historical name),Queue Status (caption), QueueStatus (attribute name), and QUEUESTATU (column name).

Remote Procedure Call StatusThe status of the Remote Procedure Call, such as normal, warning, critical or unknown. The typeis integer (32-bit gauge) with enumerated values. The following values are defined: Value ExceedsMaximum (2147483647), Value Exceeds Minimum (-2147483648), Unknown (0), Normal (1),Warning (2), Critical (3). Any value that does not have a definition here is displayed in the UserInterface.



The following names are defined for this attribute: RPCSTATUS (historical name), Remote ProcedureCall Status (caption), RpcStatus (attribute name), and RPCSTATUS (column name).

Subnode HostThe name of the cluster or node in the Hadoop system, if the subnode host value is 'cluster' then inthat row host name and IP address attributes display the total number of nodes that are availablein the Hadoop cluster also all the five status attributes will display the overall status of the Hadoopcluster based on the severity of individual node's health. This attribute is a key attribute. The type isstring.



The following names are defined for this attribute: HOST_MSN (historical name), Subnode Host(caption), Host_MSN (attribute name), and HOST_MSN (column name).





Cluster IDA unique ID to identify a Cluster. The type is string.



The following names are defined for this attribute: CLUSTERID (historical name), Cluster ID (caption),ClusterID (attribute name), and CLUSTERID (column name).

Node FQDNThe Fully Qualified Domain Name of Hadoop nodes that are configured with the Hadoop agent. Thetype is string.




The following names are defined for this attribute: NODEFQDN or NODEFQD (historical name), NodeFQDN (caption), NodeFQDN (attribute name), and NODEFQD (column name).

PortThe port number that is used by a daemon in the Hadoop cluster. This port number is not the actualport where the Hadoop daemon process is running. The type is integer (32-bit gauge).



The following names are defined for this attribute: PORT (historical name), Port (caption), Port(attribute name), and PORT (column name).

ClusterDetails data setThis data set provides the important data of the cluster health. Thresholds for this data set are associatedwith the Hadoop component. This data set is displayed as KH8 CLUSTERDETAILS in the threshold editor.A data sample is sent to the server every minute and is maintained for 8 days by default. The attributesshown in italic are visible in the UI. All attributes are available for thresholds.

This data set contains the following attributes:Applications Failed

The number of applications in failed state. The type is integer (64-bit gauge).



The following names are defined for this attribute: APPLICATIONSFAILED or APPSFAILED (historicalname), Applications Failed (caption), ApplicationsFailed (attribute name), and APPSFAILED (columnname).

Average MemoryHeapUsed PercentThe percentage of aggregate heap memory (in MB) used by the Java Virtual Machine. The type is realnumber (64-bit gauge) with four decimal places of precision.



The following names are defined for this attribute: AVGMEMORYHEAPUSEDPERCENTor MEMHEAPUSE (historical name), Average MemoryHeapUsed Percent (caption),AvgMemoryHeapUsedPercent (attribute name), and MEMHEAPUSE (column name).

Capacity Total GBThe total storage capacity of DataNodes in GB. The type is real number (64-bit gauge) with onedecimal places of precision.



The following names are defined for this attribute: CAPACITYTOTALGB or CAPACITYTO (historicalname), Capacity Total GB (caption), CapacityTotalGB (attribute name), and CAPACITYTO (columnname).

Capacity Used GBThe total storage capacity (in GB) that is used across all DataNodes. The type is real number (64-bitgauge) with one decimal places of precision.


Attributes 63


The following names are defined for this attribute: CAPACITYUSEDGB or CAPACITYU1 (historicalname), Capacity Used GB (caption), CapacityUsedGB (attribute name), and CAPACITYU1 (columnname).

Capacity Used PercentThe percentage of used storage capacity. The type is real number (64-bit gauge) with four decimalplaces of precision.

The source for this attribute is derived: CapacityUsedGB*100/CapacityTotalGB


The following names are defined for this attribute: CAPACITYUSEDPERCENT or CAPACITYU2(historical name), Capacity Used Percent (caption), CapacityUsedPercent (attribute name), andCAPACITYU2 (column name).

Cluster IDA unique ID to identify a Cluster. This attribute is a key attribute. The type is string.



The following names are defined for this attribute: CLUSTERID (historical name), Cluster ID (caption),ClusterID (attribute name), and CLUSTERID (column name).

Containers FailedThe number of containers in the failed state. The type is integer (64-bit gauge).



The following names are defined for this attribute: CONTAINERSFAILED or CONTNRFLD (historicalname), Containers Failed (caption), ContainersFailed (attribute name), and CONTNRFLD (columnname).

Count of Active Node ManagersThe count of Node Managers which are in the active state. The type is string.



The following names are defined for this attribute: NUMACTIVENMS or NUMACTNMS (historicalname), Count of Active Node Managers (caption), NumActiveNMs (attribute name), and NUMACTNMS(column name).

Count of Dead DatanodesThe count of Datanodes which are in dead state. The type is string.



The following names are defined for this attribute: DEADDATANODES or DEADDN (historical name),Count of Dead Datanodes (caption), DeadDataNodes (attribute name), and DEADDN (column name).

Count of Decommissioned Node ManagersThe count of Node Managers which are in the decommission state. The type is integer (64-bit gauge).



The following names are defined for this attribute: NUMDECOMMISSIONEDNMS or NUMDECONMS(historical name), Count of Decommissioned Node Managers (caption), NumDecommissionedNMs(attribute name), and NUMDECONMS (column name).


Count of Live DatanodesThe count of Datanodes which are in live state. The type is string.



The following names are defined for this attribute: LIVEDATANODES or LIVEDN (historical name),Count of Live Datanodes (caption), LiveDataNodes (attribute name), and LIVEDN (column name).

Count of Lost Node ManagersThe count of Node Managers which are in the Lost state. The type is integer (64-bit gauge).



The following names are defined for this attribute: NUMLOSTNMS (historical name), Count of LostNode Managers (caption), NumLostNMs (attribute name), and NUMLOSTNMS (column name).

Count of NodesThe count of nodes in Hadoop cluster. The type is string.



The following names are defined for this attribute: COUNTOFNODES or NODECNT (historical name),Count of Nodes (caption), countOfNodes (attribute name), and NODECNT (column name).

Count of Rebooted Node ManagersThe count of Rebooted Node Managers. The type is integer (64-bit gauge).



The following names are defined for this attribute: NUMREBOOTEDNMS or REBOOTENMS (historicalname), Count of Rebooted Node Managers (caption), NumRebootedNMs (attribute name), andREBOOTENMS (column name).

Count of Unhealthy Node ManagersThe count of Unhealthy Node Managers. The type is integer (64-bit gauge).



The following names are defined for this attribute: NUMUNHEALTHYNMS or NUMUNHEALT (historicalname), Count of Unhealthy Node Managers (caption), NumUnhealthyNMs (attribute name), andNUMUNHEALT (column name).

Custom Cluster NameThe unique name of Hadoop cluster. The type is string.



The following names are defined for this attribute: CLUSTERNAME or CLUNAME (historical name),Custom Cluster Name (caption), ClusterName (attribute name), and CLUNAME (column name).

Ha StateThe state of the high availability (HA) of the NameNode. The type is string.



The following names are defined for this attribute: HASTATE (historical name), Ha State (caption),HaState (attribute name), and HASTATE (column name).

Attributes 65

Missing BlocksThe number of missing blocks in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: MISSINGBLOCKS or MISSINGBLO (historicalname), Missing Blocks (caption), MissingBlocks (attribute name), and MISSINGBLO (column name).

Namenode uptimeThe duration in days since the Namenode daemon has been running. The type is string.



The following names are defined for this attribute: NNUPTIME or NNUPTIM (historical name),Namenode uptime (caption), NNuptime (attribute name), and NNUPTIM (column name).





Process CPULoad PercentageThe percentage of recent CPU usage of the JVM process. The type is real number (64-bit gauge) withfour decimal places of precision.



The following names are defined for this attribute: PROCESSCPULOADPERCENTAGE or PROCPULOAD(historical name), Process CPULoad Percentage (caption), ProcessCPULoadPercentage (attributename), and PROCPULOAD (column name).





Total Disk failuresThe total number of disk failures. The type is string.



The following names are defined for this attribute: TOTALDISKFAILURES or TOTDSKFAIL (historicalname), Total Disk failures (caption), TotalDiskFailures (attribute name), and TOTDSKFAIL (columnname).

DataNode data setThis data set monitors the DataNode metrics of the Hadoop cluster. This data set is configured forhistorical collection. Note: If you define a threshold for this data set, any events are not displayed in theEvents tab of the Application Performance Dashboard. Instead, they are sent to Netcool/OMNIbus if eventforwarding is configured. This data set is displayed as KH8 DATANODE in the threshold editor. A data


sample is sent to the server every minute and is maintained for 8 days by default. The attributes shown initalic are visible in the UI. All attributes are available for thresholds.

This data set contains the following attributes:Block Verification Failures

The number of block verifications that failed in the DataNode. The type is integer (64-bit gauge).



The following names are defined for this attribute: BLOCKVERIFICATIONFAILURES or BLOCKVERIF(historical name), Block Verification Failures (caption), BlockVerificationFailures (attribute name), andBLOCKVERIF (column name).

Blocks ReadThe delta of blocks read from DataNode. The type is DEFAULT(2).



The following names are defined for this attribute: BLOCKSREAD (historical name), Blocks Read(caption), BlocksRead (attribute name), and BLOCKSREAD (column name).

Blocks RemovedThe number of process blocks that are removed from the DataNode. The type is integer (64-bitgauge).



The following names are defined for this attribute: BLOCKSREMOVED or BLOCKSREMO (historicalname), Blocks Removed (caption), BlocksRemoved (attribute name), and BLOCKSREMO (columnname).

Blocks ReplicatedThe number of process blocks that are replicated in the DataNode. The type is integer (64-bit gauge).



The following names are defined for this attribute: BLOCKSREPLICATED or BLOCKSREPL (historicalname), Blocks Replicated (caption), BlocksReplicated (attribute name), and BLOCKSREPL (columnname).

Blocks VerifiedThe number of process blocks that are verified in the DataNode. The type is integer (64-bit gauge).



The following names are defined for this attribute: BLOCKSVERIFIED or BLOCKSVERI (historicalname), Blocks Verified (caption), BlocksVerified (attribute name), and BLOCKSVERI (column name).

Blocks WrittenThe delta of blocks written to DataNode. The type is DEFAULT(2).



The following names are defined for this attribute: BLOCKSWRITTEN or BLOCKSWRIT (historicalname), Blocks Written (caption), BlocksWritten (attribute name), and BLOCKSWRIT (column name).

Attributes 67

Bytes Read (Rate)The rate of change in amount of data (in bytes) read from DataNode. The type is DEFAULT(2).



The following names are defined for this attribute: BYTESREAD (historical name), Bytes Read (Rate)(caption), BytesRead (attribute name), and BYTESREAD (column name).

Bytes ReadMBThe amount of data (in MB) that is read from the DataNode. The type is real number (64-bit gauge)with four decimal places of precision.

The source for this attribute is derived: BytesRead/1048576


The following names are defined for this attribute: BYTESREADMB or BYTESREADM (historical name),Bytes ReadMB (caption), BytesReadMB (attribute name), and BYTESREADM (column name).

Bytes Written (Rate)The rate of change in amount of data (in bytes) written to DataNode. The type is DEFAULT(2).



The following names are defined for this attribute: BYTESWRITTEN or BYTESWRITT (historical name),Bytes Written (Rate) (caption), BytesWritten (attribute name), and BYTESWRITT (column name).

Bytes WrittenMBThe amount of data (in MB) that is written to the DataNode. The type is real number (64-bit gauge)with four decimal places of precision.

The source for this attribute is derived: BytesWritten/1048576


The following names are defined for this attribute: BYTESWRITTENMB or BYTESWRIT0 (historicalname), Bytes WrittenMB (caption), BytesWrittenMB (attribute name), and BYTESWRIT0 (columnname).





Heartbeats Average Time ms (Rate)The rate of change in average Heartbeat time (in milliseconds) that is spent to complete thecommunication between the DataNode and the NameNode. The type is DEFAULT(2).



The following names are defined for this attribute: HEARTBEATSAVERAGETIME_MS or HEARTBEAT0(historical name), Heartbeats Average Time ms (Rate) (caption), HeartbeatsAverageTime_ms (attributename), and HEARTBEAT0 (column name).

Heartbeats OperationsThe delta of number of heartbeat operations. The type is DEFAULT(2).




The following names are defined for this attribute: HEARTBEATSOPERATIONS or HEARTBEATS(historical name), Heartbeats Operations (caption), HeartbeatsOperations (attribute name), andHEARTBEATS (column name).

HostnameThe name of the host where the DataNode is configured. This attribute is a key attribute. The type isstring.








Reads From Local Client (Rate)The rate of change in number of read operations from local client. The type is DEFAULT(2).



The following names are defined for this attribute: READSFROMLOCALCLIENT or READSFROML(historical name), Reads From Local Client (Rate) (caption), ReadsFromLocalClient (attribute name),and READSFROML (column name).

Reads From Remote Client (Rate)The rate of change in number of read operations from remote client. The type is DEFAULT(2).



The following names are defined for this attribute: READSFROMREMOTECLIENT or READSFROMR(historical name), Reads From Remote Client (Rate) (caption), ReadsFromRemoteClient (attributename), and READSFROMR (column name).





Volume FailuresThe number of volume failures that occurred in the DataNode. The type is integer (64-bit gauge).



The following names are defined for this attribute: VOLUMEFAILURES or VOLUMEFAIL (historicalname), Volume Failures (caption), VolumeFailures (attribute name), and VOLUMEFAIL (column name).

Writes From Local Client (Rate)The rate of change in number of write operations from local client. The type is DEFAULT(2).

Attributes 69



The following names are defined for this attribute: WRITESFROMLOCALCLIENT or WRITESFROM(historical name), Writes From Local Client (Rate) (caption), WritesFromLocalClient (attribute name),and WRITESFROM (column name).

Writes From Remote Client (Rate)The rate of change in number of write operations from remote client. The type is DEFAULT(2).



The following names are defined for this attribute: WRITESFROMREMOTECLIENT or WRITESFRO0(historical name), Writes From Remote Client (Rate) (caption), WritesFromRemoteClient (attributename), and WRITESFRO0 (column name).

Block Checksum Average Time msThe average time that is spent to complete the block checksum operation. The type is real number(32-bit gauge) with one decimal places of precision.



The following names are defined for this attribute: BLOCKCHECKSUMAVERAGETIME_MSor BLOCKCHEC0 (historical name), Block Checksum Average Time ms (caption),BlockChecksumAverageTime_ms (attribute name), and BLOCKCHEC0 (column name).

Block Checksum OperationsThe number of block checksum operations that occurred in the Hadoop cluster. The type is integer(64-bit gauge).



The following names are defined for this attribute: BLOCKCHECKSUMOPERATIONS or BLOCKCHECK(historical name), Block Checksum Operations (caption), BlockChecksumOperations (attribute name),and BLOCKCHECK (column name).

Block Reports Average Time msThe average time that is required to create the process block reports. The type is real number (32-bitgauge) with one decimal places of precision.



The following names are defined for this attribute: BLOCKREPORTSAVERAGETIME_MSor BLOCKREPO0 (historical name), Block Reports Average Time ms (caption),BlockReportsAverageTime_ms (attribute name), and BLOCKREPO0 (column name).

Block Reports OperationsThe number of block report operations that occurred in the Hadoop cluster. The type is integer (64-bitgauge).



The following names are defined for this attribute: BLOCKREPORTSOPERATIONS or BLOCKREPOR(historical name), Block Reports Operations (caption), BlockReportsOperations (attribute name), andBLOCKREPOR (column name).

Blocks CachedThe total number of blocks that are cached. The type is integer (32-bit gauge).




The following names are defined for this attribute: BLOCKSCACHED or BLOCKSCACH (historicalname), Blocks Cached (caption), BlocksCached (attribute name), and BLOCKSCACH (column name).

Blocks Local Path InformationThe number of getlocalpathinfo operations that are processed for a block. The type is integer (64-bitgauge).



The following names are defined for this attribute: BLOCKSGETLOCALPATHINFO or BLOCKSGETL(historical name), Blocks Local Path Information (caption), BlocksGetLocalPathInfo (attribute name),and BLOCKSGETL (column name).

Blocks UncachedThe total number of blocks that are uncached. The type is integer (32-bit gauge).



The following names are defined for this attribute: BLOCKSUNCACHED or BLOCKSUNCA (historicalname), Blocks Uncached (caption), BlocksUncached (attribute name), and BLOCKSUNCA (columnname).

Cache ReportThe number of operations to process cache reports that occurred in the DataNode. The type is integer(64-bit gauge).



The following names are defined for this attribute: CACHEREPORT or CACHEREPOR (historical name),Cache Report (caption), CacheReport (attribute name), and CACHEREPOR (column name).

Cache Report Average Time msThe average time (in milliseconds) that is required for processing the cache reports. The type isinteger (64-bit gauge).



The following names are defined for this attribute: CACHEREPORTAVERAGETIME_MSor CACHEREPO0 (historical name), Cache Report Average Time ms (caption),CacheReportAverageTime_ms (attribute name), and CACHEREPO0 (column name).





Copy Block Operation Average Time msThe average time that is spent to complete the block copy operation. The type is real number (32-bitgauge) with one decimal places of precision.



Attributes 71

The following names are defined for this attribute: COPYBLOCKOPERATIONAVERAGETIME_MSor COPYBLOCK0 (historical name), Copy Block Operation Average Time ms (caption),CopyBlockOperationAverageTime_ms (attribute name), and COPYBLOCK0 (column name).

Copy Block OperationsThe number of block copy operations that occurred in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: COPYBLOCKOPERATIONS or COPYBLOCKO(historical name), Copy Block Operations (caption), CopyBlockOperations (attribute name), andCOPYBLOCKO (column name).

File Synchronization CountThe number of file synchronization APIs that are called in the cluster. The type is integer (64-bitgauge).



The following names are defined for this attribute: FSYNCCOUNT (historical name), FileSynchronization Count (caption), FsyncCount (attribute name), and FSYNCCOUNT (column name).

File Synchronization Nanos Average TimeThe average time (in nanoseconds) that is spent to process the file synchronization operations. Thetype is real number (32-bit gauge) with one decimal places of precision.



The following names are defined for this attribute: FSYNCNANOSAVERAGETIME_MS or FSYNCNANO0(historical name), File Synchronization Nanos Average Time (caption), FsyncNanosAverageTime_ms(attribute name), and FSYNCNANO0 (column name).

File Synchronization Nanos OperationsThe number of file synchronization operations that occurred in the cluster. The type is integer (64-bitgauge).



The following names are defined for this attribute: FSYNCNANOSOPERATIONS or FSYNCNANOS(historical name), File Synchronization Nanos Operations (caption), FsyncNanosOperations (attributename), and FSYNCNANOS (column name).

Flush Nanos Average TimeThe average time (in nanoseconds) that is spent for flush operations. The type is real number (32-bitgauge) with one decimal places of precision.



The following names are defined for this attribute: FLUSHNANOSAVERAGETIME_MS or FLUSHNANO0(historical name), Flush Nanos Average Time (caption), FlushNanosAverageTime_ms (attribute name),and FLUSHNANO0 (column name).

Flush Nanos OperationsThe number of flush operations that occurred in the cluster. The type is integer (64-bit gauge).




The following names are defined for this attribute: FLUSHNANOSOPERATIONS or FLUSHNANOS(historical name), Flush Nanos Operations (caption), FlushNanosOperations (attribute name), andFLUSHNANOS (column name).

Packet Round Trip Nanos OperationsThe number of acknowledgement round trip operations that occurred in the cluster. The type isinteger (64-bit gauge).



The following names are defined for this attribute: PACKETROUNDTRIPTIMENANOSOPERATIONSor PACKETACKR (historical name), Packet Round Trip Nanos Operations (caption),PacketRoundTripTimeNanosOperations (attribute name), and PACKETACKR (column name).

Packet Round Trip Time Nanos Average TimeThe average time (in nanoseconds) of the acknowledgement round trip operations. The type is realnumber (32-bit gauge) with one decimal places of precision.



The following names are defined for this attribute:PACKETROUNDTRIPTIMENANOSAVERAGETIME_MS or PACKETACK0 (historical name), Packet RoundTrip Time Nanos Average Time (caption), PacketRoundTripTimeNanosAverageTime_ms (attributename), and PACKETACK0 (column name).

Read Block OperationThe number of block read operations that are processed in the cluster. The type is integer (64-bitgauge).



The following names are defined for this attribute: READBLOCKOPERATION or READBLOCKO(historical name), Read Block Operation (caption), ReadBlockOperation (attribute name), andREADBLOCKO (column name).

Read Block Operation Average Time msThe average time that is spent to complete block read operations. The type is real number (32-bitgauge) with one decimal places of precision.



The following names are defined for this attribute: READBLOCKOPERATIONAVERAGETIME_MSor READBLOCK0 (historical name), Read Block Operation Average Time ms (caption),ReadBlockOperationAverageTime_ms (attribute name), and READBLOCK0 (column name).

Replace Block Average Time msThe average time that is spent to complete the block replace operations. The type is real number (32-bit gauge) with one decimal places of precision.



The following names are defined for this attribute: REPLACEBLOCKAVERAGETIME_MSor REPLACEBL0 (historical name), Replace Block Average Time ms (caption),ReplaceBlockAverageTime_ms (attribute name), and REPLACEBL0 (column name).

Replace Block OperationsThe number of block replace operations that occurred in the cluster. The type is integer (64-bitgauge).

Attributes 73



The following names are defined for this attribute:REPLACEBLOCKOPERATIONNUMBEROFOPERATIONS or REPLACEBLO (historical name), ReplaceBlock Operations (caption), ReplaceBlockOperationNumberOfOperations (attribute name), andREPLACEBLO (column name).

Send DataPacket Blocked On Network Nanos Average TimeThe average waiting time (in nanoseconds) for packet send operations. The type is real number (32-bit gauge) with one decimal places of precision.



The following names are defined for this attribute:SENDDATAPACKETBLOCKEDONNETWORKNANOSAVERAGETIME_MS or SENDDATAP0(historical name), Send DataPacket Blocked On Network Nanos Average Time (caption),SendDataPacketBlockedOnNetworkNanosAverageTime_ms (attribute name), and SENDDATAP0(column name).

Send DataPacket Blocked On Network Nanos OperationsThe number of packet send operations that occurred in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute:SENDDATAPACKETBLOCKEDONNETWORKNANOSOPERATIONS or SENDDATAPA(historical name), Send DataPacket Blocked On Network Nanos Operations (caption),SendDataPacketBlockedOnNetworkNanosOperations (attribute name), and SENDDATAPA (columnname).

Send DataPacket Transfer Nanos Average TimeThe average transfer time (in nanoseconds) for packet send operations. The type is real number (32-bit gauge) with one decimal places of precision.



The following names are defined for this attribute:SENDDATAPACKETTRANSFERNANOSAVERAGETIME_MS or SENDDATAP2 (historical name), SendDataPacket Transfer Nanos Average Time (caption), SendDataPacketTransferNanosAverageTime_ms(attribute name), and SENDDATAP2 (column name).

Send DataPacket Transfer Nanos OperationsThe number of packet send operations. The type is integer (64-bit gauge).



The following names are defined for this attribute: SENDDATAPACKETTRANSFERNANOSOPERATIONSor SENDDATAP1 (historical name), Send DataPacket Transfer Nanos Operations (caption),SendDataPacketTransferNanosOperations (attribute name), and SENDDATAP1 (column name).

Session IdThe session in which the metrics data was collected. The type is integer (32-bit gauge) withenumerated values. The following values are defined: Value Exceeds Maximum (2147483647),Value Exceeds Minimum (-2147483648), null (-1). Any value that does not have a definition here isdisplayed in the User Interface.




The following names are defined for this attribute: SESSIONID (historical name), Session Id (caption),SessionId (attribute name), and SESSIONID (column name).

Write Block Average Time msThe average time that is spent to complete block write operations. The type is real number (32-bitgauge) with one decimal places of precision.



The following names are defined for this attribute: WRITEBLOCKAVERAGETIME_MS or WRITEBLOC0(historical name), Write Block Average Time ms (caption), WriteBlockAverageTime_ms (attributename), and WRITEBLOC0 (column name).

Write Block OperationsThe number of block write operations that occurred in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: WRITEBLOCKOPERATIONS or WRITEBLOCK(historical name), Write Block Operations (caption), WriteBlockOperations (attribute name), andWRITEBLOCK (column name).

Druid data setThis data set monitors the metrics for server and client components of Druid Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 DRUID in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.













Attributes 75





















































Attributes 77























Falcon data setThis data set monitors the metrics for server and client components of Falcon Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 FALCON in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.





























Attributes 79





















































Attributes 81








Flume data setThis data set monitors the metrics for server and client components of Flume Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 FLUME in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.














































Attributes 83











































FS Name System data setThis data set monitors the Hadoop Distributed File System. This data set is configured for historicalcollection. Note: If you define a threshold for this data set, any events are not displayed in the Eventstab of the Application Performance Dashboard. Instead, they are sent to Netcool/OMNIbus if eventforwarding is configured. This data set is displayed as KH8 FSNAMESYSTEM in the threshold editor. A datasample is sent to the server every minute and is maintained for 8 days by default. The attributes shown initalic are visible in the UI. All attributes are available for thresholds.

This data set contains the following attributes:Block Capacity MB

The storage capacity of a block in MB. The type is integer (64-bit gauge).

The source for this attribute is derived: BlockCapacity/1048576


Attributes 85

The following names are defined for this attribute: BLOCKCAPACITYMB or BLOCKCAPA0 (historicalname), Block Capacity MB (caption), BlockCapacityMB (attribute name), and BLOCKCAPA0 (columnname).

Block CapacityThe storage capacity of a block in bytes. The type is integer (64-bit gauge).



The following names are defined for this attribute: BLOCKCAPACITY or BLOCKCAPAC (historicalname), Block Capacity (caption), BlockCapacity (attribute name), and BLOCKCAPAC (column name).

Blocks TotalThe number of blocks in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: BLOCKSTOTAL or BLOCKSTOTA (historical name),Blocks Total (caption), BlocksTotal (attribute name), and BLOCKSTOTA (column name).

Capacity Used PercentThe percentage of used storage capacity. This attribute is a key attribute. The type is real number (64-bit gauge) with four decimal places of precision.

The source for this attribute is derived: CapacityUsedGB*100/CapacityTotalGB


The following names are defined for this attribute: CAPACITYUSEDPERCENT or CAPACITYU2(historical name), Capacity Used Percent (caption), CapacityUsedPercent (attribute name), andCAPACITYU2 (column name).





Corrupt BlocksThe number of corrupt blocks in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: CORRUPTBLOCKS or CORRUPTBLO (historicalname), Corrupt Blocks (caption), CorruptBlocks (attribute name), and CORRUPTBLO (column name).

Excess BlocksThe number of excess blocks in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: EXCESSBLOCKS or EXCESSBLOC (historical name),Excess Blocks (caption), ExcessBlocks (attribute name), and EXCESSBLOC (column name).

Files TotalThe total number of files in the cluster. The type is integer (64-bit gauge).




The following names are defined for this attribute: FILESTOTAL (historical name), Files Total (caption),FilesTotal (attribute name), and FILESTOTAL (column name).

Has StateThe state of the high availability of the NameNode. The type is string.



The following names are defined for this attribute: HASSTATE or HASTATE (historical name), Has State(caption), HasState (attribute name), and HASTATE (column name).





Last Written Transaction IdThe last transaction ID that is written to the log. The type is integer (64-bit gauge).



The following names are defined for this attribute: LASTWRITTENTRANSACTIONID or LASTWRITTE(historical name), Last Written Transaction Id (caption), LastWrittenTransactionId (attribute name),and LASTWRITTE (column name).

Missing BlocksThe number of missing blocks in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: MISSINGBLOCKS or MISSINGBLO (historicalname), Missing Blocks (caption), MissingBlocks (attribute name), and MISSINGBLO (column name).





Pending Deletion BlocksThe number of blocks that are waiting to be deleted. The type is integer (64-bit gauge).



The following names are defined for this attribute: PENDINGDELETIONBLOCKS or PENDINGDEL(historical name), Pending Deletion Blocks (caption), PendingDeletionBlocks (attribute name), andPENDINGDEL (column name).

Pending Replication BlocksThe number of blocks pending to be replicated. The type is integer (64-bit gauge).


Attributes 87


The following names are defined for this attribute: PENDINGREPLICATIONBLOCKS or PENDINGREP(historical name), Pending Replication Blocks (caption), PendingReplicationBlocks (attribute name),and PENDINGREP (column name).

Postponed Misreplicated BlocksThe number of blocks that are postponed for replication. The type is integer (64-bit gauge).



The following names are defined for this attribute: POSTPONEDMISREPLICATEDBLOCKSor POSTPONEDM (historical name), Postponed Misreplicated Blocks (caption),PostponedMisreplicatedBlocks (attribute name), and POSTPONEDM (column name).

Scheduled Replication BlocksThe number of blocks that are scheduled for replication. The type is integer (64-bit gauge).



The following names are defined for this attribute: SCHEDULEDREPLICATIONBLOCKS orSCHEDULEDR (historical name), Scheduled Replication Blocks (caption), ScheduledReplicationBlocks(attribute name), and SCHEDULEDR (column name).





Total FilesThe delta of number of files and directories. The type is DEFAULT(2).



The following names are defined for this attribute: TOTALFILES (historical name), Total Files (caption),TotalFiles (attribute name), and TOTALFILES (column name).

Transactions Since Last CheckpointThe number of transactions that occurred since the last checkpoint. The type is integer (64-bit gauge).



The following names are defined for this attribute: TRANSACTIONSSINCELASTCHECKPOINTor TRANSACTIO (historical name), Transactions Since Last Checkpoint (caption),TransactionsSinceLastCheckpoint (attribute name), and TRANSACTIO (column name).

Transactions Since Last RollbackThe number of transactions since the last log roll. The type is integer (64-bit gauge).



The following names are defined for this attribute: TRANSACTIONSSINCELASTROLLBACKor TRANSACTI0 (historical name), Transactions Since Last Rollback (caption),TransactionsSinceLastRollback (attribute name), and TRANSACTI0 (column name).


UnderReplicated BlocksThe number of blocks that are being replicated. The type is integer (64-bit gauge).



The following names are defined for this attribute: UNDERREPLICATEDBLOCKS or UNDERREPLI(historical name), UnderReplicated Blocks (caption), UnderReplicatedBlocks (attribute name), andUNDERREPLI (column name).

Capacity Remaining BytesThe available storage capacity of the file system in bytes. The type is integer (64-bit gauge).



The following names are defined for this attribute: CAPACITYREMAININGBYTES or CAPACITYR0(historical name), Capacity Remaining Bytes (caption), CapacityRemainingBytes (attribute name), andCAPACITYR0 (column name).

Capacity Remaining in GBThe available storage capacity (in GB) of the file system. The type is real number (64-bit gauge) withone decimal places of precision.



The following names are defined for this attribute: CAPACITYREMAININGGB or CAPACITYRE(historical name), Capacity Remaining in GB (caption), CapacityRemainingGB (attribute name), andCAPACITYRE (column name).

Capacity Total BytesThe storage capacity of DataNodes in bytes. The type is integer (64-bit gauge).



The following names are defined for this attribute: CAPACITYTOTALBYTES or CAPACITYT0 (historicalname), Capacity Total Bytes (caption), CapacityTotalBytes (attribute name), and CAPACITYT0 (columnname).

Capacity Total GBThe total storage capacity of DataNodes in GB. The type is real number (64-bit gauge) with onedecimal places of precision.



The following names are defined for this attribute: CAPACITYTOTALGB or CAPACITYTO (historicalname), Capacity Total GB (caption), CapacityTotalGB (attribute name), and CAPACITYTO (columnname).

Capacity Used BytesThe storage capacity (in bytes) that is used across all DataNodes. The type is integer (64-bit gauge).



The following names are defined for this attribute: CAPACITYUSEDBYTES or CAPACITYUS (historicalname), Capacity Used Bytes (caption), CapacityUsedBytes (attribute name), and CAPACITYUS(column name).

Attributes 89

Capacity Used GBThe total storage capacity (in GB) that is used across all DataNodes. The type is real number (64-bitgauge) with one decimal places of precision.



The following names are defined for this attribute: CAPACITYUSEDGB or CAPACITYU1 (historicalname), Capacity Used GB (caption), CapacityUsedGB (attribute name), and CAPACITYU1 (columnname).

Capacity Used NonDFS BytesThe storage space (in bytes) that is used by DataNodes for non DFS. The type is integer (64-bit gauge).



The following names are defined for this attribute: CAPACITYUSEDNONDFSBYTES or CAPACITYU0(historical name), Capacity Used NonDFS Bytes (caption), CapacityUsedNonDFSBytes (attributename), and CAPACITYU0 (column name).

Capacity Used NonDFS GBThe storage capacity (in GB) of a block that is not used by the Hadoop Distributed File System. Thetype is integer (64-bit gauge).

The source for this attribute is derived: CapacityUsedNonDFSBytes/1073741824


The following names are defined for this attribute: CAPACITYUSEDNONDFSGB or CAPACITYU3(historical name), Capacity Used NonDFS GB (caption), CapacityUsedNonDFSGB (attribute name), andCAPACITYU3 (column name).





Corrupt Blocks PercentThe percentage of corrupt blocks in the cluster. The type is integer (32-bit gauge).

The source for this attribute is derived: (CorruptBlocks/BlocksTotal)*100


The following names are defined for this attribute: CORRUPTBLOCKSPERCENT or CORRUPTBL0(historical name), Corrupt Blocks Percent (caption), CorruptBlocksPercent (attribute name), andCORRUPTBL0 (column name).

Expired HeartbeatsThe number of expired heartbeat sessions. The type is integer (64-bit gauge).



The following names are defined for this attribute: EXPIREDHEARTBEATS or EXPIREDHEA (historicalname), Expired Heartbeats (caption), ExpiredHeartbeats (attribute name), and EXPIREDHEA (columnname).

Last Checkpoint Time msThe time of last checkpoint. The type is integer (64-bit gauge).




The following names are defined for this attribute: LASTCHECKPOINTTIME_MS or LASTCHECKP(historical name), Last Checkpoint Time ms (caption), LastCheckpointTime_ms (attribute name), andLASTCHECKP (column name).

Last Loaded EditsThe elapsed time (in milliseconds) since the last standby NameNode load edit log was generated. Thetype is integer (64-bit gauge).



The following names are defined for this attribute: MILLISSINCELASTLOADEDEDITS or MILLISSINC(historical name), Last Loaded Edits (caption), MillisSinceLastLoadedEdits (attribute name), andMILLISSINC (column name).

Missing Blocks PercentThe percentage of process blocks that are missing in the cluster. The type is integer (32-bit gauge).

The source for this attribute is derived: (MissingBlocks/BlocksTotal)*100


The following names are defined for this attribute: MISSINGBLOCKSPERCENT or MISSINGBL0(historical name), Missing Blocks Percent (caption), MissingBlocksPercent (attribute name), andMISSINGBL0 (column name).

Pending DataNode Message CountThe number of block-related messages that are waiting to be processed. The type is integer (64-bitgauge).



The following names are defined for this attribute: PENDINGDATANODEMESSAGECOUNTor PENDINGDAT (historical name), Pending DataNode Message Count (caption),PendingDataNodeMessageCount (attribute name), and PENDINGDAT (column name).

SnapshotsThe number of snapshots that are created in the file system. The type is integer (64-bit gauge).



The following names are defined for this attribute: SNAPSHOTS (historical name), Snapshots(caption), Snapshots (attribute name), and SNAPSHOTS (column name).

Snapshottable DirectoriesThe number of snapshot table directories in the file system. The type is integer (64-bit gauge).



The following names are defined for this attribute: SNAPSHOTTABLEDIRECTORIES or SNAPSHOTTA(historical name), Snapshottable Directories (caption), SnapshottableDirectories (attribute name), andSNAPSHOTTA (column name).

Stale DataNodesThe number of DataNodes that are marked as stale due to delay in the heartbeat. The type is integer(64-bit gauge).


Attributes 91


The following names are defined for this attribute: STALEDATANODES or STALEDATAN (historicalname), Stale DataNodes (caption), StaleDataNodes (attribute name), and STALEDATAN (columnname).

Total LoadThe number of connections in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: TOTALLOAD (historical name), Total Load (caption),TotalLoad (attribute name), and TOTALLOAD (column name).

HBase data setThis data set monitors the metrics for server and client components of HBase Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 HBASE in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.














































Attributes 93











































HDFS data setThis data set monitors the metrics for server and client components of HDFS Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 HDFS in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.





Attributes 95























































Attributes 97






























Hive data setThis data set monitors the metrics for server and client components of Hive Service in the Hadoop clusterfor Ambari based Hadoop installations. Thresholds for this data set are associated with the Hadoopcomponent. This data set is displayed as KH8 HIVE in the threshold editor. A data sample is sent to theserver every minute and is maintained for 8 days by default. The attributes shown in italic are visible inthe UI. All attributes are available for thresholds.





















Attributes 99






















































Attributes 101














HOS Performance Object Status data setThe Performance Object Status data set contains information that reflects the status of other data sets soyou can see the status of all performance objects that make up this application all at once. Each of theseother performance data sets is represented by a row in this table (or other type of view). The status for adata set reflects the result of the last attempt to collect data for that data set, so you can see whether theagent is collecting data correctly. Unlike other data sets, the Performance Object Status data set does notreflect the state of the monitored application. This data set is most often used to determine why data isnot available for one of the performance data sets.

This data set contains the following attributes:Average Collection Duration

The average duration of all data collections of this group in seconds. The type is real number (32-bit counter) with two decimal places of precision with enumerated values. The following values aredefined: NO DATA (-100). Any value that does not have a definition here is displayed in the UserInterface.



The following names are defined for this attribute: AVERAGE_COLLECTION_DURATION or COLAVGD(historical name), Average Collection Duration (caption), Average_Collection_Duration (attributename), and COLAVGD (column name).

Cache Hit PercentThe percentage of external data requests for this group that were satisfied from the cache. The type isreal number (32-bit counter) with two decimal places of precision.




The following names are defined for this attribute: CACHE_HIT_PERCENT or CACHPCT (historicalname), Cache Hit Percent (caption), Cache_Hit_Percent (attribute name), and CACHPCT (columnname).

Cache HitsThe number of times an external data request for this group was satisfied from the cache. The type isinteger (32-bit counter).



The following names are defined for this attribute: CACHE_HITS or CACHEHT (historical name), CacheHits (caption), Cache_Hits (attribute name), and CACHEHT (column name).

Cache MissesThe number of times an external data request for this group was not available in the cache. The type isinteger (32-bit counter).



The following names are defined for this attribute: CACHE_MISSES or CACHEMS (historical name),Cache Misses (caption), Cache_Misses (attribute name), and CACHEMS (column name).

Error CodeThe error code associated with the query. The type is integer with enumerated values. The followingvalues are defined: NO ERROR (0), GENERAL ERROR (1), OBJECT NOT FOUND (2), COUNTER NOTFOUND (3), NAMESPACE ERROR (4), OBJECT CURRENTLY UNAVAILABLE (5), COM LIBRARY INITFAILURE (6), SECURITY INIT FAILURE (7), PROXY SECURITY FAILURE (9), NO INSTANCES RETURNED(10), ASSOCIATOR QUERY FAILED (11), REFERENCE QUERY FAILED (12), NO RESPONSE RECEIVED(13), CANNOT FIND JOINED QUERY (14), CANNOT FIND JOIN ATTRIBUTE IN QUERY 1 RESULTS (15),CANNOT FIND JOIN ATTRIBUTE IN QUERY 2 RESULTS (16), QUERY 1 NOT A SINGLETON (17), QUERY2 NOT A SINGLETON (18), NO INSTANCES RETURNED IN QUERY 1 (19), NO INSTANCES RETURNEDIN QUERY 2 (20), CANNOT FIND ROLLUP QUERY (21), CANNOT FIND ROLLUP ATTRIBUTE (22),FILE OFFLINE (23), NO HOSTNAME (24), MISSING LIBRARY (25), ATTRIBUTE COUNT MISMATCH(26), ATTRIBUTE NAME MISMATCH (27), COMMON DATA PROVIDER NOT STARTED (28), CALLBACKREGISTRATION ERROR (29), MDL LOAD ERROR (30), AUTHENTICATION FAILED (31), CANNOTRESOLVE HOST NAME (32), SUBNODE UNAVAILABLE (33), SUBNODE NOT FOUND IN CONFIG (34),ATTRIBUTE ERROR (35), CLASSPATH ERROR (36), CONNECTION FAILURE (37), FILTER SYNTAXERROR (38), FILE NAME MISSING (39), SQL QUERY ERROR (40), SQL FILTER QUERY ERROR (41),SQL DB QUERY ERROR (42), SQL DB FILTER QUERY ERROR (43), PORT OPEN FAILED (44), ACCESSDENIED (45), TIMEOUT (46), NOT IMPLEMENTED (47), REQUESTED A BAD VALUE (48), RESPONSETOO BIG (49), GENERAL RESPONSE ERROR (50), SCRIPT NONZERO RETURN (51), SCRIPT NOTFOUND (52), SCRIPT LAUNCH ERROR (53), CONF FILE DOES NOT EXIST (54), CONF FILE ACCESSDENIED (55), INVALID CONF FILE (56), EIF INITIALIZATION FAILED (57), CANNOT OPEN FORMATFILE (58), FORMAT FILE SYNTAX ERROR (59), REMOTE HOST UNAVAILABLE (60), EVENT LOG DOESNOT EXIST (61), PING FILE DOES NOT EXIST (62), NO PING DEVICE FILES (63), PING DEVICE LISTFILE MISSING (64), SNMP MISSING PASSWORD (65), DISABLED (66), URLS FILE NOT FOUND (67),XML PARSE ERROR (68), NOT INITIALIZED (69), ICMP SOCKETS FAILED (70), DUPLICATE CONF FILE(71), DELETED CONFIGURATION (72). Any value that does not have a definition here is displayed inthe User Interface.



The following names are defined for this attribute: ERROR_CODE or ERRCODE (historical name), ErrorCode (caption), Error_Code (attribute name), and ERRCODE (column name).

Attributes 103

Intervals SkippedThe number of times a background data collection for this group was skipped because the previouscollection was still running when the next one was due to start. The type is integer (32-bit counter).



The following names are defined for this attribute: INTERVALS_SKIPPED or INTSKIP (historical name),Intervals Skipped (caption), Intervals_Skipped (attribute name), and INTSKIP (column name).

Last Collection DurationThe duration of the most recently completed data collection of this group in seconds. The type is realnumber (32-bit counter) with two decimal places of precision.



The following names are defined for this attribute: LAST_COLLECTION_DURATION or COLDURA(historical name), Last Collection Duration (caption), Last_Collection_Duration (attribute name), andCOLDURA (column name).

Last Collection FinishedThe most recent time a data collection of this group finished. The type is timestamp with enumeratedvalues. The following values are defined: NOT COLLECTED (0691231190000000), NOT COLLECTED(0000000000000001). Any value that does not have a definition here is displayed in the UserInterface.



The following names are defined for this attribute: LAST_COLLECTION_FINISHED or COLFINI(historical name), Last Collection Finished (caption), Last_Collection_Finished (attribute name), andCOLFINI (column name).

Last Collection StartThe most recent time a data collection of this group started. The type is timestamp with enumeratedvalues. The following values are defined: NOT COLLECTED (0691231190000000), NOT COLLECTED(0000000000000001). Any value that does not have a definition here is displayed in the UserInterface.



The following names are defined for this attribute: LAST_COLLECTION_START or COLSTRT (historicalname), Last Collection Start (caption), Last_Collection_Start (attribute name), and COLSTRT (columnname).





Number of CollectionsThe number of data collections for this group since the agent started. The type is integer (32-bitcounter).




The following names are defined for this attribute: NUMBER_OF_COLLECTIONS or NUMCOLL(historical name), Number of Collections (caption), Number_of_Collections (attribute name), andNUMCOLL (column name).

Object NameThe name of the performance object. The type is string.



The following names are defined for this attribute: OBJECT_NAME or OBJNAME (historical name),Object Name (caption), Object_Name (attribute name), and OBJNAME (column name).

Object StatusThe status of the performance object. The type is integer with enumerated values. The followingvalues are defined: ACTIVE (0), INACTIVE (1). Any value that does not have a definition here isdisplayed in the User Interface.



The following names are defined for this attribute: OBJECT_STATUS or OBJSTTS (historical name),Object Status (caption), Object_Status (attribute name), and OBJSTTS (column name).

Object TypeThe type of the performance object. The type is integer with enumerated values. The following valuesare defined: WMI (0), PERFMON (1), WMI ASSOCIATION GROUP (2), JMX (3), SNMP (4), SHELLCOMMAND (5), JOINED GROUPS (6), CIMOM (7), CUSTOM (8), ROLLUP DATA (9), WMI REMOTEDATA (10), LOG FILE (11), JDBC (12), CONFIG DISCOVERY (13), NT EVENT LOG (14), FILTER (15),SNMP EVENT (16), PING (17), DIRECTOR DATA (18), DIRECTOR EVENT (19), SSH REMOTE SHELLCOMMAND (20). Any value that does not have a definition here is displayed in the User Interface.



The following names are defined for this attribute: OBJECT_TYPE or OBJTYPE (historical name),Object Type (caption), Object_Type (attribute name), and OBJTYPE (column name).

Query NameThe name of the attribute group. This attribute is a key attribute. The type is string.



The following names are defined for this attribute: QUERY_NAME or ATTRGRP (historical name),Query Name (caption), Query_Name (attribute name), and ATTRGRP (column name).

Refresh IntervalThe interval at which this group is refreshed in seconds. The type is integer (32-bit counter).



The following names are defined for this attribute: REFRESH_INTERVAL or REFRINT (historical name),Refresh Interval (caption), Refresh_Interval (attribute name), and REFRINT (column name).





Attributes 105

Hosts nodes data setThis data set provides the data of the nodes that are available in the Hadoop cluster. Thresholds for thisdata set are associated with the Hadoop component. This data set is displayed as KH8 HOSTS_NODESin the threshold editor. A data sample is sent to the server every minute and is maintained for 8 days bydefault. The attributes shown in italic are visible in the UI. All attributes are available for thresholds.

This data set contains the following attributes:Node

The managed system name of the agent. This attribute is a key attribute. The type is string.




Subnode AffinityThe affinity of this subnode. The type is string.



The following names are defined for this attribute: SUBNODE_AFFINITY or SN_AFFIN (historicalname), Subnode Affinity (caption), Subnode_Affinity (attribute name), and SN_AFFIN (column name).

Subnode MSNThe Managed System Name of this subnode. This attribute is a key attribute. The type is string.



The following names are defined for this attribute: SUBNODE_MSN or SN_MSN (historical name),Subnode MSN (caption), Subnode_MSN (attribute name), and SN_MSN (column name).

Subnode Resource NameThe resource name of this subnode. The type is string.



The following names are defined for this attribute: SUBNODE_RESOURCE_NAME or SN_RES(historical name), Subnode Resource Name (caption), Subnode_Resource_Name (attribute name), andSN_RES (column name).

Subnode TypeThe node type of this subnode. This attribute is a key attribute. The type is string.



The following names are defined for this attribute: SUBNODE_TYPE or SN_TYPE (historical name),Subnode Type (caption), Subnode_Type (attribute name), and SN_TYPE (column name).

Subnode VersionThe version of this subnode. The type is string.



The following names are defined for this attribute: SUBNODE_VERSION or SN_VER (historical name),Subnode Version (caption), Subnode_Version (attribute name), and SN_VER (column name).






JVM Metrics data setThis data set monitors the Java Virtual Machine (JVM) metrics of the Hadoop cluster. Note: If you define athreshold for this data set, any events are not displayed in the Events tab of the Application PerformanceDashboard. Instead, they are sent to Netcool/OMNIbus if event forwarding is configured. This data set isdisplayed as KH8 JVMMETRICS in the threshold editor. A data sample is sent to the server every minuteand is maintained for 8 days by default. The attributes shown in italic are visible in the UI. All attributesare available for thresholds.

This data set contains the following attributes:Garbage Collection Rate

The rate at which Garbage collection is done. The type is real number (64-bit gauge) with four decimalplaces of precision.

The source for this attribute is derived: ((GarbageCollectionCount/GarbageCollectionTime_ms)*1000)/60


The following names are defined for this attribute: GCRATE (historical name), Garbage Collection Rate(caption), GcRate (attribute name), and GCRATE (column name).

Garbage Collection Warning ThresholdThe garbage collection warning threshold value for the node. The type is integer (64-bit gauge)with enumerated values. The following values are defined: NA (-1). Any value that does not have adefinition here is displayed in the User Interface.



The following names are defined for this attribute: GARBAGECOLLECTIONWARNINGTHRESHOLDor GARBAGECOL (historical name), Garbage Collection Warning Threshold (caption),GarbageCollectionWarningThreshold (attribute name), and GARBAGECOL (column name).

HostnameThe name of the host where Java Virtual Machine is installed. This attribute is a key attribute. The typeis string.




Logs ErrorThe number of logs that are in the error state. The type is integer (32-bit gauge).



The following names are defined for this attribute: LOGERROR (historical name), Logs Error (caption),LogError (attribute name), and LOGERROR (column name).

Attributes 107

Logs FatalThe number of logs that are in the fatal state. The type is integer (32-bit gauge).



The following names are defined for this attribute: LOGFATAL (historical name), Logs Fatal (caption),LogFatal (attribute name), and LOGFATAL (column name).

Logs WarnThe number of logs that are in the warning state. The type is integer (32-bit gauge).



The following names are defined for this attribute: LOGWARN (historical name), Logs Warn (caption),LogWarn (attribute name), and LOGWARN (column name).

Memory Heap Used PercentThe percentage of heap memory (in MB) that is used by the Java Virtual Machine of the daemon. Thetype is real number (64-bit gauge) with four decimal places of precision.

The source for this attribute is derived: (MemoryHeapUsedMB/MemoryHeapMaximumMB)*100


The following names are defined for this attribute: MEMHEAPUSEDPERCENT or MEMHUPER(historical name), Memory Heap Used Percent (caption), MemHeapUsedPercent (attribute name), andMEMHUPER (column name).

Memory HeapCommitted MBThe heap memory (in MB) that is committed by the Java Virtual Machine of the daemon. The type isreal number (64-bit gauge) with four decimal places of precision.



The following names are defined for this attribute: MEMORYHEAPCOMMITTEDMB or MEMHEAPCOM(historical name), Memory HeapCommitted MB (caption), MemoryHeapCommittedMB (attributename), and MEMHEAPCOM (column name).

Memory HeapUsed MBThe heap memory (in MB) that is used by the Java Virtual Machine of the daemon. The type is realnumber (64-bit gauge) with four decimal places of precision.



The following names are defined for this attribute: MEMORYHEAPUSEDMB or MEMHEAPUSE(historical name), Memory HeapUsed MB (caption), MemoryHeapUsedMB (attribute name), andMEMHEAPUSE (column name).

Memory Maximum MBThe maximum amount of memory (in MB) that is assigned to the Java Virtual Machine of the daemon.The type is real number (64-bit gauge) with four decimal places of precision.



The following names are defined for this attribute: MEMORYMAXIMUMMB or MEMMAXM (historicalname), Memory Maximum MB (caption), MemoryMaximumMB (attribute name), and MEMMAXM(column name).


Memory NonHeap Committed MBThe non-heap memory (in MB) that is committed by the Java Virtual Machine of the daemon. The typeis real number (64-bit gauge) with four decimal places of precision.



The following names are defined for this attribute: MEMORYNONHEAPCOMMITTEDMBor MEMNONHEA0 (historical name), Memory NonHeap Committed MB (caption),MemoryNonHeapCommittedMB (attribute name), and MEMNONHEA0 (column name).

Memory NonHeap Free MBThe non heap memory (in MB) that is available in the node of the cluster. The type is real number (64-bit gauge) with four decimal places of precision.

The source for this attribute is derived: MemoryNonHeapCommittedMB-MemoryNonHeapUsedMB


The following names are defined for this attribute: MEMORYNONHEAPFREEMB or MEMNONHEA1(historical name), Memory NonHeap Free MB (caption), MemoryNonHeapFreeMB (attribute name), andMEMNONHEA1 (column name).

Memory NonHeap Used MBThe non-heap memory (in MB) that is used by Java Virtual Machine of the daemon. The type is realnumber (64-bit gauge) with four decimal places of precision.



The following names are defined for this attribute: MEMORYNONHEAPUSEDMB or MEMNONHEAP(historical name), Memory NonHeap Used MB (caption), MemoryNonHeapUsedMB (attribute name),and MEMNONHEAP (column name).





Process NameThe name of the process of the node in the cluster. This attribute is a key attribute. The type is string.



The following names are defined for this attribute: PROCESSNAME or PROCESSNAM (historical name),Process Name (caption), ProcessName (attribute name), and PROCESSNAM (column name).

Threads BlockedThe number of threads that are in the blocked state. The type is integer (32-bit gauge).



The following names are defined for this attribute: THREADSBLOCKED or THREADSBLO (historicalname), Threads Blocked (caption), ThreadsBlocked (attribute name), and THREADSBLO (columnname).

Threads NewThe number of new threads that are available in the cluster. The type is integer (32-bit gauge).

Attributes 109



The following names are defined for this attribute: THREADSNEW (historical name), Threads New(caption), ThreadsNew (attribute name), and THREADSNEW (column name).

Threads RunnableThe number of threads that are in the runnable state. The type is integer (32-bit gauge).



The following names are defined for this attribute: THREADSRUNNABLE or THREADSRUN (historicalname), Threads Runnable (caption), ThreadsRunnable (attribute name), and THREADSRUN (columnname).

Threads TerminatedThe number of terminated threads. The type is integer (32-bit gauge).



The following names are defined for this attribute: THREADSTERMINATED or THREADSTER (historicalname), Threads Terminated (caption), ThreadsTerminated (attribute name), and THREADSTER(column name).

Threads Timed WaitingThe number of threads that are in the timed waiting state. The type is integer (64-bit gauge).



The following names are defined for this attribute: THREADSTIMEDWAITING or THREADSTIM(historical name), Threads Timed Waiting (caption), ThreadsTimedWaiting (attribute name), andTHREADSTIM (column name).

Threads WaitingThe number of threads that are in the waiting state. The type is integer (32-bit gauge).



The following names are defined for this attribute: THREADSWAITING or THREADSWAI (historicalname), Threads Waiting (caption), ThreadsWaiting (attribute name), and THREADSWAI (columnname).














Garbage Collection CountThe count of garbage collection. The type is integer (64-bit gauge).



The following names are defined for this attribute: GARBAGECOLLECTIONCOUNT or GCCOUNT(historical name), Garbage Collection Count (caption), GarbageCollectionCount (attribute name), andGCCOUNT (column name).

Garbage Collection Count Mark SweepThe count of PS MarkSweep garbage collection. The type is integer (64-bit gauge) with enumeratedvalues. The following values are defined: NA (-1). Any value that does not have a definition here isdisplayed in the User Interface.



The following names are defined for this attribute: GARBAGECOLLECTIONCOUNTPSMARKSWEEPor GCCOUNTPSM (historical name), Garbage Collection Count Mark Sweep (caption),GarbageCollectionCountPSMarkSweep (attribute name), and GCCOUNTPSM (column name).

Garbage Collection Count ScavengeThe count of PS Scavenge garbage collection. The type is integer (64-bit gauge) with enumeratedvalues. The following values are defined: NA (-1). Any value that does not have a definition here isdisplayed in the User Interface.



The following names are defined for this attribute: GARBAGECOLLECTIONCOUNTPSSCAVENGEor GCCOUNTPSS (historical name), Garbage Collection Count Scavenge (caption),GarbageCollectionCountPSScavenge (attribute name), and GCCOUNTPSS (column name).

Garbage Collection Information ThresholdThe garbage collection threshold information for the node. The type is integer (64-bit gauge) withenumerated values. The following values are defined: NA (-1). Any value that does not have adefinition here is displayed in the User Interface.



The following names are defined for this attribute: GARBAGECOLLECTIONINFORMATIONTHRESHOLDor GARBAGECO0 (historical name), Garbage Collection Information Threshold (caption),GarbageCollectionInformationThreshold (attribute name), and GARBAGECO0 (column name).

Garbage Collection Sleep Time msThe garbage collection sleep time in milliseconds. The type is integer (64-bit gauge) with enumeratedvalues. The following values are defined: NA (-1). Any value that does not have a definition here isdisplayed in the User Interface.



Attributes 111

The following names are defined for this attribute: GARABAGECOLLECTIONSLEEPTIME_MSor GARABAGECO (historical name), Garbage Collection Sleep Time ms (caption),GarabageCollectionSleepTime_ms (attribute name), and GARABAGECO (column name).

Garbage Collection Time Mark SweepThe time (in milliseconds) that is required for the PS MarkSweep garbage collection. The type isinteger (64-bit gauge) with enumerated values. The following values are defined: NA (-1). Any valuethat does not have a definition here is displayed in the User Interface.



The following names are defined for this attribute:GARBAGECOLLECTIONTIMEMILLISPSMARKSWEEP or GCTIMEMIL0 (historical name), GarbageCollection Time Mark Sweep (caption), GarbageCollectionTimeMillisPSMarkSweep (attribute name),and GCTIMEMIL0 (column name).

Garbage Collection Time msThe time (in milliseconds) that is required for the garbage collection. The type is integer (64-bitgauge).



The following names are defined for this attribute: GARBAGECOLLECTIONTIME_MS or GCTIMEMIL1(historical name), Garbage Collection Time ms (caption), GarbageCollectionTime_ms (attribute name),and GCTIMEMIL1 (column name).

Garbage Collection Time Scavenge msThe time (in milliseconds) that is required for the PS Scavenge garbage collection. The type is integer(64-bit gauge) with enumerated values. The following values are defined: NA (-1). Any value that doesnot have a definition here is displayed in the User Interface.



The following names are defined for this attribute: GARBAGECOLLECTIONTIMEPSSCAVENGEMSor GCTIMEMILL (historical name), Garbage Collection Time Scavenge ms (caption),GarbageCollectionTimePSScavengems (attribute name), and GCTIMEMILL (column name).

Logs InformationThe number of information logs. The type is integer (32-bit gauge).



The following names are defined for this attribute: LOGINFO (historical name), Logs Information(caption), LogInfo (attribute name), and LOGINFO (column name).

Memory HeapMaximum MBThe maximum heap memory (in MB) that is used by the Java Virtual Machine of the daemon. The typeis integer (64-bit gauge).



The following names are defined for this attribute: MEMORYHEAPMAXIMUMMB or MEMORYHEAP(historical name), Memory HeapMaximum MB (caption), MemoryHeapMaximumMB (attribute name),and MEMORYHEAP (column name).

Memory NonHeap Maximum MBThe maximum non-heap memory (in MB) that is used by the Java Virtual Machine of the daemon. Thetype is integer (64-bit gauge).




The following names are defined for this attribute: MEMORYNONHEAPMAXIMUMMBor MEMORYNONH (historical name), Memory NonHeap Maximum MB (caption),MemoryNonHeapMaximumMB (attribute name), and MEMORYNONH (column name).





Kafka data setThis data set monitors the metrics for server and client components of Kafka Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 KAFKA in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.















Attributes 113























































Attributes 115



















Knox data setThis data set monitors the metrics for server and client components of Knox Service in the Hadoop clusterfor Ambari based Hadoop installations. Thresholds for this data set are associated with the Hadoopcomponent. This data set is displayed as KH8 KNOX in the threshold editor. A data sample is sent to theserver every minute and is maintained for 8 days by default. The attributes shown in italic are visible inthe UI. All attributes are available for thresholds.

































Attributes 117





















































Attributes 119




Mahout data setThis data set monitors the metrics for Mahout Tool in the Hadoop cluster for Ambari based Hadoopinstallations. Thresholds for this data set are associated with the Hadoop component. This data set isdisplayed as KH8 MAHOUT in the threshold editor. A data sample is sent to the server every minute andis maintained for 8 days by default. The attributes shown in italic are visible in the UI. All attributes areavailable for thresholds.

















































Attributes 121








































MapReduce2 data setThis data set monitors the metrics for server and client components of MapReduce2 Service in theHadoop cluster for Ambari based Hadoop installations. Thresholds for this data set are associated withthe Hadoop component. This data set is displayed as KH8 MAPREDUCE2 in the threshold editor. A datasample is sent to the server every minute and is maintained for 8 days by default. The attributes shown initalic are visible in the UI. All attributes are available for thresholds.









Attributes 123






















































Attributes 125



























NameNode data setThis data set monitors the NameNode metrics of the Hadoop cluster.

This data set contains the following attributes:Add Block

The number of add blocks operations that occurred in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: ADDBLOCK or ADDBLOCKOP (historical name), AddBlock (caption), AddBlock (attribute name), and ADDBLOCKOP (column name).

Additional DataNodeThe number of operations that occurred in the cluster to retrieve additional DataNodes. The type isinteger (64-bit gauge).



The following names are defined for this attribute: ADDITIONALDATANODE or GETADDITIO (historicalname), Additional DataNode (caption), AdditionalDatanode (attribute name), and GETADDITIO(column name).

Allow SnapshotThe number of allowsnapshot operations that occurred in the cluster. The type is integer (64-bitgauge).



The following names are defined for this attribute: ALLOWSNAPSHOT or ALLOWSNAPS (historicalname), Allow Snapshot (caption), AllowSnapshot (attribute name), and ALLOWSNAPS (column name).

Block LocationsThe number of operations that occurred in the cluster to retrieve block locations. The type is integer(64-bit gauge).



The following names are defined for this attribute: BLOCKLOCATIONS or GETBLOCKLO (historicalname), Block Locations (caption), BlockLocations (attribute name), and GETBLOCKLO (column name).

Block Received DeletedThe number of operations that occurred in the cluster to receive and delete blocks. The type is integer(64-bit gauge).



The following names are defined for this attribute: BLOCKRECEIVEDDELETED or BLOCKRECEI(historical name), Block Received Deleted (caption), BlockReceivedDeleted (attribute name), andBLOCKRECEI (column name).

Block Report Average Time msThe average time that is taken to process block reports from a node. The type is real number (32-bitgauge) with one decimal places of precision.



Attributes 127

The following names are defined for this attribute: BLOCKREPORTAVERAGETIME_MS or BLOCKREPO0(historical name), Block Report Average Time ms (caption), BlockReportAverageTime_ms (attributename), and BLOCKREPO0 (column name).

Block Report OperationsThe number of block reports that are available in a node. The type is integer (64-bit gauge).



The following names are defined for this attribute: BLOCKREPORTOPERATIONS or BLOCKREPOR(historical name), Block Report Operations (caption), BlockReportOperations (attribute name), andBLOCKREPOR (column name).

Cache ReportThe number of operations to process cache reports that occurred in the DataNode. The type is integer(64-bit gauge).



The following names are defined for this attribute: CACHEREPORT or CACHEREPOR (historical name),Cache Report (caption), CacheReport (attribute name), and CACHEREPOR (column name).

Cache Report Average TimeThe average time (in milliseconds) that is required for processing of cache reports. The type is integer(64-bit gauge).



The following names are defined for this attribute: CACHEREPORTAVERAGETIME or CACHEREPO0(historical name), Cache Report Average Time (caption), CacheReportAverageTime (attribute name),and CACHEREPO0 (column name).









Create File OperationsThe number of files that are created. The type is integer (64-bit gauge).



The following names are defined for this attribute: CREATEFILEOPERATIONS or CREATEFILE(historical name), Create File Operations (caption), CreateFileOperations (attribute name), andCREATEFILE (column name).


Create SnapshotThe number of snapshots that are created in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: CREATESNAPSHOT or CREATESNAP (historicalname), Create Snapshot (caption), CreateSnapshot (attribute name), and CREATESNAP (columnname).

Delete SnapshotThe number of snapshots that are deleted in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: DELETESNAPSHOT or DELETESNAP (historicalname), Delete Snapshot (caption), DeleteSnapshot (attribute name), and DELETESNAP (columnname).

Deleted FileThe number of delete file operations that occurred in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: DELETEFILE (historical name), Deleted File(caption), DeleteFile (attribute name), and DELETEFILE (column name).

Disallow SnapshotThe number of disallowsnapshot operations that occurred in the cluster. The type is integer (64-bitgauge).



The following names are defined for this attribute: DISALLOWSNAPSHOT or DISALLOWSN (historicalname), Disallow Snapshot (caption), DisallowSnapshot (attribute name), and DISALLOWSN (columnname).

Edit Average Time msThe average time (in milliseconds) that is required to process an edit operation. The type is integer(64-bit gauge).



The following names are defined for this attribute: EDITAVERAGETIME_MS or EDITAVERAG (historicalname), Edit Average Time ms (caption), EditAverageTime_ms (attribute name), and EDITAVERAG(column name).

Edit OperationsThe number of edit operations that occurred in the secondary NameNode. The type is integer (64-bitgauge).



The following names are defined for this attribute: EDITOPERATIONS or EDITOPERAT (historicalname), Edit Operations (caption), EditOperations (attribute name), and EDITOPERAT (column name).

File InformationThe number of operations that occurred in the cluster for reading file information. The type is integer(64-bit gauge).

Attributes 129



The following names are defined for this attribute: FILEINFO or FILEINFOOP (historical name), FileInformation (caption), FileInfo (attribute name), and FILEINFOOP (column name).

File System Image Load Time msThe time (in milliseconds) that is required for loading the File System Image when the NameNode isstarted. The type is integer (64-bit gauge).



The following names are defined for this attribute: FILESYSTEMIMAGELOADTIME_MS or FSIMAGELOA(historical name), File System Image Load Time ms (caption), FileSystemImageLoadTime_ms(attribute name), and FSIMAGELOA (column name).

Files AppendedThe number of files that are appended. The type is integer (64-bit gauge).



The following names are defined for this attribute: FILESAPPENDED or FILESAPPEN (historical name),Files Appended (caption), FilesAppended (attribute name), and FILESAPPEN (column name).

Files CreatedThe delta of number of files and directories created by create or mkdir operations. The type isDEFAULT(2).



The following names are defined for this attribute: FILESCREATED or FILESCREAT (historical name),Files Created (caption), FilesCreated (attribute name), and FILESCREAT (column name).

Files DeletedThe number of files that are deleted in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: FILESDELETED or FILESDELET (historical name),Files Deleted (caption), FilesDeleted (attribute name), and FILESDELET (column name).

Files ListsThe number of files that are listed in the cluster by using the get listing operation. The type is integer(64-bit gauge).



The following names are defined for this attribute: FILESINGETLISTS or FILESINGET (historicalname), Files Lists (caption), FilesInGetLists (attribute name), and FILESINGET (column name).

Files RenamedThe number of files that are renamed in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: FILESRENAMED or FILESRENAM (historical name),Files Renamed (caption), FilesRenamed (attribute name), and FILESRENAM (column name).


FsImage Download Average Time msThe average time (in milliseconds) that is taken to download fsimage from Secondary NameNode. Thetype is integer (64-bit gauge).



The following names are defined for this attribute: GETIMAGETIME_MS or GETIMAGETI (historicalname), FsImage Download Average Time ms (caption), GetImageTime_ms (attribute name), andGETIMAGETI (column name).

FsImage Download CountTotal number of fsimage downloads from Secondary NameNode. The type is integer (32-bit gauge).



The following names are defined for this attribute: GETIMAGE (historical name), FsImage DownloadCount (caption), GetImage (attribute name), and GETIMAGE (column name).

FsImage Upload Average Time msThe average time (in milliseconds) that is taken to upload the fsimage to Secondary NameNode. Thetype is integer (64-bit gauge).



The following names are defined for this attribute: PUTIMAGEAVERAGETIME_MS or PUTIMAGEAV(historical name), FsImage Upload Average Time ms (caption), PutImageAverageTime_ms (attributename), and PUTIMAGEAV (column name).

FsImage Upload CountTotal number of fsimage uploads to Secondary NameNode The type is integer (64-bit gauge).



The following names are defined for this attribute: PUTIMAGE (historical name), FsImage UploadCount (caption), PutImage (attribute name), and PUTIMAGE (column name).





Link TargetThe number of files and directories that are listed by directory listing operations. The type is integer(64-bit gauge).



The following names are defined for this attribute: GETLINKTARGET or GETLINKTAR (historical name),Link Target (caption), GetLinkTarget (attribute name), and GETLINKTAR (column name).

Links CreatedThe number of symbolic links that are created in the cluster. The type is integer (64-bit gauge).



Attributes 131

The following names are defined for this attribute: CREATELINK or CREATESYML (historical name),Links Created (caption), Createlink (attribute name), and CREATESYML (column name).

List Snapshottable DirectoriesThe number of operations that occurred to list snapshottable directories. The type is integer (64-bitgauge).



The following names are defined for this attribute: LISTSNAPSHOTTABLEDIRECTORIES orLISTSNAPSH (historical name), List Snapshottable Directories (caption), ListSnapshottableDirectories(attribute name), and LISTSNAPSH (column name).

ListsThe number of file listing operations that occurred in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: GETLISTS or GETLISTING (historical name), Lists(caption), GetLists (attribute name), and GETLISTING (column name).





Process NameThe name of the process. The type is string.



The following names are defined for this attribute: PROCESSNAME or PROCESSNAM (historical name),Process Name (caption), ProcessName (attribute name), and PROCESSNAM (column name).

Rename SnapshotThe number of snapshots that are renamed. The type is integer (64-bit gauge).



The following names are defined for this attribute: RENAMESNAPSHOT or RENAMESNAP (historicalname), Rename Snapshot (caption), RenameSnapshot (attribute name), and RENAMESNAP (columnname).

Safe Mode Time msThe time (in milliseconds) during which the NameNode remains in the safe mode. The type is integer(64-bit gauge).



The following names are defined for this attribute: SAFEMODETIME_MS or SAFEMODETI (historicalname), Safe Mode Time ms (caption), SafeModeTime_ms (attribute name), and SAFEMODETI (columnname).






Snapshot ReportThe number of operations that occurred in the cluster to retrieve snapshot differences. The type isinteger (64-bit gauge).



The following names are defined for this attribute: SNAPSHOTREPORT or SNAPSHOTDI (historicalname), Snapshot Report (caption), SnapshotReport (attribute name), and SNAPSHOTDI (columnname).

Storage Block ReportThe number of block reports that the DataNode generates for each storage. The type is integer (64-bitgauge).



The following names are defined for this attribute: STORAGEBLOCKREPORT or STORAGEBLO(historical name), Storage Block Report (caption), StorageBlockReport (attribute name), andSTORAGEBLO (column name).

Synchronization Average Time msThe average time that is required for sync operations. The type is real number (32-bit gauge) with onedecimal places of precision.



The following names are defined for this attribute: SYNCHRONIZATIONAVERAGETIME_MSor SYNCSAVGTI (historical name), Synchronization Average Time ms (caption),SynchronizationAverageTime_ms (attribute name), and SYNCSAVGTI (column name).

Synchronization OperationsThe number of sync operations that occurred in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: SYNCHRONIZATIONOPERATIONS orSYNCSNUMOP (historical name), Synchronization Operations (caption), SynchronizationOperations(attribute name), and SYNCSNUMOP (column name).





Attributes 133

TransactionsThe number of transactions that occurred in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: TRANSACTIONS or TRANSACTIO (historical name),Transactions (caption), Transactions (attribute name), and TRANSACTIO (column name).

Transactions Average Time msThe average time that is required for processing a transaction. The type is real number (32-bit gauge)with one decimal places of precision.



The following names are defined for this attribute: TRANSACTIONSAVERAGETIME_MSor TRANSACTI0 (historical name), Transactions Average Time ms (caption),TransactionsAverageTime_ms (attribute name), and TRANSACTI0 (column name).

Transactions Batched In SynchronizationThe number of transactions that are batched together. The type is integer (64-bit gauge).



The following names are defined for this attribute: TRANSACTIONSBATCHEDINSYNCHRONIZATIONor TRANSACTI1 (historical name), Transactions Batched In Synchronization (caption),TransactionsBatchedInSynchronization (attribute name), and TRANSACTI1 (column name).

NiFi data setThis data set monitors the metrics for server and client components of NiFi Service in the Hadoop clusterfor Ambari based Hadoop installations. Thresholds for this data set are associated with the Hadoopcomponent. This data set is displayed as KH8 NIFI in the threshold editor. A data sample is sent to theserver every minute and is maintained for 8 days by default. The attributes shown in italic are visible inthe UI. All attributes are available for thresholds.






































Attributes 135



















































Attributes 137

NiFi Registry data setThis data set monitors the metrics for server and client components of NiFi Registry Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 NIFIREGISTRY in the threshold editor. A datasample is sent to the server every minute and is maintained for 8 days by default. The attributes shown initalic are visible in the UI. All attributes are available for thresholds.



















































Attributes 139






































NodeManager Metrics data setThis data set monitors the NodeManager in the cluster.

This data set contains the following attributes:Allocated Containers

The number of allocated containers to a node. The type is integer (64-bit gauge).



The following names are defined for this attribute: ALLOCATEDCONTAINERS or ALLOCATEDC(historical name), Allocated Containers (caption), AllocatedContainers (attribute name), andALLOCATEDC (column name).

Available Space GBThe amount of available memory in GB. The type is integer (64-bit gauge).



The following names are defined for this attribute: AVAILABLESPACEGB or AVAILABLEG (historicalname), Available Space GB (caption), AvailableSpaceGB (attribute name), and AVAILABLEG (columnname).





Attributes 141

Containers Allocated Space GBThe amount of allocated memory in GB. The type is integer (64-bit gauge).



The following names are defined for this attribute: ALLOCATEDSPACEGB or ALLOCATEDG (historicalname), Containers Allocated Space GB (caption), AllocatedSpaceGB (attribute name), andALLOCATEDG (column name).

Containers CompletedThe number of containers that are completed by an application. The type is integer (64-bit gauge).



The following names are defined for this attribute: CONTAINERSCOMPLETED or CONTAINER0(historical name), Containers Completed (caption), ContainersCompleted (attribute name), andCONTAINER0 (column name).

Containers FailedThe number of containers in the failed state. The type is integer (64-bit gauge).



The following names are defined for this attribute: CONTAINERSFAILED or CONTAINER1 (historicalname), Containers Failed (caption), ContainersFailed (attribute name), and CONTAINER1 (columnname).

Containers InitiatedThe number of containers that are in the initializing state. The type is integer (64-bit gauge).



The following names are defined for this attribute: CONTAINERSINITIATED or CONTAINER3(historical name), Containers Initiated (caption), ContainersInitiated (attribute name), andCONTAINER3 (column name).

Containers KilledThe number of containers that are in the killed state. The type is integer (64-bit gauge).



The following names are defined for this attribute: CONTAINERSKILLED or CONTAINER2 (historicalname), Containers Killed (caption), ContainersKilled (attribute name), and CONTAINER2 (columnname).

Containers LaunchedThe number of containers that are opened by an application. The type is integer (64-bit gauge).



The following names are defined for this attribute: CONTAINERSLAUNCHED or CONTAINERS(historical name), Containers Launched (caption), ContainersLaunched (attribute name), andCONTAINERS (column name).

Containers RunningThe number of containers that are in the running state. The type is integer (64-bit gauge).




The following names are defined for this attribute: CONTAINERSRUNNING or CONTAINER4 (historicalname), Containers Running (caption), ContainersRunning (attribute name), and CONTAINER4 (columnname).

ContextThe interface for sharing information across components in a NodeManager. The type is string.




HostnameThe name of the host where the node is configured. This attribute is a key attribute. The type is string.












Oozie data setThis data set monitors the metrics for server and client components of Oozie Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 OOZIE in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.






Attributes 143






















































Attributes 145






























Operating System data setThis data set monitors the Operating System details of the Host node. Note: If you define a threshold forthis data set, any events are not displayed in the Events tab of the Application Performance Dashboard.Instead, they are sent to Netcool/OMNIbus if event forwarding is configured. This data set is displayedas KH8 OPERATINGSYSTEM in the threshold editor. A data sample is sent to the server every minute andis maintained for 8 days by default. The attributes shown in italic are visible in the UI. All attributes areavailable for thresholds.

This data set contains the following attributes:AvailableProcessors

The total number of processors on system. The type is integer (64-bit gauge).



The following names are defined for this attribute: AVAILABLEPROCESSORS or AVAIPROC (historicalname), AvailableProcessors (caption), AvailableProcessors (attribute name), and AVAIPROC (columnname).













ProcessCPULoadThe recent cpu usage for the Java Virtual Machine process. The type is real number (64-bit gauge)with four decimal places of precision.



Attributes 147

The following names are defined for this attribute: PROCESSCPULOAD or PROCPUL (historical name),ProcessCPULoad (caption), ProcessCPULoad (attribute name), and PROCPUL (column name).

SystemCpuLoadThe recent cpu usage for the whole system. The type is real number (64-bit gauge) with four decimalplaces of precision.



The following names are defined for this attribute: SYSTEMCPULOAD or SYSCPUL (historical name),SystemCpuLoad (caption), SystemCpuLoad (attribute name), and SYSCPUL (column name).





Performance Object Status data setThe Performance Object Status data set contains information that reflects the status of other data sets soyou can see the status of all performance objects that make up this application all at once. Each of theseother performance data sets is represented by a row in this table (or other type of view). The status for adata set reflects the result of the last attempt to collect data for that data set, so you can see whether theagent is collecting data correctly. Unlike other data sets, the Performance Object Status data set does notreflect the state of the monitored application. This data set is most often used to determine why data isnot available for one of the performance data sets.

This data set contains the following attributes:Average Collection Duration

The average duration of all data collections of this group in seconds. The type is real number (32-bit counter) with two decimal places of precision with enumerated values. The following values aredefined: NO DATA (-100). Any value that does not have a definition here is displayed in the UserInterface.



The following names are defined for this attribute: AVERAGE_COLLECTION_DURATION or COLAVGD(historical name), Average Collection Duration (caption), Average_Collection_Duration (attributename), and COLAVGD (column name).

Cache Hit PercentThe percentage of external data requests for this group that were satisfied from the cache. The type isreal number (32-bit counter) with two decimal places of precision.



The following names are defined for this attribute: CACHE_HIT_PERCENT or CACHPCT (historicalname), Cache Hit Percent (caption), Cache_Hit_Percent (attribute name), and CACHPCT (columnname).

Cache HitsThe number of times an external data request for this group was satisfied from the cache. The type isinteger (32-bit counter).




The following names are defined for this attribute: CACHE_HITS or CACHEHT (historical name), CacheHits (caption), Cache_Hits (attribute name), and CACHEHT (column name).

Cache MissesThe number of times an external data request for this group was not available in the cache. The type isinteger (32-bit counter).



The following names are defined for this attribute: CACHE_MISSES or CACHEMS (historical name),Cache Misses (caption), Cache_Misses (attribute name), and CACHEMS (column name).

Error CodeThe error code associated with the query. The type is integer with enumerated values. The followingvalues are defined: NO ERROR (0), GENERAL ERROR (1), OBJECT NOT FOUND (2), COUNTER NOTFOUND (3), NAMESPACE ERROR (4), OBJECT CURRENTLY UNAVAILABLE (5), COM LIBRARY INITFAILURE (6), SECURITY INIT FAILURE (7), PROXY SECURITY FAILURE (9), NO INSTANCES RETURNED(10), ASSOCIATOR QUERY FAILED (11), REFERENCE QUERY FAILED (12), NO RESPONSE RECEIVED(13), CANNOT FIND JOINED QUERY (14), CANNOT FIND JOIN ATTRIBUTE IN QUERY 1 RESULTS (15),CANNOT FIND JOIN ATTRIBUTE IN QUERY 2 RESULTS (16), QUERY 1 NOT A SINGLETON (17), QUERY2 NOT A SINGLETON (18), NO INSTANCES RETURNED IN QUERY 1 (19), NO INSTANCES RETURNEDIN QUERY 2 (20), CANNOT FIND ROLLUP QUERY (21), CANNOT FIND ROLLUP ATTRIBUTE (22),FILE OFFLINE (23), NO HOSTNAME (24), MISSING LIBRARY (25), ATTRIBUTE COUNT MISMATCH(26), ATTRIBUTE NAME MISMATCH (27), COMMON DATA PROVIDER NOT STARTED (28), CALLBACKREGISTRATION ERROR (29), MDL LOAD ERROR (30), AUTHENTICATION FAILED (31), CANNOTRESOLVE HOST NAME (32), SUBNODE UNAVAILABLE (33), SUBNODE NOT FOUND IN CONFIG (34),ATTRIBUTE ERROR (35), CLASSPATH ERROR (36), CONNECTION FAILURE (37), FILTER SYNTAXERROR (38), FILE NAME MISSING (39), SQL QUERY ERROR (40), SQL FILTER QUERY ERROR (41),SQL DB QUERY ERROR (42), SQL DB FILTER QUERY ERROR (43), PORT OPEN FAILED (44), ACCESSDENIED (45), TIMEOUT (46), NOT IMPLEMENTED (47), REQUESTED A BAD VALUE (48), RESPONSETOO BIG (49), GENERAL RESPONSE ERROR (50), SCRIPT NONZERO RETURN (51), SCRIPT NOTFOUND (52), SCRIPT LAUNCH ERROR (53), CONF FILE DOES NOT EXIST (54), CONF FILE ACCESSDENIED (55), INVALID CONF FILE (56), EIF INITIALIZATION FAILED (57), CANNOT OPEN FORMATFILE (58), FORMAT FILE SYNTAX ERROR (59), REMOTE HOST UNAVAILABLE (60), EVENT LOG DOESNOT EXIST (61), PING FILE DOES NOT EXIST (62), NO PING DEVICE FILES (63), PING DEVICE LISTFILE MISSING (64), SNMP MISSING PASSWORD (65), DISABLED (66), URLS FILE NOT FOUND (67),XML PARSE ERROR (68), NOT INITIALIZED (69), ICMP SOCKETS FAILED (70), DUPLICATE CONF FILE(71), DELETED CONFIGURATION (72). Any value that does not have a definition here is displayed inthe User Interface.



The following names are defined for this attribute: ERROR_CODE or ERRCODE (historical name), ErrorCode (caption), Error_Code (attribute name), and ERRCODE (column name).

Intervals SkippedThe number of times a background data collection for this group was skipped because the previouscollection was still running when the next one was due to start. The type is integer (32-bit counter).



The following names are defined for this attribute: INTERVALS_SKIPPED or INTSKIP (historical name),Intervals Skipped (caption), Intervals_Skipped (attribute name), and INTSKIP (column name).

Attributes 149

Last Collection DurationThe duration of the most recently completed data collection of this group in seconds. The type is realnumber (32-bit counter) with two decimal places of precision.



The following names are defined for this attribute: LAST_COLLECTION_DURATION or COLDURA(historical name), Last Collection Duration (caption), Last_Collection_Duration (attribute name), andCOLDURA (column name).

Last Collection FinishedThe most recent time a data collection of this group finished. The type is timestamp with enumeratedvalues. The following values are defined: NOT COLLECTED (0691231190000000), NOT COLLECTED(0000000000000001). Any value that does not have a definition here is displayed in the UserInterface.



The following names are defined for this attribute: LAST_COLLECTION_FINISHED or COLFINI(historical name), Last Collection Finished (caption), Last_Collection_Finished (attribute name), andCOLFINI (column name).

Last Collection StartThe most recent time a data collection of this group started. The type is timestamp with enumeratedvalues. The following values are defined: NOT COLLECTED (0691231190000000), NOT COLLECTED(0000000000000001). Any value that does not have a definition here is displayed in the UserInterface.



The following names are defined for this attribute: LAST_COLLECTION_START or COLSTRT (historicalname), Last Collection Start (caption), Last_Collection_Start (attribute name), and COLSTRT (columnname).





Number of CollectionsThe number of data collections for this group since the agent started. The type is integer (32-bitcounter).



The following names are defined for this attribute: NUMBER_OF_COLLECTIONS or NUMCOLL(historical name), Number of Collections (caption), Number_of_Collections (attribute name), andNUMCOLL (column name).

Object NameThe name of the performance object. The type is string.




The following names are defined for this attribute: OBJECT_NAME or OBJNAME (historical name),Object Name (caption), Object_Name (attribute name), and OBJNAME (column name).

Object StatusThe status of the performance object. The type is integer with enumerated values. The followingvalues are defined: ACTIVE (0), INACTIVE (1). Any value that does not have a definition here isdisplayed in the User Interface.



The following names are defined for this attribute: OBJECT_STATUS or OBJSTTS (historical name),Object Status (caption), Object_Status (attribute name), and OBJSTTS (column name).

Object TypeThe type of the performance object. The type is integer with enumerated values. The following valuesare defined: WMI (0), PERFMON (1), WMI ASSOCIATION GROUP (2), JMX (3), SNMP (4), SHELLCOMMAND (5), JOINED GROUPS (6), CIMOM (7), CUSTOM (8), ROLLUP DATA (9), WMI REMOTEDATA (10), LOG FILE (11), JDBC (12), CONFIG DISCOVERY (13), NT EVENT LOG (14), FILTER (15),SNMP EVENT (16), PING (17), DIRECTOR DATA (18), DIRECTOR EVENT (19), SSH REMOTE SHELLCOMMAND (20). Any value that does not have a definition here is displayed in the User Interface.



The following names are defined for this attribute: OBJECT_TYPE or OBJTYPE (historical name),Object Type (caption), Object_Type (attribute name), and OBJTYPE (column name).

Query NameThe name of the attribute group. This attribute is a key attribute. The type is string.



The following names are defined for this attribute: QUERY_NAME or ATTRGRP (historical name),Query Name (caption), Query_Name (attribute name), and ATTRGRP (column name).

Refresh IntervalThe interval at which this group is refreshed in seconds. The type is integer (32-bit counter).



The following names are defined for this attribute: REFRESH_INTERVAL or REFRINT (historical name),Refresh Interval (caption), Refresh_Interval (attribute name), and REFRINT (column name).





Pig data setThis data set monitors the metrics for Pig tool in the Hadoop cluster for Ambari based Hadoopinstallations. Thresholds for this data set are associated with the Hadoop component. This data set isdisplayed as KH8 PIG in the threshold editor. A data sample is sent to the server every minute and ismaintained for 8 days by default. The attributes shown in italic are visible in the UI. All attributes areavailable for thresholds.

Attributes 151























































Attributes 153


































Queue Metrics data setThis data set monitors the Queue metrics for the Hadoop cluster. This data set is configured for historicalcollection. Note: If you define a threshold for this data set, any events are not displayed in the Eventstab of the Application Performance Dashboard. Instead, they are sent to Netcool/OMNIbus if eventforwarding is configured. This data set is displayed as KH8 QUEUEMETRICS in the threshold editor. A datasample is sent to the server every minute and is maintained for 8 days by default. The attributes shown initalic are visible in the UI. All attributes are available for thresholds.

This data set contains the following attributes:Allocated Space MB

The amount of allocated memory (in MB) for a queue. The type is integer (64-bit gauge).



The following names are defined for this attribute: ALLOCATEDSPACEMB or ALLOCATEDM (historicalname), Allocated Space MB (caption), AllocatedSpaceMB (attribute name), and ALLOCATEDM (columnname).

Applications CompletedThe number of completed applications. The type is integer (64-bit gauge).



The following names are defined for this attribute: APPLICATIONSCOMPLETED or APPSCOMPLE(historical name), Applications Completed (caption), ApplicationsCompleted (attribute name), andAPPSCOMPLE (column name).

Applications FailedThe number of applications in failed state. The type is integer (64-bit gauge).



The following names are defined for this attribute: APPLICATIONSFAILED or APPSFAILED (historicalname), Applications Failed (caption), ApplicationsFailed (attribute name), and APPSFAILED (columnname).

Applications KilledThe number of applications that are killed in the cluster. The type is integer (64-bit gauge).



Attributes 155

The following names are defined for this attribute: APPLICATIONSKILLED or APPSKILLED (historicalname), Applications Killed (caption), ApplicationsKilled (attribute name), and APPSKILLED (columnname).

Applications PendingThe number of applications that are in the pending state. The type is integer (64-bit gauge).



The following names are defined for this attribute: APPLICATIONSPENDING or APPSPENDIN(historical name), Applications Pending (caption), ApplicationsPending (attribute name), andAPPSPENDIN (column name).

Applications RunningThe number of applications that are in the running state. The type is integer (64-bit gauge).



The following names are defined for this attribute: APPLICATIONSRUNNING or APPSRUNNIN(historical name), Applications Running (caption), ApplicationsRunning (attribute name), andAPPSRUNNIN (column name).

Applications SubmittedThe number of submitted applications in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: APPLICATIONSSUBMITTED or APPSSUBMIT(historical name), Applications Submitted (caption), ApplicationsSubmitted (attribute name), andAPPSSUBMIT (column name).

Available Space MBThe amount of available memory (in MB) for a queue. The type is integer (64-bit gauge).



The following names are defined for this attribute: AVAILABLESPACEMB or AVAILABLEM (historicalname), Available Space MB (caption), AvailableSpaceMB (attribute name), and AVAILABLEM (columnname).









Pending Space MBThe amount of pending memory (in MB) in a queue. The type is integer (64-bit gauge).




The following names are defined for this attribute: PENDINGSPACEMB or PENDINGMB (historicalname), Pending Space MB (caption), PendingSpaceMB (attribute name), and PENDINGMB (columnname).

Queue NameFull Queue path name. This attribute is a key attribute. The type is string.



The following names are defined for this attribute: QUEUENAME or QUEUE (historical name), QueueName (caption), QueueName (attribute name), and QUEUE (column name).

Reserved Space MBThe amount of reserved memory (in MB) in a queue. The type is integer (64-bit gauge).



The following names are defined for this attribute: RESERVEDSPACEMB or RESERVEDMB (historicalname), Reserved Space MB (caption), ReservedSpaceMB (attribute name), and RESERVEDMB (columnname).

Running 0The number of running applications' for which the elapsed time is less than or equal to 60 min. Thetype is integer (64-bit gauge).



The following names are defined for this attribute: RUNNING_0 (historical name), Running 0 (caption),running_0 (attribute name), and RUNNING_0 (column name).

Running 1440The number of running applications' for which the elapsed time is more than 1440 mins. The type isinteger (64-bit gauge).



The following names are defined for this attribute: RUNNING_1440 or RUNNING_14 (historicalname), Running 1440 (caption), running_1440 (attribute name), and RUNNING_14 (column name).

Running 300The number of running applications' for which the elapsed time is greater than 300 and less than orequal to 1440 mins. The type is integer (64-bit gauge).



The following names are defined for this attribute: RUNNING_300 or RUNNING_30 (historical name),Running 300 (caption), running_300 (attribute name), and RUNNING_30 (column name).

Running 60The number of running applications' for which the elapsed time is greater than 60 and less than orequal to 300 mins. The type is integer (64-bit gauge).



Attributes 157

The following names are defined for this attribute: RUNNING_60 (historical name), Running 60(caption), running_60 (attribute name), and RUNNING_60 (column name).

Short Queue NameShort Queue name. The type is string.



The following names are defined for this attribute: SHORTQUEUENAME or SHORTQUEUE (historicalname), Short Queue Name (caption), ShortQueueName (attribute name), and SHORTQUEUE (columnname).





UserName of the user. The type is string.



The following names are defined for this attribute: USER (historical name), User (caption), User(attribute name), and USER (column name).

Active ApplicationsThe number of applications in active state in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: ACTIVEAPPLICATIONS or ACTIVEAPPL (historicalname), Active Applications (caption), ActiveApplications (attribute name), and ACTIVEAPPL (columnname).

Active UsersThe number of active users in the cluster. The type is integer (32-bit gauge).



The following names are defined for this attribute: ACTIVEUSERS or ACTIVEUSER (historical name),Active Users (caption), ActiveUsers (attribute name), and ACTIVEUSER (column name).

Aggregate Containers AllocatedThe total number of allocated containers. The type is integer (64-bit gauge).



The following names are defined for this attribute: AGGREGATECONTAINERSALLOCATEDor AGGREGATEC (historical name), Aggregate Containers Allocated (caption),AggregateContainersAllocated (attribute name), and AGGREGATEC (column name).

Aggregate Containers ReleasedThe total number of containers released. The type is integer (64-bit gauge).




The following names are defined for this attribute: AGGREGATECONTAINERSRELEASEDor AGGREGATE0 (historical name), Aggregate Containers Released (caption),AggregateContainersReleased (attribute name), and AGGREGATE0 (column name).

Allocated ContainersThe number of currently allocated containers. The type is integer (64-bit gauge).



The following names are defined for this attribute: ALLOCATEDCONTAINERS or ALLOCATEDC(historical name), Allocated Containers (caption), AllocatedContainers (attribute name), andALLOCATEDC (column name).

Allocated Memory PercentThe percentage of allocated memory. The type is integer (32-bit gauge).

The source for this attribute is derived: (AllocatedSpaceMB/(AvailableSpaceMB+PendingSpaceMB+ReservedSpaceMB+AllocatedSpaceMB))*100


The following names are defined for this attribute: ALLOCATEDMEMORYPERCENT or ALLOCATED0(historical name), Allocated Memory Percent (caption), AllocatedMemoryPercent (attribute name),and ALLOCATED0 (column name).

Allocated Virtual CoresThe number of virtual cores allocated in the cluster. The type is integer (32-bit gauge).



The following names are defined for this attribute: ALLOCATEDVCORES or ALLOCATEDV (historicalname), Allocated Virtual Cores (caption), AllocatedVCores (attribute name), and ALLOCATEDV (columnname).

Available Virtual CoresThe number of virtual cores available in the cluster. The type is integer (32-bit gauge).



The following names are defined for this attribute: AVAILABLEVCORES or AVAILABLEV (historicalname), Available Virtual Cores (caption), AvailableVCores (attribute name), and AVAILABLEV (columnname).








Attributes 159


Failed Applications PercentThe percentage of applications that are in the failed state. The type is integer (32-bit gauge).

The source for this attribute is derived: (ApplicationsFailed/(ApplicationsCompleted+ApplicationsFailed+ApplicationsKilled))*100


The following names are defined for this attribute: FAILEDAPPLICATIONSPERCENT or FAILEDAPPL(historical name), Failed Applications Percent (caption), FailedApplicationsPercent (attribute name),and FAILEDAPPL (column name).

Fair Share MBThe current fair share of memory in MB. The type is integer (64-bit gauge) with enumerated values.The following values are defined: NA (-1). Any value that does not have a definition here is displayedin the User Interface.



The following names are defined for this attribute: FAIRSHAREMB or FAIRSHAREM (historical name),Fair Share MB (caption), FairShareMB (attribute name), and FAIRSHAREM (column name).

Fair Share Virtual CoresThe current fair share of CPU in virtual cores. The type is integer (64-bit gauge) with enumeratedvalues. The following values are defined: NA (-1). Any value that does not have a definition here isdisplayed in the User Interface.



The following names are defined for this attribute: FAIRSHAREVCORES or FAIRSHAREV (historicalname), Fair Share Virtual Cores (caption), FairShareVCores (attribute name), and FAIRSHAREV(column name).

Killed Applications PercentThe percentage of applications that are killed in the cluster. The type is integer (32-bit gauge).

The source for this attribute is derived: (ApplicationsKilled/(ApplicationsCompleted+ApplicationsFailed+ApplicationsKilled))*100


The following names are defined for this attribute: KILLEDAPPLICATIONSPERCENT or KILLEDAPPS(historical name), Killed Applications Percent (caption), KilledApplicationsPercent (attribute name),and KILLEDAPPS (column name).

Maximum Share MBThe maximum share of memory in MB. The type is integer (64-bit gauge) with enumerated values. Thefollowing values are defined: NA (-1). Any value that does not have a definition here is displayed in theUser Interface.



The following names are defined for this attribute: MAXIMUMSHAREMB or MAXIMUMSHA (historicalname), Maximum Share MB (caption), MaximumShareMB (attribute name), and MAXIMUMSHA(column name).


Maximum Share Virtual CoresThe maximum share of CPU in virtual cores. The type is integer (64-bit gauge) with enumeratedvalues. The following values are defined: NA (-1). Any value that does not have a definition here isdisplayed in the User Interface.



The following names are defined for this attribute: MAXIMUMSHAREVCORES or MAXIMUMSH0(historical name), Maximum Share Virtual Cores (caption), MaximumShareVCores (attribute name),and MAXIMUMSH0 (column name).

Minimum Share MBThe minimum share of memory in MB. The type is integer (64-bit gauge) with enumerated values. Thefollowing values are defined: NA (-1). Any value that does not have a definition here is displayed in theUser Interface.



The following names are defined for this attribute: MINIMUMSHAREMB or MINIMUMSHA (historicalname), Minimum Share MB (caption), MinimumShareMB (attribute name), and MINIMUMSHA (columnname).

Minimum Share Virtual CoresThe minimum share of CPU in virtual cores. The type is integer (64-bit gauge) with enumerated values.The following values are defined: NA (-1). Any value that does not have a definition here is displayedin the User Interface.



The following names are defined for this attribute: MINIMUMSHAREVCORES or MINIMUMSH0(historical name), Minimum Share Virtual Cores (caption), MinimumShareVCores (attribute name), andMINIMUMSH0 (column name).

Pending ContainersThe number of pending containers. The type is integer (64-bit gauge).



The following names are defined for this attribute: PENDINGCONTAINERS or PENDINGCON (historicalname), Pending Containers (caption), PendingContainers (attribute name), and PENDINGCON (columnname).

Pending Virtual CoresThe number of virtual cores in the pending state. The type is integer (64-bit gauge).



The following names are defined for this attribute: PENDINGVCORES or PENDINGVCO (historicalname), Pending Virtual Cores (caption), PendingVCores (attribute name), and PENDINGVCO (columnname).

Reserved ContainersThe number of reserved containers in the cluster. The type is integer (64-bit gauge).



Attributes 161

The following names are defined for this attribute: RESERVEDCONTAINERS or RESERVEDCO(historical name), Reserved Containers (caption), ReservedContainers (attribute name), andRESERVEDCO (column name).

Reserved Virtual CoresThe number of virtual cores reserved in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: RESERVEDVCORES or RESERVEDVC (historicalname), Reserved Virtual Cores (caption), ReservedVCores (attribute name), and RESERVEDVC (columnname).

Ranger data setThis data set monitors the metrics for server and client components of Ranger Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 RANGER in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.














































Attributes 163


Init Count in ClusterThis attribute indicates the count of service components in the init state. The type is integer (32-bitgauge).









































Roles data setThis data set gives the details of roles managed in the cluster. Note: If you define a threshold for thisdata set, any events are not displayed in the Events tab of the Application Performance Dashboard.Instead, they are sent to Netcool/OMNIbus if event forwarding is configured. This data set is displayedas KH8 ROLES in the threshold editor. A data sample is sent to the server every minute and is maintainedfor 8 days by default. The attributes shown in italic are visible in the UI. All attributes are available forthresholds.

This data set contains the following attributes:Daemon

The daemons managed by the node. The type is string.



Attributes 165

The following names are defined for this attribute: DAEMON (historical name), Daemon (caption),Daemon (attribute name), and DAEMON (column name).













RPC data setThis data set monitors the RPC metrics of the Hadoop cluster. Note: If you define a threshold for this dataset, any events are not displayed in the Events tab of the Application Performance Dashboard. Instead,they are sent to Netcool/OMNIbus if event forwarding is configured. This data set is displayed as KH8 RPCin the threshold editor. A data sample is sent to the server every 5 minutes and is maintained for 8 days bydefault. The attributes shown in italic are visible in the UI. All attributes are available for thresholds.

This data set contains the following attributes:Authentication Failures

The number of failed RPC authentication calls. The type is integer (64-bit gauge).



The following names are defined for this attribute: RPCAUTHENTICATIONFAILURES or RPCAUTHEN0(historical name), Authentication Failures (caption), RpcAuthenticationFailures (attribute name), andRPCAUTHEN0 (column name).

Authentication SuccessesThe number of successful RPC authentication calls. The type is integer (64-bit gauge).



The following names are defined for this attribute: RPCAUTHENTICATIONSUCCESSES orRPCAUTHENT (historical name), Authentication Successes (caption), RpcAuthenticationSuccesses(attribute name), and RPCAUTHENT (column name).

Authorization FailuresThe number of failed RPC authorization calls. The type is integer (64-bit gauge).




The following names are defined for this attribute: RPCAUTHORIZATIONFAILURES or RPCAUTHOR0(historical name), Authorization Failures (caption), RpcAuthorizationFailures (attribute name), andRPCAUTHOR0 (column name).

Authorization SuccessesThe number of successful RPC authorization calls. The type is integer (64-bit gauge).



The following names are defined for this attribute: RPCAUTHORIZATIONSUCCESSES or RPCAUTHORI(historical name), Authorization Successes (caption), RpcAuthorizationSuccesses (attribute name),and RPCAUTHORI (column name).

HostnameThe hostname of Hadoop node. This attribute is a key attribute. The type is string.








Open ConnectionsThe number of open connections on a port in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: OPENCONNECTIONS or NUMOPENCON (historicalname), Open Connections (caption), OpenConnections (attribute name), and NUMOPENCON (columnname).

PortThe port number that is used to connect to the Hadoop cluster. This attribute is a key attribute. Thetype is integer (32-bit gauge).



The following names are defined for this attribute: PORT (historical name), Port (caption), Port(attribute name), and PORT (column name).

Processed Requests CountTotal number of processed RPC requests. The type is integer (64-bit gauge).



The following names are defined for this attribute: RPCPROCESSINGTIME_MS or RPCPROCES0(historical name), Processed Requests Count (caption), RpcProcessingTime_ms (attribute name), andRPCPROCES0 (column name).

Attributes 167

Processing Average Time in minutesThe average time (in minutes) that is required for processing RPC requests The type is integer (64-bitgauge).

The source for this attribute is derived: RpcProcessingAverageTime_ms/60000


The following names are defined for this attribute: RPCPROCESSINGAVERAGETIME_Mor RPCPROCES1 (historical name), Processing Average Time in minutes (caption),RpcProcessingAverageTime_M (attribute name), and RPCPROCES1 (column name).

Processing Average Time msThe average time that is required for processing RPC requests. The type is real number (64-bit gauge)with two decimal places of precision.



The following names are defined for this attribute: RPCPROCESSINGAVERAGETIME_MSor RPCPROCESS (historical name), Processing Average Time ms (caption),RpcProcessingAverageTime_ms (attribute name), and RPCPROCESS (column name).

Queue Average Time in minutesThe average time (in minutes) that is spent by an RPC request in the queue. The type is integer (64-bitgauge).

The source for this attribute is derived: RpcQueueAverageTime_ms/60000


The following names are defined for this attribute: RPCQUEUEAVERAGETIME_M or RPCQUEUET1(historical name), Queue Average Time in minutes (caption), RpcQueueAverageTime_M (attributename), and RPCQUEUET1 (column name).

Queue Average Time msThe average time that is spent by an RPC request in the queue. The type is real number (64-bit gauge)with two decimal places of precision.



The following names are defined for this attribute: RPCQUEUEAVERAGETIME_MS or RPCQUEUETI(historical name), Queue Average Time ms (caption), RpcQueueAverageTime_ms (attribute name), andRPCQUEUETI (column name).

Queued Requests CountTotal number of queued RPC requests. The type is integer (64-bit gauge).



The following names are defined for this attribute: RPCQUEUETIME_MS or RPCQUEUET0 (historicalname), Queued Requests Count (caption), RpcQueueTime_ms (attribute name), and RPCQUEUET0(column name).

Received BytesThe number of RPC bytes received by the node. The type is integer (64-bit gauge).



The following names are defined for this attribute: RECEIVEDBYTES or RECEIVEDBY (historical name),Received Bytes (caption), ReceivedBytes (attribute name), and RECEIVEDBY (column name).


Received Data MBThe number of RPC bytes (in MB) received by the node. The type is integer (64-bit gauge).

The source for this attribute is derived: ReceivedBytes/1048576


The following names are defined for this attribute: RECEIVEDBYTESMB or RECEIVEDB0 (historicalname), Received Data MB (caption), ReceivedBytesMB (attribute name), and RECEIVEDB0 (columnname).

Sent BytesThe number of RPC bytes sent by the node. The type is integer (64-bit gauge).



The following names are defined for this attribute: SENTBYTES (historical name), Sent Bytes (caption),SentBytes (attribute name), and SENTBYTES (column name).

Sent Data MBThe number of RPC bytes (in MB) sent by the node. The type is integer (64-bit gauge).

The source for this attribute is derived: SentBytes/1048576


The following names are defined for this attribute: SENTBYTESMB or SENTBYTESM (historical name),Sent Data MB (caption), SentBytesMB (attribute name), and SENTBYTESM (column name).





Call Queue LengthThe current length of the call queue in the cluster. The type is integer (64-bit gauge).



The following names are defined for this attribute: CALLQUEUELENGTH or CALLQUEUEL (historicalname), Call Queue Length (caption), CallQueueLength (attribute name), and CALLQUEUEL (columnname).








Attributes 169


IP AddressThe IP Address of the specific node of the Hadoop cluster. The type is string.

The source for this attribute is derived: nameToIpAddress(Hostname)


The following names are defined for this attribute: IP_ADDRESS (historical name), IP Address(caption), IP_Address (attribute name), and IP_ADDRESS (column name).

Schema Registry data setThis data set monitors the metrics for server and client components of Schema Registry Service in theHadoop cluster for Ambari based Hadoop installations. Thresholds for this data set are associated withthe Hadoop component. This data set is displayed as KH8 SCHEMAREGISTRY in the threshold editor. Adata sample is sent to the server every minute and is maintained for 8 days by default. The attributesshown in italic are visible in the UI. All attributes are available for thresholds.















































Attributes 171










































Services Overview data setThis data set provides the overall summary of the services present in Hadoop cluster for Ambari basedHadoop installations. Thresholds for this data set are associated with the Hadoop component. This dataset is displayed as KH8 SERVICESOVERVIEW in the threshold editor. A data sample is sent to the serverevery minute and is maintained for 8 days by default. The attributes shown in italic are visible in the UI. Allattributes are available for thresholds.






Service NameName of the Ambari services/components available in Hadoop Cluster monitored by Hadoop agent.This attribute is a key attribute. The type is string.

Attributes 173



The following names are defined for this attribute: SERVICENAME or SERVICENAM (historical name),Service Name (caption), ServiceName (attribute name), and SERVICENAM (column name).

Service StatusThe status of the service, if the service component is of server type then status 'installed' meansservice is stopped. The type is string.



The following names are defined for this attribute: SERVICESTATUS or SERVICESTA (historical name),Service Status (caption), ServiceStatus (attribute name), and SERVICESTA (column name).





Slider data setThis data set monitors the metrics for Slider tool in the Hadoop cluster for Ambari based Hadoopinstallations. Thresholds for this data set are associated with the Hadoop component. This data set isdisplayed as KH8 SLIDER in the threshold editor. A data sample is sent to the server every minute andis maintained for 8 days by default. The attributes shown in italic are visible in the UI. All attributes areavailable for thresholds.









































Attributes 175
















































SmartSense data setThis data set monitors the metrics for server and client components of SmartSense Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 SMARTSENSE in the threshold editor. A datasample is sent to the server every minute and is maintained for 8 days by default. The attributes shown initalic are visible in the UI. All attributes are available for thresholds.

This data set contains the following attributes:

Attributes 177

Component NameName of the component that is associated with the service. This attribute is a key attribute. The typeis string.




















StateThis attribute indicates the current state of the service component. For example, if the servicecomponent is of server type, then status 'installed' means service component is stopped. The type isstring.

































Attributes 179





Other Count in ClusterIn case of some Ambari versions, the attributes like 'init_count_in_cluster','install_failed_count_in_cluster', 'unknown_count_in_cluster' are not available, then the'other_count_in_cluster' attribute indicates the count of service components neither started norinstalled, which might be in init, install_failed or unknown state. The type is integer (32-bit gauge).








Stale ConfigsThis attribute indicates if the host components need to restart. The type is string.





















Solr data setThis data set monitors the metrics for server and client components of Solr Service in the Hadoop clusterfor Ambari based Hadoop installations. Thresholds for this data set are associated with the Hadoopcomponent. This data set is displayed as KH8 SOLR in the threshold editor. A data sample is sent to theserver every minute and is maintained for 8 days by default. The attributes shown in italic are visible inthe UI. All attributes are available for thresholds.














Attributes 181






















































Attributes 183





















Spark data setThis data set monitors the metrics for server and client components of Spark Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 SPARK in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.































Attributes 185





















































Attributes 187






Sqoop data setThis data set monitors the metrics for Sqoop tool in the Hadoop cluster for Ambari based Hadoopinstallations. Thresholds for this data set are associated with the Hadoop component. This data set isdisplayed as KH8 SQOOP in the threshold editor. A data sample is sent to the server every minute andis maintained for 8 days by default. The attributes shown in italic are visible in the UI. All attributes areavailable for thresholds.















































Attributes 189










































Startup Progress data setThis data set monitors the startup performance of the Hadoop cluster.

This data set contains the following attributes:Collect Timestamp

The time at which the data was collected. The type is timestamp.




Elapsed Time msThe total time elapsed in millisecond. The type is integer (64-bit gauge).



Attributes 191

The following names are defined for this attribute: ELAPSEDTIME_MS or ELAPSEDTIM (historicalname), Elapsed Time ms (caption), ElapsedTime_ms (attribute name), and ELAPSEDTIM (columnname).





Loading Edits CountThe total number of load edit operations. The type is integer (64-bit gauge).



The following names are defined for this attribute: LOADINGEDITSCOUNT or LOADINGEDI (historicalname), Loading Edits Count (caption), LoadingEditsCount (attribute name), and LOADINGEDI (columnname).

Loading Edits Elapsed Time msThe duration that is required to perform the load edit operations. The type is integer (64-bit gauge).



The following names are defined for this attribute: LOADINGEDITSELAPSEDTIME_MS or LOADINGED0(historical name), Loading Edits Elapsed Time ms (caption), LoadingEditsElapsedTime_ms (attributename), and LOADINGED0 (column name).

Loading Edits Percent CompleteThe percentage of load edit operations that are completed. The type is real number (64-bit gauge)with one decimal places of precision.



The following names are defined for this attribute: LOADINGEDITSPERCENTCOMPLETEor LOADINGED2 (historical name), Loading Edits Percent Complete (caption),LoadingEditsPercentComplete (attribute name), and LOADINGED2 (column name).

Loading Edits TotalThe total number of load edit operations. The type is integer (64-bit gauge).



The following names are defined for this attribute: LOADINGEDITSTOTAL or LOADINGED1 (historicalname), Loading Edits Total (caption), LoadingEditsTotal (attribute name), and LOADINGED1 (columnname).

Loading File System Image CountThe number of load FS (File System) Image operations. The type is integer (64-bit gauge).



The following names are defined for this attribute: LOADINGFILESYSTEMIMAGECOUNTor LOADINGFSI (historical name), Loading File System Image Count (caption),LoadingFileSystemImageCount (attribute name), and LOADINGFSI (column name).


Loading File System Image Elapsed Time msThe duration that is required for the load FS (File System) Image operations. The type is integer (64-bit gauge).



The following names are defined for this attribute: LOADINGFILESYSTEMIMAGEELAPSEDTIME_MSor LOADINGFS0 (historical name), Loading File System Image Elapsed Time ms (caption),LoadingFileSystemImageElapsedTime_ms (attribute name), and LOADINGFS0 (column name).

Loading File System Image Percent CompleteThe percentage of load FS (File System) Image operations that are completed. The type is realnumber (64-bit gauge) with one decimal places of precision.



The following names are defined for this attribute: LOADINGFILESYSTEMIMAGEPERCENTCOMPLETEor LOADINGFS2 (historical name), Loading File System Image Percent Complete (caption),LoadingFileSystemImagePercentComplete (attribute name), and LOADINGFS2 (column name).

Loading File System Image TotalThe total number of load FS (File System) Image operations. The type is integer (64-bit gauge).



The following names are defined for this attribute: LOADINGFILESYSTEMIMAGETOTALor LOADINGFS1 (historical name), Loading File System Image Total (caption),LoadingFileSystemImageTotal (attribute name), and LOADINGFS1 (column name).





Percent CompleteThe current completion rate of the NameNode startup progress. The maximum value is not 1.0. Thetype is real number (64-bit gauge) with one decimal places of precision.



The following names are defined for this attribute: PERCENTCOMPLETE or PERCENTCOM (historicalname), Percent Complete (caption), PercentComplete (attribute name), and PERCENTCOM (columnname).

SafeMode CountThe number of safemodes for a NameNode. The type is integer (64-bit gauge).



The following names are defined for this attribute: SAFEMODECOUNT or SAFEMODECO (historicalname), SafeMode Count (caption), SafeModeCount (attribute name), and SAFEMODECO (columnname).

Attributes 193

SafeMode Elapsed Time msThe duration that is required for a NameNode to enter into the safemode. The type is integer (64-bitgauge).



The following names are defined for this attribute: SAFEMODEELAPSEDTIME_MS or SAFEMODEEL(historical name), SafeMode Elapsed Time ms (caption), SafeModeElapsedTime_ms (attribute name),and SAFEMODEEL (column name).

SafeMode Percent CompleteThe percentage of the NameNodes that have completed entering in the SafeMode. The type is realnumber (64-bit gauge) with one decimal places of precision.



The following names are defined for this attribute: SAFEMODEPERCENTCOMPLETE or SAFEMODEPE(historical name), SafeMode Percent Complete (caption), SafeModePercentComplete (attributename), and SAFEMODEPE (column name).

SafeMode TotalThe total number of the SafeMode. The type is integer (64-bit gauge).



The following names are defined for this attribute: SAFEMODETOTAL or SAFEMODETO (historicalname), SafeMode Total (caption), SafeModeTotal (attribute name), and SAFEMODETO (column name).

Saving Checkpoint CountThe number of save checkpoint operations. The type is integer (64-bit gauge).



The following names are defined for this attribute: SAVINGCHECKPOINTCOUNT or SAVINGCHEC(historical name), Saving Checkpoint Count (caption), SavingCheckpointCount (attribute name), andSAVINGCHEC (column name).

Saving Checkpoint Elapsed Time msThe duration that is required for the save checkpoint operation. The type is integer (64-bit gauge).



The following names are defined for this attribute: SAVINGCHECKPOINTELAPSEDTIME_MSor SAVINGCHE0 (historical name), Saving Checkpoint Elapsed Time ms (caption),SavingCheckpointElapsedTime_ms (attribute name), and SAVINGCHE0 (column name).

Saving Checkpoint Percent CompleteThe percentage of completed save checkpoint operations. The type is real number (64-bit gauge) withone decimal places of precision.



The following names are defined for this attribute: SAVINGCHECKPOINTPERCENTCOMPLETEor SAVINGCHE2 (historical name), Saving Checkpoint Percent Complete (caption),SavingCheckpointPercentComplete (attribute name), and SAVINGCHE2 (column name).

Saving Checkpoint TotalThe total number of save checkpoint operations. The type is integer (64-bit gauge).




The following names are defined for this attribute: SAVINGCHECKPOINTTOTAL or SAVINGCHE1(historical name), Saving Checkpoint Total (caption), SavingCheckpointTotal (attribute name), andSAVINGCHE1 (column name).





Streaming Analytics Manager data setThis data set monitors the metrics for server and client components of Streaming AnalyticsManager Service in the Hadoop cluster for Ambari based Hadoop installations. Thresholds forthis data set are associated with the Hadoop component. This data set is displayed as KH8STREAMINGANALYTICSMANAGER in the threshold editor. A data sample is sent to the server everyminute and is maintained for 8 days by default. The attributes shown in italic are visible in the UI. Allattributes are available for thresholds.
















Attributes 195























































Attributes 197


















Superset data setThis data set monitors the metrics for server and client components of Superset Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 SUPERSET in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.

































Attributes 199





















































Attributes 201




Take Action Status data setThe Take Action Status data set contains information about the results of actions this agent ran.

This data set contains the following attributes:Action App Return Code

The application return code of the action is the actual return code of the command run. The type isinteger (32-bit numeric property).



The following names are defined for this attribute: ACTION_APP_RETURN_CODE or TSKAPRC(historical name), Action App Return Code (caption), Action_App_Return_Code (attribute name), andTSKAPRC (column name).

Action CommandThe command that was run by the action. The type is string.



The following names are defined for this attribute: ACTION_COMMAND or TSKCMND (historical name),Action Command (caption), Action_Command (attribute name), and TSKCMND (column name).

Action IDThe id of the action. The type is integer (32-bit numeric property).



The following names are defined for this attribute: ACTION_ID or TSKID (historical name), Action ID(caption), Action_ID (attribute name), and TSKID (column name).

Action InstanceThe instance that is associated with the output produced by running the action. The type is string.



The following names are defined for this attribute: ACTION_INSTANCE or TSKINST (historical name),Action Instance (caption), Action_Instance (attribute name), and TSKINST (column name).

Action MessageThe message that is associated with the return code of the action. The type is string.



The following names are defined for this attribute: ACTION_MESSAGE or TSKMSGE (historical name),Action Message (caption), Action_Message (attribute name), and TSKMSGE (column name).

Action NameThe name of the action that was run. The type is string.




The following names are defined for this attribute: ACTION_NAME or TSKNAME (historical name),Action Name (caption), Action_Name (attribute name), and TSKNAME (column name).

Action NodeThe node where the action ran. The type is string.



The following names are defined for this attribute: ACTION_NODE or TSKORGN (historical name),Action Node (caption), Action_Node (attribute name), and TSKORGN (column name).

Action OwnerThe name of the situation or user that initiated the action. The type is string.



The following names are defined for this attribute: ACTION_OWNER or TSKOWNR (historical name),Action Owner (caption), Action_Owner (attribute name), and TSKOWNR (column name).

Action ResultsThe output that is produced by running the action. The type is string.



The following names are defined for this attribute: ACTION_RESULTS or TSKOUTP (historical name),Action Results (caption), Action_Results (attribute name), and TSKOUTP (column name).

Action StatusThe return code from the Action Status dialog, which is the return code category that is defined for theapplication return code. The type is integer (32-bit numeric property).



The following names are defined for this attribute: ACTION_STATUS or TSKSTAT (historical name),Action Status (caption), Action_Status (attribute name), and TSKSTAT (column name).

Action SubnodeThe subnode where the action ran. The type is string.



The following names are defined for this attribute: ACTION_SUBNODE or TSKSBND (historical name),Action Subnode (caption), Action_Subnode (attribute name), and TSKSBND (column name).

Action TypeThe type of the action. The type is integer (32-bit numeric property) with enumerated values. Thefollowing values are defined: UNKNOWN (0), AUTOMATION (1). Any value that does not have adefinition here is displayed in the User Interface.



The following names are defined for this attribute: ACTION_TYPE or TSKTYPE (historical name),Action Type (caption), Action_Type (attribute name), and TSKTYPE (column name).


Attributes 203




TimestampThe time the event was generated. The type is string.




Tez data setThis data set monitors the metrics for client components of Tez Service in the Hadoop cluster for Ambaribased Hadoop installations. Thresholds for this data set are associated with the Hadoop component. Thisdata set is displayed as KH8 TEZ in the threshold editor. A data sample is sent to the server every minuteand is maintained for 8 days by default. The attributes shown in italic are visible in the UI. All attributesare available for thresholds.














































Attributes 205











































Thread Pool Status data setThe Thread Pool Status data set contains information that reflects the status of the internal thread poolused to collect data asynchronously.






Thread Pool Active ThreadsThe number of threads in the thread pool currently active doing work. The type is integer (32-bitgauge) with enumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Anyvalue that does not have a definition here is displayed in the User Interface.

Attributes 207



The following names are defined for this attribute: THREAD_POOL_ACTIVE_THREADS or TPACTTH(historical name), Thread Pool Active Threads (caption), Thread_Pool_Active_Threads (attributename), and TPACTTH (column name).

Thread Pool Avg Active ThreadsThe average number of threads in the thread pool simultaneously active doing work. The type is realnumber (32-bit gauge) with two decimal places of precision with enumerated values. The followingvalues are defined: NO DATA (-1), NO DATA (-100). Any value that does not have a definition here isdisplayed in the User Interface.



The following names are defined for this attribute: THREAD_POOL_AVG_ACTIVE_THREADSor TPAVGAT (historical name), Thread Pool Avg Active Threads (caption),Thread_Pool_Avg_Active_Threads (attribute name), and TPAVGAT (column name).

Thread Pool Avg Job WaitThe average time a job spends waiting on the thread pool queue in seconds. The type is real number(32-bit gauge) with two decimal places of precision with enumerated values. The following values aredefined: NO DATA (-1), NO DATA (-100). Any value that does not have a definition here is displayed inthe User Interface.



The following names are defined for this attribute: THREAD_POOL_AVG_JOB_WAIT or TPAVJBW(historical name), Thread Pool Avg Job Wait (caption), Thread_Pool_Avg_Job_Wait (attribute name),and TPAVJBW (column name).

Thread Pool Avg Queue LengthThe average length of the thread pool queue during this run. The type is real number (32-bit gauge)with two decimal places of precision with enumerated values. The following values are defined: NODATA (-1), NO DATA (-100). Any value that does not have a definition here is displayed in the UserInterface.



The following names are defined for this attribute: THREAD_POOL_AVG_QUEUE_LENGTH or TPAVGQL(historical name), Thread Pool Avg Queue Length (caption), Thread_Pool_Avg_Queue_Length(attribute name), and TPAVGQL (column name).

Thread Pool Max Active ThreadsThe peak number of threads in the thread pool that were simultaneously active doing work. The typeis integer (32-bit counter) with enumerated values. The following values are defined: NO DATA (-1),NO DATA (-100). Any value that does not have a definition here is displayed in the User Interface.



The following names are defined for this attribute: THREAD_POOL_MAX_ACTIVE_THREADSor TPMAXAT (historical name), Thread Pool Max Active Threads (caption),Thread_Pool_Max_Active_Threads (attribute name), and TPMAXAT (column name).

Thread Pool Max Queue LengthThe peak length the thread pool queue reached. The type is integer (32-bit counter) with enumeratedvalues. The following values are defined: NO DATA (-1), NO DATA (-100). Any value that does not havea definition here is displayed in the User Interface.




The following names are defined for this attribute: THREAD_POOL_MAX_QUEUE_LENGTHor TPMAXQL (historical name), Thread Pool Max Queue Length (caption),Thread_Pool_Max_Queue_Length (attribute name), and TPMAXQL (column name).

Thread Pool Max SizeThe maximum number of threads that are allowed to exist in the thread pool. The type is integer (32-bit numeric property) with enumerated values. The following values are defined: NO DATA (-1), NODATA (-100). Any value that does not have a definition here is displayed in the User Interface.



The following names are defined for this attribute: THREAD_POOL_MAX_SIZE or TPMAXSZ (historicalname), Thread Pool Max Size (caption), Thread_Pool_Max_Size (attribute name), and TPMAXSZ(column name).

Thread Pool Min Active ThreadsThe smallest number of threads in the thread pool that were simultaneously active doing work. Thetype is integer (32-bit counter) with enumerated values. The following values are defined: NO DATA(-1), NO DATA (-100). Any value that does not have a definition here is displayed in the User Interface.



The following names are defined for this attribute: THREAD_POOL_MIN_ACTIVE_THREADSor TPMINAT (historical name), Thread Pool Min Active Threads (caption),Thread_Pool_Min_Active_Threads (attribute name), and TPMINAT (column name).

Thread Pool Min Queue LengthThe minimum length the thread pool queue reached. The type is integer (32-bit counter) withenumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Any value thatdoes not have a definition here is displayed in the User Interface.



The following names are defined for this attribute: THREAD_POOL_MIN_QUEUE_LENGTH or TPMINQL(historical name), Thread Pool Min Queue Length (caption), Thread_Pool_Min_Queue_Length(attribute name), and TPMINQL (column name).

Thread Pool Queue LengthThe number of jobs currently waiting in the thread pool queue. The type is integer (32-bit gauge) withenumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Any value thatdoes not have a definition here is displayed in the User Interface.



The following names are defined for this attribute: THREAD_POOL_QUEUE_LENGTH or TPQLGTH(historical name), Thread Pool Queue Length (caption), Thread_Pool_Queue_Length (attribute name),and TPQLGTH (column name).

Thread Pool SizeThe number of threads currently existing in the thread pool. The type is integer (32-bit gauge) withenumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Any value thatdoes not have a definition here is displayed in the User Interface.



Attributes 209

The following names are defined for this attribute: THREAD_POOL_SIZE or THPSIZE (historical name),Thread Pool Size (caption), Thread_Pool_Size (attribute name), and THPSIZE (column name).

Thread Pool Total JobsThe number of jobs that are completed by all threads in the pool since agent start. The type is integer(32-bit counter) with enumerated values. The following values are defined: NO DATA (-1), NO DATA(-100). Any value that does not have a definition here is displayed in the User Interface.



The following names are defined for this attribute: THREAD_POOL_TOTAL_JOBS or TPTJOBS(historical name), Thread Pool Total Jobs (caption), Thread_Pool_Total_Jobs (attribute name), andTPTJOBS (column name).





Titan data setThis data set monitors the metrics for Titan tool in the Hadoop cluster for Ambari based Hadoopinstallations. Thresholds for this data set are associated with the Hadoop component. This data set isdisplayed as KH8 TITAN in the threshold editor. A data sample is sent to the server every minute andis maintained for 8 days by default. The attributes shown in italic are visible in the UI. All attributes areavailable for thresholds.









































Attributes 211
















































UGI Metrics data setThis data set monitors the User and Group Information (UGI) metrics of the Hadoop cluster.

This data set contains the following attributes:Collect Timestamp

The time at which the data was collected. The type is timestamp.



Attributes 213






Group Average Time msThe average time (in milliseconds) that is required for completing a group operation. The type isinteger (64-bit gauge).



The following names are defined for this attribute: GROUPAVERAGETIME_MS or GROUPAVERA(historical name), Group Average Time ms (caption), GroupAverageTime_ms (attribute name), andGROUPAVERA (column name).

Group OperationsThe number of group operations that occurred in the Hadoop cluster. The type is integer (64-bitgauge).



The following names are defined for this attribute: GROUPOPERATIONS or GROUPOPERA (historicalname), Group Operations (caption), GroupOperations (attribute name), and GROUPOPERA (columnname).





Login Failure Average Time msThe average time that is required for the failed login attempts. The type is real number (32-bit gauge)with one decimal places of precision.



The following names are defined for this attribute: LOGINFAILUREAVERAGETIME_MS or LOGINFAIL0(historical name), Login Failure Average Time ms (caption), LoginFailureAverageTime_ms (attributename), and LOGINFAIL0 (column name).

Login Failure Number Of OperationsThe number of failed login attempts. The type is integer (32-bit gauge).



The following names are defined for this attribute: LOGINFAILURENUMBEROFOPERATIONSor LOGINFAILU (historical name), Login Failure Number Of Operations (caption),LoginFailureNumberOfOperations (attribute name), and LOGINFAILU (column name).


Login SuccessThe number of successful login attempts. The type is integer (32-bit gauge).



The following names are defined for this attribute: LOGINSUCCESS or LOGINSUCCE (historical name),Login Success (caption), LoginSuccess (attribute name), and LOGINSUCCE (column name).

Login Success Average Time msThe average time that is required for the successful login attempts. The type is real number (32-bitgauge) with one decimal places of precision.



The following names are defined for this attribute: LOGINSUCCESSAVERAGETIME_MSor LOGINSUCC0 (historical name), Login Success Average Time ms (caption),LoginSuccessAverageTime_ms (attribute name), and LOGINSUCC0 (column name).





ServiceNameThe name of daemon process running in Hadoop Cluster This attribute is a key attribute. The type isstring.



The following names are defined for this attribute: SERVICENAME or SERVICENAM (historical name),ServiceName (caption), ServiceName (attribute name), and SERVICENAM (column name).





Unified Console data setThis data set monitors the metrics for server and client components of Unified Console Service in theHadoop cluster for Ambari based Hadoop installations. Thresholds for this data set are associated withthe Hadoop component. This data set is displayed as KH8 UNIFIEDCONSOLE in the threshold editor. Adata sample is sent to the server every minute and is maintained for 8 days by default. The attributesshown in italic are visible in the UI. All attributes are available for thresholds.




Attributes 215























































Attributes 217































YARN data setThis data set monitors the metrics for server and client components of YARN Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 YARN in the threshold editor. A data sample issent to the server every minute and is maintained for 8 days by default. The attributes shown in italic arevisible in the UI. All attributes are available for thresholds.


















Attributes 219






















































Attributes 221

















ZooKeeper data setThis data set monitors the metrics for server and client components of ZooKeeper Service in the Hadoopcluster for Ambari based Hadoop installations. Thresholds for this data set are associated with theHadoop component. This data set is displayed as KH8 ZOOKEEPER in the threshold editor. A data sampleis sent to the server every minute and is maintained for 8 days by default. The attributes shown in italicare visible in the UI. All attributes are available for thresholds.


































Attributes 223




















































Attributes 225





Chapter 5. Workspaces

A workspace is the working area of the Tivoli Enterprise Portal application window. The Navigator containsa list of the workspaces provided by the agent.

About workspaces

Use the Navigator to select the workspace you want to see. As part of the application window, the statusbar shows the Tivoli Enterprise Portal Server name and port number to which the displayed informationapplies and the ID of the current user.

When you select an item in the Navigator, a default workspace is displayed. When you right-click anavigator item, a menu that includes a Workspace item is displayed. The Workspace item contains a listof workspaces for that navigator item. Each workspace has at least one view. Some views have links toother workspaces. You can also use the Workspace Gallery tool as described in the Tivoli Enterprise PortalUser's Guide to open workspaces.

The workspaces in the Navigator are displayed in a Physical view that shows your enterprise as a physicalmapping or a dynamically populated logical view that is agent-specific. You can also create a Logical view.The Physical view is the default view.

To select the dynamically populated logical view, select Hyper-V from the View list in the Navigator. Toview the dynamically populated Hyper-V logical view, you must log in to the Tivoli Enterprise Portal as asystem administrator.

To select the dynamically populated logical view, select ADO from the View list in the Navigator. To viewthe dynamically populated ADO logical view, you must log in to the Tivoli Enterprise Portal as a systemadministrator.

This monitoring agent provides predefined workspaces. You cannot modify or delete the predefinedworkspaces, but you can create new workspaces by editing them and saving the changes with a differentname.

The Monitoring Agent for Hadoop provides various default workspaces. These workspaces are displayedin the Navigator under the following nodes and subnodes for this monitoring agent:Hadoop

Corresponds to a Hadoop instance and contains agent instance-level workspaces.Hadoop Hosts

Host Name

When a single instance of the monitoring agent is defined on a system, the top-level node is Hadoop -Instance:Hostname:H8. The Hadoop workspace is defined at this node. When multiple instances of themonitoring agent are defined on a system, the top-level node becomes Hadoop. The Hadoop workspaceis undefined at this node. A node for each instance is created called Instance:Hostname:H8. A workspacethat is called Instance:Hostname:H8 is associated with the instance node. This workspace is comparableto the Hadoop workspace.

Workspace views can be any combination of query-based views, event views, and special purpose views.

Additional information about workspaces

For more information about creating, customizing, and working with workspaces, see "Using workspaces"in the Tivoli Enterprise Portal User's Guide.

For a list of the predefined workspaces for this monitoring agent and a description of each workspace, seePredefined workspaces and the information about each individual workspace.

Some attribute groups for this monitoring agent might not be represented in the predefined workspacesor views for this agent. For a full list of the attribute groups, see “Data sets for the monitoring agent” onpage 44.


If you are using remote management to navigate to your systems in the Tivoli Enterprise Portal, navigatefrom the host name of the computer where you installed the agent.

When you add another instance of the VMware VI agent to a configuration that has as instance of thisagent, the new instance is displayed dynamically in the Tivoli Enterprise Portal. Each instance nameis presented in the Tivoli Enterprise Portal when more than one instance is reporting from a specifichost. To identify an instance, navigate from the host name of the computer where you installed themonitoring agent. For example, with one instance, you see hostname and the contained node is Hadoop.The workspaces that display data for this application are contained in the Hadoop node. When youadd an instance, both instances are displayed under hostname, and an extra level is displayed as thehostname:H8. In the Navigator, the instance name is shown only if there are two or more instances.

Workspace descriptionsEach workspace description provides information about the workspace such as the purpose and a list ofviews in the workspace.

Workspaces are listed under navigator items. When the agent has subnodes, the navigator items are listedunder the subnode.

Hadoop navigator itemThe workspace descriptions are organized by the navigator item to which the workspaces are relevant.

Hadoop workspace

This workspace contains the following views:

This workspace contains the following view:

.placeholder

Performance Object Status navigator itemThe workspace descriptions are organized by the navigator item to which the workspaces are relevant.

Performance Object Status workspaceThis workspace displays the overall health of the application.



Data Collection StatusDisplays the status of the collection of data from the application. Normally this will display NOERROR indicating that the agent is collecting application data correctly. If some of the agent'sother views are empty this view will help isolate the cause of the failure. CUSTOM objects willdisplay the name of the attribute group. Each CUSTOM group may display error values specific tothe data collection. These are documented in the User's Guide.

placeholder

Services navigator itemThe workspace descriptions are organized by the navigator item to which the workspaces are relevant.

placeholder


Hadoop Hosts subnodeThe predefined workspace descriptions for the subnode are organized by the navigator item to which theworkspaces are relevant.

Hadoop Hosts navigator itemplaceholder

HOS Performance Object Status navigator itemHOS Performance Object Status workspace

This workspace displays the overall health of the application.



Data Collection StatusDisplays the status of the collection of data from the application. Normally this will display NOERROR indicating that the agent is collecting application data correctly. If some of the agent'sother views are empty this view will help isolate the cause of the failure. CUSTOM objects willdisplay the name of the attribute group. Each CUSTOM group may display error values specific tothe data collection. These are documented in the User's Guide.

placeholder

Workspaces 229


Chapter 6. Situations

A situation is a logical expression involving one or more system conditions. Situations are used to monitorthe condition of systems in your network. You can manage situations from the Tivoli Enterprise Portal byusing the Situation Editor or from the command-line interface using the tacmd commands for situations.You can manage private situations in the private configuration XML file.

About situations

The monitoring agents that you use to monitor your system environment include a set of predefinedsituations that you can use as-is. You can also create new situations to meet your requirements.

Predefined situations contain attributes that check for system conditions common to many enterprises.Using predefined situations can improve the speed with which you can begin using the Monitoring Agentfor Hadoop. You can change the conditions or values being monitored by a predefined situation to theconditions or values best suited to your enterprise.

You can display predefined situations and create your own situations using the Situation editor. TheSituation editor initially lists the situations associated with the navigator item that you selected. When youclick a situation name or create a situation, a panel opens with the following tabs:Formula

Formula describing the condition being tested.Distribution

List of managed systems (operating systems, subsystems, or applications) to which the situation canbe distributed. All the Hadoop agent managed systems are assigned by default.

Expert adviceComments and instructions to be read in the event workspace.

ActionCommand to be sent to the system.

EIFCustomize forwarding of the event to an Event Integration Facility receiver. (Available when the TivoliEnterprise Monitoring Server is configured to forward events.)

UntilOptions to close the event after a period of time, or when another situation becomes true.

Additional information about situations

The Tivoli Enterprise Portal User's Guide contains more information about predefined and customsituations and how to use them to respond to alerts.

For a list of the predefined situations and information about each individual situation for this monitoringagent, see “Predefined situations” on page 231.

Predefined situationsThe monitoring agent contains predefined situations, which are organized by Navigator item.

Agent level Navigator items

• Hadoop

– Not applicable• Performance Object Status

– Not applicable• Services


– Not applicable

Hadoop Hosts (HOS) subnode

• Hadoop Hosts

– Not applicable• HOS Performance Object Status

– Not applicable

Situation descriptionsEach situation description provides information about the situation that you can use to monitor thecondition of systems in your network.

The situation descriptions provide the following information:Description

Information about the conditions that the situation tests.Attribute groups

Names of the attribute groups that contain the attributes from which the situation retrieves datasamples.

FormulaSyntax that contains one or more logical expressions that describe the conditions for the situation tomonitor. The information center topic that corresponds to this situation contains the formula for thisagent.

DistributionWhether the situation is automatically distributed to instances of the agent or is available for manualdistribution.

Run at startupWhether the situation starts monitoring when the agent starts.

Sampling intervalNumber of seconds that elapse between one sample of data that the monitoring agent collects for theserver and the next sample.

Situation persistenceWhether the conditions specified in the situation evaluate to "true" for the defined number ofoccurrences in a row before the situation is raised. The default of one means that no persistence-checking takes place.

SeveritySeverity of the predefined events: Warning, Informational, or Critical.

Clearing conditionsControls when a true situation closes: after a period, when another situation is true, or whicheveroccurs first if both are selected.

Hadoop navigator itemNo predefined situations are included for this navigator item. The situation descriptions are organized bythe navigator item to which the situations are relevant.

placeholder

Performance Object Status navigator itemNo predefined situations are included for this navigator item. The situation descriptions are organized bythe navigator item to which the situations are relevant.

placeholder


Services navigator itemNo predefined situations are included for this navigator item. The situation descriptions are organized bythe navigator item to which the situations are relevant.

placeholder

Hadoop Hosts subnodeThe situation descriptions are organized by the navigator item to which the situations are relevant.

Hadoop Hosts navigator item

No predefined situations are included for this navigator item.

placeholder

HOS Performance Object Status navigator item

No predefined situations are included for this navigator item.

placeholder

Situations 233


Chapter 7. Take Action commands

Take Action commands can be run from the portal client or included in a situation or a policy.

About Take Action commands

When included in a situation, the command runs when the situation becomes true. A Take Actioncommand in a situation is also referred to as reflex automation. When you enable a Take Action commandin a situation, you automate a response to system conditions. For example, you can use a Take Actioncommand to send a command to restart a process on the managed system or to send a text message to acell phone.

In advanced automation, policies are used to take actions, schedule work, and automate manual tasks.A policy comprises a series of automated steps called activities that are connected to create a workflow.After an activity is completed, the Tivoli Enterprise Portal receives return-code feedback, and advancedautomation logic responds with subsequent activities that are prescribed by the feedback.

A basic Take Action command shows the return code of the operation in a message box that is displayedafter the action is completed or in a log file. After you close this window, no further information isavailable for this action.

Additional information about Take Action commandsFor more information about working with Take Action commands, see "Take Action commands" in theTivoli Enterprise Portal User's Guide.

For a list of the Take Action commands for this monitoring agent and a description of each command, see“Predefined Take Action commands” on page 235 and the information for each individual command.

Predefined Take Action commandsNot all agents have predefined Take Action commands. But you can create Take Action commands for anyagent.

The Hadoop does not provide predefined Take Action commands.

This monitoring agent contains the following Take Action commands:

• placeholder for when no items in list

Take Action command descriptionsEach Take Action command description provides information you can use to decide whether to run theTake Action command or whether to include the Take Action command in a situation or a policy.

The descriptions of the Take Action commands provide the following information:Description

Actions the command performs on the system to which it is sent, and the permissions required for theTake Action command to function.

System commandSyntax for the command required to run the Take Action command from a situation or policy.

ArgumentsList of parameters, if any, for the Take Action command with a short description and the default value(if any) for each one. This section is not included if the Take Action command has no arguments.


Destination systemsWhere the command is to be run, which can be on the Managed System (agent) where the agent islocated or on the Managing System (Tivoli Enterprise Monitoring Server) to which it is connected.

Return codesInformation that the Take Action command returns.


Chapter 8. Policies

Policies are used as an advanced automation technique for implementing more complex workflowstrategies than you can create through simple automation. All agents do not provide predefined policies,but you can create policies for any agent.

A policy is a set of automated system processes that can take actions, schedule work for users, orautomate manual tasks. You use the Workflow Editor to design policies. You control the order in whichthe policy executes a series of automated steps, which are also called activities. Policies are connectedto create a workflow. After an activity is completed, the Tivoli Enterprise Portal receives return-codefeedback, and advanced automation logic responds with subsequent activities prescribed by thefeedback.

For more information about working with policies, see "Automation with policies" in the Tivoli EnterprisePortal User's Guide.

For information about using the Workflow Editor, see the IBM Tivoli Monitoring Administrator's Guide orthe Tivoli Enterprise Portal online help.

Predefined policiesNot all agents have predefined policies. But you can create policies for any agent.

The Monitoring Agent for Hadoop does not provide predefined policies.

This monitoring agent contains the following policies:

• Policy1 name• Policy2 name

Policy descriptionsEach policy description provides information you can use to decide whether to implement the policy.

The descriptions of the policies provide the following information:

• Actions the policy takes• Workflow activities

Actions you can take when the policy runs

Policy1 namepolicy short description

policy details

KVM_VM_CreatedThis policy sends a create request to Tivoli Application Dependency Discovery Manager when a newvirtual machine is created.

The create request is sent so that the corresponding virtual machine CDM object is created inthe Tivoli Application Dependency Discovery Manager database. This policy is triggered by theKVM_Virtual_Machine_Created situation.

This policy includes two workflow activities:


On Demand Report activityUsed to collect additional information about the virtual machine being created that is not present inthe situation processed, for example, the virtual machine name.

Send a Tivoli Application Dependency Discovery Manager Update activityUsed to send a create update to Tivoli Application Dependency Discovery Manager. The payloadconsists of the data contained in the situation processed and the data returned by the On DemandReport.

MS_SQL_DB_free_space_criticalThis policy provides actions to take on low free space on the MS SQL server.

This policy is triggered by the MS_SQL_DB_Freespace_Critical situation.

When triggered, the workflow requires that you select one of the following actions:

• Run the koqignor command.• Run the koqmail command.

Where:database user id

Connection user IDpassword

Password as a sysadmin authorityemail id

E-mail address of the database administrator


Chapter 9. Event mapping

The Tivoli Event Integration Facility (EIF) interface is used to forward situation events to Tivoli Netcool/OMNIbus or Tivoli Enterprise Console®.

EIF events specify an event class, and the event data is specified as name-value pairs that identify thename of an event slot and the value for the slot. An event class can have subclasses. IBM Tivoli Monitoringprovides the base event class definitions and a set of base slots that are included in all monitoring events.Agents extend the base event classes to define subclasses that include agent-specific slots. For Hadoopagent events, the event classes correspond to the agent attribute groups, and the agent-specific slotscorrespond to the attributes in the attribute group.

The situation editor in the Tivoli Enterprise Portal can be used to perform custom mapping of data to EIFslots instead of using the default mapping described in this topic. For more information about EIF slotcustomization, see the Tivoli Enterprise Portal User's Guide.

Tivoli Enterprise Console requires that event classes and their slots are defined in BAROC (Basic Recorderof Objects in C) files. Each agent provides a BAROC file that contains event class definitions for the agentand is installed on the Tivoli Enterprise Monitoring Server in the TECLIB directory (install_dir/cms/TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems)when application support for the agent is installed. The BAROC file for the agent and the base BAROC filesprovided with Tivoli Monitoring must also be installed onto the Tivoli Enterprise Console. For details, see"Setting up event forwarding to Tivoli Enterprise Console" in the IBM Tivoli Monitoring Installation andSetup Guide.

Each of the event classes is a child of KH8_Base and is defined in the kh8.baroc (version 08.19.09) file.The KH8_Base event class can be used for generic rules processing for any event from the MonitoringAgent for Hadoop.

For events that are generated by situations in the Ambari Metrics attribute group, events are sent by usingthe ITM_KH8_AMBARIMETRICS event class. This event class contains the following slots:

• node: STRING

• timestamp: STRING

• cluster_name: STRING

• component_name: STRING

• desired_stack_id: STRING

• desired_state: STRING

• hdp_version: STRING

• host_name: STRING

• init_count_in_cluster: INTEGER

• init_count_in_cluster_enum: STRING

• installed_count_in_cluster: INTEGER

• installed_count_in_cluster_enum: STRING

• install_failed_count_in_cluster: INTEGER

• install_failed_count_in_cluster_enum: STRING

• maintenance_state: STRING

• other_count_in_cluster: INTEGER

• other_count_in_cluster_enum: STRING

• service_name: STRING


• stack_id: STRING

• stale_configs: STRING

• started_count_in_cluster: INTEGER

• started_count_in_cluster_enum: STRING

• state: STRING

• total_count_in_cluster: INTEGER

• total_count_in_cluster_enum: STRING

• unknown_count_in_cluster: INTEGER

• unknown_count_in_cluster_enum: STRING

• upgrade_state: STRING

For events that are generated by situations in the Atlas attribute group, events are sent by using theITM_KH8_ATLAS event class. This event class contains the following slots:

• node: STRING






















• state: STRING







For events that are generated by situations in the Big SQL attribute group, events are sent by using theITM_KH8_BIGSQL event class. This event class contains the following slots:

• node: STRING






















• state: STRING






For events that are generated by situations in the Cluster Metrics attribute group, events are sent by usingthe ITM_KH8_CLUSTERMETRICS event class. This event class contains the following slots:

• node: STRING


• activenodemanagers: REAL

• activenodemanagers_enum: STRING

• clustermetrics: STRING

• collect_timestamp: STRING

Event mapping 241

• context: STRING

• decommissionednodemanagers: REAL

• decommissionednodemanagers_enum: STRING

• kh8_hostname: STRING

• lostnodemanagers: REAL

• lostnodemanagers_enum: STRING

• rebootednodemanagers: REAL

• rebootednodemanagers_enum: STRING

• unhealthynodemanagers: REAL

• unhealthynodemanagers_enum: STRING

For events that are generated by situations in the Cluster Overview attribute group, events are sent byusing the ITM_KH8_CLUSTEROVERVIEW event class. This event class contains the following slots:

• node: STRING


• clusterid: STRING

• datanodestatus: INTEGER

• datanodestatus_enum: STRING

• filesystemstatus: INTEGER

• filesystemstatus_enum: STRING

• host_msn: STRING

• ip_address: STRING

• jvmstatus: INTEGER

• jvmstatus_enum: STRING


• nodefqdn: STRING

• port: INTEGER

• port_enum: STRING

• queuestatus: INTEGER

• queuestatus_enum: STRING

• rpcstatus: INTEGER

• rpcstatus_enum: STRING

For events that are generated by situations in the ClusterDetails attribute group, events are sent by usingthe ITM_KH8_CLUSTERDETAILS event class. This event class contains the following slots:

• node: STRING


• applicationsfailed: REAL

• applicationsfailed_enum: STRING

• avgmemoryheapusedpercent: REAL

• avgmemoryheapusedpercent_enum: STRING


• capacitytotalgb: REAL

• capacitytotalgb_enum: STRING

• capacityusedgb: REAL

• capacityusedgb_enum: STRING

• capacityusedpercent: REAL

• capacityusedpercent_enum: STRING

• clusterid: STRING

• clustername: STRING

• containersfailed: REAL

• containersfailed_enum: STRING

• countofnodes: STRING

• deaddatanodes: STRING

• hastate: STRING

• livedatanodes: STRING

• missingblocks: REAL

• missingblocks_enum: STRING

• nnuptime: STRING

• numactivenms: STRING

• numdecommissionednms: REAL

• numdecommissionednms_enum: STRING

• numlostnms: REAL

• numlostnms_enum: STRING

• numrebootednms: REAL

• numrebootednms_enum: STRING

• numunhealthynms: REAL

• numunhealthynms_enum: STRING

• processcpuloadpercentage: REAL

• processcpuloadpercentage_enum: STRING

• totaldiskfailures: STRING

For events that are generated by situations in the DataNode attribute group, events are sent by using theITM_KH8_DATANODE event class. This event class contains the following slots:

• node: STRING


• blockchecksumaveragetime_ms: REAL

• blockchecksumaveragetime_ms_enum: STRING

• blockchecksumoperations: REAL

• blockchecksumoperations_enum: STRING

• blockreportsaveragetime_ms: REAL

• blockreportsaveragetime_ms_enum: STRING

Event mapping 243

• blockreportsoperations: REAL

• blockreportsoperations_enum: STRING

• blockscached: INTEGER

• blockscached_enum: STRING

• blocksgetlocalpathinfo: REAL

• blocksgetlocalpathinfo_enum: STRING

• blocksread: INTEGER

• blocksread_enum: STRING

• blocksremoved: REAL

• blocksremoved_enum: STRING

• blocksreplicated: REAL

• blocksreplicated_enum: STRING

• blocksuncached: INTEGER

• blocksuncached_enum: STRING

• blocksverified: REAL

• blocksverified_enum: STRING

• blockswritten: INTEGER

• blockswritten_enum: STRING

• blockverificationfailures: REAL

• blockverificationfailures_enum: STRING

• bytesread: REAL

• bytesreadmb: REAL

• bytesreadmb_enum: STRING

• bytesread_enum: STRING

• byteswritten: REAL

• byteswrittenmb: REAL

• byteswrittenmb_enum: STRING

• byteswritten_enum: STRING

• cachereport: REAL

• cachereportaveragetime_ms: REAL

• cachereportaveragetime_ms_enum: STRING

• cachereport_enum: STRING


• context: STRING

• copyblockoperationaveragetime_ms: REAL

• copyblockoperationaveragetime_ms_enum: STRING

• copyblockoperations: REAL

• copyblockoperations_enum: STRING

• flushnanosaveragetime_ms: REAL


• flushnanosaveragetime_ms_enum: STRING

• flushnanosoperations: REAL

• flushnanosoperations_enum: STRING

• fsynccount: REAL

• fsynccount_enum: STRING

• fsyncnanosaveragetime_ms: REAL

• fsyncnanosaveragetime_ms_enum: STRING

• fsyncnanosoperations: REAL

• fsyncnanosoperations_enum: STRING

• heartbeatsaveragetime_ms: REAL

• heartbeatsaveragetime_ms_enum: STRING

• heartbeatsoperations: INTEGER

• heartbeatsoperations_enum: STRING


• packetroundtriptimenanosaveragetime_ms: REAL

• packetroundtriptimenanosaveragetime_ms_enum: STRING

• packetroundtriptimenanosoperations: REAL

• packetroundtriptimenanosoperations_enum: STRING

• readblockoperation: REAL

• readblockoperationaveragetime_ms: REAL

• readblockoperationaveragetime_ms_enum: STRING

• readblockoperation_enum: STRING

• readsfromlocalclient: INTEGER

• readsfromlocalclient_enum: STRING

• readsfromremoteclient: INTEGER

• readsfromremoteclient_enum: STRING

• replaceblockaveragetime_ms: REAL

• replaceblockaveragetime_ms_enum: STRING

• replaceblockoperationnumberofoperations: REAL

• replaceblockoperationnumberofoperations_enum: STRING

• senddatapacketblockedonnetworknanosaveragetime_ms: REAL

• senddatapacketblockedonnetworknanosaveragetime_ms_enum: STRING

• senddatapacketblockedonnetworknanosoperations: REAL

• senddatapacketblockedonnetworknanosoperations_enum: STRING

• senddatapackettransfernanosaveragetime_ms: REAL

• senddatapackettransfernanosaveragetime_ms_enum: STRING

• senddatapackettransfernanosoperations: REAL

• senddatapackettransfernanosoperations_enum: STRING

• sessionid: INTEGER

Event mapping 245

• sessionid_enum: STRING

• volumefailures: REAL

• volumefailures_enum: STRING

• writeblockaveragetime_ms: REAL

• writeblockaveragetime_ms_enum: STRING

• writeblockoperations: REAL

• writeblockoperations_enum: STRING

• writesfromlocalclient: INTEGER

• writesfromlocalclient_enum: STRING

• writesfromremoteclient: INTEGER

• writesfromremoteclient_enum: STRING

For events that are generated by situations in the Druid attribute group, events are sent by using theITM_KH8_DRUID event class. This event class contains the following slots:

• node: STRING






















• state: STRING







For events that are generated by situations in the Falcon attribute group, events are sent by using theITM_KH8_FALCON event class. This event class contains the following slots:

• node: STRING






















• state: STRING






For events that are generated by situations in the Flume attribute group, events are sent by using theITM_KH8_FLUME event class. This event class contains the following slots:

• node: STRING





Event mapping 247


















• state: STRING






For events that are generated by situations in the FS Name System attribute group, events are sent byusing the ITM_KH8_FSNAMESYSTEM event class. This event class contains the following slots:

• node: STRING


• blockcapacity: REAL

• blockcapacitymb: REAL

• blockcapacitymb_enum: STRING

• blockcapacity_enum: STRING

• blockstotal: REAL

• blockstotal_enum: STRING

• capacityremainingbytes: REAL

• capacityremainingbytes_enum: STRING

• capacityremaininggb: REAL

• capacityremaininggb_enum: STRING

• capacitytotalbytes: REAL

• capacitytotalbytes_enum: STRING


• capacitytotalgb: REAL

• capacitytotalgb_enum: STRING

• capacityusedbytes: REAL

• capacityusedbytes_enum: STRING

• capacityusedgb: REAL

• capacityusedgb_enum: STRING

• capacityusednondfsbytes: REAL

• capacityusednondfsbytes_enum: STRING

• capacityusednondfsgb: REAL

• capacityusednondfsgb_enum: STRING

• capacityusedpercent: REAL

• capacityusedpercent_enum: STRING


• context: STRING

• corruptblocks: REAL

• corruptblockspercent: INTEGER

• corruptblockspercent_enum: STRING

• corruptblocks_enum: STRING

• excessblocks: REAL

• excessblocks_enum: STRING

• expiredheartbeats: REAL

• expiredheartbeats_enum: STRING

• filestotal: REAL

• filestotal_enum: STRING

• hasstate: STRING


• lastcheckpointtime_ms: REAL

• lastcheckpointtime_ms_enum: STRING

• lastwrittentransactionid: REAL

• lastwrittentransactionid_enum: STRING

• millissincelastloadededits: REAL

• millissincelastloadededits_enum: STRING

• missingblocks: REAL

• missingblockspercent: INTEGER

• missingblockspercent_enum: STRING

• missingblocks_enum: STRING

• pendingdatanodemessagecount: REAL

• pendingdatanodemessagecount_enum: STRING

• pendingdeletionblocks: REAL

Event mapping 249

• pendingdeletionblocks_enum: STRING

• pendingreplicationblocks: REAL

• pendingreplicationblocks_enum: STRING

• postponedmisreplicatedblocks: REAL

• postponedmisreplicatedblocks_enum: STRING

• scheduledreplicationblocks: REAL

• scheduledreplicationblocks_enum: STRING

• snapshots: REAL

• snapshots_enum: STRING

• snapshottabledirectories: REAL

• snapshottabledirectories_enum: STRING

• staledatanodes: REAL

• staledatanodes_enum: STRING

• totalfiles: INTEGER

• totalfiles_enum: STRING

• totalload: REAL

• totalload_enum: STRING

• transactionssincelastcheckpoint: REAL

• transactionssincelastcheckpoint_enum: STRING

• transactionssincelastrollback: REAL

• transactionssincelastrollback_enum: STRING

• underreplicatedblocks: REAL

• underreplicatedblocks_enum: STRING

For events that are generated by situations in the HBase attribute group, events are sent by using theITM_KH8_HBASE event class. This event class contains the following slots:

• node: STRING























• state: STRING






For events that are generated by situations in the HDFS attribute group, events are sent by using theITM_KH8_HDFS event class. This event class contains the following slots:

• node: STRING






















• state: STRING

Event mapping 251






For events that are generated by situations in the Hive attribute group, events are sent by using theITM_KH8_HIVE event class. This event class contains the following slots:

• node: STRING






















• state: STRING






For events that are generated by situations in the HOS Performance Object Status attribute group, eventsare sent by using the ITM_KH8_HOS_PERFORMANCE_OBJECT_STATUS event class. This event classcontains the following slots:

• average_collection_duration: REAL

• average_collection_duration_enum: STRING


• cache_hits: INTEGER

• cache_hit_percent: REAL

• cache_misses: INTEGER

• error_code: INTEGER

• error_code_enum: STRING

• intervals_skipped: INTEGER

• last_collection_duration: REAL

• last_collection_finished: STRING

• last_collection_finished_enum: STRING

• last_collection_start: STRING

• last_collection_start_enum: STRING

• node: STRING

• number_of_collections: INTEGER

• object_name: STRING

• object_status: INTEGER

• object_status_enum: STRING

• object_type: INTEGER

• object_type_enum: STRING

• query_name: STRING

• refresh_interval: INTEGER


For events that are generated by situations in the Hosts nodes attribute group, events are sent by usingthe ITM_KH8_HOSTS_NODES event class. This event class contains the following slots:

• node: STRING


• subnode_affinity: STRING

• subnode_msn: STRING

• subnode_resource_name: STRING

• subnode_type: STRING

• subnode_version: STRING

For events that are generated by situations in the JVM Metrics attribute group, events are sent by usingthe ITM_KH8_JVMMETRICS event class. This event class contains the following slots:

• node: STRING



• context: STRING

• garabagecollectionsleeptime_ms: REAL

• garabagecollectionsleeptime_ms_enum: STRING

• garbagecollectioncount: REAL

Event mapping 253

• garbagecollectioncountpsmarksweep: REAL

• garbagecollectioncountpsmarksweep_enum: STRING

• garbagecollectioncountpsscavenge: REAL

• garbagecollectioncountpsscavenge_enum: STRING

• garbagecollectioncount_enum: STRING

• garbagecollectioninformationthreshold: REAL

• garbagecollectioninformationthreshold_enum: STRING

• garbagecollectiontimemillispsmarksweep: REAL

• garbagecollectiontimemillispsmarksweep_enum: STRING

• garbagecollectiontimepsscavengems: REAL

• garbagecollectiontimepsscavengems_enum: STRING

• garbagecollectiontime_ms: REAL

• garbagecollectiontime_ms_enum: STRING

• garbagecollectionwarningthreshold: REAL

• garbagecollectionwarningthreshold_enum: STRING

• gcrate: REAL

• gcrate_enum: STRING


• logerror: INTEGER

• logerror_enum: STRING

• logfatal: INTEGER

• logfatal_enum: STRING

• loginfo: INTEGER

• loginfo_enum: STRING

• logwarn: INTEGER

• logwarn_enum: STRING

• memheapusedpercent: REAL

• memheapusedpercent_enum: STRING

• memoryheapcommittedmb: REAL

• memoryheapcommittedmb_enum: STRING

• memoryheapmaximummb: REAL

• memoryheapmaximummb_enum: STRING

• memoryheapusedmb: REAL

• memoryheapusedmb_enum: STRING

• memorymaximummb: REAL

• memorymaximummb_enum: STRING

• memorynonheapcommittedmb: REAL

• memorynonheapcommittedmb_enum: STRING

• memorynonheapfreemb: REAL


• memorynonheapfreemb_enum: STRING

• memorynonheapmaximummb: REAL

• memorynonheapmaximummb_enum: STRING

• memorynonheapusedmb: REAL

• memorynonheapusedmb_enum: STRING

• processname: STRING



• threadsblocked: INTEGER

• threadsblocked_enum: STRING

• threadsnew: INTEGER

• threadsnew_enum: STRING

• threadsrunnable: INTEGER

• threadsrunnable_enum: STRING

• threadsterminated: INTEGER

• threadsterminated_enum: STRING

• threadstimedwaiting: REAL

• threadstimedwaiting_enum: STRING

• threadswaiting: INTEGER

• threadswaiting_enum: STRING

For events that are generated by situations in the Kafka attribute group, events are sent by using theITM_KH8_KAFKA event class. This event class contains the following slots:

• node: STRING

















Event mapping 255






• state: STRING






For events that are generated by situations in the Knox attribute group, events are sent by using theITM_KH8_KNOX event class. This event class contains the following slots:

• node: STRING






















• state: STRING







For events that are generated by situations in the Mahout attribute group, events are sent by using theITM_KH8_MAHOUT event class. This event class contains the following slots:

• node: STRING






















• state: STRING






For events that are generated by situations in the MapReduce2 attribute group, events are sent by usingthe ITM_KH8_MAPREDUCE2 event class. This event class contains the following slots:

• node: STRING





Event mapping 257


















• state: STRING






For events that are generated by situations in the NameNode attribute group, events are sent by using theITM_KH8_NAMENODE event class. This event class contains the following slots:

• addblock: REAL

• addblock_enum: STRING

• additionaldatanode: REAL

• additionaldatanode_enum: STRING

• allowsnapshot: REAL

• allowsnapshot_enum: STRING

• blocklocations: REAL

• blocklocations_enum: STRING

• blockreceiveddeleted: REAL

• blockreceiveddeleted_enum: STRING

• blockreportaveragetime_ms: REAL

• blockreportaveragetime_ms_enum: STRING

• blockreportoperations: REAL

• blockreportoperations_enum: STRING


• cachereport: REAL

• cachereportaveragetime: REAL

• cachereportaveragetime_enum: STRING

• cachereport_enum: STRING


• context: STRING

• createfileoperations: REAL

• createfileoperations_enum: STRING

• createlink: REAL

• createlink_enum: STRING

• createsnapshot: REAL

• createsnapshot_enum: STRING

• deletefile: REAL

• deletefile_enum: STRING

• deletesnapshot: REAL

• deletesnapshot_enum: STRING

• disallowsnapshot: REAL

• disallowsnapshot_enum: STRING

• editaveragetime_ms: REAL

• editaveragetime_ms_enum: STRING

• editoperations: REAL

• editoperations_enum: STRING

• fileinfo: REAL

• fileinfo_enum: STRING

• filesappended: REAL

• filesappended_enum: STRING

• filescreated: INTEGER

• filescreated_enum: STRING

• filesdeleted: REAL

• filesdeleted_enum: STRING

• filesingetlists: REAL

• filesingetlists_enum: STRING

• filesrenamed: REAL

• filesrenamed_enum: STRING

• filesystemimageloadtime_ms: REAL

• filesystemimageloadtime_ms_enum: STRING

• getimage: INTEGER

• getimagetime_ms: REAL

• getimagetime_ms_enum: STRING

Event mapping 259

• getimage_enum: STRING

• getlinktarget: REAL

• getlinktarget_enum: STRING

• getlists: REAL

• getlists_enum: STRING


• listsnapshottabledirectories: REAL

• listsnapshottabledirectories_enum: STRING

• node: STRING

• processname: STRING

• putimage: REAL

• putimageaveragetime_ms: REAL

• putimageaveragetime_ms_enum: STRING

• putimage_enum: STRING

• renamesnapshot: REAL

• renamesnapshot_enum: STRING

• safemodetime_ms: REAL

• safemodetime_ms_enum: STRING



• snapshotreport: REAL

• snapshotreport_enum: STRING

• storageblockreport: REAL

• storageblockreport_enum: STRING

• synchronizationaveragetime_ms: REAL

• synchronizationaveragetime_ms_enum: STRING

• synchronizationoperations: REAL

• synchronizationoperations_enum: STRING


• transactions: REAL

• transactionsaveragetime_ms: REAL

• transactionsaveragetime_ms_enum: STRING

• transactionsbatchedinsynchronization: REAL

• transactionsbatchedinsynchronization_enum: STRING

• transactions_enum: STRING

For events that are generated by situations in the NiFi attribute group, events are sent by using theITM_KH8_NIFI event class. This event class contains the following slots:

• node: STRING























• state: STRING






For events that are generated by situations in the NiFi Registry attribute group, events are sent by usingthe ITM_KH8_NIFIREGISTRY event class. This event class contains the following slots:

• node: STRING











Event mapping 261












• state: STRING






For events that are generated by situations in the NodeManager Metrics attribute group, events are sentby using the ITM_KH8_NODEMANAGERMETRICS event class. This event class contains the followingslots:

• allocatedcontainers: REAL

• allocatedcontainers_enum: STRING

• allocatedspacegb: REAL

• allocatedspacegb_enum: STRING

• availablespacegb: REAL

• availablespacegb_enum: STRING


• containerscompleted: REAL

• containerscompleted_enum: STRING

• containersfailed: REAL

• containersfailed_enum: STRING

• containersinitiated: REAL

• containersinitiated_enum: STRING

• containerskilled: REAL

• containerskilled_enum: STRING

• containerslaunched: REAL

• containerslaunched_enum: STRING

• containersrunning: REAL

• containersrunning_enum: STRING


• context: STRING


• node: STRING


For events that are generated by situations in the Oozie attribute group, events are sent by using theITM_KH8_OOZIE event class. This event class contains the following slots:

• node: STRING






















• state: STRING






For events that are generated by situations in the Operating System attribute group, events are sent byusing the ITM_KH8_OPERATINGSYSTEM event class. This event class contains the following slots:

• node: STRING


• availableprocessors: REAL

Event mapping 263

• availableprocessors_enum: STRING



• processcpuload: REAL

• processcpuload_enum: STRING

• systemcpuload: REAL

• systemcpuload_enum: STRING

For events that are generated by situations in the Performance Object Status attribute group, events aresent by using the ITM_KH8_PERFORMANCE_OBJECT_STATUS event class. This event class contains thefollowing slots:

• average_collection_duration: REAL

• average_collection_duration_enum: STRING

• cache_hits: INTEGER

• cache_hit_percent: REAL

• cache_misses: INTEGER

• error_code: INTEGER

• error_code_enum: STRING

• intervals_skipped: INTEGER

• last_collection_duration: REAL

• last_collection_finished: STRING

• last_collection_finished_enum: STRING

• last_collection_start: STRING

• last_collection_start_enum: STRING

• node: STRING

• number_of_collections: INTEGER

• object_name: STRING

• object_status: INTEGER

• object_status_enum: STRING

• object_type: INTEGER

• object_type_enum: STRING

• query_name: STRING

• refresh_interval: INTEGER


For events that are generated by situations in the Pig attribute group, events are sent by using theITM_KH8_PIG event class. This event class contains the following slots:

• node: STRING























• state: STRING






For events that are generated by situations in the Queue Metrics attribute group, events are sent by usingthe ITM_KH8_QUEUEMETRICS event class. This event class contains the following slots:

• node: STRING


• activeapplications: REAL

• activeapplications_enum: STRING

• activeusers: INTEGER

• activeusers_enum: STRING

• aggregatecontainersallocated: REAL

• aggregatecontainersallocated_enum: STRING

• aggregatecontainersreleased: REAL

• aggregatecontainersreleased_enum: STRING

• allocatedcontainers: REAL

• allocatedcontainers_enum: STRING

• allocatedmemorypercent: INTEGER

• allocatedmemorypercent_enum: STRING

Event mapping 265

• allocatedspacemb: REAL

• allocatedspacemb_enum: STRING

• allocatedvcores: INTEGER

• allocatedvcores_enum: STRING

• applicationscompleted: REAL

• applicationscompleted_enum: STRING

• applicationsfailed: REAL

• applicationsfailed_enum: STRING

• applicationskilled: REAL

• applicationskilled_enum: STRING

• applicationspending: REAL

• applicationspending_enum: STRING

• applicationsrunning: REAL

• applicationsrunning_enum: STRING

• applicationssubmitted: REAL

• applicationssubmitted_enum: STRING

• availablespacemb: REAL

• availablespacemb_enum: STRING

• availablevcores: INTEGER

• availablevcores_enum: STRING


• context: STRING

• failedapplicationspercent: INTEGER

• failedapplicationspercent_enum: STRING

• fairsharemb: REAL

• fairsharemb_enum: STRING

• fairsharevcores: REAL

• fairsharevcores_enum: STRING


• killedapplicationspercent: INTEGER

• killedapplicationspercent_enum: STRING

• maximumsharemb: REAL

• maximumsharemb_enum: STRING

• maximumsharevcores: REAL

• maximumsharevcores_enum: STRING

• minimumsharemb: REAL

• minimumsharemb_enum: STRING

• minimumsharevcores: REAL

• minimumsharevcores_enum: STRING


• pendingcontainers: REAL

• pendingcontainers_enum: STRING

• pendingspacemb: REAL

• pendingspacemb_enum: STRING

• pendingvcores: REAL

• pendingvcores_enum: STRING

• queuename: STRING

• reservedcontainers: REAL

• reservedcontainers_enum: STRING

• reservedspacemb: REAL

• reservedspacemb_enum: STRING

• reservedvcores: REAL

• reservedvcores_enum: STRING

• running_0: REAL

• running_0_enum: STRING

• running_1440: REAL






• shortqueuename: STRING

• user: STRING

For events that are generated by situations in the Ranger attribute group, events are sent by using theITM_KH8_RANGER event class. This event class contains the following slots:

• node: STRING














Event mapping 267









• state: STRING






For events that are generated by situations in the Roles attribute group, events are sent by using theITM_KH8_ROLES event class. This event class contains the following slots:

• node: STRING


• daemon: STRING


For events that are generated by situations in the RPC attribute group, events are sent by using theITM_KH8_RPC event class. This event class contains the following slots:

• node: STRING


• callqueuelength: REAL

• callqueuelength_enum: STRING


• context: STRING

• ip_address: STRING


• openconnections: REAL

• openconnections_enum: STRING

• port: INTEGER

• port_enum: STRING

• receivedbytes: REAL

• receivedbytesmb: REAL

• receivedbytesmb_enum: STRING

• receivedbytes_enum: STRING

• rpcauthenticationfailures: REAL


• rpcauthenticationfailures_enum: STRING

• rpcauthenticationsuccesses: REAL

• rpcauthenticationsuccesses_enum: STRING

• rpcauthorizationfailures: REAL

• rpcauthorizationfailures_enum: STRING

• rpcauthorizationsuccesses: REAL

• rpcauthorizationsuccesses_enum: STRING

• rpcprocessingaveragetime_m: REAL

• rpcprocessingaveragetime_ms: REAL

• rpcprocessingaveragetime_ms_enum: STRING

• rpcprocessingaveragetime_m_enum: STRING

• rpcprocessingtime_ms: REAL

• rpcprocessingtime_ms_enum: STRING

• rpcqueueaveragetime_m: REAL

• rpcqueueaveragetime_ms: REAL

• rpcqueueaveragetime_ms_enum: STRING

• rpcqueueaveragetime_m_enum: STRING

• rpcqueuetime_ms: REAL

• rpcqueuetime_ms_enum: STRING

• sentbytes: REAL

• sentbytesmb: REAL

• sentbytesmb_enum: STRING

• sentbytes_enum: STRING

For events that are generated by situations in the Schema Registry attribute group, events are sent byusing the ITM_KH8_SCHEMAREGISTRY event class. This event class contains the following slots:

• node: STRING














Event mapping 269









• state: STRING






For events that are generated by situations in the Services Overview attribute group, events are sent byusing the ITM_KH8_SERVICESOVERVIEW event class. This event class contains the following slots:

• node: STRING


• servicename: STRING

• servicestatus: STRING

For events that are generated by situations in the Slider attribute group, events are sent by using theITM_KH8_SLIDER event class. This event class contains the following slots:

• node: STRING























• state: STRING






For events that are generated by situations in the SmartSense attribute group, events are sent by usingthe ITM_KH8_SMARTSENSE event class. This event class contains the following slots:

• node: STRING






















• state: STRING




Event mapping 271



For events that are generated by situations in the Solr attribute group, events are sent by using theITM_KH8_SOLR event class. This event class contains the following slots:

• node: STRING






















• state: STRING






For events that are generated by situations in the Spark attribute group, events are sent by using theITM_KH8_SPARK event class. This event class contains the following slots:

• node: STRING























• state: STRING






For events that are generated by situations in the Sqoop attribute group, events are sent by using theITM_KH8_SQOOP event class. This event class contains the following slots:

• node: STRING














Event mapping 273









• state: STRING






For events that are generated by situations in the Startup Progress attribute group, events are sent byusing the ITM_KH8_STARTUPPROGRESS event class. This event class contains the following slots:


• elapsedtime_ms: REAL

• elapsedtime_ms_enum: STRING


• loadingeditscount: REAL

• loadingeditscount_enum: STRING

• loadingeditselapsedtime_ms: REAL

• loadingeditselapsedtime_ms_enum: STRING

• loadingeditspercentcomplete: REAL

• loadingeditspercentcomplete_enum: STRING

• loadingeditstotal: REAL

• loadingeditstotal_enum: STRING

• loadingfilesystemimagecount: REAL

• loadingfilesystemimagecount_enum: STRING

• loadingfilesystemimageelapsedtime_ms: REAL

• loadingfilesystemimageelapsedtime_ms_enum: STRING

• loadingfilesystemimagepercentcomplete: REAL

• loadingfilesystemimagepercentcomplete_enum: STRING

• loadingfilesystemimagetotal: REAL

• loadingfilesystemimagetotal_enum: STRING

• node: STRING

• percentcomplete: REAL

• percentcomplete_enum: STRING


• safemodecount: REAL

• safemodecount_enum: STRING

• safemodeelapsedtime_ms: REAL

• safemodeelapsedtime_ms_enum: STRING

• safemodepercentcomplete: REAL

• safemodepercentcomplete_enum: STRING

• safemodetotal: REAL

• safemodetotal_enum: STRING

• savingcheckpointcount: REAL

• savingcheckpointcount_enum: STRING

• savingcheckpointelapsedtime_ms: REAL

• savingcheckpointelapsedtime_ms_enum: STRING

• savingcheckpointpercentcomplete: REAL

• savingcheckpointpercentcomplete_enum: STRING

• savingcheckpointtotal: REAL

• savingcheckpointtotal_enum: STRING


For events that are generated by situations in the Streaming Analytics Manager attribute group, events aresent by using the ITM_KH8_STREAMINGANALYTICSMANAGER event class. This event class contains thefollowing slots:

• node: STRING



















Event mapping 275




• state: STRING






For events that are generated by situations in the Superset attribute group, events are sent by using theITM_KH8_SUPERSET event class. This event class contains the following slots:

• node: STRING






















• state: STRING







For events that are generated by situations in the Take Action Status attribute group, events are sent byusing the ITM_KH8_TAKE_ACTION_STATUS event class. This event class contains the following slots:

• action_app_return_code: INTEGER

• action_command: STRING

• action_id: INTEGER

• action_instance: STRING

• action_message: STRING

• action_name: STRING

• action_node: STRING

• action_owner: STRING

• action_results: STRING

• action_status: INTEGER

• action_status_enum: STRING

• action_subnode: STRING

• action_type: INTEGER

• action_type_enum: STRING

• node: STRING


For events that are generated by situations in the Tez attribute group, events are sent by using theITM_KH8_TEZ event class. This event class contains the following slots:

• node: STRING



















Event mapping 277




• state: STRING






For events that are generated by situations in the Thread Pool Status attribute group, events are sent byusing the ITM_KH8_THREAD_POOL_STATUS event class. This event class contains the following slots:

• node: STRING

• thread_pool_active_threads: INTEGER

• thread_pool_active_threads_enum: STRING

• thread_pool_avg_active_threads: REAL

• thread_pool_avg_active_threads_enum: STRING

• thread_pool_avg_job_wait: REAL

• thread_pool_avg_job_wait_enum: STRING

• thread_pool_avg_queue_length: REAL

• thread_pool_avg_queue_length_enum: STRING

• thread_pool_max_active_threads: INTEGER

• thread_pool_max_active_threads_enum: STRING

• thread_pool_max_queue_length: INTEGER

• thread_pool_max_queue_length_enum: STRING

• thread_pool_max_size: INTEGER

• thread_pool_max_size_enum: STRING

• thread_pool_min_active_threads: INTEGER

• thread_pool_min_active_threads_enum: STRING

• thread_pool_min_queue_length: INTEGER

• thread_pool_min_queue_length_enum: STRING

• thread_pool_queue_length: INTEGER

• thread_pool_queue_length_enum: STRING

• thread_pool_size: INTEGER

• thread_pool_size_enum: STRING

• thread_pool_total_jobs: INTEGER

• thread_pool_total_jobs_enum: STRING


For events that are generated by situations in the Titan attribute group, events are sent by using theITM_KH8_TITAN event class. This event class contains the following slots:


• node: STRING






















• state: STRING






For events that are generated by situations in the UGI Metrics attribute group, events are sent by usingthe ITM_KH8_UGIMETRICS event class. This event class contains the following slots:


• context: STRING

• groupaveragetime_ms: REAL

• groupaveragetime_ms_enum: STRING

• groupoperations: REAL

• groupoperations_enum: STRING


• loginfailureaveragetime_ms: REAL

• loginfailureaveragetime_ms_enum: STRING

Event mapping 279

• loginfailurenumberofoperations: INTEGER

• loginfailurenumberofoperations_enum: STRING

• loginsuccess: INTEGER

• loginsuccessaveragetime_ms: REAL

• loginsuccessaveragetime_ms_enum: STRING

• loginsuccess_enum: STRING

• node: STRING

• servicename: STRING


For events that are generated by situations in the Unified Console attribute group, events are sent byusing the ITM_KH8_UNIFIEDCONSOLE event class. This event class contains the following slots:

• node: STRING






















• state: STRING







For events that are generated by situations in the YARN attribute group, events are sent by using theITM_KH8_YARN event class. This event class contains the following slots:

• node: STRING






















• state: STRING






For events that are generated by situations in the ZooKeeper attribute group, events are sent by using theITM_KH8_ZOOKEEPER event class. This event class contains the following slots:

• node: STRING







Event mapping 281
















• state: STRING







Appendix A. Documentation library

A variety of documentation is available for insert the short product name from the list.

IBM Knowledge Center contains topics of information for the product and links to relevant PDFs. In IBMKnowledge Center, you can create a custom PDF that contains only the topics in which you are interested.See the directions for Creating your own set of topics (http://www.ibm.com/support/knowledgecenter/doc/kc_help.html#create).

The following topics for this product are in IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter):

• Quick Start Guide• Product overview• Planning for installation• Downloading• Installing and configuring for each component• Using and reference for the dashboards, reporting, and capacity planning components• Link to a Troubleshooting Guide for each component and support information• Link to a Reference for each agent

Prerequisite documentationTo use the information about the components effectively, you must have some prerequisite knowledge.

The following information for Tivoli Monitoring is available in the IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter) to gain prerequisite knowledge:

• IBM Tivoli Monitoring Administrator's Guide• IBM Tivoli Monitoring Installation and Setup Guide• IBM Tivoli Monitoring High Availability Guide for Distributed Systems• IBM Tivoli Monitoring: Installation and Configuration Guides for the following agents: Operating System

agents and Warehouse agents• IBM Tivoli Monitoring: User's Guides for the following agents: Agentless OS monitors, Log File agent,

System p agents, Systems Director base agent• IBM Tivoli Monitoring Agent Builder User's Guide• IBM Tivoli Monitoring Command Reference• IBM Tivoli Monitoring: Messages• IBM Tivoli Monitoring Troubleshooting Guide• IBM Tivoli Monitoring: References for the following agents: Operating System agents and Warehouse

agents• IBM Tivoli Monitoring: Troubleshooting Guides for the following agents: Operating System agents and

Warehouse agents• Tivoli Enterprise Portal User's Guide

Other information

• Schneider Electric documentation about how to install the Andover Continuum web service before youuse the Schneider Electric Andover Continuum agent


http://www-01.ibm.com/support/knowledgecenter/doc/kc_help.html#create

http://www.ibm.com/support/knowledgecenter

http://www.ibm.com/support/knowledgecenter

Related documentationThe documentation for related products provides useful information.

See the following products in IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter/):

• Tivoli Monitoring• Tivoli Application Dependency Discovery Manager• Tivoli Business Service Manager• Tivoli Common Reporting• Tivoli Enterprise Console• Tivoli Netcool/OMNIbus

Terminology that is relevant to IBM products is consolidated in one convenient locations at the IBMTerminology website (http://www.ibm.com/software/globalization/terminology).

Tivoli Monitoring Community on Service Management ConnectService Management Connect (SMC) is a repository of technical information that is organized bycommunities.

Access Service Management Connect at https://www.ibm.com/developerworks/servicemanagement.

For information about Tivoli products, see the Application Performance Management community (http://www.ibm.com/developerworks/servicemanagement/apm/index.html).

Connect, learn, and share with Service Management professionals. Get access to developers and productsupport technical experts who provide their perspectives and expertise. You can use SMC for thesepurposes:

• Become involved with transparent development, an ongoing, open engagement between other usersand IBM developers of Tivoli products. You can access early designs, sprint demonstrations, productroadmaps, and prerelease code.

• Connect one-on-one with the experts to collaborate and network about Tivoli and the ApplicationPerformance Management community.

• Read blogs to benefit from the expertise and experience of others.• Use wikis and forums to collaborate with the broader user community.

Other sources of documentationYou can obtain additional technical documentation about monitoring products from other sources.

See the following sources of technical documentation about monitoring products:

• IBM Integrated Service Management Library (http://www.ibm.com/software/brandcatalog/ismlibrary/)is an online catalog that contains integration documentation as well as other downloadable productextensions.

• IBM Redbook publications (http://www.redbooks.ibm.com/) include Redbooks® publications,Redpapers, and Redbooks technotes that provide information about products from platform andsolution perspectives.

• Technotes (http://www.ibm.com/support/entry/portal/software), which are found through the IBMSoftware Support website, provide the latest information about known product limitations andworkarounds.


ttp://www.ibm.com/software/globalization/terminology

ttp://www.ibm.com/software/globalization/terminology

https://www.ibm.com/developerworks/servicemanagement

http://www.ibm.com/developerworks/servicemanagement/apm/index.html

http://www.ibm.com/software/brandcatalog/ismlibrary/

http://www.redbooks.ibm.com/

http://www.ibm.com/support/entry/portal/software

Conventions used in the documentationSeveral conventions are used in the documentation for special terms, actions, commands, and paths thatare dependent on your operating system.

Typeface conventions

The following typeface conventions are used in the documentation:Bold

• Lowercase commands, mixed-case commands, parameters, and environment variables that areotherwise difficult to distinguish from the surrounding text

• Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons,list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs,property sheets), labels (such as Tip:)

• Keywords and parameters in text

Italic

• Citations (examples: titles of publications, CDs, and DVDs)• Words and phrases defined in text (example: a nonswitched line is called a point-to-point line)• Emphasis of words and letters (example: The LUN address must start with the letter L.)• New terms in text , except in a definition list (example: a view is a frame in a workspace that

contains data.)• Variables and values you must provide (example: where myname represents…)

Monospace

• Examples and code examples• File names, directory names, path names, programming keywords, properties, and other elements

that are difficult to distinguish from the surrounding text• Message text and prompts• Text that you must type• Values for arguments or command options

Bold monospace

• Command names, and names of macros and utilities that you can type as commands• Environment variable names in text• Keywords• Parameter names in text: API structure parameters, command parameters and arguments, and

configuration parameters• Process names• Registry variable names in text• Script names

Operating system-dependent variables and paths

The direction of the slash for directory paths might vary in the documentation. Regardless of what you seein the documentation, follow these guidelines:

• For UNIX or Linux, use a forward slash (/).• For Windows, use a backslash (\).

The names of environment variables are not always the same in Windows and UNIX. For example, %TEMP% in Windows is equivalent to $TMPDIR in UNIX or Linux.

Documentation library 285

For environment variables, follow these guidelines:

• For UNIX or Linux, use $variable.• For Windows, use %variable%.

If you are using the bash shell on a Windows system, you can use the UNIX conventions.


Accessibility features

Accessibility features assist users who have a disability, such as restricted mobility or limited vision, touse information technology content successfully.

Accessibility features

The web-based interface of IBM Cloud Application Performance Management is the Cloud APM console.The console includes the following major accessibility features:

• Enables users to use assistive technologies, such as screen-reader software and digital speechsynthesizer, to hear what is displayed on the screen.1 Consult the product documentation of theassistive technology for details on using those technologies with this product.

• Enables users to operate specific or equivalent features using only the keyboard.• Communicates all information independently of color.2

The Cloud APM console uses the latest W3C Standard, WAI-ARIA 1.0, US Section 508, and Web ContentAccessibility Guidelines (WCAG) 2.0. To take advantage of accessibility features, use the latest release ofyour screen reader in combination with the latest web browser that is supported by this product.

The Cloud APM console online product documentation in IBM Knowledge Center is enabled foraccessibility. The accessibility features of IBM Knowledge Center are described at IBM Knowledge Centerrelease notes.

Keyboard navigation

This product uses standard navigation keys.

Interface information

The Cloud APM console web user interface does not rely on cascading style sheets to render contentproperly and to provide a usable experience. However, the product documentation does rely on cascadingstyle sheets. IBM Knowledge Center provides an equivalent way for low-vision users to use their customdisplay settings, including high-contrast mode. You can control font size by using the device or browsersettings.

The Cloud APM console web user interface includes WAI-ARIA navigational landmarks that you can use toquickly navigate to functional areas in the application.

The Cloud APM console user interface does not have content that flashes 2 - 55 times per second.

Related accessibility information

In addition to standard IBM help desk and support websites, IBM has established a TTY telephoneservice for use by deaf or hard of hearing customers to access sales and support services:

TTY service 800-IBM-3383 (800-426-3383) (within North America)

IBM and accessibility

For more information about the commitment that IBM has to accessibility, see IBM Accessibility .

1 Exceptions include some of the Agent Configuration pages and historical line charts in the Cloud APMconsole.

2 Exceptions include some Agent Configuration pages of the Cloud APM console.


http://www.w3.org/TR/wai-aria/

http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards

http://www.w3.org/TR/WCAG20/

http://www.w3.org/TR/WCAG20/

http://www.ibm.com/support/knowledgecenter/en/about/releasenotes.html?view=kc#accessibility

http://www.ibm.com/support/knowledgecenter/en/about/releasenotes.html?view=kc#accessibility

http://www.ibm.com/able


Notices

This information was developed for products and services offered in the US. This material might beavailable from IBM in other languages. However, you may be required to own a copy of the product orproduct version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currently availablein your area. Any reference to an IBM product, program, or service is not intended to state or imply thatonly that IBM product, program, or service may be used. Any functionally equivalent product, program, orservice that does not infringe any IBM intellectual property right may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.The furnishing of this document does not grant you any license to these patents. You can send licenseinquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate withoutincurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US


Such information may be available, subject to appropriate terms and conditions, including in some cases,payment of a fee.

The licensed program described in this document and all licensed material available for it are provided byIBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or anyequivalent agreement between us.

The performance data discussed herein is presented as derived under specific operating conditions.Actual results may vary.

The client examples cited are presented for illustrative purposes only. Actual performance results mayvary depending on specific configurations and operating conditions.

The performance data and client examples cited are presented for illustrative purposes only. Actualperformance results may vary depending on specific configurations and operating conditions.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those productsand cannot confirm the accuracy of performance, compatibility or any other claims related tonon-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change withoutnotice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to actual people or business enterprises isentirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platformfor which the sample programs are written. These examples have not been thoroughly tested underall conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative workmust include a copyrightnotice as follows:© (your company name) (year).Portions of this code are derived from IBM Corp. Sample Programs.© Copyright IBM Corp. 2014, 2015.

Programming interface information

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might


be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks ortrademarks of Adobe Systems Incorporated in the United States, other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer and TelecommunicationsAgency which is now part of the Office of Government Commerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon,Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation orits subsidiaries in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of The Minister for the CabinetOffice, and is registered in the U.S. Patent and Trademark Office.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, othercountries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. andQuantum in the U.S. and other countries.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the following terms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBM website.

Personal use

You may reproduce these publications for your personal, noncommercial use provided that all proprietarynotices are preserved. You may not distribute, display or make derivative work of these publications, orany portion thereof, without the express consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within your enterprise providedthat all proprietary notices are preserved. You may not make derivative works of these publications, orreproduce, distribute or display these publications or any portion thereof outside your enterprise, withoutthe express consent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, eitherexpress or implied, to the publications or any information, data, software or other intellectual propertycontained therein.

Notices 291

http://www.ibm.com/legal/us/en/copytrade.shtml

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the useof the publications is detrimental to its interest or, as determined by IBM, the above instructions are notbeing properly followed.

You may not download, export or re-export this information except in full compliance with all applicablelaws and regulations, including all United States export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONSARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT,AND FITNESS FOR A PARTICULAR PURPOSE.

IBM Online Privacy StatementIBM Software products, including software as a service solutions, ("Software Offerings") may use cookiesor other technologies to collect product usage information, to help improve the end user experience,to tailor interactions with the end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offerings can help enable youto collect personally identifiable information. If this Software Offering uses cookies to collect personallyidentifiable information, specific information about this offering's use of cookies is set forth in thefollowing paragraphs.

Depending upon the configurations deployed, this Software Offering may use session cookies thatcollect each user's user name for purposes of session management, authentication, and single sign-onconfiguration. These cookies can be disabled, but disabling them will also likely eliminate the functionalitythey enable.

If the configurations deployed for this Software Offering provide you as customer the ability to collectpersonally identifiable information from end users via cookies and other technologies, you should seekyour own legal advice about any laws applicable to such data collection, including any requirements fornotice and consent.

For more information about the use of various technologies, including cookies, for these purposes,See IBM's Privacy Policy at http://www.ibm.com/privacy and IBM's Online Privacy Statement at http://www.ibm.com/privacy/details the section entitled "Cookies, Web Beacons and Other Technologies" andthe "IBM Software Products and Software-as-a-Service Privacy Statement" at http://www.ibm.com/software/info/product-privacy.

Safety and environmental notices


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

http://www.ibm.com/software/info/product-privacy

Index

Aaccessibility features 287Action App Return Code attribute 202Action Command attribute 202Action ID attribute 202Action Instance attribute 202Action Message attribute 202Action Name attribute 202Action Node attribute 203Action Owner attribute 203Action Results attribute 203Action Status attribute 203Action Subnode attribute 203Action Type attribute 203Active Applications attribute 158Active NodeManagers attribute 59Active Users attribute 158activities 237Add Block attribute 127Additional DataNode attribute 127additional information

attributes 43situations 231Take Action commands 235Workspaces 227

Aggregate Containers Allocated attribute 158Aggregate Containers Released attribute 158Allocated Containers attribute 141, 159Allocated Memory Percent attribute 159Allocated Space MB attribute 155Allocated Virtual Cores attribute 159Allow Snapshot attribute 127Ambari Metrics data set 48Application Performance Management community on SMC284Applications Completed attribute 155Applications Failed attribute 63, 155Applications Killed attribute 155Applications Pending attribute 156Applications Running attribute 156Applications Submitted attribute 156Atlas data set 52attribute groups

overview 43attributes

Action App Return Code 202Action Command 202Action ID 202Action Instance 202Action Message 202Action Name 202Action Node 203Action Owner 203Action Results 203Action Status 203Action Subnode 203

Action Type 203Active Applications 158Active NodeManagers 59Active Users 158Add Block 127Additional DataNode 127Aggregate Containers Allocated 158Aggregate Containers Released 158Allocated Containers 141, 159Allocated Memory Percent 159Allocated Space MB 155Allocated Virtual Cores 159Allow Snapshot 127Ambari Metrics 48Applications Completed 155Applications Failed 63, 155Applications Killed 155Applications Pending 156Applications Running 156Applications Submitted 156Atlas 52Authentication Failures 166Authentication Successes 166Authorization Failures 166Authorization Successes 167Available Space GB 141Available Space MB 156Available Virtual Cores 159AvailableProcessors 147Average Collection Duration 102, 148Average MemoryHeapUsed Percent 63Big SQL 55Block Capacity 86Block Capacity MB 85Block Checksum Average Time ms 70Block Checksum Operations 70Block Locations 127Block Received Deleted 127Block Report Average Time ms 127Block Report Operations 128Block Reports Average Time ms 70Block Reports Operations 70Block Verification Failures 67Blocks Cached 70Blocks Local Path Information 71Blocks Read 67Blocks Removed 67Blocks Replicated 67Blocks Total 86Blocks Uncached 71Blocks Verified 67Blocks Written 67Bytes Read (Rate) 68Bytes ReadMB 68Bytes Written (Rate) 68Bytes WrittenMB 68Cache Hit Percent 102, 148

293

Cache Hits 103, 148Cache Misses 103, 149Cache Report 71, 128Cache Report Average Time 128Cache Report Average Time ms 71Call Queue Length 169Capacity Remaining Bytes 89Capacity Remaining in GB 89Capacity Total Bytes 89Capacity Total GB 63, 89Capacity Used Bytes 89Capacity Used GB 63, 90Capacity Used NonDFS Bytes 90Capacity Used NonDFS GB 90Capacity Used Percent 64, 86Cluster ID 62, 64Cluster Metrics 59, 59Cluster Name 49, 53, 56, 76, 80, 83, 93, 96, 100, 114,117, 121, 124, 135, 139, 144, 153, 163, 171, 175,179, 182, 186, 189, 196, 199, 205, 211, 217, 220, 223Cluster Overview 60ClusterDetails 63Collect Timestamp 59, 68, 86, 110, 128, 141, 147, 159,169, 191, 213Component Name 48, 52, 55, 75, 79, 82, 92, 95, 99,113, 116, 120, 123, 134, 138, 143, 152, 162, 170,174, 178, 181, 184, 188, 195, 198, 204, 210, 215,219, 222Containers Allocated Space GB 142Containers Completed 142Containers Failed 64, 142Containers Initiated 142Containers Killed 142Containers Launched 142Containers Running 142Context 59, 71, 90, 111, 128, 143, 159, 169, 214Copy Block Operation Average Time ms 71Copy Block Operations 72Corrupt Blocks 86Corrupt Blocks Percent 90Count of Active Node Managers 64Count of Dead Datanodes 64Count of Decommissioned Node Managers 64Count of Live Datanodes 65Count of Lost Node Managers 65Count of Nodes 65Count of Rebooted Node Managers 65Count of Unhealthy Node Managers 65Create File Operations 128Create Snapshot 129Custom Cluster Name 65Daemon 165DataNode 67DataNode Status 61Decommissioned NodeManagers 59Delete Snapshot 129Deleted File 129Desired Stack Id 49, 53, 56, 76, 80, 83, 93, 97, 100,114, 118, 121, 124, 135, 139, 145, 153, 163, 171,175, 179, 182, 186, 189, 196, 200, 205, 211, 217,220, 224Desired State 50, 53, 57, 76, 80, 83, 93, 97, 100, 114,118, 121, 125, 136, 139, 145, 153, 163, 171, 175,179, 182, 186, 189, 196, 200, 205, 211, 217, 220, 224

Disallow Snapshot 129Druid 75Edit Average Time ms 129Edit Operations 129Elapsed Time ms 191Error Code 103, 149Excess Blocks 86Expired Heartbeats 90Failed Applications Percent 160Fair Share MB 160Fair Share Virtual Cores 160Falcon 78File Information 129File Synchronization Count 72File Synchronization Nanos Average Time 72File Synchronization Nanos Operations 72File System Image Load Time ms 130File System Status 61Files Appended 130Files Created 130Files Deleted 130Files Lists 130Files Renamed 130Files Total 86Flume 82Flush Nanos Average Time 72Flush Nanos Operations 72FS Name System 85FsImage Download Average Time ms 131FsImage Download Count 131FsImage Upload Average Time ms 131FsImage Upload Count 131Garbage Collection Count 111Garbage Collection Count Mark Sweep 111Garbage Collection Count Scavenge 111Garbage Collection Information Threshold 111Garbage Collection Rate 107Garbage Collection Sleep Time ms 111Garbage Collection Time Mark Sweep 112Garbage Collection Time ms 112Garbage Collection Time Scavenge ms 112Garbage Collection Warning Threshold 107Group Average Time ms 214Group Operations 214Ha State 65Has State 87HBase 92HDFS 95HDP Version 50, 53, 57, 77, 80, 83, 93, 97, 100, 114,118, 121, 125, 136, 139, 145, 153, 163, 171, 176,179, 183, 186, 189, 196, 200, 205, 212, 217, 220, 224Heartbeats Average Time ms (Rate) 68Heartbeats Operations 68Hive 99HOS Performance Object Status 102Hostname 48, 52, 55, 59, 61, 69, 75, 79, 82, 87, 92,96, 99, 107, 113, 117, 120, 123, 131, 134, 138, 143,144, 147, 152, 156, 162, 166, 167, 170, 174, 178,181, 185, 188, 192, 195, 199, 204, 210, 214, 216,219, 223Hosts nodes 106Init Count in Cluster 50, 53, 57, 77, 80, 84, 94, 97, 100,115, 118, 121, 125, 136, 139, 145, 153, 164, 172,

294

176, 179, 183, 186, 190, 197, 200, 206, 212, 217,221, 224Install failed Count in Cluster 50, 54, 57, 77, 80, 84, 94,97, 101, 115, 118, 122, 125, 136, 140, 145, 153, 164,172, 176, 179, 183, 186, 190, 197, 200, 206, 212,217, 221, 224Installed Count in Cluster 50, 54, 57, 77, 81, 84, 94,97, 101, 115, 118, 122, 125, 136, 140, 145, 154, 164,172, 176, 180, 183, 186, 190, 197, 200, 206, 212,217, 221, 224Intervals Skipped 104, 149IP Address 61, 170Java Virtual Machine Status 61JVM Metrics 107Kafka 113Killed Applications Percent 160Knox 116Last Checkpoint Time ms 90Last Collection Duration 104, 150Last Collection Finished 104, 150Last Collection Start 104, 150Last Loaded Edits 91Last Written Transaction Id 87Link Target 131Links Created 131List Snapshottable Directories 132Lists 132Loading Edits Count 192Loading Edits Elapsed Time ms 192Loading Edits Percent Complete 192Loading Edits Total 192Loading File System Image Count 192Loading File System Image Elapsed Time ms 193Loading File System Image Percent Complete 193Loading File System Image Total 193Login Failure Average Time ms 214Login Failure Number Of Operations 214Login Success 215Login Success Average Time ms 215Logs Error 107Logs Fatal 108Logs Information 112Logs Warn 108Lost NodeManagers 60Mahout 120Maintenance State 49, 52, 56, 75, 79, 82, 92, 96, 99,113, 117, 120, 124, 135, 138, 144, 152, 162, 170,174, 178, 181, 185, 188, 195, 199, 204, 210, 216,219, 223MapReduce2 123Maximum Share MB 160Maximum Share Virtual Cores 161Memory Heap Used Percent 108Memory HeapCommitted MB 108Memory HeapMaximum MB 112Memory HeapUsed MB 108Memory Maximum MB 108Memory NonHeap Committed MB 109Memory NonHeap Free MB 109Memory NonHeap Maximum MB 112Memory NonHeap Used MB 109Minimum Share MB 161Minimum Share Virtual Cores 161Missing Blocks 66, 87

Missing Blocks Percent 91NameNode 127Namenode uptime 66NiFi 134NiFi Registry 138Node 49, 52, 56, 60, 61, 66, 69, 76, 79, 82, 87, 92, 96,99, 104, 106, 109, 113, 117, 120, 124, 132, 135, 138,143, 144, 147, 150, 152, 156, 162, 166, 167, 170,173, 175, 178, 182, 185, 188, 193, 195, 199, 203,204, 207, 211, 215, 216, 219, 223Node FQDN 62NodeManager Metrics 141Number of Collections 104, 150Object Name 105, 150Object Status 105, 151Object Type 105, 151Oozie 143Open Connections 167Operating System 147Other Count in Cluster 50, 54, 57, 77, 81, 84, 94, 98,101, 115, 119, 122, 125, 136, 140, 146, 154, 164,172, 176, 180, 183, 187, 190, 197, 201, 206, 212,218, 221, 225overview 43Packet Round Trip Nanos Operations 73Packet Round Trip Time Nanos Average Time 73Pending Containers 161Pending DataNode Message Count 91Pending Deletion Blocks 87Pending Replication Blocks 87Pending Space MB 156Pending Virtual Cores 161Percent Complete 193Performance Object Status 148Pig 151Port 63, 167Postponed Misreplicated Blocks 88Process CPULoad Percentage 66Process Name 109, 132ProcessCPULoad 147Processed Requests Count 167Processing Average Time in minutes 168Processing Average Time ms 168Query Name 105, 151Queue Average Time in minutes 168Queue Average Time ms 168Queue Metrics 155Queue Name 157Queue Status 62Queued Requests Count 168Ranger 162Read Block Operation 73Read Block Operation Average Time ms 73Reads From Local Client (Rate) 69Reads From Remote Client (Rate) 69Rebooted NodeManagers 60Received Bytes 168Received Data MB 169Refresh Interval 105, 151Remote Procedure Call Status 62Rename Snapshot 132Replace Block Average Time ms 73Replace Block Operations 73Reserved Containers 161

295

Reserved Space MB 157Reserved Virtual Cores 162Roles 165RPC 166Running 0 157Running 1440 157Running 300 157Running 60 157Safe Mode Time ms 132SafeMode Count 193SafeMode Elapsed Time ms 194SafeMode Percent Complete 194SafeMode Total 194Saving Checkpoint Count 194Saving Checkpoint Elapsed Time ms 194Saving Checkpoint Percent Complete 194Saving Checkpoint Total 194Scheduled Replication Blocks 88Schema Registry 170Send DataPacket Blocked On Network Nanos AverageTime 74Send DataPacket Blocked On Network NanosOperations 74Send DataPacket Transfer Nanos Average Time 74Send DataPacket Transfer Nanos Operations 74Sent Bytes 169Sent Data MB 169Service Name 49, 52, 56, 76, 79, 83, 93, 96, 99, 114,117, 120, 124, 135, 138, 144, 152, 163, 171, 173,175, 178, 182, 185, 189, 196, 199, 205, 211, 216,220, 223Service Status 174ServiceName 215Services Overview 173Session Id 74, 113, 133Short Queue Name 158Slider 174SmartSense 177Snapshot Report 133Snapshots 91Snapshottable Directories 91Solr 181Spark 184Sqoop 188Stack Id 51, 54, 58, 77, 81, 84, 94, 98, 101, 115, 119,122, 126, 137, 140, 146, 154, 164, 172, 176, 180,183, 187, 190, 197, 201, 206, 212, 218, 221, 225Stale Configs 51, 54, 58, 78, 81, 84, 94, 98, 101, 115,119, 122, 126, 137, 140, 146, 154, 164, 172, 177,180, 184, 187, 190, 197, 201, 206, 213, 218, 221, 225Stale DataNodes 91Started Count in Cluster 51, 54, 58, 78, 81, 85, 95, 98,101, 116, 119, 122, 126, 137, 140, 146, 154, 165,173, 177, 180, 184, 187, 191, 198, 201, 207, 213,218, 222, 225Startup Progress 191State 49, 52, 56, 76, 79, 83, 93, 96, 100, 114, 117,121, 124, 135, 138, 144, 152, 163, 171, 175, 178,182, 185, 189, 196, 199, 205, 211, 216, 220, 223Storage Block Report 133Streaming Analytics Manager 195Subnode Affinity 106Subnode Host 62Subnode MSN 106

Subnode Resource Name 106Subnode Type 106Subnode Version 106Superset 198Synchronization Average Time ms 133Synchronization Operations 133SystemCpuLoad 148Take Action Status 202Tez 204Thread Pool Active Threads 207Thread Pool Avg Active Threads 208Thread Pool Avg Job Wait 208Thread Pool Avg Queue Length 208Thread Pool Max Active Threads 208Thread Pool Max Queue Length 208Thread Pool Max Size 209Thread Pool Min Active Threads 209Thread Pool Min Queue Length 209Thread Pool Queue Length 209Thread Pool Size 209Thread Pool Status 207Thread Pool Total Jobs 210Threads Blocked 109Threads New 109Threads Runnable 110Threads Terminated 110Threads Timed Waiting 110Threads Waiting 110Timestamp 49, 53, 56, 60, 62, 66, 69, 76, 79, 83, 88,93, 96, 100, 105, 107, 110, 114, 117, 121, 124, 133,135, 139, 143, 144, 148, 151, 152, 158, 163, 166,169, 171, 174, 175, 178, 182, 185, 189, 195, 196,199, 204, 205, 210, 211, 215, 216, 220, 223Titan 210Total Count in Cluster 51, 55, 58, 78, 81, 85, 95, 98,102, 116, 119, 123, 126, 137, 140, 146, 154, 165,173, 177, 180, 184, 187, 191, 198, 201, 207, 213,218, 222, 225Total Disk failures 66Total Files 88Total Load 92Transactions 134Transactions Average Time ms 134Transactions Batched In Synchronization 134Transactions Since Last Checkpoint 88Transactions Since Last Rollback 88UGI Metrics 213UnderReplicated Blocks 89Unhealthy NodeManagers 60Unified Console 215Unknown Count in Cluster 51, 55, 58, 78, 81, 85, 95,98, 102, 116, 119, 123, 126, 137, 141, 146, 154, 165,173, 177, 181, 184, 187, 191, 198, 201, 207, 213,218, 222, 225Upgrade State 51, 55, 58, 78, 82, 85, 95, 98, 102, 116,119, 123, 126, 137, 141, 146, 155, 165, 173, 177,181, 184, 188, 191, 198, 201, 207, 213, 219, 222, 225User 158Volume Failures 69Write Block Average Time ms 75Write Block Operations 75Writes From Local Client (Rate) 69Writes From Remote Client (Rate) 70YARN 219

296

ZooKeeper 222Authentication Failures attribute 166Authentication Successes attribute 166Authorization Failures attribute 166Authorization Successes attribute 167Available Space GB attribute 141Available Space MB attribute 156Available Virtual Cores attribute 159AvailableProcessors attribute 147Average Collection Duration attribute 102, 148Average MemoryHeapUsed Percent attribute 63

BBig SQL data set 55Block Capacity attribute 86Block Capacity MB attribute 85Block Checksum Average Time ms attribute 70Block Checksum Operations attribute 70Block Locations attribute 127Block Received Deleted attribute 127Block Report Average Time ms attribute 127Block Report Operations attribute 128Block Reports Average Time ms attribute 70Block Reports Operations attribute 70Block Verification Failures attribute 67Blocks Cached attribute 70Blocks Local Path Information attribute 71Blocks Read attribute 67Blocks Removed attribute 67Blocks Replicated attribute 67Blocks Total attribute 86Blocks Uncached attribute 71Blocks Verified attribute 67Blocks Written attribute 67Bytes Read (Rate) attribute 68Bytes ReadMB attribute 68Bytes Written (Rate) attribute 68Bytes WrittenMB attribute 68

CCache Hit Percent attribute 102, 148Cache Hits attribute 103, 148Cache Misses attribute 103, 149Cache Report attribute 71, 128Cache Report Average Time attribute 128Cache Report Average Time ms attribute 71Call Queue Length attribute 169Capacity Remaining Bytes attribute 89Capacity Remaining in GB attribute 89Capacity Total Bytes attribute 89Capacity Total GB attribute 63, 89Capacity Used Bytes attribute 89Capacity Used GB attribute 63, 90Capacity Used NonDFS Bytes attribute 90Capacity Used NonDFS GB attribute 90Capacity Used Percent attribute 64, 86Cluster ID attribute 62, 64Cluster Metrics attribute 59Cluster Metrics data set 59

Cluster Name attribute 49, 53, 56, 76, 80, 83, 93, 96, 100,114, 117, 121, 124, 135, 139, 144, 153, 163, 171, 175,179, 182, 186, 189, 196, 199, 205, 211, 217, 220, 223Cluster Overview data set 60ClusterDetails data set 63Collect Timestamp attribute 59, 68, 86, 110, 128, 141, 147,159, 169, 191, 213commands

Take Action 235Component Name attribute 48, 52, 55, 75, 79, 82, 92, 95,99, 113, 116, 120, 123, 134, 138, 143, 152, 162, 170, 174,178, 181, 184, 188, 195, 198, 204, 210, 215, 219, 222Containers Allocated Space GB attribute 142Containers Completed attribute 142Containers Failed attribute 64, 142Containers Initiated attribute 142Containers Killed attribute 142Containers Launched attribute 142Containers Running attribute 142Context attribute 59, 71, 90, 111, 128, 143, 159, 169, 214conventions in documentation 285Copy Block Operation Average Time ms attribute 71Copy Block Operations attribute 72Corrupt Blocks attribute 86Corrupt Blocks Percent attribute 90Count of Active Node Managers attribute 64Count of Dead Datanodes attribute 64Count of Decommissioned Node Managers attribute 64Count of Live Datanodes attribute 65Count of Lost Node Managers attribute 65Count of Nodes attribute 65Count of Rebooted Node Managers attribute 65Count of Unhealthy Node Managers attribute 65Create File Operations attribute 128create PDF 283Create Snapshot attribute 129Custom Cluster Name attribute 65

DDaemon attribute 165dashboard 3data set

attributes 48data sets

Ambari Metrics 48Atlas 52Big SQL 55Cluster Metrics 59Cluster Overview 60ClusterDetails 63DataNode 66Druid 75Falcon 78Flume 82FS Name System 85HBase 92HDFS 95Hive 99HOS Performance Object Status 102Hosts nodes 106JVM Metrics 107Kafka 113Knox 116

297

list of all 44Mahout 120MapReduce2 123NameNode 127NiFi 134NiFi Registry 138NodeManager Metrics 141Oozie 143Operating System 147overview 43Performance Object Status 148Pig 151Queue Metrics 155Ranger 162Roles 165RPC 166Schema Registry 170Services Overview 173Slider 174SmartSense 177Solr 181Spark 184Sqoop 188Startup Progress 191Streaming Analytics Manager 195Superset 198Take Action Status 202Tez 204Thread Pool Status 207Titan 210UGI Metrics 213Unified Console 215YARN 219ZooKeeper 222

DataNode data set 66DataNode Status attribute 61Decommissioned NodeManagers attribute 59Delete Snapshot attribute 129Deleted File attribute 129descriptions 232Desired Stack Id attribute 49, 53, 56, 76, 80, 83, 93, 97,100, 114, 118, 121, 124, 135, 139, 145, 153, 163, 171,175, 179, 182, 186, 189, 196, 200, 205, 211, 217, 220,224Desired State attribute 50, 53, 57, 76, 80, 83, 93, 97, 100,114, 118, 121, 125, 136, 139, 145, 153, 163, 171, 175,179, 182, 186, 189, 196, 200, 205, 211, 217, 220, 224Disallow Snapshot attribute 129documentation

IBM Tivoli Monitoring 283Integrated Service Management Library 284prerequisite 283Redbooks 284related 284Technotes 284

Druid data set 75

EEdit Average Time ms attribute 129Edit Operations attribute 129Elapsed Time ms attribute 191Error Code attribute 103, 149

eventmapping 239

Excess Blocks attribute 86Expired Heartbeats attribute 90

FFailed Applications Percent attribute 160Fair Share MB attribute 160Fair Share Virtual Cores attribute 160Falcon data set 78File Information attribute 129File Synchronization Count attribute 72File Synchronization Nanos Average Time attribute 72File Synchronization Nanos Operations attribute 72File System Image Load Time ms attribute 130File System Status attribute 61Files Appended attribute 130Files Created attribute 130Files Deleted attribute 130Files Lists attribute 130Files Renamed attribute 130Files Total attribute 86Flume data set 82Flush Nanos Average Time attribute 72Flush Nanos Operations attribute 72FS Name System data set 85FsImage Download Average Time ms attribute 131FsImage Download Count attribute 131FsImage Upload Average Time ms attribute 131FsImage Upload Count attribute 131

GGarbage Collection Count attribute 111Garbage Collection Count Mark Sweep attribute 111Garbage Collection Count Scavenge attribute 111Garbage Collection Information Threshold attribute 111Garbage Collection Rate attribute 107Garbage Collection Sleep Time ms attribute 111Garbage Collection Time Mark Sweep attribute 112Garbage Collection Time ms attribute 112Garbage Collection Time Scavenge ms attribute 112Garbage Collection Warning Threshold attribute 107Group Average Time ms attribute 214Group Operations attribute 214

HHa State attribute 65Hadoop

situations 232workspaces

descriptions 228Hadoop Hosts

situations 233, 233workspaces

descriptions 229Hadoop workspace 228Has State attribute 87HBase data set 92HDFS data set 95

298

HDP Version attribute 50, 53, 57, 77, 80, 83, 93, 97, 100,114, 118, 121, 125, 136, 139, 145, 153, 163, 171, 176,179, 183, 186, 189, 196, 200, 205, 212, 217, 220, 224Heartbeats Average Time ms (Rate) attribute 68Heartbeats Operations attribute 68Hive data set 99HOS Performance Object Status

situations 233HOS Performance Object Status data set 102Hostname attribute 48, 52, 55, 59, 61, 69, 75, 79, 82, 87,92, 96, 99, 107, 113, 117, 120, 123, 131, 134, 138, 143,144, 147, 152, 156, 162, 166, 167, 170, 174, 178, 181,185, 188, 192, 195, 199, 204, 210, 214, 216, 219, 223Hosts nodes data set 106

IInit Count in Cluster attribute 50, 53, 57, 77, 80, 84, 94, 97,100, 115, 118, 121, 125, 136, 139, 145, 153, 164, 172,176, 179, 183, 186, 190, 197, 200, 206, 212, 217, 221,224Install failed Count in Cluster attribute 50, 54, 57, 77, 80,84, 94, 97, 101, 115, 118, 122, 125, 136, 140, 145, 153,164, 172, 176, 179, 183, 186, 190, 197, 200, 206, 212,217, 221, 224Installed Count in Cluster attribute 50, 54, 57, 77, 81, 84,94, 97, 101, 115, 118, 122, 125, 136, 140, 145, 154, 164,172, 176, 180, 183, 186, 190, 197, 200, 206, 212, 217,221, 224Integrated Service Management Library documentation 284Intervals Skipped attribute 104, 149Introduction 1IP Address attribute 61, 170

JJava Virtual Machine Status attribute 61JVM Metrics data set 107

KKafka data set 113Killed Applications Percent attribute 160Knox data set 116KPIs 3KVM_VM_Created 237

LLast Checkpoint Time ms attribute 90Last Collection Duration attribute 104, 150Last Collection Finished attribute 104, 150Last Collection Start attribute 104, 150Last Loaded Edits attribute 91Last Written Transaction Id attribute 87Link Target attribute 131Links Created attribute 131List Snapshottable Directories attribute 132Lists attribute 132Loading Edits Count attribute 192Loading Edits Elapsed Time ms attribute 192Loading Edits Percent Complete attribute 192Loading Edits Total attribute 192

Loading File System Image Count attribute 192Loading File System Image Elapsed Time ms attribute 193Loading File System Image Percent Complete attribute 193Loading File System Image Total attribute 193Login Failure Average Time ms attribute 214Login Failure Number Of Operations attribute 214Login Success attribute 215Login Success Average Time ms attribute 215Logs Error attribute 107Logs Fatal attribute 108Logs Information attribute 112Logs Warn attribute 108Lost NodeManagers attribute 60

MMahout data set 120Maintenance State attribute 49, 52, 56, 75, 79, 82, 92, 96,99, 113, 117, 120, 124, 135, 138, 144, 152, 162, 170, 174,178, 181, 185, 188, 195, 199, 204, 210, 216, 219, 223MapReduce2 data set 123Maximum Share MB attribute 160Maximum Share Virtual Cores attribute 161Memory Heap Used Percent attribute 108Memory HeapCommitted MB attribute 108Memory HeapMaximum MB attribute 112Memory HeapUsed MB attribute 108Memory Maximum MB attribute 108Memory NonHeap Committed MB attribute 109Memory NonHeap Free MB attribute 109Memory NonHeap Maximum MB attribute 112Memory NonHeap Used MB attribute 109Minimum Share MB attribute 161Minimum Share Virtual Cores attribute 161Missing Blocks attribute 66, 87Missing Blocks Percent attribute 91MS_SQL_DB_free_space_critical 238

NNameNode data set 127Namenode uptime attribute 66NiFi data set 134NiFi Registry data set 138Node attribute 49, 52, 56, 60, 61, 66, 69, 76, 79, 82, 87, 92,96, 99, 104, 106, 109, 113, 117, 120, 124, 132, 135, 138,143, 144, 147, 150, 152, 156, 162, 166, 167, 170, 173,175, 178, 182, 185, 188, 193, 195, 199, 203, 204, 207,211, 215, 216, 219, 223Node FQDN attribute 62NodeManager Metrics data set 141Number of Collections attribute 104, 150

OObject Name attribute 105, 150Object Status attribute 105, 151Object Type attribute 105, 151Oozie data set 143Open Connections attribute 167Operating System data set 147Other Count in Cluster attribute 50, 54, 57, 77, 81, 84, 94,98, 101, 115, 119, 122, 125, 136, 140, 146, 154, 164, 172,

299

176, 180, 183, 187, 190, 197, 201, 206, 212, 218, 221,225

PPacket Round Trip Nanos Operations attribute 73Packet Round Trip Time Nanos Average Time attribute 73path conventions 285Pending Containers attribute 161Pending DataNode Message Count attribute 91Pending Deletion Blocks attribute 87Pending Replication Blocks attribute 87Pending Space MB attribute 156Pending Virtual Cores attribute 161Percent Complete attribute 193Performance Object Status


descriptions 228Performance Object Status data set 148Performance Object Status workspace 228Pig data set 151policies

descriptions 237Policies

KVM_VM_Created 237MS_SQL_DB_free_space_critical 238policy name 237

policy name 237Port attribute 63, 167Postponed Misreplicated Blocks attribute 88prerequisite documentation 283Process CPULoad Percentage attribute 66Process Name attribute 109, 132ProcessCPULoad attribute 147Processed Requests Count attribute 167Processing Average Time in minutes attribute 168Processing Average Time ms attribute 168publications

Service Management Connect 284SMC, See Service Management ConnectSee also documentation

Qqueries, using attributes 43Query Name attribute 105, 151Queue Average Time in minutes attribute 168Queue Average Time ms attribute 168Queue Metrics data set 155Queue Name attribute 157Queue Status attribute 62Queued Requests Count attribute 168

RRanger data set 162Read Block Operation attribute 73Read Block Operation Average Time ms attribute 73Reads From Local Client (Rate) attribute 69Reads From Remote Client (Rate) attribute 69Rebooted NodeManagers attribute 60Received Bytes attribute 168

Received Data MB attribute 169Redbooks 284Refresh Interval attribute 105, 151Remote Procedure Call Status attribute 62Rename Snapshot attribute 132Replace Block Average Time ms attribute 73Replace Block Operations attribute 73Reserved Containers attribute 161Reserved Space MB attribute 157Reserved Virtual Cores attribute 162Roles data set 165RPC data set 166Running 0 attribute 157Running 1440 attribute 157Running 300 attribute 157Running 60 attribute 157

SSafe Mode Time ms attribute 132SafeMode Count attribute 193SafeMode Elapsed Time ms attribute 194SafeMode Percent Complete attribute 194SafeMode Total attribute 194Saving Checkpoint Count attribute 194Saving Checkpoint Elapsed Time ms attribute 194Saving Checkpoint Percent Complete attribute 194Saving Checkpoint Total attribute 194Scheduled Replication Blocks attribute 88Schema Registry data set 170Send DataPacket Blocked On Network Nanos Average Timeattribute 74Send DataPacket Blocked On Network Nanos Operationsattribute 74Send DataPacket Transfer Nanos Average Time attribute 74Send DataPacket Transfer Nanos Operations attribute 74Sent Bytes attribute 169Sent Data MB attribute 169Service Management Connect 284Service Name attribute 49, 52, 56, 76, 79, 83, 93, 96, 99,114, 117, 120, 124, 135, 138, 144, 152, 163, 171, 173,175, 178, 182, 185, 189, 196, 199, 205, 211, 216, 220,223Service Status attribute 174ServiceName attribute 215Services


descriptions 228Services Overview data set 173Session Id attribute 74, 113, 133Short Queue Name attribute 158situations

additional informationpredefined, defined 231

overview 231predefined 231Situation Editor 231

situations, using attributes 43Slider data set 174SmartSense data set 177SMC, See Service Management ConnectSnapshot Report attribute 133Snapshots attribute 91

300

Snapshottable Directories attribute 91Solr data set 181Spark data set 184Sqoop data set 188Stack Id attribute 51, 54, 58, 77, 81, 84, 94, 98, 101, 115,119, 122, 126, 137, 140, 146, 154, 164, 172, 176, 180,183, 187, 190, 197, 201, 206, 212, 218, 221, 225Stale Configs attribute 51, 54, 58, 78, 81, 84, 94, 98, 101,115, 119, 122, 126, 137, 140, 146, 154, 164, 172, 177,180, 184, 187, 190, 197, 201, 206, 213, 218, 221, 225Stale DataNodes attribute 91Started Count in Cluster attribute 51, 54, 58, 78, 81, 85, 95,98, 101, 116, 119, 122, 126, 137, 140, 146, 154, 165, 173,177, 180, 184, 187, 191, 198, 201, 207, 213, 218, 222,225Startup Progress data set 191State attribute 49, 52, 56, 76, 79, 83, 93, 96, 100, 114,117, 121, 124, 135, 138, 144, 152, 163, 171, 175, 178,182, 185, 189, 196, 199, 205, 211, 216, 220, 223Storage Block Report attribute 133Streaming Analytics Manager data set 195Subnode Affinity attribute 106Subnode Host attribute 62Subnode MSN attribute 106Subnode Resource Name attribute 106Subnode Type attribute 106Subnode Version attribute 106Superset data set 198Synchronization Average Time ms attribute 133Synchronization Operations attribute 133SystemCpuLoad attribute 148

TTake Action commands

additional information 235overview 235predefined 235, 237

Take Action Status data set 202take actions

descriptions 235Technotes 284terms 284Tez data set 204Thread Pool Active Threads attribute 207Thread Pool Avg Active Threads attribute 208Thread Pool Avg Job Wait attribute 208Thread Pool Avg Queue Length attribute 208Thread Pool Max Active Threads attribute 208Thread Pool Max Queue Length attribute 208Thread Pool Max Size attribute 209Thread Pool Min Active Threads attribute 209Thread Pool Min Queue Length attribute 209Thread Pool Queue Length attribute 209Thread Pool Size attribute 209Thread Pool Status data set 207Thread Pool Total Jobs attribute 210Threads Blocked attribute 109Threads New attribute 109Threads Runnable attribute 110Threads Terminated attribute 110Threads Timed Waiting attribute 110Threads Waiting attribute 110thresholds 37

thresholds, using attributes 43Timestamp attribute 49, 53, 56, 60, 62, 66, 69, 76, 79, 83,88, 93, 96, 100, 105, 107, 110, 114, 117, 121, 124, 133,135, 139, 143, 144, 148, 151, 152, 158, 163, 166, 169,171, 174, 175, 178, 182, 185, 189, 195, 196, 199, 204,205, 210, 211, 215, 216, 220, 223Titan data set 210Tivoli Enterprise Console

event mapping 239Total Count in Cluster attribute 51, 55, 58, 78, 81, 85, 95,98, 102, 116, 119, 123, 126, 137, 140, 146, 154, 165, 173,177, 180, 184, 187, 191, 198, 201, 207, 213, 218, 222,225Total Disk failures attribute 66Total Files attribute 88Total Load attribute 92Transactions attribute 134Transactions Average Time ms attribute 134Transactions Batched In Synchronization attribute 134Transactions Since Last Checkpoint attribute 88Transactions Since Last Rollback attribute 88typeface conventions 285

UUGI Metrics data set 213UnderReplicated Blocks attribute 89Unhealthy NodeManagers attribute 60Unified Console data set 215Unknown Count in Cluster attribute 51, 55, 58, 78, 81, 85,95, 98, 102, 116, 119, 123, 126, 137, 141, 146, 154, 165,173, 177, 181, 184, 187, 191, 198, 201, 207, 213, 218,222, 225Upgrade State attribute 51, 55, 58, 78, 82, 85, 95, 98, 102,116, 119, 123, 126, 137, 141, 146, 155, 165, 173, 177,181, 184, 188, 191, 198, 201, 207, 213, 219, 222, 225User attribute 158

Vvariables conventions 285views

Hadoop workspace 228Performance Object Status workspace 228

Volume Failures attribute 69

Wwidgets 3Workflow Editor 237workspaces

descriptions 228Hadoop 228, 228Hadoop Hosts 229Performance Object Status 228, 228Services 228

Workspacesadditional information 227overview 227

Write Block Average Time ms attribute 75Write Block Operations attribute 75Writes From Local Client (Rate) attribute 69Writes From Remote Client (Rate) attribute 70

301

YYARN data set 219

ZZooKeeper data set 222

302

IBM®

Documents

· Contents Chapter 1. Monitoring Agent for Hadoop................................................................1 Chapter 2. Dashboard in the Cloud APM console