-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create aws-lex-monitoring-integration.mdx
- Loading branch information
Showing
1 changed file
with
156 additions
and
0 deletions.
There are no files selected for viewing
156 changes: 156 additions & 0 deletions
156
...re/amazon-integrations/aws-integrations-list/aws-lex-monitoring-integration.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,156 @@ | ||
| --- | ||
| title: Amazon Lex monitoring integration | ||
| tags: | ||
| - Integrations | ||
| - Amazon integrations | ||
| - AWS integrations list | ||
| metaDescription: "New Relic's AWS Lex monitoring integration: what data it reports, and how to enable it." | ||
| redirects: | ||
| - /docs/integrations/amazon-integrations/aws-integrations-list/aws-lex-monitoring-integration | ||
| - /docs/aws-lex-integration | ||
| - /docs/infrastructure/infrastructure-integrations/amazon-integrations/aws-lex-integration | ||
| - /docs/infrastructure/amazon-integrations/amazon-integrations/aws-lex-monitoring-integration | ||
| --- | ||
|
|
||
| [New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an Amazon Lex integration for reporting your Lex data to New Relic. Here we explain how to activate our integration and what data can be reported. | ||
|
|
||
| Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. | ||
|
|
||
| ## Features [#features] | ||
|
|
||
| [Amazon Lex](https://aws.amazon.com/lex/) (Lex) is an AWS service for building conversational interfaces into applications using voice and text. With New Relic's Lex integration, you'll be able to monitor number of requests, channels used for Bot conversation and more. You'll be able to create custom charts of your data and [create alert conditions](/docs/infrastructure/new-relic-infrastructure/infrastructure-alert-conditions/infrastructure-alerts-add-edit-or-view-host-alert-information) based on changes in Lex data or configuration. | ||
|
|
||
| ## Activate integration [#activate] | ||
|
|
||
| To enable this integration follow standard procedures to [connect AWS services to New Relic](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/connect/aws-metric-stream/#set-up-metric-stream). | ||
|
|
||
| ## Find and use data [#find-data] | ||
|
|
||
| To find this integration's data, go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS** and select one of the Amazon Lex integration links. | ||
|
|
||
| You can [query and explore your data](/docs/using-new-relic/data/understand-data/query-new-relic-data) using the `LexSample` [event type](/docs/data-apis/understand-data/new-relic-data-types/#event-data), with a `provider` value of `Lex`. | ||
|
|
||
| For more on how to find and use integration data, see [Understand integration data](/docs/infrastructure/integrations/find-use-infrastructure-integration-data). | ||
|
|
||
| ## Metric data [#metrics] | ||
|
|
||
| This New Relic infrastructure integration collects the following Amazon Lex data: | ||
|
|
||
| <Callout variant="tip"> | ||
| For full descriptions of each metric, see [Amazon's Lex Dimensions and Metrics](https://docs.aws.amazon.com/lex/latest/dg/monitoring-aws-lex-cloudwatch.html). | ||
| </Callout> | ||
|
|
||
| <table> | ||
| <thead> | ||
| <tr> | ||
| <th width={200}> | ||
| Name | ||
| </th> | ||
|
|
||
| <th width={100}> | ||
| Data type | ||
| </th> | ||
| </tr> | ||
| </thead> | ||
|
|
||
| <tbody> | ||
| <tr> | ||
| <td> | ||
| `RuntimeRequestCount` | ||
| </td> | ||
|
|
||
| <td> | ||
| bytes | ||
| </td> | ||
| </tr> | ||
|
|
||
| <tr> | ||
| <td> | ||
| `RuntimeSuccessfulRequestLatency` | ||
| </td> | ||
|
|
||
| <td> | ||
| integer/count | ||
| </td> | ||
| </tr> | ||
|
|
||
| <tr> | ||
| <td> | ||
| `RuntimeThrottledEvents` | ||
| </td> | ||
|
|
||
| <td> | ||
| seconds | ||
| </td> | ||
| </tr> | ||
|
|
||
| <tr> | ||
| <td> | ||
| `RuntimeSystemErrors` | ||
| `RuntimeLambdaErrors` | ||
| `RuntimePollyErrors` | ||
| `RuntimeUserErrors` | ||
| </td> | ||
|
|
||
| <td> | ||
| seconds | ||
| </td> | ||
| </tr> | ||
|
|
||
| <tr> | ||
| <td> | ||
| `RuntimeConcurrency` | ||
| </td> | ||
|
|
||
| <td> | ||
| integer/count | ||
| </td> | ||
| </tr> | ||
|
|
||
| <tr> | ||
| <td> | ||
| `BotChannelRequestCount` | ||
| </td> | ||
|
|
||
| <td> | ||
| percent | ||
| </td> | ||
| </tr> | ||
|
|
||
| <tr> | ||
| <td> | ||
| `BotChannelInboundThrottledEvents` | ||
| `BotChannelOutboundThrottledEvents` | ||
| </td> | ||
|
|
||
| <td> | ||
| count | ||
| </td> | ||
| </tr> | ||
|
|
||
| <tr> | ||
| <td> | ||
| `ConversationLogsAudioDeliverySuccess` | ||
| `ConversationLogsAudioDeliveryFailure` | ||
| `ConversationLogsTextDeliverySuccess` | ||
| `ConversationLogsTextDeliveryFailure` | ||
| </td> | ||
|
|
||
| <td> | ||
| percent | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td> | ||
| `BotChannelAuthErrors` | ||
| `BotChannelConfigurationErrors` | ||
| `BotChannelResponseCardErrors` | ||
| `BotChannelSystemErrors` | ||
| </td> | ||
|
|
||
| <td> | ||
| count | ||
| </td> | ||
| </tr> | ||
| </tbody> | ||
| </table> |