| title | tags | metaDescription | redirects | freshnessValidatedDate | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
Amazon EMR monitoring integration |
|
New Relic's Amazon EMR monitoring integration: what data it reports, and how to enable it. |
|
never |
New Relic infrastructure integrations include an integration for reporting your Amazon EMR (Elastic MapReduce) data to New Relic. This document explains how to activate this integration and describes the data that can be reported.
You can monitor and alert on your EMR data directly from New Relic, and query data and create dashboards.
To enable this integration follow standard procedures to Connect AWS services to New Relic.
You can change the polling frequency and filter data using configuration options.
Default polling information for the Amazon EMR integration:
- New Relic polling interval: 5 minutes
- Resolution: 1 data point every 5 minutes
To use your integration data, go to one.newrelic.com > All capabilities > Infrastructure > AWS and select one of the EMR integration links.
You can query and explore your data using the ElasticMapReduceClusterSample event type, with a provider value of ElasticMapReduceCluster.
This integration collects the following Amazon EMR data. For use cases and additional information, see Amazon's EMR documentation.
<th>
Description
</th>
</tr>
<td>
Indicates that a cluster is no longer performing work, but is still alive and accruing charges. It is set to 1 if no tasks are running and no jobs are running, and set to 0 otherwise.
This value is checked at five-minute intervals, and a value of 1 indicates only that the cluster was idle when checked, not that it was idle for the entire five minutes. <DNT>**Recommendation:**</DNT> To avoid false positives, raise an alerting threshold when this value has been 1 for more than one consecutive five-minute check. For example, raise an alert on this value if it has been 1 for thirty minutes or longer.
</td>
</tr>
<tr>
<td>
`coreNodesRunning`
</td>
<td>
The number of core nodes working. Data points for this metric are reported only when a corresponding instance group exists.
</td>
</tr>
<tr>
<td>
`coreNodesPending`
</td>
<td>
The number of core nodes waiting to be assigned. All of the core nodes requested may not be immediately available; this metric reports the pending requests. Data points for this metric are reported only when a corresponding instance group exists.
</td>
</tr>
<tr>
<td>
`liveDataNodesPercentage`
</td>
<td>
The percentage of data nodes that are receiving work from Hadoop.
</td>
</tr>
<tr>
<td>
`s3WrittenBytes`
</td>
<td>
The number of bytes written to Amazon S3. This metric aggregates MapReduce jobs only. It does not apply for other workloads on EMR.
</td>
</tr>
<tr>
<td>
`s3ReadBytes`
</td>
<td>
The number of bytes read from Amazon S3. This metric aggregates MapReduce jobs only, and does not apply for other workloads on EMR.
</td>
</tr>
<tr>
<td>
`hdfsUtilizationPercentage`
</td>
<td>
The percentage of HDFS storage currently used.
</td>
</tr>
<tr>
<td>
`hdfsReadBytes`
</td>
<td>
The number of bytes read from HDFS.
</td>
</tr>
<tr>
<td>
`hdfsWrittenBytes`
</td>
<td>
The number of bytes written to HDFS.
</td>
</tr>
<tr>
<td>
`missingBlocks`
</td>
<td>
The number of blocks in which HDFS has no replicas. These might be corrupt blocks.
</td>
</tr>
<tr>
<td>
`totalLoad`
</td>
<td>
The current, total number of readers and writers reported by all DataNodes in a cluster.
</td>
</tr>
<tr>
<td>
`mostRecentBackupDurationMinutes`
</td>
<td>
The amount of time it took the previous backup to complete. This metric is set regardless of whether the last completed backup succeeded or failed.
While the backup is ongoing, this metric returns the number of minutes after the backup started. This metric is only reported for HBase clusters.
</td>
</tr>
<tr>
<td>
`timeSinceLastSuccessfulBackupMinutes`
</td>
<td>
The number of elapsed minutes after the last successful HBase backup started on your cluster. This metric is only reported for HBase clusters.
</td>
</tr>
| Name |
|---|
| `isIdle` |
The following metrics appear in the sample depending on the Hadoop version of the resource.
<th>
Description
</th>
</tr>
<td>
The number of jobs in the cluster that are currently running.
</td>
</tr>
<tr>
<td>
`jobsFailed`
</td>
<td>
The number of jobs in the cluster that have failed.
</td>
</tr>
<tr>
<td>
`mapTasksRunning`
</td>
<td>
The number of running map tasks for each job. If you have a scheduler installed and multiple jobs running, multiple graphs are generated.
</td>
</tr>
<tr>
<td>
`mapTasksRemaining`
</td>
<td>
The number of remaining map tasks for each job. If you have a scheduler installed and multiple jobs running, multiple graphs are generated. A remaining map task is one that is not in any of the following states: `Running`, `Killed`, or `Completed`.
</td>
</tr>
<tr>
<td>
`mapSlotsOpen`
</td>
<td>
The unused map task capacity. This is calculated as the maximum number of map tasks for a given cluster, less the total number of map tasks currently running in that cluster.
</td>
</tr>
<tr>
<td>
`remainingMapTasksPerSlot`
</td>
<td>
The ratio of the total map tasks remaining to the total map slots available in the cluster.
</td>
</tr>
<tr>
<td>
`reduceTasksRunning`
</td>
<td>
The number of running reduce tasks for each job. If you have a scheduler installed and multiple jobs running, multiple graphs are generated.
</td>
</tr>
<tr>
<td>
`reduceTasksRemaining`
</td>
<td>
The number of running reduce tasks for each job. If you have a scheduler installed and multiple jobs running, multiple graphs are generated.
</td>
</tr>
<tr>
<td>
`reduceSlotsOpen`
</td>
<td>
Unused reduce task capacity. This is calculated as the maximum reduce task capacity for a given cluster, less the number of reduce tasks currently running in that cluster.
</td>
</tr>
<tr>
<td>
`taskNodesRunning`
</td>
<td>
The number of task nodes working. Data points for this metric are reported only when a corresponding instance group exists.
</td>
</tr>
<tr>
<td>
`taskNodesPending`
</td>
<td>
The number of core nodes waiting to be assigned. All of the task nodes requested may not be immediately available; this metric reports the pending requests. Data points for this metric are reported only when a corresponding instance group exists.
</td>
</tr>
<tr>
<td>
`liveTaskTrackersPercentage`
</td>
<td>
The percentage of task trackers that are functional.
</td>
</tr>
<tr>
<td>
`backupFailed`
</td>
<td>
Whether the last backup failed. This is set to 0 by default and updated to 1 if the previous backup attempt failed. This metric is only reported for HBase clusters.
</td>
</tr>
| Name |
|---|
| `jobsRunning` |
<th>
Description
</th>
</tr>
<td>
The number of resource containers allocated by the ResourceManager.
</td>
</tr>
<tr>
<td>
`containerReserved`
</td>
<td>
The number of resource containers allocated by the ResourceManager.
</td>
</tr>
<tr>
<td>
`containerPending`
</td>
<td>
The number of containers in the queue that have not yet been allocated.
</td>
</tr>
<tr>
<td>
`containerPendingRatio`
</td>
<td>
The ratio of pending containers to containers allocated.
</td>
</tr>
<tr>
<td>
`appsCompleted`
</td>
<td>
The number of applications submitted to YARN that have completed.
</td>
</tr>
<tr>
<td>
`appsFailed`
</td>
<td>
The number of applications submitted to YARN that have failed to complete.
</td>
</tr>
<tr>
<td>
`appsKilled`
</td>
<td>
The number of applications submitted to YARN that have been killed.
</td>
</tr>
<tr>
<td>
`appsPending`
</td>
<td>
The number of applications submitted to YARN that are in a pending state.
</td>
</tr>
<tr>
<td>
`appsRunning`
</td>
<td>
The number of applications submitted to YARN that are running.
</td>
</tr>
<tr>
<td>
`appsSubmitted`
</td>
<td>
The number of applications submitted to YARN.
</td>
</tr>
<tr>
<td>
`mrTotalNodes`
</td>
<td>
The number of nodes presently available to MapReduce jobs.
</td>
</tr>
<tr>
<td>
`mrActiveNodes`
</td>
<td>
The number of nodes presently running MapReduce tasks or jobs.
</td>
</tr>
<tr>
<td>
`mrLostNodes`
</td>
<td>
The number of nodes allocated to MapReduce that have been marked in a LOST state.
</td>
</tr>
<tr>
<td>
`mrUnhealthyNodes`
</td>
<td>
The number of nodes available to MapReduce jobs marked in an UNHEALTHY state.
</td>
</tr>
<tr>
<td>
`mrDecommissionedNodes`
</td>
<td>
The number of nodes allocated to MapReduce applications that have been marked in a DECOMMISSIONED state.
</td>
</tr>
<tr>
<td>
`mrRebootedNodes`
</td>
<td>
The number of nodes available to MapReduce that have been rebooted and marked in a REBOOTED state.
</td>
</tr>
<tr>
<td>
`corruptBlocks`
</td>
<td>
The number of blocks that HDFS reports as corrupted.
</td>
</tr>
<tr>
<td>
`memoryTotalBytes`
</td>
<td>
The total amount of memory in the cluster.
</td>
</tr>
<tr>
<td>
`memoryReservedBytes`
</td>
<td>
The amount of memory reserved.
</td>
</tr>
<tr>
<td>
`memoryAvailableBytes`
</td>
<td>
The amount of memory available to be allocated.
</td>
</tr>
<tr>
<td>
`memoryAllocatedBytes`
</td>
<td>
The amount of memory allocated to the cluster.
</td>
</tr>
<tr>
<td>
`yarnMemoryAvailablePercentage`
</td>
<td>
The percentage of remaining memory available to YARN
</td>
</tr>
<tr>
<td>
`underReplicatedBlocks`
</td>
<td>
The number of blocks that need to be replicated one or more times.
</td>
</tr>
<tr>
<td>
`dfsPendingReplicationBlocks`
</td>
<td>
The status of block replication: blocks being replicated, age of replication requests, and unsuccessful replication requests.
</td>
</tr>
<tr>
<td>
`capacityRemainingBytes`
</td>
<td>
The amount of remaining HDFS disk capacity.
</td>
</tr>
<tr>
<td>
`hbaseBackupFailed`
</td>
<td>
Whether the last backup failed. This is set to 0 by default and updated to 1 if the previous backup attempt failed. This metric is only reported for HBase clusters.
</td>
</tr>
| Name |
|---|
| `containerAllocated` |