New Relic integrates with Amazon Web Services (AWS) for reporting your Amazon Elastic Transcoder metrics and other data to New Relic.
This document explains how to activate the integration, and describes the data reported.
Features
Collect and send telemetry data to New Relic from your Amazon Elastic Transcoder services using our integration. Monitor your services, query incoming data, and build dashboards to observe everything at a glance.
Get started
This integration is available through CloudWatch Metric Streams.
To enable this integration, see how to connect AWS services to New Relic via CloudWatch Metric Streams.
Find and use data
To find your integration's metrics, go to one.newrelic.com > Metrics and events and filter by aws.elastictranscoder.
Additionally, you can find the entities associated with Amazon Elastic Transcoder by going to one.newrelic.com and searching for elastictranscoder.
Metric data
This integration collects the following Amazon Elastic Transcoder data:
SWF metric data
Metric (min, max, average, count, sum) | Unit | Description |
|---|---|---|
| Seconds | The number of billable seconds of audio output for a pipeline. |
| Seconds | The number of billable seconds of SD output for a pipeline. |
| Seconds | The number of billable seconds of SD output for a pipeline. |
| Count | The number of errors caused by invalid operation parameters, such as a request for a job status that does not include the job ID. |
| Count | The number of jobs completed by this pipeline. |
| Count | The number of jobs that failed because of invalid inputs, such as a request to transcode a file that is not in the given input bucket. |
| Seconds | The number of seconds before Elastic Transcoder started transcoding a job. |
| Count | The number of times that Elastic Transcoder automatically throttled an operation. |
All imported data has one dimension: Domain
Create alerts
You can set up to notify you if there are any changes. For example, you can set up an alert to notify your team members of critical or fatal errors. For more information, see NRQL alert conditions.