New Relic infrastructure integrations now include an integration for AWS Elemental MediaTailor, sending its metric data to New Relic.
This document explains the integration's features, how to activate it, and what data can be reported.
Features
Collect and send telemetry data to New Relic from your AWS Elemental MediaTailor using our integration. Monitor your services, query incoming data, and build dashboards to observe everything at a glance.
Activate integration
To enable this integration, see how to connect AWS services to New Relic.
Find and use data
To find your integration's metrics, go to one.newrelic.com > Metrics and events and filter by aws.mediatailor.
Metric data
This New Relic infrastructure integration collects the following AWS Elemental MediaTailor data:
All imported data has one dimension: ConfigurationName
AWS Elemental MediaTailor metric data
Metric (min, max, average, count, sum) | Unit | Description |
|---|---|---|
| Count | The number of 4xx errors. |
| Count | The number of 5xx errors. |
| Count | The total number of requests. |
| Milliseconds | The amount of time that the application server took to process the request, including the time used to receive bytes from and write bytes to the client and network. |
| Count | The count of ads included in ad decision server (ADS) responses within the CloudWatch time period that you specified. |
| Milliseconds | The total duration, in milliseconds, of all ads that MediaTailor received from the ADS within the CloudWatch time period that you specified. |
| Count | The number of non-HTTP 200 status code responses, empty responses, and timed-out responses that MediaTailor received from the ADS within the CloudWatch time period that you specified. |
| Percent | The simple average of the rates at which the responses from the ADS filled the corresponding individual ad avails for the time period that you specified. |
| Milliseconds | The response time in milliseconds for requests made by MediaTailor to the ADS. |
| Count | The number of timed-out requests to the ADS in the CloudWatch time period that you specified. |
| Count | The number of times that the ADS pointed at an ad that wasn't yet transcoded by the internal transcoder service in the time period that you specified. |
| Count | The number of ads for which MediaTailor bills customers based on insertion. |
| Milliseconds | The planned total number of milliseconds of ad avails within the CloudWatch time period. |
| Milliseconds | The planned number of milliseconds of ad avail time that MediaTailor will fill with ads within the CloudWatch time period. |
| Percent | The planned simple average of the rates at which MediaTailor will fill individual ad avails within the CloudWatch time period. |
| Count | The number of ads with impression tracking events that MediaTailor sees during server-side beaconing (not the number of impressions). |
| Milliseconds | The observed total number of milliseconds of ad avails that occurred within the CloudWatch time period. |
| Milliseconds | The observed number of milliseconds of ad avail time that MediaTailor filled with ads within the CloudWatch time period. |
| Percent | The observed simple average of the rates at which MediaTailor filled individual ad avails within the CloudWatch time period. |
| Milliseconds | The observed total number of milliseconds of slate that was inserted within the CloudWatch period. |
| Count | The number of errors received while MediaTailor was generating manifests in the CloudWatch time period that you specified. |
| Milliseconds | The MediaTailor response time in milliseconds for the request to generate manifests. |
| Count | The number of non-HTTP 200 status code responses and timed-out responses that MediaTailor received from the origin server in the CloudWatch time period that you specified. |
| Milliseconds | The response time for requests made by MediaTailor to your content origin server. |
| Bytes | The file size of the origin manifest in bytes for both HLS and DASH. |
| Count | The number of responses from the origin that have a manifest size larger than the configured amount. |
| Count | The number of timed-out requests to the origin server in the CloudWatch time period that you specified. |
| Count | The number of concurrent transactions per second across all request types. |
| Count | The number of ads that were not inserted into an avail because the ADS returned a duration of ads that was greater than the specified avail duration. |
| Count | The number of ads skipped due to an early CUE-IN. |
| Count | The number of ads skipped due to a MediaTailor internal error. |
| Count | The number of ads that were not inserted into an avail because it was the first time the asset had been requested by a client. |
| Count | The number of ads skipped due to there being no variant match between the ad and content. |
| Count | The duration of ads exceeding the Personalization Threshold setting in this configuration. |
| Count | The number of ads skipped due to the transcoding profile not being found. |
| Count | The number of ads skipped due to a transcode error. |
| Count | The count of the number of ads that were not inserted into an avail because the ad had not yet been transcoded. |
Create alerts
You can set up to notify you if there are any changes. For example, you can set up an alert to notify relevant parties of critical or fatal errors.
Learn more about creating alerts here.