Our AWS CloudWatch Internet Monitor integration reports your CloudWatch Internet Monitor data to the New Relic platform.
Features
With this integration, you can collect and send telemetry data to New Relic from your CloudWatch Internet Monitor. 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
We have two options for reporting this data. The recommended path is setting up our Amazon CloudWatch Metric Streams integration. Alternatively, you can use our older Amazon integration that relies on polling.
Get logs data
Logs data can be reported to New Relic using our Log ingestion Lambda. Be sure to add triggers to the Lambda and select the log group corresponding to internet-monitor at country, city, subdivision, and metro level.
Find and 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 > Metrics and events and filter by aws.internetmonitor.
Metric data
Metric (min, max, average, count, sum) | Unit | Description |
|---|---|---|
| percentage | Percentage of total application internet traffic for this monitor. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| percentage | Traffic that is not seeing reachability anomalies. |
| percentage | Traffic that is not seeing latency anomalies. |
| count | Bytes received. |
| count | Bytes sent. |
| ms | How long a request takes. |
Logs data
We provide insights about the logs obtained from AWS Cloudwatch. Here are the major metrics received from logs.
Log tags | Unit | Description |
|---|---|---|
| String | Different log groups configured in AWS for |
| percentage | Calculated by including performance and availability scores, and when Internet Monitor creates and resolves health events. |
| percentage | How much performance impact was caused by a health event at a client location. |
| percentage | The impact on total traffic that a health event has, in increased latency or reduced availability. |
| percentage | Percentage of how much round-trip time increased during the event compared to typical round-trip time for your application for traffic. |
| percentage | Calculated by including performance and availability scores and when Internet Monitor creates and resolves health events. |
Tips on using your data
You can create 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.