Filtering and viewing historical data in Amazon CloudWatch Internet Monitor (Historical explorer tab)
Use the Historical explorer tab in the CloudWatch console, under Internet Monitor, to filter and view data for your application that's in CloudWatch Logs. Internet Monitor publishes measurements to CloudWatch Logs specific to your application for availability, performance, monitored bytes transferred (or client connection count, for WorkSpaces directories only), and round-trip time for your monitored city-networks in Amazon Web Services Regions.
Note
Internet Monitor publishes internet measurements to CloudWatch Logs every five minutes for the top 500 (by traffic volume) city-networks (that is, client locations and ASNs, typically internet service providers or ISPs) that send traffic to each monitor. Optionally, you can choose to publish internet measurements for all monitored city-networks (up to the 500,000 city-networks service limit) to an Amazon S3 bucket. For more information, see Publishing internet measurements to Amazon S3 in Amazon CloudWatch Internet Monitor.
To start exploring your application's data, select a time period. Then, choose a specific geographical location, such a city, and (optionally) other filters. Internet Monitor applies the filters to the data in the internet measurements logs that it has published for the city-networks for your application traffic. Then you can see graphs of the data that show the performance score, availability score, monitored bytes transferred (for VPCs, Network Load Balancers, and CloudFront distributions) or client connection counts (for WorkSpaces directories), and round-trip time (RTT) for your application over time.
The All events table below the graphs shows you the health events that your filter returns for your application traffic, with information about each event. It includes the following columns.
| Description | |
|---|---|
| Event start | The time that the health event started. |
| Status | Whether the event is still active or is resolved. |
| Client location | The location of the end users who were impacted by the event, who experienced increased latency or reduced performance. To learn more about client location accuracy in Internet Monitor, see Geolocation information and accuracy in Internet Monitor. |
| Traffic impact | The weighted impact of the event on the location of the health event. That is, for example, the impact on latency, compared to typical performance for traffic from a client location to the Amazon location over the client ASN, typically an internet service provider (ISP). Similarly, for an event that affects availability, you see the impact on availability compared to typical availability for the client location for the Amazon location over the client ASN. |
| Event duration | How long the event lasted. Internet Monitor terminates health events when they no longer affect more than 5% (in total) of your application's client locations. |
| Client ISP | The ASN, typically the internet service provider (ISP), that was the carrier for the network traffic. |
| Service location | The service location that the network traffic originated from, which can be an Amazon Web Services Region or internet edge location. |
Alternatively, you can look at your application's measurements by accessing the logs directly for each data point. In the Actions menu, choose View CloudWatch Logs. Note that because measurement events are published to your account when they're created, you can create other CloudWatch dashboards or alarms based on them as well. For more information, see Getting insights to improve application performance in Amazon CloudWatch Internet Monitor (Traffic insights tab) and Creating alarms with Amazon CloudWatch Internet Monitor.
In addition to exploring and analyzing Internet Monitor measurements and metrics, and creating dashboards and alarms based on them, you can use Internet Monitor to help you understand ways that you could improve performance for your application. The Traffic insights tab has several ways to help you explore options. For more information, see Traffic optimization suggestions on the Traffic insights tab. In addition, you can see the specific examples in the Internet Monitor use cases chapter.