---
title: Amazon Polly monitoring integration
source: https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-polly-monitoring-integration
---

[New Relic infrastructure integrations](https://docs.newrelic.com/docs/infrastructure/introduction-infra-monitoring) include an integration for Amazon Polly that reports your Polly metrics to New Relic.

## Features [#features]

With this integration, collect and send telemetry data to New Relic from your [Amazon Polly](https://docs.aws.amazon.com/polly) service. Monitor your services, query incoming data, and build dashboards to observe everything at a glance.

## Report data [#report-data]

We have two options for reporting this data. The recommended path is setting up our [Amazon CloudWatch Metric Streams integration](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/connect/aws-metric-stream). Alternatively, you can use our [older Amazon integration that relies on polling](https://docs.newrelic.com/docs/infrastructure/infrastructure-integrations/cloud-integrations/configure-polling-frequency-data-collection-cloud-integrations).

## Find and use data [#find-use-data]

Data from this integration is attached to the `Metric` data type. To find this data in the UI: Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Metrics and events** and filter for `aws.polly`.

## Metric data [#metrics]

| Metric (min, max, average, count, sum) | Unit         | Description                                                                                              |
| -------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------- |
| `RequestCharacters`                    | count        | The number of billable characters in requests.                                                           |
| `ResponseLattency`                     | milliseconds | The latency between when the request was made and the start of the streaming response.                   |
| `5XXCount`                             | count        | The number of server errors. The HTTP response code range for a server error is 500 to 599.              |
| `2XXCount`                             | count        | The number of successful translation requests. The response code for a successful request is 200 to 299. |
| `4XXCount`                             | count        | The number of user errors that occurred. The HTTP response code range for a user error is 400 to 499.    |

## Tips on using your data [#use-data]

You can create alerts to notify you of any developing changes. For example, an alert can be set up to notify relevant parties of critical or fatal errors. [Learn more about creating alerts](https://docs.newrelic.com/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/introduction-alerts).