--- title: Amazon CloudWatch Internet Monitor integration source: https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-internet-monitor-integration --- Our AWS CloudWatch Internet Monitor integration reports your CloudWatch Internet Monitor data to the New Relic platform. ## Features [#features] With this integration, you can collect and send telemetry data to New Relic from your [CloudWatch Internet Monitor](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-InternetMonitor.html). Once integrated you can monitor your services, query incoming data, monitor logs, and use pre-built dashboards to observe everything at a glance. ## Get metrics data [#get-metrics-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). ## Get logs data [#get-logs-data] Logs data can be reported to New Relic using our [Log ingestion Lambda](https://docs.newrelic.com/docs/logs/forward-logs/aws-lambda-sending-cloudwatch-logs). Be sure to [add triggers](https://docs.newrelic.com/docs/logs/forward-logs/aws-lambda-sending-cloudwatch-logs/#create-trigger) to the Lambda and select the log group corresponding to `internet-monitor` at `country`, `city`, `subdivision`, and `metro` level. ## Find and use data [#find-use-data] Metrics data from this integration is attached to the `Metric` data type. To see your data: go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Metrics and events** and filter by `aws.internetmonitor`. ## Metric data [#metric-data] | Metric (min, max, average, count, sum) | Unit | Description | | -------------------------------------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | `TrafficMonitoredPercent` | percentage | Percentage of total application internet traffic for this monitor. | | `CityNetworksFor100PercentTraffic` | percentage | The number that you should set your city-networks maximum limit to if you want to monitor 100% of your application internet traffic in Internet Monitor. | | `CityNetworksFor99PercentTraffic` | percentage | The number that you should set your city-networks maximum limit to if you want to monitor 99% of your application internet traffic in Internet Monitor. | | `CityNetworksFor95PercentTraffic` | percentage | The number that you should set your city-networks maximum limit to if you want to monitor 95% of your application internet traffic in Internet Monitor. | | `CityNetworksFor90PercentTraffic` | percentage | The number that you should set your city-networks maximum limit to if you want to monitor 90% of your application internet traffic in Internet Monitor. | | `CityNetworksFor75PercentTraffic` | percentage | The number that you should set your city-networks maximum limit to if you want to monitor 75% of your application internet traffic in Internet Monitor. | | `CityNetworksFor50PercentTraffic` | percentage | The number that you should set your city-networks maximum limit to if you want to monitor 50% of your application internet traffic in Internet Monitor. | | `CityNetworksFor25PercentTraffic` | percentage | The number that you should set your city-networks maximum limit to if you want to monitor 25% of your application internet traffic in Internet Monitor. | | `AvailabilityScore` | percentage | Traffic that is not seeing reachability anomalies. | | `PerformanceScore` | percentage | Traffic that is not seeing latency anomalies. | | `BytesIn` | count | Bytes received. | | `BytesOut` | count | Bytes sent. | | `RoundTripTime` | ms | How long a request takes. | ## Logs data [#logs-data] We provide insights about the logs obtained from AWS Cloudwatch. Here are the major metrics received from logs. | Log tags | Unit | Description | | --------------------------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------------------- | | `aws.logGroup` | String | Different log groups configured in AWS for `country`, `subdivision`, `metro`, and `city`. | | `experienceScore` | percentage | Calculated by including performance and availability scores, and when Internet Monitor creates and resolves health events. | | `PercentOfClientLocationImpacted` | percentage | How much performance impact was caused by a health event at a client location. | | `PercentOfTotalTrafficImpacted` | percentage | The impact on total traffic that a health event has, in increased latency or reduced availability. | | `RoundTripTime` | percentage | Percentage of how much round-trip time increased during the event compared to typical round-trip time for your application for traffic. | | `percentageOfTotalTraffic` | percentage | Calculated by including performance and availability scores and when Internet Monitor creates and resolves health events. | ## 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).